Surface Book won't boot the kernel

[Quazz]

@x23piracy Not that I’m aware of, though they could work, it’s hard to say without people trying it out.

Does not look good so far, though. I’m very far from being an expert, but I reckon the current iPXE kernels don’t yet support this.

Aside from has_usb_nic=1 , try using the kernel command iommu=soft as well.

edit: Also, if it’s possible to turn of xHCI in BIOS, try that as well.

[george1421]

@x23piracy There was just a kernel update released by the developers. 4.11.6 that was released with FOG 1.4.4. I have FOG 1.4.0 loaded on my production servers, with kernel 4.11.0 if you want to try a down level bzImage file.

So the question to you is, did a previous version of the kernel work on this surface pro, or is it a new surface pro?

@Quazz is right, if you are starting to boot the FOS kernel then iPXE is out of the picture and not your issue.

Since this system isn’t registered, you can either manually register and schedule a debug deploy or temporarily add the kernel parameter isdebug=yes and then pxe boot the target computer to get to the FOS command prompt.

Once there we might issue a lsusb to see if that external dock is detected.

[Tom Elliott]

Host Kernel is not IPXE Booting.

[Tom Elliott]

Boot files are set by the dhcp server Option 67, not by anything in the GUI.

[x23piracy]

@george1421 said in Surface Book won't boot the kernel:

So the question to you is, did a previous version of the kernel work on this surface pro, or is it a new surface pro?

No, this is my first Surface Book i ever tried with FOG, Surface 3/4 Pro are working with ipxe7154.efi

Since this system isn’t registered, you can either manually register and schedule a debug deploy or temporarily add the

I tried to use the MS Surface 3 Pro USB NIC, it’s MAC was already registered to a different system were i used that usb nic for imaging so i just tried to boot to FOS with that registration to another host but it still cannot boot to FOS.

Anyone here who is working with Surface Books?

I don’t think that the Dock’s internals are different to the Surface 4 Pro Docks, they look pretty the same, i cannot swear it’s the same hw inside but i would bet. And i could succesfully a Surface 4 Pro with that Dock.

@Quazz said in Surface Book won't boot the kernel:

edit: Also, if it’s possible to turn of xHCI in BIOS, try that as well.

I can try this tomorrow.

@Tom-Elliott said in Surface Book won't boot the kernel:

Host Kernel is not IPXE Booting.

What else can be done with that option?

@george1421 said in Surface Book won't boot the kernel:

Once there we might issue a lsusb to see if that external dock is detected.

Boot to shell, then firing a lsusb? Ok, i will do this tomorrow too.

Regards X23

[x23piracy]

@Quazz said in Surface Book won't boot the kernel:

Aside from has_usb_nic=1 , try using the kernel command iommu=soft as well.

@Quazz has_usb_nic=1 did the job, excellent man
Surface Book is now working with FOG… Applause.

Please mark as solved, thanks.

Regards X23

[x23piracy]

Hi,

ok it’s not working it just booted once over the surface 3 pro usb nic and the supplied dock for surface book, but just a single time. Another strange issue in my it life…

[x23piracy]

Hi,

is there a difference between choosing system information in fog menu and do a inventory of the machine?
I only could boot once with usb nic or the dock when i add has_usb_nic=1 but i didn’t choose to image i just started the system information entry then it booted up but i don’t know if there is a difference between that and for example planing a deploy task.

Regards X23

[x23piracy]

Hi,

has no one around the forums a Surface Book that could be tried with FOG please?

Regards X23

[Tom Elliott]

@x23piracy Have you tried ipxe7156.efi files?

[x23piracy]

@Tom-Elliott said in Surface Book won't boot the kernel:

@x23piracy Have you tried ipxe7156.efi files?

sure, 7154 are my default files because we have a lot of surface 3/4 Pro, since 7154 isnt working i also tried ipxe.efi, same error.
If you say file(s) are there more then one ipxe7154.efi files?

[Tom Elliott]

@x23piracy There are. If you know the “model” of the nic, you could try the realtek7154.efi, or intel7154.efi or, or or…

[x23piracy]

@Tom-Elliott I found the following (filtered) in /tftpboot:

i386-7156-efi
i386-efi
intel7156.efi
intel.efi
ipxe7156.efi
ipxe.efi
realtek7156.efi
realtek.efi
snp7156.efi
snp.efi
snponly7156.efi
snponly.efi

Should i try them all or are senseless ones listed?

What about:

has_usb_nic=1
iommu=soft

should i set these values as arguments?

Afaik the nic in the dock should be from intel.

[x23piracy]

@Tom-Elliott i was wrong with the nic
Here is a teardown: https://blogs.msdn.microsoft.com/danchar/surface-dock-teardown-brick-shaped-dock-for-sp3sp4surfacebook/

It should be a Realtek RTL8153AM Ethernet:
http://www.realtek.com.tw/search/default.aspx?keyword=8153

Will try the realtek efi’s tomorrow at work

Regards X23

[x23piracy]

It doesn’t work with any of the efi files.

[Sebastian Roth]

@x23piracy This seems to be a totally different issue than what we see with the surface pro 3/4 devices. Those hang on init.xz... ok as far as I know. This SurfaceBook device seems to get past this (using the ipxe7156.efi binary) but then hangs because the linux kernel (!= ipxe binary/kernel) does not recognize the USB/dock NIC. The messages on screen look like there is a USB communication issue. What happens when you press enter as is says on the screen? Do you get any further? I think we need more information on that USB dock device. are you able to live boot a linux system and run lsusb?

Hmm?? https://paulphilippov.com/articles/how-to-fix-device-not-accepting-address-error

[Sebastian Roth]

This sounds interesting as well:

Strange. I think it’s just a quirk on my end and actually cause by the Windows hybrid shutdown. It seems Windows doesn’t fully release the SD card (and potentially other hardware) when shut down, which then causes Linux to not be able to see the SD card when booting. I switched back to a stock initramfs and everything works unless I boot into Windows and shut down to boot into Linux. Fortunately the Windows Recovery menu will let me boot from USB, and everything start magically working again.

As well this sounds very similar but was fixed in the 3.x and early 4.x main line kernel already: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1455376

[x23piracy]

@sebastian-roth about the live system, i need to find the time today, i have the book until next friday.