Can't do PXE-boot on HP Probook 645 (Fog 1.2.0)
-
I forgot til mention that the HP Probook 645 have Ethernet LAN HW and Vendor-ID: 10EC:8168
This is, as i can see, a RealTek RTL8110SC(L) (RTL8110S/RTL8110SB(L)/RTL8169SB(L)/RTL8169S(L)/RTL8169) NIC.The problem is that this BIOS show GUI-screen and i can’t see any BIOS error-code that must appear. It do receive IP-address from dhcp, so it do commmunicate with the Fog-server.
-
I’m only guessing here, as I own an HP Probook 645 G1 and haven’t seen this issue, are you trying to boot with UEFI enabled?
-
I new test with HP Probook 6475b send PXE in infinty loop.
Status:
- HP Probook 6460b -> Ok
- HP Probook 6475b -> iPXE infinity loop
- HP Probook 645 Legacy boot -> iPXE infinity loop
-
[quote=“Tom Elliott, post: 34607, member: 7271”]I’m only guessing here, as I own an HP Probook 645 G1 and haven’t seen this issue, are you trying to boot with UEFI enabled?[/quote]
Yes! UEFI Native (Without CSM)
-
This is likely the issue you’re having. Right now, you need to boot the NIC’s in legacy mode.
-
[quote=“Tom Elliott, post: 34610, member: 7271”]This is likely the issue you’re having. Right now, you need to boot the NIC’s in legacy mode.[/quote]
I change it to “Legacy boot” and now i can see PXE-message. It goes into infinity loop like the 6475b.
I’ve read something about “Infinity loop” and i need to do some change in dhcp-config.
Do you know something about this? -
I’m aware of the ipxe infinity loop. Which undionly file are you using? Did you build your own?
-
[quote=“Tom Elliott, post: 34612, member: 7271”]I’m aware of the ipxe infinity loop. Which undionly file are you using? Did you build your own?[/quote]
I use the default; “undionly.kpxe”
I don’t know the difference between all the boot-files and i don’t know how to build my own
-
Hi Ronny,
i am not sure but try to check if it supports legacy and uefi boot sources.
If possible switch of uefi boot sources and use legacy onesThis is from my HP ProBook 6450b:
[IMG]http://i.imgur.com/ToPV6SL.jpg[/IMG]
Regards X23
-
Hi!
I’ve switched off UEFI, but now it goes into “iPXE infinity loop”.
The question is; How do i fix Infinity loop?RS
[quote=“x23piracy, post: 34633, member: 3982”]Hi Ronny,
i am not sure but try to check if it supports legacy and uefi boot sources.
If possible switch of uefi boot sources and use legacy onesThis is from my HP ProBook 6450b:
[IMG]http://i.imgur.com/ToPV6SL.jpg[/IMG]
Regards X23[/quote]
-
it’s hard to know what the problem is based on “iPXE infinity loop”
do you see the menu? -
No! It re-run initializing iPXE before the Fog-menu appears.
There is no error-msg. -
have you tried using any of the alternative ipxe boot file? like undionly.kkpxe ?
-
Yes i guess i did. I change dhcpd.conf to different boot-files and restarted dhcp. I guess i was testing the different files. Hope i did it right. Same result on all boot-files. I don’t know what’s the difference between the boot-files and what to use.
Some says that with “Infinity loop”, then we need to compile a new boot-file for this PC. This i don’t know how to do.[quote=“Junkhacker, post: 34707, member: 21583”]have you tried using any of the alternative ipxe boot file? like undionly.kkpxe ?[/quote]
-
What undi files are you using? What I mean, are you copying them from other places?
Can you capture video of the system booting and looping to see if we can see a boot problem?
Does your network have STP, if so can you enable Portfast or Rapid STP? Can you disable STP to remove that as a possible issue? Can the system actually get dhcp? Does it load the ipxe stuff or bootloop before that far? From the sounds of it, the network is loading undionly.{k,kk}pxe file, but not receiving the DHCP which will cause the system to reboot. That’s why I ask the questions about Spanning Tree and if you can disable or use Rapid/Portfast.
-
Hi!
The funny thing is that we installed Fog 1.2.0 on another computer and now it do iPXE-boot without problem.
This meen that HP Probook 645 is working with the latest Fog with default boot-file(undionly.kpxe).
So the problem must be something else. (I will do some more testing and then take video/pic of boot).Now our problem is how to upload image from a Win8.1-PC and deploy it. As long PC are setup with UEFI/Secure boot and GPT-partition, it want work. We did upload "Single disk, multiple partition) from a computer with Secure boot and UEFI disabled, but with factory disk-setup (GPT). This uploaded without problem, men we couldn’t deploy it back to same computer. Get error-msg about missing system-files. I guess its impossible to imaging PC with factory setup Win8.1 and we have to clear harddrive and install everything from scratch.
Do you know an Tutorial/Guide/Wiki on how to upload image and deploy when OS is Win8.1 Pro?
RS
[quote=“Tom Elliott, post: 34732, member: 7271”]What undi files are you using? What I mean, are you copying them from other places?
Can you capture video of the system booting and looping to see if we can see a boot problem?
Does your network have STP, if so can you enable Portfast or Rapid STP? Can you disable STP to remove that as a possible issue? Can the system actually get dhcp? Does it load the ipxe stuff or bootloop before that far? From the sounds of it, the network is loading undionly.{k,kk}pxe file, but not receiving the DHCP which will cause the system to reboot. That’s why I ask the questions about Spanning Tree and if you can disable or use Rapid/Portfast.[/quote]
-
UPDATE
OK! I did now try to change boot-file til “undionly.kkpxe” and restarted dhcp. Now it did som loops, but suddenly it works.
I don’t know the different between undionly.(k)kpxe, but on this Fog-server the .kkpxe works with HP Probook 645.
On the other Fog-server(same setup) the default .kpxe works.
For now this problem seems to be solved.Thanks for helping!
-
updated Working Devices to include
[FONT=sans-serif][COLOR=#000000][SIZE=13px]HP ProBook 6450b ✓ Defualt bzImage undionly.kpxe 2014-06-13
HP Probook 645 ✓ Defualt bzImage undionly.kkpxe 2014-06-13 Disable UEFI-Bootdodus in BIOS. undionly.kkpxe is not a typo you need to use this file to boot properly.[/SIZE][/COLOR][/FONT]
