Legacy boot HP Stream 11 *Not Working*
-
Ok. I can PXE boot all of my wired NIC devices now.
So far, i have upgraded to FOG Trunk 6541, Kernal 4.4.3, and i have replaced the ipxe.efi binary.When checking the DHCP Settings, we have Windows Server 2008 R2, Do we still have to point it to the “undionly.kkpxe or ipxe.pxe/kpxe/kkpxe” binary files as @Sebastian-Roth was saying?
Also, @drc0nc I disabled legacy boot on the streams. When i network boot it, it says Start PXE over IPv4… then it quickly flashes an ip address and some other info that i could not catch that quick. Then it boots into windows.
Thanks and sorry for the wait!
-
The screen that flashes quickly show the
Workstation’s IP, Server’s IP, NBD Filename is undionly.kpxe, NBP Filesize. Downloading NBP file… Succeed to download NBP file
I then proceeded to replace the undionly.kpxe file with the one from This Site… Still have no luck pxe booting into fog
-
@cojohnson That’s because undionly is not the file it’s going to operate with
you need to use one of the .efi labeled files. In your case I believe ipxe.efi works best for the Stream 11’s. -
@Tom-Elliott I have already replaced the ipxe.efi file in the /tftpboot directory… any other suggestions?
-
@cojohnson YOu may have replaced but your dhcp server is not handing it out.
-
This post is deleted! -
It is working now thanks for everyones help!!!
However, now when i am booting another device that was working before the change, I get an error that says “NBP is too big to fit in free base memory” is there any way around this?
Thanks Again!!
-
-
@cojohnson Just a minute here, it works but it doesn’t?
OK, lets get a little clarity here. Are you trying to boot a device in bios mode and then a second device in efi mode? The ipxe boot files are different for these two devices.
-
@george1421 Yeah, i suppose so!! I was booting my HP Stream 11 off of the usb to ethernet adapter. At the same time i am network booting a HP 4530s from its internal Network Card.
-
@Sebastian-Roth Thanks. It just so happens that our school is running Windows Server 2008 R2. So… These steps are not going to work according to the document…???
I will go in and fiddle with it for a minute. Just to see.
-
@cojohnson If you are running the older dhcp server then you MUST do dhcp reservations for one or the other group of computers. I would setup the normal dhcp option 67 for the majority of your clinets, then setup a dhcp reservation with the changed option 67 for the exceptions to the rule. You may be able to overcome this issue with dnsmasq, by letting the fog server supply the option 66 and 67 settings instead of going through the reservation route. If you only have one or two of the efi devices then dhcp reservation is the easiest route.
HINT: The best choice is to upgrade your main dhcp server so you can take advantage of the new functionality.
-
@cojohnson This might be interesting as well: https://forums.fogproject.org/topic/6119/set-option-3-on-window-2008-r2-for-bios-and-uefi-co-existence
-
@Sebastian-Roth Just for reference: I could never make that work correctly on 2008. I may have missed something or two, but I messed with trying to get it to work for a day or so and gave up. Maybe someone else better than me can get it working.