Description of problem: Can not select updated kernel According to https://bugs.mageia.org/show_bug.cgi?id=27638#c7 and https://wiki.mageia.org/en/Persistent_live_systems#Original_kernel This was working in mga8 at least during testing before release. Version-Release number of selected component (if applicable): Released mga8 Live (Plasma variant tested) How reproducible: 100%, Repeated twice Steps to Reproduce: 1. Prepare mga8 Live USB stick with persistence 2. Boot it 3. Update kernel and kernel-devel (tested latest 5.15 once, and on clean persistence next try with 5.10.78) This also force 12 prioritised packages get installed first concerning glibc, rpm, perl, python. 4. Reboot 5. No [F1] option in sight. Press it anyway, nothing. Did this break before release, or is it related to any of the packages it installed in point 5? It works in Mageia 9 Live Xfce 64bit beta2 [F1] shows up on a row above the [F2] option. (default is booting the latest) Is there a manual workaround?
Update errata 8 and https://wiki.mageia.org/en/Persistent_live_systems That it is broken, and hopefully how to fix it.
Assignee: bugsquad => mageiatoolsKeywords: (none) => FOR_ERRATA8
What filesystem are you using for the persistent partition, and which version of Mageia did you use to create and format it?
CC: (none) => mageia
To create the stick i used current isodumper on current Cauldron. Selected persistence, default is ext4 ... so that ext4 got formatted by Mageia 9 tools. - but never mounted on Mageia 9. Persistence itself do work, it remebers my network, and rpm -qa|grep kernel lists that i do have two kernels installed.
OK, this is more fallout from bug 31641. The GRUB bootloader on the Live ISOs is too old to handle the new ext4 option, so it can't read what's in your persistent partition. I believe you can disable that option on a cauldron system by editing /etc/mke2fs.conf. Alternatively, use a Mageia 8 system to (re)format the partition.
Thank you Martin. I will try later and note it somewhere. Maybe Errata is the correct place, but I let it stand as a reminder for now. Except for the F1 choice in grub, the persistence seem to work nicely, but i have not tested much. Should we warn about creating persistence on live Mageia 8 (and earlier) using Mageia 9 or other systems using ext4 "feature C12"? We do have instructions for creating persistence on Live operating on itself. https://wiki.mageia.org/en/Persistent_live_systems#Removing_or_recreating_persistence_on_itself
Summary: Mga8 Live kernel selection is broken => Mga8 Live kernel selection is broken if persistence was made using mga9Status comment: (none) => to verify and note in wiki
(In reply to Martin Whitaker from comment #4) > > I believe you can disable that option on a cauldron system by editing > /etc/mke2fs.conf. Alternatively, use a Mageia 8 system to (re)format the > partition. If partition formats are incompatible, why have they the same name ext4 (question is not for you)? More proactive, is there means to give option in formatting from isodumper to use the old format?
CC: (none) => yves.brungard_mageia
(In reply to papoteur from comment #6) > More proactive, is there means to give option in formatting from isodumper > to use the old format? I think mkfs.ext4 -O ^metadata_csum_seed,^orphan_file should do it, but I haven't tested it.
I verified F1 works when I used the Mga8 Live to crate persistence on itself (Comment 5) https://wiki.mageia.org/en/Persistent_live_systems#Ext4_option_difference For now regarding IsoDumper, an entry under https://wiki.mageia.org/en/Mageia_9_Errata#Various_software And https://wiki.mageia.org/en/Mageia_8_Errata#Live_images Leaving bug open for IsoDumper: Make it handle the problem or close this bug.
Keywords: FOR_ERRATA8 => IN_ERRATA8, IN_ERRATA9
Status comment: to verify and note in wiki => (none)
fs2progs package has been modified to not include metadata_csum_seed nor orphan_file options. Thus closing.
Status: NEW => RESOLVEDResolution: (none) => FIXED
Udated (a while ago) Erratas and Persistent Live wiki page.
I assume /etc/mke2fs.conf is not modified by the update in an already earlier installed (i.e beta2) system?
Summary: Mga8 Live kernel selection is broken if persistence was made using mga9 => Mga8 Live kernel selection is broken if persistence was made using mga9 (beta 2 and earlier)
(In reply to Morgan Leijström from comment #11) > I assume /etc/mke2fs.conf is not modified by the update in an already > earlier installed (i.e beta2) system? Indeed, the configuration parameters are used at the formatting time. Once the format is done, it's done.
I was thinking about an Mageia 9 alpha..beta2 installed this winter... in that i think /etc/mke2fs.conf still include metadata_csum_seed and orphan_file options, even after all updates until now? And when using that system to make a Live USB, when running isodumper those options will be used for creating persistence?