Bug 23901

Summary:	Failure of nvidia proprietary driver to be installed during boot from Live iso
Product:	Mageia	Reporter:	Len Lawrence <tarazed25>
Component:	Release (media or process)	Assignee:	ISO building group <isobuild>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	andrewsfarm, kernel, mageia, marja11, tmb
Version:	Cauldron	Keywords:	7beta1
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Bug Depends on:	24037
Bug Blocks:

Description Len Lawrence 2018-11-26 02:16:37 CET

Description of problem:
The latest Live isos cannot be booted under the nvidia proprietary driver.  A console shows that the module is being built and that there is an attempt to install it - this probably fails (my guess is improperly installed) - and the cycle starts again.  It is an endless loop.  Based on the troubles with nvidia since the new support scheme was announced, another guess is that this is another example of the wrong version of the proprietary driver being selected.

Version-Release number of selected component (if applicable):
Mageia7 beta1 second round Plasma/GNOME

How reproducible:
Always

Steps to Reproduce:
1. Boot one of the live isos from a USB stick on an nvidia machine
2. Select the proprietary driver
3. Hit Esc to see what is going on under the hood - endless loop of building and installing the kmod for nvidia.

Marja Van Waes 2018-11-26 09:04:17 CET

CC: sysadmin-bugs => kernel, marja11
Assignee: bugsquad => isobuild
Keywords: (none) => 7beta1

Comment 1 Martin Whitaker 2018-11-26 20:42:01 CET

Which version of the proprietary driver works on this machine (in cauldron)? When booting, you should see a message telling you which driver is being built and installed - is it the right one?

CC: (none) => mageia

Comment 2 Thomas Backlund 2018-11-26 21:29:46 CET

Actually I just fund out drakx is not handling the new/ upstream changed layout of the nvidia-current driver, so I need to fix it

CC: (none) => tmb

Comment 3 Thomas Backlund 2018-11-26 22:29:06 CET

Ok, so drakx checks for existence of libglx.
When I was about to change that I realized there might be other software out there that searches for libglx (that exists in all other nvidia drivers, so I went the other way...

I've added libglx compat symlinks in  nvidia-current-410.78-2.mga7 so it will cover both older and newer code..

Comment 4 Len Lawrence 2018-11-27 00:57:46 CET

@Martin, re comment 1:
I have lost track of what was happening with the Lives but with normal nvidia updates there have been a couple of instances of nividia304 being built on reboot, which is entirely inappropriate for the hardware and out of step with installing series 420 and later using drakx11, either in runlevel 3 or before rebooting.

Let's hope that Thomas's latest changes resolve the confusion around nvidia installations.

Comment 5 Martin Whitaker 2018-11-27 09:55:06 CET

nvidia304 is no longer available in cauldron, so it would definitely fail to build. If you do still see it being chosen, please open a bug for that.

Comment 6 Martin Whitaker 2018-12-19 16:09:20 CET

Although Thomas's changes should fix the original problem Len saw, there is another problem that prevents the proprietary drivers being installed during Live system boot - see bug 24037.

Depends on: (none) => 24037
CC: (none) => andrewsfarm

Comment 7 Martin Whitaker 2019-05-18 21:06:51 CEST

I think this is fixed now. Len, feel free to reopen if you disagree.

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

Comment 8 Len Lawrence 2019-05-19 01:28:30 CEST

No, I agree Martin.  I have not seen any problems lately.