Re: hd-media efi grub

2026-03-10 Thread Carl Karsten
On Tue, Mar 10, 2026 at 6:45 PM Steve McIntyre  wrote:

> On Tue, Mar 10, 2026 at 01:23:28PM -0500, Carl Karsten wrote:
> >my guess is I needed:
> >\EFI\boot\bootx64.efi
> >qemu... no change
> >
> >just to be sure, I put it everwhere:
> >
> >$ find /tmp/mk_hd_grub/img -iname *.efi
> >/tmp/mk_hd_grub/img/bootnetx64.efi
> >/tmp/mk_hd_grub/img/boot/grub/grubx64.efi
> >/tmp/mk_hd_grub/img/boot/grub/bootx64.efi
> >/tmp/mk_hd_grub/img/boot/grubx64.efi
> >/tmp/mk_hd_grub/img/boot/bootx64.efi
> >/tmp/mk_hd_grub/img/EFI/BOOT/grubx64.efi
> >/tmp/mk_hd_grub/img/EFI/BOOT/bootx64.efi
> >/tmp/mk_hd_grub/img/EFI/grubx64.efi
> >/tmp/mk_hd_grub/img/EFI/bootx64.efi
> >/tmp/mk_hd_grub/img/grubx64.efi
> >/tmp/mk_hd_grub/img/bootx64.efi
>
> What partition layout and filesystem type do you have there? UEFI
> wants the EFI system partition to be FAT, and ideally tagged as type
> EF on an MBR scheme or EF00 on GPT.
>
>
I would expect efi-image and   gen-hd-image is doing the right thing:

https://salsa.debian.org/carlfk-guest/debian-installer/-/blob/hd-grub/build/util/mk_hd_grub.sh#L39-47

sfdisk --dump ${img_name}
label: dos

label-id: 0x69b05fcf
device: /tmp/mk_hd_grub/hd-grub.img

unit: sectors

sector-size: 512
  /tmp/mk_hd_grub/hd-grub.img1 : start=2048, size=  157952,
type=c, bootable



> >I need  modules to boot the installer
> >grubnetx64-installer.efi.signed has installer in the name, but I'm
> guessing
> >that isn't my problem, yet.
>
> Yeah, see when you get a bit further. :-)
>
> --
> Steve McIntyre, Cambridge, UK.
> [email protected]
> You raise the blade, you make the change... You re-arrange me 'til I'm
> sane...
>
>

-- 
Carl K


Re: hd-media efi grub

2026-03-10 Thread Steve McIntyre
On Tue, Mar 10, 2026 at 01:23:28PM -0500, Carl Karsten wrote:
>my guess is I needed: 
>\EFI\boot\bootx64.efi
>qemu... no change 
>
>just to be sure, I put it everwhere: 
>
>$ find /tmp/mk_hd_grub/img -iname *.efi
>/tmp/mk_hd_grub/img/bootnetx64.efi
>/tmp/mk_hd_grub/img/boot/grub/grubx64.efi
>/tmp/mk_hd_grub/img/boot/grub/bootx64.efi
>/tmp/mk_hd_grub/img/boot/grubx64.efi
>/tmp/mk_hd_grub/img/boot/bootx64.efi
>/tmp/mk_hd_grub/img/EFI/BOOT/grubx64.efi
>/tmp/mk_hd_grub/img/EFI/BOOT/bootx64.efi
>/tmp/mk_hd_grub/img/EFI/grubx64.efi
>/tmp/mk_hd_grub/img/EFI/bootx64.efi
>/tmp/mk_hd_grub/img/grubx64.efi
>/tmp/mk_hd_grub/img/bootx64.efi

What partition layout and filesystem type do you have there? UEFI
wants the EFI system partition to be FAT, and ideally tagged as type
EF on an MBR scheme or EF00 on GPT.

>I need  modules to boot the installer 
>grubnetx64-installer.efi.signed has installer in the name, but I'm guessing
>that isn't my problem, yet.

Yeah, see when you get a bit further. :-)

-- 
Steve McIntyre, Cambridge, [email protected]
You raise the blade, you make the change... You re-arrange me 'til I'm sane...



Re: hd-media efi grub

2026-03-10 Thread Carl Karsten
my guess is I needed:
\EFI\boot\bootx64.efi
qemu... no change

just to be sure, I put it everwhere:

$ find /tmp/mk_hd_grub/img -iname *.efi
/tmp/mk_hd_grub/img/bootnetx64.efi
/tmp/mk_hd_grub/img/boot/grub/grubx64.efi
/tmp/mk_hd_grub/img/boot/grub/bootx64.efi
/tmp/mk_hd_grub/img/boot/grubx64.efi
/tmp/mk_hd_grub/img/boot/bootx64.efi
/tmp/mk_hd_grub/img/EFI/BOOT/grubx64.efi
/tmp/mk_hd_grub/img/EFI/BOOT/bootx64.efi
/tmp/mk_hd_grub/img/EFI/grubx64.efi
/tmp/mk_hd_grub/img/EFI/bootx64.efi
/tmp/mk_hd_grub/img/grubx64.efi
/tmp/mk_hd_grub/img/bootx64.efi


I need  modules to boot the installer
grubnetx64-installer.efi.signed has installer in the name, but I'm guessing
that isn't my problem, yet.


