iPxe initialising devices... Sticking

[Dragnous]

Hello all.

We have started to test a new option. We have purchased a ton of laptops (Stream 11 Pro Commercial Grade) from Hp and they have provided us with Pxe bootable USB to Ethernet adapters.

So far it starts to work however when it gets to "iPxe Initialising Devices… " It just hangs there and doesnt go past.

Any thoughts or advice.

[cml]

What version of Fog and what pxe file are you booting?

Booting off of undionly.kkpxe may resolve your issue.

[Dragnous]

Latest Version: 1.2.0 fog
not sure on the pxe file. Where do i check this?

[cml]

You are more than likely using undionly.kpxe, but if windows is handling your dhcp it would be option 67. You can also rename the old file and symlink the new one.

cd /tftpboot
mv undionly.kpxe undionly.kpxe.REAL
ln -s undionly.kkpxe undionly.kpxe

[Dragnous]

@cml said:

What version of Fog and what pxe file are you booting?

Booting off of undionly.kkpxe may resolve your issue.

I was talking with my network guy he said we set it up to undionly.kpxe in DHCP

[Dragnous]

Still looking for a solution anyone have any experience with this

[Wayne Workman]

@Dragnous Ask your network guy to change the DHCP scope option 067 to this:

undionly.kkpxe

And let us know how it goes. This is the more simple way of doing what @cml was wanting you to try. I don’t think we can move forward until you’ve tried undionly.kkpxe. It’s the next step in troubleshooting.

[Dragnous]

@Wayne-Workman said:

@Dragnous Ask your network guy to change the DHCP scope option 067 to this:

undionly.kkpxe

And let us know how it goes. This is the more simple way of doing what @cml was wanting you to try. I don’t think we can move forward until you’ve tried undionly.kkpxe. It’s the next step in troubleshooting.

Oh maybe I misunderstood, what is difference between undionly.kpxe and undionly.kkpxe ?

Also note sure if this needs to be noted but using linux box as DHCP

[Wayne Workman]

@Dragnous https://wiki.fogproject.org/wiki/index.php/Filename_Information

and so you know, any computer that is compatible with undionly.kpxe is also compatible with undionly.kkpxe.

[Dragnous]

@cml said:

You are more than likely using undionly.kpxe, but if windows is handling your dhcp it would be option 67. You can also rename the old file and symlink the new one.

cd /tftpboot
mv undionly.kpxe undionly.kpxe.REAL
ln -s undionly.kkpxe undionly.kpxe

Ok now that I understand what you where stating… I tried this and it works

Edit: New issue! lol Now when performing full host registration its hanging there too

/bzImage… ok
/init.xz… ok
[] <— just hangs there

Edit: I noticed that the connectivity lights on the adapter just go dead…

[Wayne Workman]

@Dragnous Make sure Secure Boot is turned off, make sure Legacy BIOS and Legacy Option ROM support is turned on. and (u)EFI and UEFI is off.

I don’t know the exact names that HP will call these things, but it’ll be along those lines.

[Dragnous]

Secure Boot <Disabled>
Legacy Support <Enabled>
Network Boot Protocol <IPv4 (Legacy)>

Those are my current Settings. Still same issue.

[Wayne Workman]

@Dragnous Do you get to the FOG boot menu at all now? Can you run the compatibility tests there?

[Dragnous]

@Wayne-Workman said:

@Dragnous Do you get to the FOG boot menu at all now? Can you run the compatibility tests there?

Yes I get the menu and anything I try to do fog hangs and the adapter goes dead… Think its driver related but unsure.

[Dragnous]

Question: Once Kernel is loaded and init.xz is loaded what happens next… I am fearing that its because there is a lack of drivers for the USB Adapter. I do have the Drivers for the device however they would need to be build into the Kernel correct?
Any more help that could be provided would be helpful as I have 2k of these devices coming for the school year and Id like to use fog instead of clonezilla.

[Tom Elliott]

I’d be surprised if the drivers for this device were NOT already in the kernel.

That said, have you tried?

See there was a feature added to FOG a few months ago specifically to address the USB NIC issue you’re describing.

Under the hosts that need the USB Nic, add the kernel argument has_usb_nic=1.

While it doesn’t save any time, directly, it should allow the device to operate as intended.

The way the argument works is by waiting for you to disconnect, then reconnect the device. This, for whatever reason, seems to work.

[Dragnous]

@Tom-Elliott said:

has_usb_nic=1

Oh… question where do i add that exactly.

[cml]

@Dragnous

On the host management page

The same setting exists on the group management page, so you can apply it to a group of computers.

[Dragnous]

@cml said:

@Dragnous

On the host management page

The same setting exists on the group management page, so you can apply it to a group of computers.

Ok so i take it I will have to manually register the host first, than add the argument

[Tom Elliott]

You can alter the args list for registration if you need to. Look at the FOG Configuration->iPXE Boot Menu Configuration->fog.reginput boot options add has_usb_nic=1.

This option should be removed for non-usb nic hosts, but if you’re focused only on these for now, this should get you where you need to go at least.