[ipxe-devel] I have a trouble booting iPXE from a specific laptop

Tue Dec 13 17:33:54 UTC 2016

Hi,

For reference, what is the exact model number of that Lenovo?

The http://ipxe.org/appnote/hardware_drivers list is not up to date and is
more for ease of use then anything, for current support make sure you have
a local copy of git master and run ./src/util/niclist.pl
However that is still irrelevant in this case since you are using
undionly.kpxe (which uses the UNDI PXE standard so driver support is not
relevant at all)

Actually right now there is several versions of i219 added to ipxe so you
might have better luck by running ipxe.pxe instead of undionly.kpxe.

What is the reason for you to use rom-o-matic? what kind of modifications
do you use it for?
Have you tried the official built undionly.kpxe from http://boot.ipxe.org?
If not please do so. (at least for debugging purposes)

The linked forum post says that the nic is not found - hard to know why -
but the image you posted before clearly shows that the nic is found and
dhcp configuration is attempted, so I don't think it is the same issue at
all.

Please try to chain into the officially built undionly.kpxe from
http://boot.ipxe.org then press ctrl-b when prompted and type dhcp, when it
returns to the iPXE> prompt type ifstat and post a picture of that and we
might be able to figure out what is going wrong in more details.

When this is done it is very likely that we will need to do more debugging,
for that it would be great if you have a machine where you can build ipxe
yourself.

And i still put my money on this being a issue with the Lenovo firmware :D
- and yes undionly.kpxe should work with any and all UNDI stacks provided
by BIOS based NIC ROMs if not it is very likely that they have a issue with
their BIOS.

/Christian

On Tue, Dec 13, 2016 at 2:21 PM, Esben Storgaard Nielsen <esn at solar.dk>
wrote:

> Hi Again
>
>
>
> I still have some trouble bootin iPXE from 1 type of computer.
>
> Lenovo tells me, that they can’t help because the net card isn’t on a
> compatibility list from iPXE.
>
> That’s correct, http://ipxe.org/appnote/hardware_drivers
>
>
>
> The net card used is an “Intel i219LM“
>
>
>
> I use undionly.kpxe and use the site https://rom-o-matic.eu/ for building
> my file, and here is the net card is presented on the net card list.
>
> So I think that the compatibility list isn’t updated.
>
>
>
> I can see on the FAQ forum that the problem has being reported once before.
>
> http://forum.ipxe.org/showthread.php?tid=7713&highlight=i219
>
>
>
> I can’t see where I can try the suggestion, there is no option in the
> advance section on rom-o-matic.eu
>
>
>
>
>
> Could you came with some suggestions, so I can get further with this task.
>
>
>
>
>
> Med venlig hilsen / Kind regards,
>
>
>
>
>
>
> *Esben Storgaard Nielsen *Systems Administrator, Server
>
> [image: http://emailsignature.solar.eu/General/Solar_Logo.jpg]
>
>
>
>
>
> Phone Direct +45 79300314 <+45%2079%2030%2003%2014>
> Mobile           +45 40342836 <+45%2040%2034%2028%2036>
> E-mail            esn at solar.dk
> Internet          www.solar.eu
>
>
>
> *Solar A/S*
> Industrivej Vest 43
> 6600 Vejen
> Phone  79 30 00 00
>
>
>
> *From:* Christian Nilsson [mailto:nikize at gmail.com]
> *Sent:* 25. november 2016 01:11
> *To:* Esben Storgaard Nielsen <esn at solar.dk>
> *Cc:* ipxe-devel at lists.ipxe.org
> *Subject:* Re: [ipxe-devel] I have a trouble booting iPXE from a specific
> laptop
>
>
>
> In the image it looks like you have BIOS doing PXE DHCP request, getting
> response and loading some version of ipxe.
>
> After that you should have another DHCP request but this time from iPXE,
> is this second dhcp request seen by the dhcp server?
>
>
>
> The ipxe in the image is missing the "git version id" please make sure you
> have the latest version of ipxe git master and that the git version id is
> shown when booting.
>
>
>
> One thing that might be interesting is if you press ctrl-b to get the iPXE
> shell and then type dhcp enter followed by ifstat to get some info about
> nic driver and how it looks in regards to packets received and sent and any
> possible error.
>
>
>
> You are using ipxe.pxe? have you tried undionly.kpxe instead?
>
>
>
> /Christian
>
>
>
> On Thu, Nov 24, 2016 at 11:37 AM, Esben Storgaard Nielsen <esn at solar.dk>
> wrote:
>
> Hi
>
>
>
> We using IPXE to boot our SCCM boot image, and its works very fine.
>
>
>
> But now we got at strange issue, with a new Lenovo T460P laptop.
>
>
>
> When we try booting PXE, I got a ip address, and it contact the iPXE
> server, and on the tftp log, we can see it sends the boot menu file, but
> nothing happens on the laptop.
>
> When we use the T460 there is no problems.
>
> And both computers have the same net card.
>
>
>
> Any suggestions to solve my issue?
>
>
>
> I have attached a picture of the failure computer.
>
>
>
>
>
>
>
>
>
> Med venlig hilsen / Kind regards,
>
>
>
>
>
>
> *Esben Storgaard Nielsen *Systems Administrator, Server
>
>
>
>
>
>
>
> Phone Direct +45 79300314
> Mobile           +45 40342836
> E-mail            esn at solar.dk
> Internet          www.solar.eu
>
>
>
> *Solar A/S*
> Industrivej Vest 43
> 6600 Vejen
> Phone  79 30 00 00
>
>
> <http://www.linkedin.com/company/14368?trk=tyah&trkInfo=tas%3Asolar%20A%2FS%2Cidx%3A1-1-1>
>
>
> <http://www.linkedin.com/company/14368?trk=tyah&trkInfo=tas%3Asolar%20A%2FS%2Cidx%3A1-1-1>
>
>
> <http://www.linkedin.com/company/14368?trk=tyah&trkInfo=tas%3Asolar%20A%2FS%2Cidx%3A1-1-1>
>
>
>
> <http://www.linkedin.com/company/14368?trk=tyah&trkInfo=tas%3Asolar%20A%2FS%2Cidx%3A1-1-1>
>
>
> _______________________________________________
> ipxe-devel mailing list
> *ipxe-devel at lists.ipxe.org*
> *https://lists.ipxe.org/mailman/listinfo.cgi/ipxe-devel*
> <http://www.linkedin.com/company/14368?trk=tyah&trkInfo=tas%3Asolar%20A%2FS%2Cidx%3A1-1-1>
>
>
> <http://www.linkedin.com/company/14368?trk=tyah&trkInfo=tas%3Asolar%20A%2FS%2Cidx%3A1-1-1>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ipxe.org/pipermail/ipxe-devel/attachments/20161213/76c0b392/attachment.htm>