On Tue, Mar 10, 2026 at 7:07 AM Steve McIntyre  wrote:

> Hi Carl!
>
> On Mon, Mar 09, 2026 at 12:21:40PM -0500, Carl Karsten wrote:
> >I am trying to replace syslinux with grub to support efi on hd-media
> >some background:
> >
> https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/7#
> >note_75072
> >
> >In poking around, I got lost. I suspect I need help with grub.conf, where
> to
> >put it and what goes in it.
> >
> >I wrote a script that builds an image, but doesn't ... boot grub I think?
> >
> >I see gen-hd-image and efi-image  which seems like things I should use.
> >
> >Here is my failing attempt
> >
> https://salsa.debian.org/carlfk-guest/debian-installer/-/blob/hd-grub/build/
> >util/mk_hd_grub.sh
> >
> >I test with qemu -bios OVMF.fd
> >I end up at an efi shell
> >
> >UEFI Interactive Shell v2.2
> >EDK II
> >UEFI v2.70 (Debian distribution of EDK II, 0x0001)
> >Mapping table
> >  FS0: Alias(s):HD1a0b:;BLK2:
> >  PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(1,MBR,0x69AD6B31)
> > BLK0: Alias(s):
> >  PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
> > BLK1: Alias(s):
> >  PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)
> >Press ESC in 4 seconds to skip startup.nsh or any other key to continue.
> >Shell>
>
> If you're seeing this, then you don't have a bootloader in the
> removable media path [1]. You're not even getting as far as loading
> grub here. You'll need to copy one of the grub binaries from
> grub-efi-$ARCH-signed into place. There's a selection of different
> grub binaries in that package to choose from, depending on what
> modules you want included.
>
> [1] https://wiki.debian.org/UEFI#Booting_from_removable_media
>
> --
> Steve McIntyre, Cambridge, UK.
> [email protected]
> Into the distance, a ribbon of black
> Stretched to the point of no turning back
>
>

-- 
Carl K


Re: hd-media efi grub

2026-03-10 Thread Steve McIntyre
Hi Carl!

On Mon, Mar 09, 2026 at 12:21:40PM -0500, Carl Karsten wrote:
>I am trying to replace syslinux with grub to support efi on hd-media
>some background:
>https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/7#
>note_75072
>
>In poking around, I got lost. I suspect I need help with grub.conf, where to
>put it and what goes in it.
>
>I wrote a script that builds an image, but doesn't ... boot grub I think?
>
>I see gen-hd-image and efi-image  which seems like things I should use.  
>
>Here is my failing attempt 
>https://salsa.debian.org/carlfk-guest/debian-installer/-/blob/hd-grub/build/
>util/mk_hd_grub.sh
>
>I test with qemu -bios OVMF.fd
>I end up at an efi shell
>
>UEFI Interactive Shell v2.2
>EDK II
>UEFI v2.70 (Debian distribution of EDK II, 0x0001)
>Mapping table
>      FS0: Alias(s):HD1a0b:;BLK2:
>          PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(1,MBR,0x69AD6B31)
>     BLK0: Alias(s):
>          PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
>     BLK1: Alias(s):
>          PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)
>Press ESC in 4 seconds to skip startup.nsh or any other key to continue.
>Shell>

If you're seeing this, then you don't have a bootloader in the
removable media path [1]. You're not even getting as far as loading
grub here. You'll need to copy one of the grub binaries from
grub-efi-$ARCH-signed into place. There's a selection of different
grub binaries in that package to choose from, depending on what
modules you want included.

[1] https://wiki.debian.org/UEFI#Booting_from_removable_media

-- 
Steve McIntyre, Cambridge, [email protected]
Into the distance, a ribbon of black
Stretched to the point of no turning back



hd-media efi grub

2026-03-09 Thread Carl Karsten
I am trying to replace syslinux with grub to support efi on hd-media
some background:
https://salsa.debian.org/installer-team/debian-installer/-/merge_requests/7#note_75072

In poking around, I got lost. I suspect I need help with grub.conf, where
to put it and what goes in it.

I wrote a script that builds an image, but doesn't ... boot grub I think?

I see gen-hd-image and efi-image  which seems like things I should use.

Here is my failing attempt
https://salsa.debian.org/carlfk-guest/debian-installer/-/blob/hd-grub/build/util/mk_hd_grub.sh

I test with qemu -bios OVMF.fd
I end up at an efi shell

UEFI Interactive Shell v2.2
EDK II
UEFI v2.70 (Debian distribution of EDK II, 0x0001)
Mapping table
  FS0: Alias(s):HD1a0b:;BLK2:
  PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)/HD(1,MBR,0x69AD6B31)
 BLK0: Alias(s):
  PciRoot(0x0)/Pci(0x1,0x1)/Ata(0x0)
 BLK1: Alias(s):
  PciRoot(0x0)/Pci(0x1,0x2)/USB(0x0,0x0)
Press ESC in 4 seconds to skip startup.nsh or any other key to continue.
Shell>

to demo the test is somewhat valid, I can  boot linux if I drop in a bunch
of syslinx stuff by flipping false to true, then qemu:
Loading linux... ok
Loading initrd.gz...ok

so how do I do that but with grub?


-- 
Carl K