Boot File Testing for SR

[Psycholiquid]

@sebastian-roth said in Microsoft Surface Pro 4:

@Psycholiquid Please add the has_usb_nic=1 parameter (either in the host’s settings if it is registered already or in the general settings page (you’d see this for all hosts then). On boot it should prompt you to remove and replug the USB NIC. Then DHCP should work.

By the way: Which version of FOG do you have? Tom has added the feature to recognize clients by sysuuid rather than MAC address. See here. AFAIK this should work in FOG 1.4.4

I am on 1.5.0 RC7. Trying the has_usb_nic=1 now that has worked in the past but I opted for the USB nic that just works in using in a lab environment it is a pain to go around unplugging and plugging back in. But I will do it for you anyway and come back with results.

[Avaryan]

@sebastian-roth said in Microsoft Surface Pro 4:

@Psycholiquid Please add the has_usb_nic=1 parameter (either in the host’s settings if it is registered already or in the general settings page (you’d see this for all hosts then). On boot it should prompt you to remove and replug the USB NIC. Then DHCP should work.

By the way: Which version of FOG do you have? Tom has added the feature to recognize clients by sysuuid rather than MAC address. See here. AFAIK this should work in FOG 1.4.4

I did not know about the has_usb_nic parameter. That’s helpful for me. Thanks. I was just timing it and unplug/plugging in.

[Sebastian Roth]

@Psycholiquid If you are keen enough we might even figure out that issue as well and get rid of that need to unplug/replug USB NICs as well. But let’s focus on the iPXE issue first. Thanks for testing!

[Psycholiquid]

@sebastian-roth said in Microsoft Surface Pro 4:

@Psycholiquid Please add the has_usb_nic=1 parameter (either in the host’s settings if it is registered already or in the general settings page (you’d see this for all hosts then). On boot it should prompt you to remove and replug the USB NIC. Then DHCP should work.

By the way: Which version of FOG do you have? Tom has added the feature to recognize clients by sysuuid rather than MAC address. See here. AFAIK this should work in FOG 1.4.4

Surface Test 1 with no USB NIC and using file 04_ipxe.efi I get the following:

It will get to the menu without issue. I am choosing the last option to Compatibility to see it hit the init file and the following happens:

So all in all it works but again you have to run arond unplugging and replugging docks or USB NICs (Docks in the case of Surfaces/

[Psycholiquid]

@sebastian-roth said in Microsoft Surface Pro 4:

@Psycholiquid If you are keen enough we might even figure out that issue as well and get rid of that need to unplug/replug USB NICs as well. But let’s focus on the iPXE issue first. Thanks for testing!

No problem Its what I do LOL

[Psycholiquid]

Surface Test with no USB NIC and using file 05_ipxe.efi I get the following:

It will get to the menu without issue. I am choosing the last option to Compatibility to see it hit the init file and the following happens:

Never gets past init.xz

[Psycholiquid]

Surface Test with USB NIC and using file 04_ipxe.efi I get the following:

It will get to the menu without issue. I am choosing the last option to Compatibility to see it hit the init file and the following happens:

Works without issue, eth0 doesn’t pick up on DHCP but secondary USB NIC does and works to image or register hosts.

[Psycholiquid]

EFI timer test:

[Psycholiquid]

EFI 01 Timer Test:

but I have the hsa_usb_nic=1 still on

[Psycholiquid]

@psycholiquid and DHCP failed (This doesnt have the secondary NIC plugged in

[Psycholiquid]

svn5835_ipxe: no hang on init.xz

[Psycholiquid]

svn5836_ipxe: hang on init.xz

[Psycholiquid]

svn5901_ipxe: hang on init.xz

[Psycholiquid]

svn5902_ipxe: hang on init.xz

[Psycholiquid]

svn5918_ipxe: hang on init.xz

[Tom Elliott]

Not understanding what the bug is here.

[Psycholiquid]

He requested me to test them and put weather it hung or not.

@Sebastian-Roth

[Psycholiquid]

svn5938_ipxe: hang on init.xz

[Tom Elliott]

Are you just trying to find out when Surface Pro booting became an issue? From the boot file you should post the ipxe version. It appears in the “ipxe (abcdef)” of the connection request. The parenthesis should show us the version when it worked.

[Psycholiquid]

Not sure exactly what SR is looking for, he just requested that I try each file and let him know the result as posted. Using his template.

We have about the same time frame work wise so I told him I would test them all for him today