nvidia Driver Problems

[drichard58]

Lots of posts regarding nvidia drivers and problems with M4, but none seem to address the issue I have, so here goes. I was running M3 with an nvidia GT218 (GeForce 210) graphics card with no issues. After upgrade, everything looks OK until the desktop appears. My background flashes momentarily and then I get a solid grey background.

To add to the troubles, some applications (GnuCash in particular) seem to open and then immediately close. Maybe unrelated as ps does not show the app running.

When I go to MCC and look at the graphical server settings, it is set for nvidia GeForce 8100 and the Test button shows a black screen. I tried adjusting the settings and different drivers, but nothing seems to work.

Any suggestions?

[doktor5000]

Please show the output of

Code: Select all

grep -i driver /var/log/Xorg.0.log
lspcidrake -v | grep VGA

[isadora]

Results of "grep -i driver /var/log/Xorg.0.log"

Code: Select all

[   148.193]    X.Org Video Driver: 14.1
[   148.193]    X.Org XInput driver : 19.1
[   148.331] (II) Loading /usr/lib64/xorg/modules/drivers/v4l_drv.so
[   148.331]    ABI class: X.Org Video Driver, version 14.1
[   151.620]    Module class: X.Org Video Driver
[   151.620] (II) v4l driver for Video4Linux
[   151.620] (II) NVIDIA dlloader X Driver  331.49  Wed Feb 12 19:57:36 PST 2014
[   151.620] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   152.233] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[   152.336] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[   153.301]    Module class: X.Org XInput Driver
[   153.301]    ABI class: X.Org Video Driver, version 14.1
[   151.620]    Module class: X.Org Video Driver
[   151.620] (II) v4l driver for Video4Linux
[   151.620] (II) NVIDIA dlloader X Driver  331.49  Wed Feb 12 19:57:36 PST 2014
[   151.620] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[   152.233] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
[   152.336] (II) NVIDIA(0): [DRI2]   VDPAU driver: nvidia
[   153.301]    Module class: X.Org XInput Driver
[   153.301]    ABI class: X.Org XInput driver, version 19.1
[   153.301] (II) Using input driver 'evdev' for 'Power Button'
[   153.330] (II) Using input driver 'evdev' for 'Sleep Button'
[   153.330] (II) No input driver specified, ignoring this device.
[   153.331] (II) No input driver specified, ignoring this device.
[   153.331] (II) No input driver specified, ignoring this device.
[   153.331] (II) No input driver specified, ignoring this device.
[   153.332] (II) No input driver specified, ignoring this device.
[   153.332] (II) No input driver specified, ignoring this device.
[   153.332] (II) No input driver specified, ignoring this device.
[   153.332] (II) No input driver specified, ignoring this device.
[   153.333] (II) No input driver specified, ignoring this device.
[   153.333] (II) No input driver specified, ignoring this device.
[   153.333] (II) No input driver specified, ignoring this device.
[   153.334] (II) No input driver specified, ignoring this device.
[   153.334] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[   153.335] (II) Using input driver 'evdev' for 'ImExPS/2 Logitech Explorer Mouse'
[   153.335] (II) No input driver specified, ignoring this device.

Results of "lspcidrake -v | grep VGA"

Code: Select all

    Card:NVIDIA GeForce 8100 to GeForce 360: NVIDIA Corporation|GT218 [GeForce 210] [DISPLAY_VGA] (vendor:10de device:0a65 subv:3842 subd:1310) (rev: a2)

[doktor5000]

Looks OK. Apart from the solid grey background when the desktop loads, does it behave normally, or do you only get a grey background and the system is unusable at that point?

Also, how did you upgrade exactly? Which of the methods did you choose from https://wiki.mageia.org/en/Mageia_4_Rel ... m_Mageia_3

[drichard58]

OK - you are right. The issue is not the graphics card. I prefer the Gnome Classic and log in with that configuration. I created a test account and logged in with the new Gnome and the background comes in fine.

So it seems it may be something to do with the Gnome Classic log-in configuration.