Surface Pro 4 won't get to registration menu

[Sebastian Roth]

You mean a full FOG trunk install or just the init’s being updated to the latest? Really confusing anyway. I think I’ve seen this in the last days already but why would the newer kernel not recognize your NIC??

[Tom Elliott]

@Sebastian-Roth I am trying to see the same thing. This is a separate and FULL fog server \0/. At any rate, I don’t know, yet, if it’s kernel doesn’t recognize the nic, or if it’s related to the nic being usb.

[sarge_212]

@Tom-Elliott Hey Tom, good morning! I tried to do the debug push to the surface and it is not able to grab that. I’ll try today on the USB-ethernet adapter. Thanks!

[sarge_212]

@Tom-Elliott So, we had to order some USB -ethernet adapters. We’re waiting on those. On the USB dock, I get this when trying to do debug push:

Is this something with the inits? Let me know, thanks!

[Tom Elliott]

@sarge_212 Don’t use Advanced -> Debug to do a debug task.

Schedule your task like you normally would, but before confirming check the “Schedule as debug” checkbox.

[sarge_212]

@Tom-Elliott Okay, I’m in debug mode. What information will help? I’m using the USB dock. I did an ip addr show and on eth0 I’m not seeing inet address.

[george1421]

@sarge_212 said:

@Tom-Elliott Okay, I’m in debug mode. What information will help? I’m using the USB dock. I did an ip addr show and on eth0 I’m not seeing inet address.

I’ve been kind of loosely following this thread. So you are booted into debug mode. How many ethernet adapters do you see when you do an ip link show?

Do you have the usb ethernet adapter installed?

Do you only see eth0 and can you confirm by the mac address this is the usb ethernet adapter or is this the wifi ethernet adapter?

[sarge_212]

@george1421 This is the Surface USB dock I’m using right now as I am waiting for some usb ethernet adapters from amazon. My old one broke… The eth0 is the usb one, that is the one that I’ve registered in the webGUI. I’ll have to see if its any different once those usb adapters get in.

[Wayne Workman]

@sarge_212 Please keep us informed on exactly the USB adapter vendor and model and version number. This is important stuff and we don’t have enough info about it.

[sarge_212]

@Wayne-Workman Thanks Wayne. We just ordered an Amazon Basics Ethernet 2.0 USB adapter, the one found here:

http://www.amazon.com/AmazonBasics-USB-Ethernet-Network-Adapter/dp/B00M77HLII/ref=sr_1_4?ie=UTF8&qid=1455902388&sr=8-4&keywords=ethernet+usb+2.0+adapter

It works in the OS, just not when trying to PXE boot. The interesting thing is, the Surface dock, when connected via that, I do get it to PXE boot.

[george1421]

@sarge_212 said:

It works in the OS, just not when trying to PXE boot. The interesting thing is, the Surface dock, when connected via that, I do get it to PXE boot.

I’ve been loosely following this thread, so this may have already been answered, but why not just add the surface dock nic to the FOG kernel?

If the usb nic you are purchasing does not work for pxe booting, but does work in FOS, then you can just usb boot the surface into the fog menu. (It would sound logical to $Donate$ to the FOG project and request that the nic for the surface pro 4 be added to the list of supported devices. That way you won’t have to mess with it as you add to your fleet of systems.

[Tom Elliott]

@george1421 The NIC is already in the kernel, and I suspect the same for all of the nic’s that have been tested.

However, i think it’s the has_usb_nic thing that needs to be retested to see if we can get things working again.

[Sebastian Roth]

@sarge_212 Well then, could you please add has_usb_nic=1 to the host’s kernel parameter and try PXE booting with the dock again?

[sarge_212]

@Sebastian-Roth Yes of course. I didn’t know there was such a parameter. I’ll test now. Thanks FOG Team!

[sarge_212]

@Sebastian-Roth UPDATE:

So, I successfully pxe booted off the surface dock. Then it prompted for a USB adatper, so I unplugged the ethernet cable from the surface dock and plugged in the USB>ethernet adapter and it started to capture the image. However, I have the image set to single disk - Resizable and it started to do a whole RAW image copy. of 254G. Is there anyway to make the image smaller? I am going to try multiple partition single disk now. However, on the raw transfer, it appeared to hang after about 3.1G of transfer. Let me know your thoughts.

[Sebastian Roth]

@sarge_212 Why would it do RAW? I have no idea. Could you please post a picture of the messages on screen just before partclone (that blue “capture” screen) comes up?

FOG should be able to read the data in your partitions if they are FAT, NTFS, EXT2/3/4 and many other formats - in NON RAW mode!

[sarge_212]

@Sebastian-Roth Well, crap. I already am letting it upload the image as raw. I switched to Multiple partitions single disk and let it upload the 254 GB image. That’s almost done. I can create a second image definition and upload that once I’m done with this one here which should be done in about 4 minutes. I’ll try and get a solid video of the process but that may not be until tomorrow.

[sarge_212]

Okay, so we’ve made some progress so far. We were able to get a win10 upload working on an amazon usb 2.0 adapter. However, we wanted to try a 3.0 adapter for faster speeds, but that isn’t working. Also, another issue, when the upload appears to be done, I get a database error (of which I’ll post a picture should it happen again). The USB 3.0 adapter model is a Linksys usb 3.0 gig ethernet adapter, USB 3GIGv1 as found here: http://www.amazon.com/Linksys-Ethernet-Chromebook-Ultrabook-USB3GIG/dp/B00LIW8TBG/ref=sr_1_2?ie=UTF8&qid=1456499881&sr=8-2&keywords=linksys+3.0+usb+ethernet+adapter

Yeah. That’s where we’re at now. I’m doing an upload now and if it fails with that database error I’ll let you know. I’m pretty certain it’s not FTP creds, because other images are able to be uploaded.

[sarge_212]

@Sebastian-Roth Also, I forgot to mention, we did single disk resizable and it no longer is doing it as a RAW upload. That is good.

[sarge_212]