After upgrading a virtualbox guest from Mageia 5 to 6 using mgaapplet, the graphics do not work until the kernel option nokmsboot has been added manually. Ideally upgrading should detect whether the Mageia 6 system will or will not require the nokmsboot option, and alter the kernel parameters accordingly. If we can't do this, or if we need a decision table for users to use to indicate when the option is needed, for the wiki and errata.
CC: (none) => mageia, tmbAssignee: bugsquad => thierry.vignaudBlocks: (none) => 21340
As mentioned on qa-discuss, it's the opposite for me - no problems without nokmsboot, kernel oops or complete hang with nokmsboot.
From my poll on qa-discuss, nobody else is seeing this bug. Dave, could you attach the journal and Xorg.0.log from a boot without the nokmsboot option, so we can see where it's failing.
Fixed the bug summary. In working Mageia 5 vb installs I have the nomodeset kernel option. After upgrading to Mageia 6, the option has to be manually removed or X fails to start. Sorry for the confusion I caused mixing up the options.
Summary: nokmsboot kernel option has to be added manually after upgrade => nomodeset kernel option has to be manually removed after upgrade
Now I'm really confused. My working x86_64 Mageia 5 vb install does not have the nomodeset option. It's only on the i586 install, which is what I've mostly been using for my upgrade tests. Re-testing upgrade of the x86_64 install shortly.
(In reply to Dave Hodgins from comment #3) > Fixed the bug summary. > > In working Mageia 5 vb installs I have the nomodeset kernel option. > > After upgrading to Mageia 6, the option has to be manually removed or X fails > to start. OK, that matches my experience. This can be fixed by running '/sbin/display_driver_helper --setup-boot-kms'. We could make mgaapplet-upgrade-helper do this automatically after completing the upgrade.
Created attachment 10264 [details] journalctl -b output After x86_64 upgrade test, X is failing to start. Tried with and without nokmsboot, with and without nomodeset.
Created attachment 10265 [details] Xorg.0.log contents
Not sure why yet, but on this latest x86_64 m5 to m6 upgrade, the vboxvideo module is not being loaded at boot. After running "modprobe -v vboxvideo", startx is working.
Think I've found the cause of that problem. # ll /etc/modprobe.d/vboxvideo.conf -rw-r--r-- 1 root root 20 Oct 18 2016 /etc/modprobe.d/vboxvideo.conf [root@x5v module]# cat /etc/modprobe.d/vboxvideo.conf blacklist vboxvideo Why that was added, and how it was working in m5, I have no idea. Don't remember adding it, but obviously at some point I did. Removing that file fixes the x86_64 x11 problem.
Found where I added it ... https://bugs.mageia.org/show_bug.cgi?id=19213#c66 When I removed it during that testing, must have only done so in a snapshot, and forgotten to redo it after reverting the snapshot.
On first boot after upgrade, get the message a reboot is needed due to a display driver change. Would be nicer if the nomodeset kernel option was removed during the upgrade rather then on the first boot, but this works. Yeah! :-) Closing as fixed. Thanks everyone.
Resolution: (none) => FIXEDStatus: NEW => RESOLVED