recent kernel/nvidia update breaks my system

[wintpe]

OK so , this is my media center PC in the living room,
after doing an update and rebooting graphics wont start at all.
reboot of last kernel and its fine.

So i guess you guys will want the specific details so that it can be diagnosed.

first the rpm's at fault

Code: Select all

nvidia340-kernel-4.1.15-desktop-2.mga5-340.96-1.mga5.nonfree.x86_64
kernel-userspace-headers-4.1.15-2.mga5.x86_64
kernel-desktop-latest-4.1.15-2.mga5.x86_64
kernel-desktop-devel-latest-4.1.15-2.mga5.x86_64
kernel-desktop-devel-4.1.15-2.mga5-1-1.mga5.x86_64
kernel-desktop-4.1.15-2.mga5-1-1.mga5.x86_64



then the kernel and modules that the system is successfully running of of.

Code: Select all

name -a
Linux localhost 4.1.13-desktop-2.mga5 #1 SMP Wed Nov 11 01:02:41 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
[root@localhost ~]# rpm -qa|grep 4.1.13
kernel-desktop-4.1.13-2.mga5-1-1.mga5
nvidia340-kernel-4.1.13-desktop-2.mga5-340.93-3.mga5.nonfree
kernel-desktop-devel-4.1.13-2.mga5-1-1.mga5


and finally hardware

Code: Select all

[root@localhost ~]# lspci
00:00.0 RAM memory: NVIDIA Corporation MCP67 Memory Controller (rev a2)
00:01.0 ISA bridge: NVIDIA Corporation MCP67 ISA Bridge (rev a2)
00:01.1 SMBus: NVIDIA Corporation MCP67 SMBus (rev a2)
00:01.2 RAM memory: NVIDIA Corporation MCP67 Memory Controller (rev a2)
00:02.0 USB controller: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:02.1 USB controller: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:04.0 USB controller: NVIDIA Corporation MCP67 OHCI USB 1.1 Controller (rev a2)
00:04.1 USB controller: NVIDIA Corporation MCP67 EHCI USB 2.0 Controller (rev a2)
00:06.0 IDE interface: NVIDIA Corporation MCP67 IDE Controller (rev a1)
00:08.0 PCI bridge: NVIDIA Corporation MCP67 PCI Bridge (rev a2)
00:09.0 IDE interface: NVIDIA Corporation MCP67 AHCI Controller (rev a2)
00:0a.0 Ethernet controller: NVIDIA Corporation MCP67 Ethernet (rev a2)
00:0b.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:0c.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:0d.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:0e.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:0f.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:10.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:11.0 PCI bridge: NVIDIA Corporation MCP67 PCI Express Bridge (rev a2)
00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Address Map
00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
01:09.0 Multimedia audio controller: Creative Labs SB Audigy (rev 04)
01:09.1 Input device controller: Creative Labs SB Audigy Game Port (rev 04)
01:09.2 FireWire (IEEE 1394): Creative Labs SB Audigy FireWire Port (rev 04)
02:00.0 VGA compatible controller: NVIDIA Corporation G92 [GeForce GTS 250] (rev a2)


thanks

regards peter

[doktor5000]

What do you have in /var/log/Xorg.0.log when X server doesn't start?

edit doktor5000: FWIW, the most recent update has been validated as https://bugs.mageia.org/show_bug.cgi?id=17603
Best open a new bug report, and reference that one. And maybe for next nvidia340 update you could help QA team with the validation, as they don't have all sorts of hardware at their disposal, and they can only test what they use

[doktor5000]

Our kernel maintainer mentioned that you could be missing the x11-driver-video-nvidia340 package. Can you please post the full output of

Code: Select all

rpm -qa|sort|grep nvidia

[jiml8]

I get my nVidia driver from the nVidia website and compile it in. I do this for reasons ancient and probably no longer relevant, but it is a long-term habit.

I had a lot of trouble with the 340 driver when I was using it. Doktor might recall a thread of mine where I was having a chronic problem with my virtual consoles vanishing. That was with the 340 driver. When I moved to the 346 driver, my problems disappeared. I would recommend moving off of the 340 driver. That is likely to solve the problem.