FS#72663 - [grub,booster] grub generate menuentry with missing initrd line
Attached to Project:
Arch Linux
Opened by fsdsfd (BCD889) - Monday, 08 November 2021, 10:11 GMT
Last edited by Toolybird (Toolybird) - Sunday, 11 June 2023, 03:50 GMT
Opened by fsdsfd (BCD889) - Monday, 08 November 2021, 10:11 GMT
Last edited by Toolybird (Toolybird) - Sunday, 11 June 2023, 03:50 GMT
|
Details
Hi
I switched to booster from mkinitcpio, when regenerated grub config file, grub-mkconfig create 2 menuentry blocks: block 0 with missing initrd line and a second menuentry with kernel and initramfs image respectively. obviously after reboot, a kernel panic occurred. as a temporary workaround, at least on my machine, is to add GRUB_DEFAULT=1 to /etc/default/grub * package version(s) - grub 2:2.06-2 - booster 0.7-1 Steps to reproduce: sudo grub-mkconfig -o /boot/grub/grub.cfg |
This task depends upon
Closed by Toolybird (Toolybird)
Sunday, 11 June 2023, 03:50 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments from PM.
Sunday, 11 June 2023, 03:50 GMT
Reason for closing: Not a bug
Additional comments about closing: See comments from PM.
Arch includes a patch that also looks for `booster-*.img` initrd images to make the "booster" entries. This doesn't alter the above functionality from upstream. I think the expectation is that users will have both mkinitcpio and booster installed side by side and can change `GRUB_DEFAULT=` as you did to select a default.
If you want a single entry using the booster initrd then you can `booster-linux-zen.img` to `initrd-linux-zen.img`.
/boot/grub/
/boot/amd-ucode.img
/boot/booster-linux-zen.img
/boot/vmlinuz-linux-zen
Additional entries are generated for alternative initrd images.
So not generating the first entry may break other setups...