[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: iPXE efi chainloading grub2 pxe efi file

From: Rivard, Matthew T
Subject: RE: iPXE efi chainloading grub2 pxe efi file
Date: Fri, 18 Sep 2015 19:59:00 +0000

Thanks, its loading the menu now, however, I appear to be hitting the same 
problem I was going from grub to ipxe.  The adapters are there, but won't 
autoconfigure, and if I try to manually set an IP address, I see the debugging 
data start spewing from ipxe (which appears to be still running underneath 
grub) before the system eventually halts.  

I'll try your rollback, but was it mean to come out in the email as a long hash 

-----Original Message-----
From: Andrei Borzenkov [mailto:address@hidden 
Sent: Thursday, September 17, 2015 8:52 PM
To: Rivard, Matthew T; address@hidden
Subject: Re: iPXE efi chainloading grub2 pxe efi file

18.09.2015 03:05, Rivard, Matthew T пишет:
> I've got a good working EFI Grub2 efi Bootloader that works fine when its 
> directly handed off to by the DHCP for PXE, however, if I attempt to 
> chainload it from iPXE snponly.efi, it goes straight to the grub command 
> prompt.
> I've tried embedding the grub.cfg file via -c on the grub-mkimage command, 
> but it spews out the grub file as a stream of "command not found prompts" and 
> then still goes to the grub command line.

Embedded config is processed very early, before normal.mod is loaded, so only 
commands available at rescue prompts are present.

> If I try embedding all of the modules directly into grub.efi during mkimage, 
> along with the config file, it then throws a grub_divmod64_full not found 
> error.

Embedding all modules in grub.efi is usually wrong (not all modules can be 
loaded concurrently) either.

Try creating standalone image with grub-mkstandalone. This image contains all 
grub modules in memory disk (as cpio archive) and grub is configured with 
$prefix pointing to this disk. You can also add own files, in particular put 
grub.cfg in memory disk.

> What is the ideal way to chain load my grub.efi file from iPXE so that it 
> works the same as if it was the direct handoff from the DHCP/TFTP server?
> Unfortunately, in order to allow for selecting either our EFI WDS Server or 
> our EFI Linux Server, I have to use iPXE first, as chainloading snponly.efi 
> from grub2 ends up with iPXE snp not being able to enumerate anything from 
> the PCI Bus.

Hmm ... this actually sounds like exclusive SNP open (used by both iPXE and 
GRUB) messes something up. For testing you could try to revert
49426e9fd2e562c73a4f1206f32eff9e424a1a73 (and 
f348aee7b33dd85e7da62b497a96a7319a0bf9dd which depends on it) to see if it 
makes any difference.

> Using git pulls for both that were from yesterday.
> Matt R.
> _______________________________________________
> Help-grub mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]