With encrypted persistence, boot fail. (the first boot) Message suggest to add rd.debug to kernel line for more debug. Doing that, kernel say illegal file name. Version-Release number of selected component: Mageia Live 8b1 xfce 32 bit iso -i have not checked the other Mageia 8 isos
I can't reproduce that. Are you sure you didn't mistype?
CC: (none) => mageia
Iso: Mageia Live 8b1 xfce 32 bit iso Writer: Isodumper 1-27-1 on mga7-64 desktop Operating machine: Thinkpad T43 __With nonencrypted persistence__ It only get to black screen with blinking cursor top left and square mouse pointer. Ctrl-Alt-F12 display journal, and i can see it gets in some timeout-retry loop. Picture attached. __With encrypted persistence__ After user entered encryption key, the bubbling cauldron is shown for a couple minutes, then fail, and tip about rd.debug. Both picture and rdsosreport.txt attached. Then picture where i have entered rd.debug to boot line, and a picture of the message "invalid file name". It also say press any key to continue, but in a few seconds it proceeds regardless, and kernel panic.
Created attachment 12018 [details] rdsosreport.txt, compressed, failed boot encrypted persistence i586 xfce 8b1
? why was sysadmin-bugs CC ?
CC: sysadmin-bugs => (none)
The failure with encrypted persistence is just bug 27638. No pictures attached yet... I believe sysadmin-bugs is automatically added to CC when you create a bug with component "Release (media or process)".
(In reply to Martin Whitaker from comment #5) > The failure with encrypted persistence is just bug 27638. OK. But no way to get out of it, right? (no old kernel) > No pictures attached yet... $consultantjob hit. Coming... > I believe sysadmin-bugs is automatically added to CC when you create a bug > with component "Release (media or process)". Probably :)
Created attachment 12019 [details] non encrypted loop booting Ctrl-Alt-F12 journal picture
Created attachment 12020 [details] encrypted boot ends with this a couple minutes after encr key is given
Created attachment 12021 [details] rd.debug added to command line
Created attachment 12022 [details] Invalid file name rd.debug
You need to add rd.debug to the line starting with "$linux" (the kernel command line), not the one starting "$initrd".
doh! I saw it like one long broken line... Now i feel stupid. Well, that is healthy sometimes. Thank you for the quick replies!
Resolution: (none) => INVALIDStatus: NEW => RESOLVED