migration from grub legacy to grub2 [solved]

[DaggyStyle]

Greetings,

I'm in the process of migrating my system from grub legacy to grub2.
in grub legacy I had a script doing this after the kernel was compiled:

1. make ${JOBS} modules_install
   
2. mount /boot/
   
3. cp arch/x86/boot/bzImage /boot/kernel64-${FULL_NEW_KERNEL_VERSION}.img
   
4. OLD_KERNEL="$(sed -n "${GRUB_CFG_ENTRY_LINE_START}p" /boot/grub/grub.conf | awk '{print $4}')"
   
5. NEW_ENTRY="$(cat /boot/grub/grub.conf | sed -n "${GRUB_CFG_ENTRY_LINE_START},$((${GRUB_CFG_ENTRY_LINE_START}+${GRUB_CFG_ENTRY_LENGTH}))p" | sed ':a;N;$!ba;s/\n/\\n/g' | sed "s/${OLD_KERNEL}/${FULL_NEW_KERNEL_VERSION}/g")"
   
6. sed -i \"${GRUB_CFG_ENTRY_LINE_START} i ${NEW_ENTRY}\" /boot/grub/grub.conf
   
7. n -sf /boot/kernel64-${FULL_NEW_KERNEL_VERSION}.img /boot/kernel64-rescue.img
   

this resulted in a bootable image with custom initrd. with grub2 I need to use grub-mkconfig -o /boot/grub/grub.cfg, my problem is getting the above to work.
I assume I cannot use the cp method and I'd should use the make install, if that so, how can I instruct grub2 to use my initrd?

Thanks.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein

[Tony0945]

[DaggyStyle]

[DaggyStyle]

looks like this: https://wiki.gentoo.org/wiki/EFI_stub_kernel#Optional:_Initramfs is my answer, but how does grub2 enters here I'm not sure

EDIT:
this https://wiki.gentoo.org/wiki/Custom_Initramfs#Using_GRUB looks like what actually need, but what should I select? what are the gains in efi stub or grub.
afaicu, efi stub doesn't needs grub as efi bootmgr does all the work.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein

[Phoenix591]

Correct, with efistub no boot loader is needed, just the BIOS (efi firmware) executing the kernel. The arguments and initrd set by either compiling in the kernel itself a default command line (under processor type and features->, built in kernel command line, something like root=LABEL=Gentoo dobtrfs initrd=\intel-uc.img initrd=\initrd-current do note efi path notations use \ rather than / ), or when creating the boot entry with efibootmgr (anything in quotes after the -u or --unicode is passed to the kernel), and letting the BIOS (efi firmware) handle displaying any alternative boot options (ie press f12 to display the menu).


https://wiki.gentoo.org/wiki/GRUB2 and https://wiki.gentoo.org/wiki/GRUB2_Migration are the two most relevant grub 2 articles for getting started and migrating to grub 2 if you havn't found it yet (no experience with it personally)

Imo, it comes down to taste, if you need/want many boot choices, and if your efi firmware is quirky or not: Some efi firmware can have strange bugs and other quirks, my own, for instance, ignores the efi system partition on my second hard drive, and can natively read ntfs partitions ( that was handy for creating and using windows 10 installation usb stick), others refuse to acknowledge efi executables other than the default ( efi partition/EFI/BOOT/BOOTX64.EFI ). If you're satisfied with the visual appearance of your efi firmware's boot menu and can work within any quirks of your own board's efi firmware, you can go bare bones with efistub. If not, Grub (2), rEFInd, both provide the traditional boot loader experience with theme-able menus etc ( with systemd-boot providing a more bare bones menu option)

[DaggyStyle]

thought so, I've went the grub2 path, now I only need to get it to boot.

Thanks.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein