Hi, this is an old syslinux menu entry I try to convert to a grub.cfg menu entry. $ grep "X .Moon" /boot/syslinux/syslinux.cfg -B1 -A3 LABEL Moonstudio MENU LABEL Ubuntu X ^Moon Studio lowlatency LINUX /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency APPEND root=LABEL=moonstudio ro INITRD /.boot/ubuntu_moonstudio/boot/initrd.img-lowlatency I don't understand a few things provided by https://wiki.archlinux.org/title/GRUB#Boot_menu_entry_examples . The syslinux bootloader, syslinux.cfg and the path /.boot/ubuntu_moonstudio/boot/ are on a MBR partition with the label "s3.archlinux", the directories of the other Linux install's root directory are on a partition with the label "moonstudio". The new grub2 and grub.cfg are on a GPT partition with the label "m1.xubu20.04", but this shouldn't matter. IIUC the grub.cfg entry should read menuentry "Ubuntu X Moon Studio lowlatency" { search --no-floppy --set=root --label s3.archlinux linux /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency root=LABEL=moonstudio ro initrd /.boot/ubuntu_moonstudio/boot/initrd.img-lowlatency } OTOH I've got some doubts, should it be vice versa search --no-floppy --set=root --label moonstudio linux /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency root=LABEL=s3.archlinux ro should it read root=LABEL or root=label or else? The fstab of the "Ubuntu X Moon Studio lowlatency" install contains a line to bind mount boot: /mnt/archlinux/.boot/ubuntu_moonstudio/boot /boot none bind 0 0 Regards, Ralf
On Mon, 2023-04-10 at 10:11 +0200, Ralf Mardorf wrote:
should it read root=LABEL or root=label or else?
Replying to myself root=/dev/disk/by-label/FOO ro
On Mon, 2023-04-10 at 10:11 +0200, Ralf Mardorf wrote:
IIUC the grub.cfg entry should read
menuentry "Ubuntu X Moon Studio lowlatency" { search --no-floppy --set=root --label s3.archlinux linux /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency root=LABEL=moonstudio ro initrd /.boot/ubuntu_moonstudio/boot/initrd.img-lowlatency } OTOH I've got some doubts, should it be vice versa
search --no-floppy --set=root --label moonstudio linux /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency root=LABEL=s3.archlinux ro
"set root=(hdX,Y) sets the boot partition, where the kernel and GRUB modules are stored (boot need not be a separate partition, and may simply be a directory under the "root" partition (/)" - https://wiki.archlinux.org/title/GRUB#Custom_grub.cfg Ok, IIUC usually it's the partition that holds /boot (not necessarily /boot/grub/, too). So IIUC it should read menuentry "Ubuntu X Moon Studio lowlatency" { search --no-floppy --set=root --label s3.archlinux linux /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency root=/dev/disk/by-label/moonstudio ro initrd /.boot/ubuntu_moonstudio/boot/initrd.img-lowlatency } Usually I would simply test it, but due to issues with new hardware "just testing" is tricky.
Hi, I made 4 Test entries and the first entry already worked without an issue: $ grep 1..Test /mnt/m1.xubu20.04/boot/grub/grub.cfg -A4 menuentry "Ubuntu X Moon Studio lowlatency, ro 1. Test root=/dev/disk/by-label/" { search --no-floppy --set=root --label s3.archlinux linux /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency root=/dev/disk/by-label/moonstudio230406 ro initrd /.boot/ubuntu_moonstudio/boot/initrd.img-lowlatency } I'm surprised since on Arch Linux I can only boot the kernels v6+. Startup hangs when I try to boot the v4.19+ or 5+ kernels with the new hardware. $ pacman -Q linux{,-rt{-lts,,-cornflower,-pussytoes,-securityink}}|awk '{print $1"\t"$2}' linux 6.2.10.arch1-1 linux-rt-lts 5.15.96.61.realtime1-2 linux-rt 6.2.0.3.realtime1-3 linux-rt-cornflower 1:4.19.271_rt120-0.300 linux-rt-pussytoes 1:4.19.269_rt119-0.300 linux-rt-securityink 1:4.19.265_rt117-0.300 The Ubuntu kernel I booted is way older $ /bin/ls -l /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency lrwxrwxrwx 1 root root 28 Apr 21 2021 /.boot/ubuntu_moonstudio/boot/vmlinuz-lowlatency -> vmlinuz-4.4.0-210-lowlatency However, this doesn't matter now. Regards, Ralf
participants (1)
-
Ralf Mardorf