Legacy boot HP Stream 11 *Not Working*
-
I’ve been imaging these now for awhile. The only way i can get them to work is having the legacy support disabled. ALSO you have to use the ipxe.efi binary.
I’m curious as to what Ethernet/USB adapter you’re using. -
Alright. I think I made reverse progress…
So, I logged into the fog server and created a host for the HP Stream 11 using the USB to Ethernet’s MAC Address. and when doing so i added the arguement “has_usb_nic=1” for that host.
Now i am trying to image another machine that has a ethernet card built in. and it to is getting hung up at “iPXE Initializing Devices.” Maybe there is an issue there now???
-
As I said the host kernel parameter
has_usb_nicis not playing a role that early in the boot process! Cannot be related!! Maybe you also used a different iPXE binary which now causes the hang on a different machine…?!When researching on this topic I am sure you came across this: https://forums.fogproject.org/topic/6036/hp-stream-11-pro (please read through the full thread!)
-
@cojohnson Can you please tell us the exact make and model of the USB adapter your using? This does matter.
-
@Wayne-Workman said:
Can you please tell us the exact make and model of the USB adapter your using? This does matter.
Thanks for pointing this out! It actually is one of the most important things in this equation!!
-
Hello, I am using an official HP USB to Ethernet adapter.
AX88772C/772B/772A/772…
Also drc0nc said I have to use the ipxe.efi binary. Should i grab any of the other file from
PXE Binaries??Thanks!!
-
@cojohnson I use that same HP official adapter. ipxe.efi should be it. make sure you change option 67 in windows DHCP (if that’s what you’re using.)
-
@drc0nc Alright. Thats above my paygrade!!! I will have to have my superior check on that when he gets back on Monday! Thanks for your help!!
-
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.
