Bug 19461 - Changing driver from nouveau to nvidia makes the system unbootable
Summary: Changing driver from nouveau to nvidia makes the system unbootable
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-26 19:14 CEST by Christian C
Modified: 2018-04-29 09:38 CEST (History)
3 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments
/var/message extract when installing nvidia driver (24.48 KB, text/plain)
2016-09-26 19:21 CEST, Christian C
Details
dmesg when booting with nvidia drivers (57.31 KB, application/x-trash)
2016-09-26 19:31 CEST, Christian C
Details

Description Christian C 2016-09-26 19:14:56 CEST
Description of problem:
I installed the non free drivers from nvidia for my graphic card but couldn't boot. the system freezes at restart. see the file joined.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Christian C 2016-09-26 19:21:03 CEST
Created attachment 8448 [details]
/var/message extract when installing nvidia driver
Comment 2 Christian C 2016-09-26 19:31:05 CEST
Created attachment 8449 [details]
dmesg when booting with nvidia drivers
Marja Van Waes 2016-09-27 10:43:03 CEST

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

Comment 3 Rémi Verschelde 2016-09-27 10:45:18 CEST
How did you install the nvidia drivers? The ones packaged by Mageia, or the ones provided by nvidia?
Comment 4 Christian C 2016-09-27 15:59:06 CEST
I used drakconf that propose to install the Mageia nvidia packages.
See /var/log/messages in attachment 8448 [details] https://bugs.mageia.org/attachment.cgi?id=8448
Comment 5 Thomas Backlund 2016-09-29 20:22:59 CEST
Thierry, it looks like the drakx code to prefer prebuilt kmods now bites us since we dont have prebuilt proprietary drivers anymore...

From the log:
drakx11[24329]: those kernel module packages can be installed: dkms-nvidia340 nvidia340-kernel-3.19.8-desktop-3.mga5 dkms-nvidia340 dkms-nvidia340 nvidia340-kernel-4.1.12-desktop-1.mga5 nvidia340-kernel-4.1.13-desktop-2.mga5 dkms-nvidia340 dkms-nvidia340 dkms-nvidia340 nvidia340-kernel-4.1.12-desktop-1.mga5 nvidia340-kernel-4.1.13-desktop-2.mga5 dkms-nvidia340 


Then it goes ahead and pulls in / "downgrades to ancient release kernel" with matching kmods:
[RPM][24353]: install kernel-desktop-3.19.8-3.mga5-1-1.mga5.x86_64: success
[RPM][24353]: install nvidia340-kernel-3.19.8-desktop-3.mga5-340.76-27.mga5.nonfree.x86_64: success


even if the user had newer kernels:
bootloader-config[24455]: current labels: linux-nonfb failsafe desktop 4.1.12-1.mga5 desktop 4.1.13-2.mga5 linux desktop 4.4.13-1.mga5 desktop 4.4.16-1.mga5


and poof...

CC: (none) => thierry.vignaud, tmb

Comment 6 Marja Van Waes 2018-04-29 09:38:00 CEST
(In reply to Thomas Backlund from comment #5)
> Thierry, it looks like the drakx code to prefer prebuilt kmods now bites us
> since we dont have prebuilt proprietary drivers anymore...
> 
<snip>
> 
> 
> Then it goes ahead and pulls in / "downgrades to ancient release kernel"
> with matching kmods:
> [RPM][24353]: install kernel-desktop-3.19.8-3.mga5-1-1.mga5.x86_64: success
> [RPM][24353]: install
> nvidia340-kernel-3.19.8-desktop-3.mga5-340.76-27.mga5.nonfree.x86_64: success
>
<snip> 
> 
> even if the user had newer kernels:
> bootloader-config[24455]: current labels: linux-nonfb failsafe desktop
> 4.1.12-1.mga5 desktop 4.1.13-2.mga5 linux desktop 4.4.13-1.mga5 desktop
> 4.4.16-1.mga5
> 
So regardless of whether drakx got fixed, this cannot happen in Mageia 6 or later.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

Closing as OLD

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


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