Bug 18408

Summary: nvidia broken after the last kernel update
Product: Mageia Reporter: Len Lawrence <tarazed25>
Component: RPM PackagesAssignee: Kernel and Drivers maintainers <kernel>
Status: RESOLVED FIXED QA Contact:
Severity: major    
Priority: Normal CC: marja11, sysadmin-bugs
Version: CauldronKeywords: 6sta1, NEEDINFO
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: CVE:
Status comment:

Description Len Lawrence 2016-05-08 13:49:22 CEST
Description of problem:
Running 6sta1 classic install of GNOME on Dell XPS M1730
Installed the latest kernel and nvidia driver updates and rebooted to a monitor test pattern (alternating coloured screens).  The result is the same with the other two installed kernels and failsafe mode, so there is no way into the system.  Consoles are not available.  My guess is that the wrong generation nvidia driver has been selected.  Should I have rejected the driver update?

Version-Release number of selected component (if applicable):
Really don't know how to classify this:
either Mageia-6-sta1-LiveDVD-PLASMA5-x86_64-DVD
or kernel-4.6.0-desktop-0.rc6.2.mga6/nvidia340.96

Labelling this as Major but it could be a matter of user ignorance and therefore trivial.

How reproducible:
Not possible to reproduce - the system is unreachable.

Steps to Reproduce:
1. Once only:  Install the kernel and nvidia updates noted above
2. Reboot to any kernel
3. Watch the light show
Comment 1 Marja Van Waes 2016-05-08 14:42:38 CEST
(In reply to Len Lawrence from comment #0)
> Description of problem:
> Running 6sta1 classic install of GNOME on Dell XPS M1730
> Installed the latest kernel and nvidia driver updates and rebooted to a
> monitor test pattern (alternating coloured screens).  The result is the same
> with the other two installed kernels and failsafe mode, so there is no way
> into the system.  

Can you try to append a space and the number 3 to the kernel options line when you see your bootloader screen?

That way you should be able to reach a VT to do a text login (and first try to update again, in case you didn't install all dependencies. If there aren't any such updates, you can run XFdrake to try a different driver).

Assignee: bugsquad => tmb
Keywords: (none) => 6sta1
CC: (none) => marja11
Component: Release (media or process) => RPM Packages

Comment 2 Len Lawrence 2016-05-08 15:19:09 CEST
Yes I shall try that.
After reinstalling the system ran fine with the rc5.2.mga6 kernel (think that it was that).
Installed all the updates and rebooted to the old (same) kernel and it was OK.
Rebooted to the new kernel; rc6.2.mga6 and it failed on nvidia.
Rebooted and tried to go back to the previous kernel but this time that failed too.

Not sure what is going on but it seems like dkms is doing something funny.

Off to try your suggestion.  Thanks Marja.
Comment 3 Len Lawrence 2016-05-08 15:28:51 CEST
OK.  Tried level 3 boot and hit the same problem with both kernels.  Could not see a console screen and was unable to see one using the CtrlAltF* sequence.

The monitor test pattern possibly means that here is no driver at all or the driver is damaged and not sending the correct signals or cannot see the monitor panel.

For this machine it is the nvidia 8100 series driver.
The panel is a Seiko/Epson at 1920x1200.
Comment 4 Len Lawrence 2016-05-08 15:55:39 CEST
Tried hitting Esc as soon as kernel selected and was given the opportunity for
linux
linuxfb
failsafe mode

The first two displayed a short stream of messages and failed at the monitor test pattern.
failsafe got past "Welcome to Mageia 6" and several more messages before "Failed" flashed off the top of the screen.  Then the monitor test pattern kicked in.
Comment 5 Len Lawrence 2016-05-08 16:05:24 CEST
As a last resort I tried an Upgrade of the whole system but that was a forlorn hope.  Have run out of options here.
Comment 6 Len Lawrence 2016-05-08 19:01:11 CEST
Another install with bad blocks checking on the system partition, just in case.  On updating, declined the kernel update but did install dkms-nvidia340.  With that the reboot was OK.  So it is looking more like a kernel problem.
Comment 7 Len Lawrence 2016-08-17 19:47:10 CEST
Not much point in keeping this going now that mageia is at RC and later kernels.
Comment 8 Marja Van Waes 2016-08-26 12:48:56 CEST
Mass-reassigning all bugs with "kernel" in the summary that are still assigned to tmb (or wrongly assigned to someone with "tmb" in his e-mail address) to the kernel packagers group, but without adding "kernel" to the SRPM field.

Please reassign if needed, or add kernel to the SRPM field if this is correct.

Assignee: tmb => kernel

Comment 9 Marja Van Waes 2017-03-05 10:23:23 CET
Is this bug still valid for newest 6sta2?

Summary: 6sta1 nvidia broken after the last kernel update => nvidia broken after the last kernel update
Keywords: (none) => NEEDINFO

Comment 10 Marja Van Waes 2021-07-02 23:27:26 CEST
This got fixed five years ago

Status: NEW => RESOLVED
Resolution: (none) => FIXED