Description of problem: Appears upgrade from MGA5 to MGA6 is causing an infinite look in the upgrade. This is a KDE to Plasma 64-bit upgrade
Version-Release number of selected component (if applicable): 6
How reproducible: VM instance, MGA5 fully patched up to 20170311 perform install/upgrade from classic ISO
Steps to Reproduce:
1. Run install/upgrade
3. I will attach journal and dmesg
Created attachment 9071 [details]
truncated journal of execution
This should contain some information from patching I did right before the upgrade and then execution after upgrade. I'll add dmesg as well.
Created attachment 9072 [details]
dmesg of the reboot and execution after the upgrade from mga5 to 6
SDDM is looping, but I'm not sure SDDM is the culprit.
CC'ing KDE team and kernel&drivers maintainers
kde, kernel, marja11
Happened with i586 and GNOME MGA5 to MGA6 upgrade as well - the 20170314 version of the classic code.
I think the system is still trying to run grub instead of grub2, could that be part of the issue?.
Anything you want me to try and get for this?
(In reply to Brian Rockwell from comment #4)
> Happened with i586 and GNOME MGA5 to MGA6 upgrade as well - the 20170314
> version of the classic code.
> I think the system is still trying to run grub instead of grub2, could that
> be part of the issue?.
CC'ing barjac and the isobuilders, keeping grub during an upgrade is intended and should not cause any problems on reboot.
> Anything you want me to try and get for this?
Yeah, please fetch /root/drakx/report.bug with the _time_stamp_ that matches the upgrade. (/root/drakx/report.bug.xz is very likely from the original Mga5 install)
Copy it to your home directory and then compress it with xz:
and then attach report.bug.xz to this report.
4052746240 Feb 28 15:03 Mageia-6-sta2-x86_64-DVD.iso =>
6RC, 6sta2, NEEDINFO
Upgrade from MGA5 KDE to MGA6 PLASMA results in loop-out (VM instance) =>
Upgrade from MGA5 KDE to MGA6 PLASMA results in loop-out (VM instance). Gnome5->6 causes a loop-out on reboot, too
Created attachment 9162 [details]
First of the three files I collected off of the upgrade from MGA5.1 KDE to 6 Plasma using Virtual Box. After reboot the system hangs and loops.
This one was done on an Intel.
Created attachment 9163 [details]
From Intel VirtualBox upgrade of MGA 5 to 6
Created attachment 9164 [details]
Only setting to release blocker in case it is one (or two!), I didn't check the provided ddebug log, yet.Keywords:
i don't pass to reproduce.
Did you tried an other update to see if this is still valid?
you update isfrom Sta2 isos or update by the internet ?
MGA 5 was current.
MGA 6 was built from mageia_6_rc_x86_64-DVD classic.
In the first attachment (the journal) I see
Mar 11 18:32:13 localhost service_harddrake: switch X.org driver from 'vboxvideo' to 'modesetting' (The graphics card 'InnoTek Systemberatung GmbH|VirtualBox Graphics Adapter' is no longer supported by driver 'vboxvideo')
which is correct. But going back to the point where you rebooted, I see
Mar 11 18:32:06 localhost kernel: Command line: BOOT_IMAGE=linux root=UUID=4d95d47d-4d08-4069-827d-d8ce3dab4323 nomodeset splash quiet noiswmd resume=UUID=12f65877-1ad2-4a8f-97cd-1d8720e0aabf audit=0 vga=788
Testing this locally, the 'nomodeset' option does stop the 'modesetting' driver working (which isn't too surprising!).
Ideally harddrake would remove the 'nomodeset' option and force a reboot in this case.
@Brian, please try removing 'nomodeset' from the boot command line in the grub menu, to see if that fixes the problem.
@Martin - removing nomodeset from the kernel options did bring me to a working desktop
Upgrade from MGA5 KDE to MGA6 PLASMA results in loop-out (VM instance). Gnome5->6 causes a loop-out on reboot, too =>
Vbox upgrade from 5 to 6 breaks due to changing driver from vboxvideo to modesetting but keeping nomodeset argumentStatus comment:
Only setting to release blocker in case it is one (or two!), I didn't check the provided ddebug log, yet. =>
The 'nomodeset' option should be removed when chaging to the modesetting driverAssignee:
(In reply to Martin Whitaker from comment #11)
> Mar 11 18:32:13 localhost service_harddrake: switch X.org driver from
> 'vboxvideo' to 'modesetting' (The graphics card 'InnoTek Systemberatung
> GmbH|VirtualBox Graphics Adapter' is no longer supported by driver
> Ideally harddrake would remove the 'nomodeset' option and force a reboot in
> this case.
Thierry, what do you think about this?
The 'nomodeset' option should be removed when chaging to the modesetting driver =>
The 'nomodeset' option should be removed when changing to the modesetting driverCC:
But I don't have much time (I've a 21 day newborn)
The code in question is in:
Created attachment 9265 [details]
Proposed fix part1
Created attachment 9266 [details]
Proposed fix part2
Try these. I've tested a mga5 to mga6 upgrade in Vbox, and they fix the bug for me.
Looks good to me
Great :) Feel free to commit and make new releases Martin, I'll push the packages.
Author: Martin Whitaker <mageia@...>
Date: Sat May 6 13:12:28 2017 +0100
service_harddrake: require reboot if nokmsboot option changed (mga#20455).
Author: Martin Whitaker <martin@...>
Date: Sat May 6 12:21:47 2017 +0100
Remove 'nomodeset' boot option when switching to a modesetting driver (mga#20455).
(In reply to Rémi Verschelde from comment #18)
> Great :) Feel free to commit and make new releases Martin, I'll push the
I think that's all done now.
Fixes pushed in drakxtools-17.82-1.mga6 and drakx-kbd-mouse-x11-1.22-1.mga6.