Description of problem: Mageia-6.1-rc-LiveDVD-Plasma-x86_64-DVD.iso md5sum: f73d5fd0910aa9d66f93dee8a0bf176d Sat Aug 4 19:07:37 CEST 2018 During install familiar screen indicating the installation of the nvidia drivers does not appear. Install proceeds normally but no nvidia driver After install attempting to install nvidia driver results in an unbootable system.
On real hardware, M6.1, Plasma, 64-bit Package(s) under test: nvidia driver lspci -k nouveau driver installed
Assignee: bugsquad => isobuildCC: (none) => marja11Component: Installer => RPM Packages
If you boot to the Live desktop, selecting the "+ use proprietary drivers" option in the boot menu, does the nvidia driver get built and used? If not, please attach the output of 'journalctl -ab > journal.log' (run as root).
CC: (none) => mageia
Sorry Martin, I've gone through so many of these things so fast that I completely missed that new comment on the boot menu. Is that new? Anyway, on real hardware from the boot menu I selected the install option and the proprietary drivers. All installed just fine, the install successfully booted to a working desktop and lspci -k indicated it was using the nvidia driver. But, having said all that if you skip that little initial setup from the boot menu and don't install the nvidia driver from the get go and try to set up the graphic server later it's looks like it borks the install. Is that ok? Gotta think about this.
(In reply to William Kenney from comment #3) > Sorry Martin, I've gone through so many of these things so fast that I > completely missed that new comment on the boot menu. Is that new? Anyway, on > real hardware from the boot menu I selected the install option and the > proprietary drivers. All installed just fine, the install successfully > booted to a working desktop and lspci -k indicated it was using the nvidia > driver. I added that new option in the boot menu in the run up to the Mageia 6 release. It was in the UEFI boot menu fairly early on, but didn't get added to the legacy boot menu until fairly late on. > But, having said all that if you skip that little initial setup from the > boot menu and don't install the nvidia driver from the get go and try to set > up the graphic server later it's looks like it borks the install. Is that > ok? Gotta think about this. That's definitely not OK. It's a pity we don't yet have classical installer ISOs, to know if it's a general problem, or something specific to the way the live system is installed. Can you boot in failsafe mode? If so, capture the log from the previous (failed) boot attempt with journalctl -b -1 > lastboot.log and attach it here.
(In reply to Martin Whitaker from comment #4) > Can you boot in failsafe mode? If so, capture the log from the previous > (failed) boot attempt with > > journalctl -b -1 > lastboot.log > > and attach it here. All gone. Lemme work on get'n the log. Yes, I await the CI's also.
So another shot at this. All on real hardware. Execute a nouveau no proprietary driver install. All is well. Then in the MCC set up the graphical server. All the files seem to install. When I go to reboot the system the boot menu does not appear When I force ( warm boot ) the system it boots to a "grub" terminal It never gets to the boot menu. See attached image.
Created attachment 10310 [details] grub screen after boot
I've tried to reproduce this on my NVIDIA test system without success. Apart from the problem that TJ always reports, that the Plasma reboot/shutdown control no longer works after you change the video driver (so you have to switch to a console and reboot from there), all worked as expected. Bill, can you try this again, but this time start the MCC from a Konsole window using the comand drakconf |& tee drakconf.log When done, attach the resulting drakconf.log file here, along with the journal.log file produced by running (as root) journalctl -ab > journal.log and copies of /boot/grub2/grub.cfg and /boot/grub2/grub.cfg.old.
Keywords: (none) => NEEDINFO
FWIW, I just tried the 32-bit Xfce Live on my one nvidia system, which uses the nvidia340 driver. I booted with the free driver, installing from the boot menu. All went as expected. Went to MCC, grabbed updates, including those that came up in tainted, and rebooted. Xfce seems to be just fine with the nouveau driver. Installed the nvidia driver, and rebooted once more. (No problem rebooting as with Plasma) Rebooted to a working desktop, no problems noted. So, it would seem this is a 64-bit problem, or a Plasma problem, or an nvidia-current problem. Will try to attempt a Plasma install this evening, so we can see if nvdia340 is affected in Plasma.
CC: (none) => andrewsfarm
My test in comment 8 was Plasma/64-bit/nvidia340.
Today I was able to capture those logs Martin. They are attached Today instead of borking the system it booted to the following error message: "Plasma is unable to start as it could not correctly use OpenGL2 Pleas check that your graphic drivers are set up correctly" Tapping "OK" resulted in a hung black screen.
Created attachment 10320 [details] drakconf.log
Created attachment 10321 [details] grub.cfg
Created attachment 10322 [details] grub.cfg.old
You seem to be lacking the nokmsboot option. Does the system boot if you add that manually in the GRUB2 boot menu? Did you capture the journal as described in comment 8? If not, and if you can boot by adding the nokmsboot option, you can get it now by running (as root) journalctl -b -2 > journal.log assuming you've not tried to boot any more times. If you have, just change the -2 to a bigger negative number reflecting the number of times you've tried to reboot since installing the video driver.
(In reply to Martin Whitaker from comment #15) > You seem to be lacking the nokmsboot option. Does the system boot if you add > that manually in the GRUB2 boot menu? Sorry, same result except that the hung black screen now has the cursor on it.
(In reply to Martin Whitaker from comment #10) > My test in comment 8 was Plasma/64-bit/nvidia340. OK then, since you and Bill have it covered, or at least as much as I could help, I'll move on to testing kernels.
(In reply to Thomas Andrews from comment #17) > OK then, since you and Bill have it covered, or at least as much as I could > help, I'll move on to testing kernels. I do not consider this a critical problem. In fact I wouldn't hold up releasing the isos because of this. Martin cannot duplicate it and if you install correctly by designating the proprietary drivers from the boot menu it will install just fine. Martin teaches me a LOT of things that I can use as tools for testing now and in the future. I have a special note pad for all of this for reference :-))
Closing this one as old - we can't fix the 6.1 ISOs now.
Status: NEW => RESOLVEDResolution: (none) => OLD