Created attachment 11438 [details] This shows where the startup hung The last two kernel updates have resulted in a boot which proceeds past the cauldron splash screen but does not get to the logon dialog box. I am running Mageia 7 via Parallels Desktop 15 for Mac Pro Edition on a Mid 2012 13 inch MacBook Air. I normally run Mageia 7 full screen on an extended desktop (a 24 inch Dell). Kernels up to 5.3.13-2 all worked ok, but 5.4.2-1 and 5.4.6-2 do not, so I am continuing to use 5.3.13-2 until this issue is resolved. The attached screen shot shows where the startup process stops.
Thank you for the report and the evidence. Sorry for the trouble, but you have the good sense to continue with an older kernel. Assigning to the kernel group. I think there have been other 5.4 related bugs.
Summary: Boot does not proceed to logon dialog box => Boot does not proceed to logon dialog box after update to kernel 5.4Assignee: bugsquad => kernel
Just downloaded kernel 5.4.10.1, same problem still exists. Reverting to 5.3.13-2 for now.
None of the more recent kernel updates, including the latest 5.5.6-2, have resolved this issue for me, so I am continuing to stay with 5.3.13-2. Have other users reported this problem? Do I need to send you some log files, or do you have enough information from me already?
Hi John! Does text mode login (ctrl+alt+f2 and see https://unix.stackexchange.com/questions/164005/non-graphical-boot-with-systemd ), possibly followed by startx, works for you in the new kernels?
CC: (none) => shlomif
Created attachment 11536 [details] Failure of startx
Hi! (In reply to John Hardie from comment #5) > Created attachment 11536 [details] > Failure of startx So at least virtual console login is possible. can you share /var/log/Xorg.0.log ?
Because I am running virtual machines on my Mac, I am able to create multiple snapshots to ensure I keep good copies of Mageia 7 while I troubleshoot. This means I don't have to worry when things don't work. To make sure I understood your suggestions, I did a text mode login using kernel 5.3.13-2 followed by a startx. This was successful and landed me in IceWM. Rather than startx, is there another command, or perhaps a switch or parameter for startx, which would start a Plasma session instead from the command prompt? Once I was satisfied that I knew what to do on order to initiate a text mode login correctly, followed by a window manager of some sort, I reverted to a normal graphical startup (Plasma) so that I could then update to the new kernel 5.5.6-2 files easily. I then did a restart with a text mode login. As you can see by my new attachment, the startx command was unable to connect to X server this time. I don't know enough about the inner workings of the kernel to know when or where that missing file comes from or gets created, but presumably it existed under kernel 5.3.13-2. Could it be this simple? Be nice if it was. Over to you. Thanks for your assistance so far.
(In reply to John Hardie from comment #7) > Because I am running virtual machines on my Mac, I am able to create > multiple snapshots to ensure I keep good copies of Mageia 7 while I > troubleshoot. This means I don't have to worry when things don't work. > > To make sure I understood your suggestions, I did a text mode login using > kernel 5.3.13-2 followed by a startx. This was successful and landed me in > IceWM. Rather than startx, is there another command, or perhaps a switch or > parameter for startx, which would start a Plasma session instead from the > command prompt? > Yes, you can use .Xclients or .xinitrc. See e.g: https://github.com/shlomif/shlomif-computer-settings/blob/master/shlomif-settings/x11/dot-Xclients . > Once I was satisfied that I knew what to do on order to initiate a text mode > login correctly, followed by a window manager of some sort, I reverted to a > normal graphical startup (Plasma) so that I could then update to the new > kernel 5.5.6-2 files easily. I then did a restart with a text mode login. > As you can see by my new attachment, the startx command was unable to > connect to X server this time. > > I don't know enough about the inner workings of the kernel to know when or > where that missing file comes from or gets created, but presumably it > existed under kernel 5.3.13-2. Could it be this simple? Be nice if it was. > > Over to you. Thanks for your assistance so far. Please share the file "/var/log/Xorg.0.log" after an unsuccessful startx in the problematic kernel.
When Mageia starts normally with the good kernel, I am able to copy files out to the Mac OS via /media/pfs (short for Parallels Shared Folders). I'll attach a screenshot of a Konsole session which shows the folders I can see. When the bad kernel prevents startx from completing correctly, I can't see these folders from the command line, therefore I have no way to copy files to where I can uses them. Therefore, in order to be able to send you the Xorg.0.log file, I have had to resort to paging through it using "less" and doing a screen shot of each page. There are 6 screen shots, and there is a bit of overlap on each page, but at least it's all there. Just for comparison, I'll send you the log file as it appears with a proper start with the good kernel. I hope this helps.
Created attachment 11537 [details] Konsole window of /media/psf Shows what I can normally see in /media/pfs
Created attachment 11538 [details] Log file of normal startup with good kernel Xorg.0.log with good kernel
Created attachment 11539 [details] Log file page 1 bad kernel Xorg.0.log page 1
Created attachment 11540 [details] Log file page 2 bad kernel Xorg.0.log page 2
Created attachment 11541 [details] Log file page 3 bad kernel Xorg.0.log page 3
Created attachment 11542 [details] Log file page 4 bad kernel Xorg.0.log page 4
Created attachment 11543 [details] Log file page 5 bad kernel Xorg.0.log page 5
Created attachment 11544 [details] Log file page 6 bad kernel Xorg.0.log page 6
(In reply to John Hardie from comment #0) > Created attachment 11438 [details] > This shows where the startup hung > > The last two kernel updates have resulted in a boot which proceeds past the > cauldron splash screen but does not get to the logon dialog box. > > I am running Mageia 7 via Parallels Desktop 15 for Mac Pro Edition on a Mid > 2012 13 inch MacBook Air. I normally run Mageia 7 full screen on an > extended desktop (a 24 inch Dell). > > Kernels up to 5.3.13-2 all worked ok, but 5.4.2-1 and 5.4.6-2 do not, so I > am continuing to use 5.3.13-2 until this issue is resolved. > Sorry, but this is not a Mageia bug as such. As you are using Parallels Desktop 15, you need to consult their support or forums about support for newer linux kernels. As you noted in comment 9 the shared folders does not work either with the newer kernels, confirming the need for fixes from Parallels. There is nothing we can do here.
Resolution: (none) => INVALIDCC: (none) => tmbStatus: NEW => RESOLVED
A quick googling found this possible fix: https://kb.parallels.com/en/124743
And according to this: https://forum.parallels.com/threads/kernel-5-5-5-breaks-parallels-tools-15-1-2-47123.349299/ "5.4.20 should build fine with the last update of Parallels (15.1.2.47123)." but no support for 5.5 series yet... unless you find an un-official patch somewhere..
(In reply to John Hardie from comment #17) > Created attachment 11544 [details] > Log file page 6 bad kernel > > Xorg.0.log page 6 Hi John! Just for the record, it should be possible to stitch together image files vertically using GraphicsMagick or similar: http://www.graphicsmagick.org/ .
Hi All! Thanks for all your help. I might give that possible quick fix a try, it's pretty simple, and if it doesn't help I can change it back. But certainly from the forum discussion it looks like Parallels is having issues with the kernel updates, so I'll just stick with 5.3.13-2 until they sort it out.