Posts made by noelpd

@Tom-Elliott Just the undionly.kpxe not .kkpxe

@george1421 I confirmed with the hardware that the NIC being used is the RealTek 8168. Found this article from couple years ago with the exact same issue, tried what fixed that problem but still no go on my end.

https://forums.fogproject.org/topic/4173/realtek-8168-nic-issue-with-pxe-bootmenu

@george1421 I changed it to realtek.kpxe and had no success.

But changing it to realtek.kpxe would effect all machines and then break others wouldn’t it? Yes, it was a completely non managed HP “Dumb” or Mini Switch. And yes, the BIOS is in legacy mode.

Hey Everyone,

I am having a problem currently with running CentOS 7 with latest stable build of FOG (1.3.5). Our HP 210 Netbooks that are using the RealTek NIC are not PXE Booting Properly (See Attached Picture Below). I have tried several different hardware with no issues PXE Booting as well as trying a Mini Switch for the HP between the real network switch and computer to rule out an issue with Spanning Tree.

My recent last ditch effort was to build an updated custom Kernel. I tried that with making sure that the RealTek NIC option in the build is supported and it still is not working. This also Kernel Panicked the other hardware types that we used, so I reverted back to the original Kernel. Any help would be greatly appreciated. Thank you.

How do I do that?

Server

• FOG Version: 1.30 RC-20
• OS: Centos 7

Client

• Service Version:
• OS: Windows 7

Description

I am trying to update to the latest RC Version. When running the git pull command for latest verison, I get the following error…

“SSL Received a record that exceeded the maximum permissible length”

Thank you guys for all the hard work on getting things updated where needed. Just out of curiosity, is there anything closer to final steps of an actual final version? Thank you.

@Tom-Elliott With the HP 470 G3 I can get to the FOG Menu itself, but after the menu when I go to inventory the machine I get the mentioned error messages.

@Tom-Elliott We made the change on the DHCP to ipxe.pxe and updated to RC-13 with ipxe.pxe in the .fogsettings file. Still no go. Any ideas? Is there another file location on the server that needs to be changed to ipxe.pxe to make it work?

@Tom-Elliott Looks like we tried ipxe.kpxe and not ipxe.pxe

@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)

@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

@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?

@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.

@Tom-Elliott We did that and it boots to a iPXE command line interface, still not working with that change.

@george1421 New ones we just got in. ProBook 470 G3, looks like its using a Realtek NIC

@george1421 I believe it is in Legacy mode, but I am not 100% sure how to confirm that.

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.