Surface Pro 4 on 7977
-
What is displayed when you use a web browser and go to http://x.x.x.x/fog/service/ipxe/boot.php?mac=58:82:a8:8b:1d:d1
Seems like the kernel isn’t taking over as it should - for whatever reason - because it hangs right at bzImage … ok and init.xz … ok.
-
Just out of curiosity, when the system appears to freeze, can you wait about 60 seconds (or 120 seconds) and see if you can ping the device at the address shown on the iPXE boot screen? We had recently another system that appeared to freeze at this point. It was actually running but it wasn’t displaying anything on the console. So you could issue a deploy command to the system it would work 100% except display anything on the console. Can you see if this is a similar issue?
-
The problem is the ipxe binaries. Give me a few minutes I’ll put the working binaries back in.
-
Should be fixed in latest.
-
@Tom-Elliott Have you talked to the iPXE devs about this yet? We heavily depend on iPXE working properly and I think that they should be told if they break things.
-
@Sebastian-Roth I have not because I have not had enough time, lately, to run git bisect to figure out where/when the issue was introduced.
-
@Tom-Elliott Sorry I didn’t get back to you earlier, I had to switch the bootfile back to undionly.kpxe because we needed to image a bunch of non UEFI machines the rest of the day. On Monday I will give it another try. Thanks to everyone else for the suggestions.
-
@fry_p slightly off topic. But if your dhcp server is 2012 server there is an option to configure it to support both uefi and bios pxe booting.
-
@george1421 said in Surface Pro 4 on 7977:
@fry_p slightly off topic. But if your dhcp server is 2012 server there is an option to configure it to support both uefi and bios pxe booting.
I did see that in another thread. I am planning on implementing that, but I haven’t had any time to sit down and do it. Plus, right now, we have a grand total of roughly 25 UEFI devices compared to the thousand plus BIOS devices. It doesn’t need to be changed often (at least not yet). We are moving administrators to Surface Pro 4’s gradually so this will become a necessity. Thanks for the heads up.
-
@fry_p Once DHCP is configured, you will never have to change it. It takes 10 minutes to setup, every step is laid out for you in here:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
-
@Wayne-Workman said in Surface Pro 4 on 7977:
@fry_p Once DHCP is configured, you will never have to change it. It takes 10 minutes to setup, every step is laid out for you in here:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
I was able to set this up this morning. Works perfectly. The only thing is we have many scopes in the building I set up Surfaces at, so I set the policy at server level. Thanks for the tip!