Lenovo Yoga L13 booting to fog
-
Will you take a clear screen shot of the error? The context of the error is almost as important as the error message itself. The “NBP is too big to fit…” message should come from the UEFI rom, you should not get even close to picking full host inventory.
Basically the error message tells me you are sending the wrong iPXE boot loader to the target computer “NBP” should signify the target computer is in uefi mode so you should be sending ipxe.efi to the target computer.
-
-
@John-L-Clark Ok that screen shot seems to indicate the laptop is in bios mode not uefi. So in this case you should be sending undionly.kpxe to the target computer.
So we can start out by:
- confirm that dhcp option 67 is indeed
undionly.kpxe - confirm that the yoga is indeed in bios/legacy mode
If both of those test out as true, then lets grab a pcap (packet capture) of the pxe boot up sequence because something is going on that is not clear. Follow this tutorial and upload the pcap to a file share site. Make sure you share the file as public read only and then either DM me the link or post it here and I’ll take a look at what is going wrong. https://forums.fogproject.org/topic/9673/when-dhcp-pxe-booting-process-goes-bad-and-you-have-no-clue
- confirm that dhcp option 67 is indeed
-
I have run the packet capture but I can not find where it puts the output. Thanks
-
It boots to the Fog menu but when you select Full host registration and inventory it gives the error in the screen shot.
-
@John-L-Clark said in Lenovo Yoga L13 booting to fog:
It boots to the Fog menu but when you select Full host registration and inventory it gives the error in the screen shot.
That’s impossible. Please take a new picture of the error and port here!
-
@John-L-Clark said in Lenovo Yoga L13 booting to fog:
It boots to the Fog menu but when you select Full host registration and inventory it gives the error in the screen shot.
The screen shot you provided happens before the iPXE menu. Unless its the case when you pick full registration from the iPXE menu the system just reboots. Then that screen would appear.
As far as the pcap it will create the pcap in the directory where you ran the tcpdump command.
-
@george1421 I have the file now. Do I just upload it here? Thank you for your help.
-
@John-L-Clark you can upload it here, just put .txt on the end since I don’t think the forum supports .pcap files.
-
-
@george1421 I looked at with Wireshark but had no idea what I was looking for.
-
@John-L-Clark I’m only seeing the tftp transfer. Is the target computer on the same subnet as the fog server? I would expect to see dhcp packets from the target computer or inform packets from other computers on the same subnet.
In this case I want to see the dhcp packets to what the client is announcing itself as as well as what the dhcp server is telling the client to do.
-
@george1421 The client is on a separate subnet than the server. I will run it again and see if anything is different.
-
@John-L-Clark ok to collect those logs we’ll need to install wireshark on a witness computer (i.e. a second computer on the same subnet) and grab a pcap that way.
Use the capture filter of
port 67 or port 68to only grab the bootp stuff. -
Is this what you need? Thanks
-
@John-L-Clark This doesn’t appear to be a wireshark pcap file, but a text file with pcap data. How did you collect this?
-
@george1421 So now it is booting to the fog menu and I select full host registration and it reboots and goes to
-
@george1421 I used wireshard but saved it as a text file. I have the pcap also. I renamed it and added it.capture.pcapng.txt
-
@John-L-Clark OK I have it lets switch over to chat for quicker turnaround. Look at the chat bubble at the top of the forum panel
-
