PXE Boot Error (NO DHCP Repsonse) - Realtek Driver - HP ProBook G3
-
Server
- FOG Version: 1.30 RC-11
- OS: CentOS 7
Client
- Service Version: N/A
- OS: Windows 7 Professional
Description
I am working on getting our new G3 HP Laptops inventoried. We are currently using the undionly.kpxe file for our DHCP Server. The G3 will get to the fog menu and let me select “Full Inventory”. However after that, I get a “No DHCP Response on interface eth0”. I read that switching to ipxe.kpxe is more compatible than undionly.kpxe. Anyone experience this or have a reccomended file to be using for the DHCP Boot? Thank you!!
-
@noelpd This is only a shot in the dark, but does the switch where this computer is connected, have spanning tree enabled? If so are you using one of the fast spanning tree protocols (fast stp, port fast, RSTP, etc)?
A test would be to put a dumb (unmanaged) switch between the building switch and the target computer then try to pxe boot again.
Logic: Basic spanning tree take 27 seconds before it starts to forward data after a link transition. You will get one link transition when the iPXE menu starts and one when the FOS Engine (the customized linux OS that captures, deploys, and registers target computers) starts up. So if spanning tree is enabled and one of the fast protocols are not used, I can understand this error.
-
I was thinking exactly what George went into. Follow his advice, he’s on the right track. We’ve seen this sort of thing several times before.
-
We are using brocade switches… in the show run configuration screen, it appears that spanning tree is disabled. We changed the DHCP File, and the G3 will boot to a PXE command line interface and not the fog menu. Older devices wont boot at all now. We reverted back to undionly.kpxe for DHCP until we get this one device figured out.
-
@noelpd Wait, I think I missed something. Is this client in bios (legacy) mode or uefi? What did you change the iPXE boot kernel to?
-
@george1421 I believe it is in Legacy mode, but I am not 100% sure how to confirm that.
-
@noelpd Go into the bios/firm where there should be a switch setting to change between legacy and uefi mode.
-
@george1421 But in your initial post you said you were able to get into the iPXE menu and select full inventory. That means if you were that far you have the right dhcp boot file (undionly.kpxe). So if this booted on the G3 then you are in legacy (bios) mode. The uefi boot kernel would not have got you anywhere. The issue is then with the FOS Engine or something else.
You said this is a HP G3 but what model number.
-
@george1421 New ones we just got in. ProBook 470 G3, looks like its using a Realtek NIC
-
@noelpd These are new like just from china new?
If that is the case the FOS Engine may not have the proper driver for it. I do see the ProBook 470 G2 are supported but no mention of the G3.
OK here is what I need you to do. I need you to manually register this computer and then schedule a capture or deploy it doesn’t matter because when you create the task, make sure you select the debug capture/deploy option. Then PXE boot this new G3.
It should take you right to what ever mode you selected, but don’t worry its not going to do anything. After a few pages where you have to hit enter you will be dropped to a linux command prompt. This is the shell of the FOS Engine.
Now we need to see what the FOS Engine sees for hardware. I need you to key in
lspci -nnThis should give you a list of built in hardware, you need to look through the list for the ethernet adapter. On that line, there will be a hex code like (8086:3D12) [that was made up]. We need to know that code. The @developers will need to see if that driver is included in the FOS kernel. -
This is the firmware.
Change the bootfile to ipxe.pxe and all should start working for those devices.
-
@Tom-Elliott We did that and it boots to a iPXE command line interface, still not working with that change.
-
@Tom-Elliott and also by changing it to ipxe.pxe it tanks our other computers and they won’t boot to FOG. Mostly the HP ProBook 6470 G1 and 640 G2 laptops.
-
@noelpd Just to be sure I didn’t loose my place here.
The original post was that when you select full inventory from the iPXE menu you get an error message in the FOS boot about no dhcp response on interface eth0? If this is the case they your iPXE boot file is correct with undionly.kpxe, IMO the issue is a FOS driver one. We’ve kind of ruled out a spanning tree issue (typically what we see here).
We will need the vendor and device code that I mentioned before.
-
@george1421 Ok, i am looking at the list now via the lspci command, however there are about 14 lines represented by the 8086, i dont see anything in relation to the mac address. Anyway to identify which one is the correct one I should be giving you?
-
@noelpd Remember I said that number starting with 8086 was made up. Actually the vendor code 8086 is for intel, so I hope you would not find it there.
try this one if there is a lot of lines
lspci -nn | grep rnet -
This post is deleted! -
@george1421 Ok pretty sure I found the line that you need…
02:00.0 “0200” “10ec” “8168” -r15 “103c” “8102”
I figured this was the right one because I ran lspci by itself and the realtek NIC was identified by the 02:00.0
-
@noelpd OK maybe the
lspce -nndoesn’t return what I expected in FOS. In centos 7 it returned something like this:0b:00.0 Ethernet controller [0200]: VMware VMXNET3 Ethernet Controller [15ad:07b0] (rev 01)Try it with only one
-n -
@george1421 That was my bad, I was not doing nn
nn seems to work. I got the following result
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
