Maybe the USB cable is bad

[dylan123]

I’d try boot the laptop normally with the adapter connected to your laptop, open up cmd > type ‘getmac’ and get the mac for the usb hub.

Once you’ve got the mac, open up the fog server, create a new host and give it the mac address of the USB hub and also add ‘has_usb_nic=1’ to the kernel arguments.

From there, you want to give it the capture/deploy tasks and with any luck you’ll see a similar kind of issue but it telling you to remove the hub, reconnect and hit enter before continuing on with the process - maybe go through a dumb switch to ensure it gets network connectivity almost instantly once it’s plugged in again.

[Quazz]

Similar problem noted here:

https://bbs.archlinux.org/viewtopic.php?id=186503

Try usbcore.old_scheme_first=1 as kernel argument

[JGeear]

@dylan123 said in Maybe the USB cable is bad:

c
That worked! It stills outputs the message. Cheers!

[JGeear]

@Quazz

This worked as well and still displayed the messages.

[Quazz]

@JGeear What if you use both arguments together? (seperate them with a space)

[fry_p]

@Quazz I just tried both arguments on a surface pro 4. As long as you put

usbcore.old_scheme_first=1

before

has_usb_nic=1

separated by a space like you said, it works with no errors.

[JGeear]

@fry_p said in Maybe the USB cable is bad:

has_usb_nic=1

Yeah, it still displays the warnings!

[JGeear]

@JGeear
I purchased a Dell USB 3.0 to Ethernet adapter with PXE boot. It worked perfectly!

[cool1107cm]

Hi @Quazz & @fry_p

How can I add kernel argument as below,
Would you please provide me more detail info?
Thank you so much

usbcore.old_scheme_first=1
has_usb_nic=1

[fry_p]

@cool1107cm said in Maybe the USB cable is bad:

Hi @Quazz & @fry_p

How can I add kernel argument as below,
Would you please provide me more detail info?
Thank you so much

usbcore.old_scheme_first=1
has_usb_nic=1

Hi @cool1107cm ,
Much has changed in the way of Surface imaging for me. At the time of this post, I was able to image using these kernel arguments with a USB NIC on a Surface Pro 4 . However, as time passed, a number of other variables have come out of the woodwork to prevent the use of FOG on Surface Pro’s for me. I have reverted to manually installing Windows. I believe for a while I was working with @Sebastian-Roth and/or @george1421 on getting this to work. If you have a surface pro/ usb nic issue, I would highly recommend starting a new thread. Perhaps someone has come up with a solution since the time of this post.

Sorry I couldn’t be much more help. For the record, I used the Host Kernel Argument box on the host information page for the particular host on the web GUI and added these arguments in the order I specified separated by a single space.