Microsoft Surface Pro 4 with Surface Docking Station - Unable to get boot file

kwetiaw

I have tried finding information on this forum but [so far I havent had any luck yet.

My server is ubuntu 14 with fog 1.3.0 RC-8. Dnsmasq with proxydns mode
The target machine is Microsoft Surface Pro 4 with official docking station ms store

I have successfully boot UEFI via USB forum link and got the bootscreen. I have then manually created the host and the boot screen recognized it has been registered.

I was like yay!

But then when I assign a capture task i encountered this error

0_1473824732598_2016-09-14 13_44_40-.png
0_1473824741646_2016-09-14 13_44_56-.png

And that’s it, it hang and not going anywhere. I have to hard power off the surface pro 4.

Here’s my ltsp.conf settings

# Sample configuration for dnsmasq to function as a proxyDHCP server,
# enabling LTSP clients to boot when an external, unmodifiable DHCP
# server is present.
# The main dnsmasq configuration is in /etc/dnsmasq.conf;
# the contents of this script are added to the main configuration.
# You may modify the file to suit your needs.

# Don't function as a DNS server:
port=0

# Log lots of extra information about DHCP transactions.
log-dhcp

# Dnsmasq can also function as a TFTP server. You may uninstall
# tftpd-hpa if you like, and uncomment the next line:
# enable-tftp

# Set the root directory for files available via FTP.
tftp-root=/tftpboot

# The boot filename.
dhcp-boot=undionly.kpxe,,10.3.24.15

# rootpath option, for NFS
dhcp-option=17,/images

# kill multicast
dhcp-option=vendor:PXEClient,6,2b

# Disable re-use of the DHCP servername and filename fields as extra
# option space. That's to avoid confusing some old or broken DHCP clients.
dhcp-no-override

# PXE menu.  The first part is the text displayed to the user.  The second is the timeout, in seconds.
pxe-prompt="Press F8 for boot menu", 3

# The known types are x86PC, PC98, IA64_EFI, Alpha, Arc_x86,
# Intel_Lean_Client, IA32_EFI, BC_EFI, Xscale_EFI and X86-64_EFI
# This option is first and will be the default if there is no input from the user.
pxe-service=X86PC, "Boot from network", undionly

# A boot service type of 0 is special, and will abort the
# net boot procedure and continue booting from local media.
pxe-service=X86PC, "Boot from local hard disk", 0

# If an integer boot service type, rather than a basename is given, then the
# PXE client will search for a suitable boot service for that type on the
# network. This search may be done by multicast or broadcast, or direct to a
# server if its IP address is provided.
# pxe-service=x86PC, "Install windows from RIS server", 1

# This range(s) is for the public interface, where dnsmasq functions
# as a proxy DHCP server providing boot information but no IP leases.
# Any ip in the subnet will do, so you may just put your server NIC ip here.
# Since dnsmasq is not providing true DHCP services, you do not want it
# handing out IP addresses.  Just put your servers IP address for the interface
# that is connected to the network on which the FOG clients exist.
# If this setting is incorrect, the dnsmasq may not start, rendering
# your proxyDHCP ineffective.
dhcp-range=10.3.24.15,proxy

# This range(s) is for the private network on 2-NIC servers,
# where dnsmasq functions as a normal DHCP server, providing IP leases.
# dhcp-range=192.168.0.20,192.168.0.250,8h

# For static client IPs, and only for the private subnets,
# you may put entries like this:
# dhcp-host=00:20:e0:3b:13:af,10.160.31.111,client111,infinite

what am I doing wrong? please help!

Wayne Workman

@george1421 said in Microsoft Surface Pro 4 with Surface Docking Station - Unable to get boot file:

@Wayne-Workman Do you think we have enough discrete bits of information to make a wiki page on the surface pro 4? As these devices become more popular I can see the volume of quesitons increase. Having one location (you look here->) would add real value from a support perspective.

I still want to do this, will start work on it maybe tomorrow - it may take the entire morning to do, this will be a large article.

@Wayne-Workman said in Microsoft Surface Pro 4 with Surface Docking Station - Unable to get boot file:

@kwetiaw I’m linking threads that deal with the Surface Pro 4 here for you to read through. All of the below threads are marked as solved. As George already said, I’d like to compile all of this information into a single #wiki article, but I don’t have a SP4 to test with. I will be out for several days after tonight.

https://forums.fogproject.org/topic/6515/surface-pro-4-won-t-get-to-registration-menu

https://forums.fogproject.org/topic/8181/surface-pro-4-image-capture

https://forums.fogproject.org/topic/7660/surface-pro-4-on-7977

https://forums.fogproject.org/topic/7353/surface-pro-4-unable-to-image

https://forums.fogproject.org/topic/8323/several-problems-with-surface-pro-4

Wayne Workman

@george1421 Ah, yes. You’re right George. lscpu, lspci, lsusb, lsisa, lsblk. I wasn’t thinking.

george1421

@kwetiaw I’m not sure that lspci (actually pretty sure) will show this network adapter. You will want to use something like lsusb -v to show all devices connected to the usb bus controller. I can’t say for sure if lsusb is included in the FOS Engine.

kwetiaw

@Wayne-Workman
i had the usb dongle connected via USB 3.0 port replicator and this replicator connected to the only USB port in Surface pro 4.

Wayne Workman

@kwetiaw Thank you so much, was the USB to Ethernet adapter plugged in when you did this? I’m guessing it was since I see a fog imaging variable dump just above.

kwetiaw

@Wayne-Workman

Here you go, hope that helps in anyway.

Cheers

kwetiaw

@Wayne-Workman Hi Wayne

I will definitely do this for you next week Monday or Tuesday.

Cheers

Wayne Workman

@kwetiaw if you would please be so kind, we want some more information about that adapter.

idk if that USB boot stick you have can do debug or not - but if it can or you can get to the CLI somehow, please run this command and give us the output:
lspci

That will tell us what exact chipset that adapter is using and will be extremely helpful to us and others.

kwetiaw

I managed to get it working with a USB2.0 to Ethernet Dongle by Lenovo here

It deploys the image successfully but it boot looped because i dont have efi image (surface pro 4 cant do legacy boot anymore)

Anyway, thanks a lot for your help and I wish I could lend/give you a microsoft surface pro 4 for your testing. This is the first one and many to come in the near future in our company here.

It seems that the issue here is the official microsoft docking station not re-acquiring network connection

Cheers

Wayne Workman

@kwetiaw I’m linking threads that deal with the Surface Pro 4 here for you to read through. All of the below threads are marked as solved. As George already said, I’d like to compile all of this information into a single #wiki article, but I don’t have a SP4 to test with. I will be out for several days after tonight.

https://forums.fogproject.org/topic/6515/surface-pro-4-won-t-get-to-registration-menu

https://forums.fogproject.org/topic/8181/surface-pro-4-image-capture

https://forums.fogproject.org/topic/7660/surface-pro-4-on-7977

https://forums.fogproject.org/topic/7353/surface-pro-4-unable-to-image

https://forums.fogproject.org/topic/8323/several-problems-with-surface-pro-4

kwetiaw

@Wayne-Workman Hi Wayne
I have upgraded to the latest RC 10 but im still stuck at pretty much the same screen

with argument has_usb_nic=1

without argument

Wayne Workman

@kwetiaw Rebuild your USB stick with the latest FOG kernel, Tom has made adjustments to better support newer style keyboards (like built in touch keyboard for surface and others) in the latest kernel.

You don’t have to go to RC-10, but I would recommend it. To simply get the latest kernel, you can just use the kernel update feature. Details are here:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_Update

kwetiaw

Right, now the issue was i didnt have USB keyboard connected. I connected it now.
I have unplug and plug as it requested, didnt seem to getting any IP address. I can confirm the previous screen (first screenshot on my original post) that it found the Fog server 10.3.24.15.

I tried another USB docking station by Lenovo USB3.0 USB, this one fails miserably.

What is the next step do you think? I havent updated to the latest RC 10 and was booting up using the USB with ipxe.efi (latest one from here)

what should i do next?

Psycholiquid

@Wayne-Workman Yeah I hear ya. I cant make any promises but I may have a spare one I can loan out, I do see these being the new laptop. We have 35 in house now that I am dealing with

Wayne Workman

@Psycholiquid We could certainly return a borrowed device, or accept it as a donation. We need a surface pro 4 to work with eventually though. Do you have a dock for the 3?

Psycholiquid

I have a SP3 just laying here but I am not sure if it is on the lease or not (Owners kid dropped it off) but I don’t think the 3 is good to work with, You would also need the dock which to say the least is a very weird dock.

george1421

@Wayne-Workman said in Microsoft Surface Pro 4 with Surface Docking Station - Unable to get boot file:

I just wish I had one of these things to test with. They are just so expensive…

Just remember that the FOG Project team is always willing to accept donations of a surface pro 4, if getting FOG 1.3.0 fully compatible with a surface pro 4 is mandatory for the posters environment.

Wayne Workman

@george1421 It’s a good idea. I just wish I had one of these things to test with. They are just so expensive…

#wiki worthy

Tom Elliott

Also keep in mind kernel support for the keyboards is very new but appears to be functional. I pushed up 4.7.3 last night fully patched as well.