Bug 32305 - Supplied Nvidia proprietary drivers do not work with GTX 1050Ti video card after install.
Summary: Supplied Nvidia proprietary drivers do not work with GTX 1050Ti video card af...
Status: NEW
Alias: None
Product: Mageia
Classification: Unclassified
Component: Release (media or process) (show other bugs)
Version: 9
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-09-20 00:30 CEST by David Savolainen
Modified: 2023-11-05 19:53 CET (History)
5 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description David Savolainen 2023-09-20 00:30:30 CEST
A fresh install of Mageia 9 will result in a blank screen a few seconds after the boiling cauldron boot screen starts, or after pressing the esc key, when the boot messages would start.  The Nvidia card in question is an Asus Geforce GTX 1050Ti.  The initial few seconds of blinking courser is shown, but the screen blanks before any boot messages are displayed.  This happens with an install from the regular .iso and the live .iso.  Booting the live .iso does work when the use proprietary driver boot option is selected.  Booting in recovery mode does display boot messages, but the screen still blanks when X would otherwise start.  Note that the screen goes blank.  Signal from the video card still exists but the screen is black.  During install from the regular .iso, the installer does ask if I want to use the proprietary driver, and appears to install it.  Also, the video configuration test feature seems to have been removed making it impossible to test the video configuration before completing installation.
Comment 1 Lewis Smith 2023-09-21 21:27:14 CEST
Thank you for the report, and sorry for your angst.

Do we understand that the installation went to end, and the problem showed on first reboot?
From a Live ISO? ("does work when the use proprietary driver boot option is selected")
From the Classic ISO? ("the video configuration test feature seems to have been removed")
Are you able to get to a virtual console (Ctl/Alt/F2 or more)? Or boot to the command line? If so, post if you can the output of:
 $ inxi -G
to describe your system's graphics.

CC'ing Morgan, Frank & Martin who know more what to expect in this GeoForce area.

CC: (none) => fri, mageia, sturm-fr

Comment 2 David Savolainen 2023-09-22 18:45:17 CEST
Do we understand that the installation went to end, and the problem showed on first reboot? - This is correct. sort of.  see comments on live ISO
When booting, the screen blanks when the boot process starts.
I also noticed that the network also dies when the screen is blanked.  The network status/activity light turns off.  
Note on booting from the live ISO.  The screen does blank on the live ISO as well as the network activity light turning off.  The screen remains blanked for several minutes until the setup screens pop up, select language, etc.  After that, the graphics work normally.  Below is the output of inxi -G when booted from the live ISO.  I cannot get a result when booting from the hard drive as Ctl/Alt/F2 does not work (or at least nothing shows on screen. I cannot tell if the computer is actually responding to the keyboard.), and I cannot ssh into the machine due to the network failing during the screen blank.

Graphics:
  Device-1: Intel 2nd Generation Core Processor Family Integrated Graphics
    driver: i915 v: kernel
  Device-2: NVIDIA GP107 [GeForce GTX 1050 Ti] driver: nvidia v: 535.86.05
  Display: x11 server: X.org v: 1.21.1.8 with: Xwayland v: 22.1.9 driver: X:
    loaded: nvidia,v4l gpu: i915,nvidia resolution: 3840x2160~30Hz
  API: OpenGL v: 4.6.0 NVIDIA 535.86.05 renderer: NVIDIA GeForce GTX 1050
    Ti/PCIe/SSE2

PS: ("the video configuration test feature seems to have been removed") This may be incidental to the main issue?  It is an annoyance I noticed though.
Comment 3 Lewis Smith 2023-09-24 20:43:05 CEST
Thank you for these clarifications.

Ping the CCs !
Comment 4 Martin Whitaker 2023-09-24 23:04:12 CEST
What is the boot command line on your installed system? (press 'e' in the GRUB menu to see it)
Comment 5 David Savolainen 2023-09-27 15:39:36 CEST
Here is the contents of the grub boot edit screen screen with line wrap exactly as shown:

setparams 'Mageia'

        savedefault
        set gfxpayload=text
        insmod gzio
        insmod part_gpt
        insmod ext2
        set root='hd0,gpt2'
        if [x$feature_platform_search_hint = xy ]; then
          search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt2 --hint-efi=h\
d0,gpt2 --hint-baremetal=ahci0,gpt2 b536ae87-51d9-40f2-b690-65ac42a9c42c
        else
          search --no-floppy --fs-uuid --set=root b536ae87-51d9-40f2-b690-65ac42a9c\
42c
        fi
        echo       'Loading Linux 6.4.9-desktop-4.mga9 ...'
        linux      /boot/vmlinuz-6.4.9-desktop-4.mga9 root=UUID=b536ae87-51d9-40f\
2-b690-65ac42a9c42c ro  ro nokmsboot splash quiet noiswmd root=UUID=b536ae87-51d9-4\
0f2-b690-65ac42a9c42c audit=0 resume=UUID=157f6997-8c6d-4e49-85f5-3148bb68df7a vga=\
791
        echo      'Loading initial ramdisk ...'
Comment 6 Morgan Leijström 2023-10-02 22:36:55 CEST
(In reply to David Savolainen from comment #2)
 
> Note on booting from the live ISO.  The screen does blank on the live ISO as
> well as the network activity light turning off.  The screen remains blanked
> for several minutes until the setup screens pop up, select language, etc. 
> After that, the graphics work normally.

From the Live boot menu, did you select to use proprietary driver or not?
Comment 7 Lewis Smith 2023-11-03 14:43:28 CET
@David
Did you succeed in the end? Have you given up?

"Booting the live .iso does work when the use proprietary driver boot option is selected" answers the previous question.
"booting from the live ISO.  The screen does blank on the live ISO as well as the network activity light turning off.  The screen remains blanked for several minutes until the setup screens pop up, select language, etc.  After that, the graphics work normally"
This problem is just nothing visible until the Installer gets going, which is disconceting but harmless - and quite common.

The main problem of no graphics on the installed system - whether from a Live or Classic ISO -is of course serious. It may well be that the particular graphics card is not supported.
CC'd people might suggest things to try (different video modes, nouveau).

@Martin
Did comment 5 help?

CC: (none) => lewyssmith

Comment 8 David Savolainen 2023-11-03 16:46:17 CET
From Comment 6:  Yes, I did select the use proprietary driver option

From Comment 7:  Yes, I gave up.  I attempted to use the live .iso without the proprietary driver, and it worked perfectly.  I did an install from the regular .iso without installing the proprietary driver, and it worked as well.  So currently, I am running Mageia 9 without the proprietary driver, and it is working sufficiently to meet my expectations.
Comment 9 Lewis Smith 2023-11-05 19:33:04 CET
Thank you for this feedback.

Assigning to Drivers maintainers, since it appears that nvidia v: 535.86.05 does not work with NVIDIA GP107 [GeForce GTX 1050 Ti]. I do not know whether it should, or whether a different nVidia driver would be more appropriate.

Assignee: bugsquad => kernel
CC: lewyssmith => (none)

Comment 10 Giuseppe Ghibò 2023-11-05 19:53:33 CET
Have you tried to boot the live ISO nonfree mode passing the option nouveau.modeset=0 to the boot (grub) cmdline?

What if you install the proprietary drivers after the installation or the live boot with the persistent partition, i.e. after having installed all the updates (kernel, etc.)?

Note that:

GeForce 1050Ti is one of the few cards supported by 5 series of drivers:

- nvidia-current (GeForce 735 and beyond in drakx11)
- nvidia470
- modesetting
- nouveau
- nvidia-newfeature

there is also actually a new series of drivers in nonfree/updates_testing.

nvidia-current: 535.129.03
nvidia470: 470.223.02
nvidia-newfeature: 545.29.02

CC: (none) => ghibomgx


Note You need to log in before you can comment on or make changes to this bug.