Avi Deitcher
Avi Deitcher
I'm more than happy to test my theory that the EFI vars are not set correctly when chain loading. I'm just at a loss as to how to do that....
@Starrry yup, exactly that. My contention is that this may not be just a grub issue, but rather a question of what it reads from. Meaning either iPXE misses setting...
It gets the IP address correctly and knows the protocol was tftp, so it must have found something. Do you know how to read that? I know conceptually is is...
> You keep writing "vars" there is no such thing. Fair enough. > See the EFI image device path, examples https://github.com/ipxe/ipxe/issues/1316 Yes! That example is solid. ``` EFI image device...
> heads up, if you mention iPXE to grub folks, they will just say, "use grub for everything" Heh, I am trying really hard not to get in the middle...
If I hadn't said it before, thanks for helping @NiKiZe 😄
I tried to follow your suggestion in the linked issue. I built `snponly.efi` with debug enabled (I probably could have done the same with `ipxe.efi`, but might as well stick...
Sure, I will hit that right away.
Pretty much the same thing: ``` Filename: ipxe.efi tftp://192.168.1.2/ipxe.efi... ok ipxe.efi : 1008704 bytes [EFI] EFI handle 0x7e4ca518 systab 0x7f9ec018 EFI does not provide protocol ConsoleControl EFI protocol ef9fc172-a1b2-4693-b327-6d32fc416042 is...
Nah that's from ipxe.efi. It only appears when I compiled it with the DEBUG= options, and you can see it loading from the first lines I included. The lines from...