Microsoft Surface Pro 4 Deployment stuck at init.xz

[fry_p]

Hey all,
So far 1.3 RC1 is great. I did run into a hiccup just now however. Using the Usb ethernet dongle that I used many times before is unable to get past the init.xz …OK phase of deployment. After it reaches this point, it freezes. I am using ipxe.efi as the bootfile and secure boot is off. I have the HAS_USB_NIC=1 argument. Really, nothing has changed besides the update to RC1 since the last Surface was imaged. I currently don’t have an EFI exit type set because frankly, I’m ignorant to what that means. That could be a factor(?)

Thanks!
Paul

[Tom Elliott]

If it’s getting to the point of loading the init.xz, it’s not the exit type causing any issues. Not at that point at least.

If you change the efi file you’re using, does it get further?

[fry_p]

@Tom-Elliott Unfortunately, no. I tried every file with the .efi extension. It either falls short of init.xz or freezes at the same point

[Tom Elliott]

@fry_p what about from cold start?

[fry_p]

@Tom-Elliott I’m forced to cold reboot once it gets stuck every time. I can get to the ipxe menu when there is no active task. If I go to quick image, it gets past init.xz,…OK but goes dark and stays like that.

[Tom Elliott]

@fry_p Can you enable kernel debug and put the loglevel to 7? This is done in fog settings under configuration.

Just to see if it’s at least attempting to load stuff from the kernel/init side or if it’s not even releasing to the kernel.

[fry_p]

@Tom-Elliott it appears to be exactly the same with the logging enabled.

Just to make sure here are the logging settings i changed:

[Tom Elliott]

Try changing your tftp files with those from:

https://sourceforge.net/p/freeghost/code/5835/tree/trunk/packages/tftp/

I don’t know why, but this particular issue seems related to something that I have literally no control over.

[fry_p]

@Tom-Elliott That worked. What was different about what I had vs. the ones you had me download? I tried re-installing this morning and that didn’t work.

[Tom Elliott]

@fry_p The files in current are much newer. I think the iPXE Version of the files you have are 7156.

[Wayne Workman]

@fry_p said in Microsoft Surface Pro 4 Deployment stuck at init.xz:

@Tom-Elliott That worked. What was different about what I had vs. the ones you had me download? I tried re-installing this morning and that didn’t work.

@Tom-Elliott we need this sorted for 1.3.0. Can we just use those files instead of the latest ones?

Maybe a way to update tftp files via the Web interface like kernels are done?

#wiki

[Tom Elliott]

@Wayne-Workman making a “repository” for the ipxe files, I think, is not a feasible option. Kernels on repository simply because they are, for the most part, interchangeable and upgrading them allows for new hardware and typically no degradation of prior working items. In the case of iPXE the issue as seen here, is new files don’t necessarily mean things from the past will still work. Knowing which is which is very difficult as well. I don’t know when a series of files may break functionality and it may take many days or weeks before we are even made aware that there is a problem.

[Scott Adams]

@Wayne-Workman Which files do I download/replace? I am having the same issue with my Surface Pro 4. I am running Ubuntu 16 and RC8.

This is a test environment that I have set up.

[Wayne Workman]

@Scott-Adams You should first update to RC-10. You already have the file you need, it’s /tftpboot/ipxe7156.efi

Please use wireshark to capture a DHCP conversation from the surface pro 4, we are collecting vendor strings for these devices, it’s kind of important to us. With this, we can tell you exactly how to configure your DHCP server to serve this particular file to your Surface Pros, and this will help everyone else too. And it’s not that big of a request. In wireshark, use the bootp filter.