Issue imaging with Surface Pro
-
@george1421 George, this Surface only has 1 USB.
Here is what I attempted. Connect Microsoft usb nic, boot to FOG, select deploy image
As soon as I selected the image, I unplugged it and connected the generic one. I received the wwan error but after it failed a few times, it went into eht0 (this is with the generic usb nic) but I received a new error.
If I can get this error fixed, at least while you look into the microsoft nic (which I appreciate so much as this is out of my knowledge), this may work as you said as a sloppy fix
-
@jemerson93 Back on point here. I looked and that usb ethernet adapter is not currently supported by the Linux kernel at least as of 4.17.13 (which is pretty new). I did find a FOG forum post ( https://forums.fogproject.org/topic/10943/surface-pro-4-registration-issues ) that discusses that exact network adapter. So it appears that the FOG Project may have a patch that enables that network adapter.
Please try this development kernel: https://drive.google.com/open?id=1WPv4HeMrWdWu9uyOyVaoJkBX3A9EGi-t
- Download that file as bzImage41713m and place it in /var/www/html/fog/service/ipxe directory on your fog server.
- Goto the fog gui and locate the the computer in host management where this ethernet adapter is connected. There is an entry for Host Kernel enter
bzImage41713minto that field. - Pxe boot the target computer to run your capture/deployment.
- Note any error messages in regards to getting a dhcp address.
I really don’t know if this will work (the FOG Project patch) or not for your install. This development kernel has quite a bit more hardware support added than previous releases of the FOS kernel. Will something else break? Probably…??, but it shouldn’t.
-
@george1421 said in Issue imaging with Surface Pro:
bzImage41713m
Did as you said, kicked in the eth0 interface and got further. Now running into this issue.
-
@jemerson93 unable to find image store means fos cannot see your image files anywhere. Do they exist? If you have other nodes, do those nodes also have the image?
-
@tom-elliott I have 1 storage node and I just tested that specific image (which used to work) on another laptop and it had the same issue.
When checking /images, I am finding all of my images except for that one listed. I will re-upload it now and test.
-
Update. I tested another one of our images just to test imaging and it successfully imaged. I appreciate the assistance so much.
I do have 2 questions. First question, I noticed when using this kernel compared to the current kernels I am using, I am back to the issue with the long erasing MBR/GPT partitions. Anyway to fix that with this custom kernel or just need to deal with it?
Secondly, is there a way for me add other usb nics as I find issues, or how to find a kernel that supports them instead of opening a forum post if I run into issues. Reason I ask is we have a Dell USB nic for some of the new XPS models and I have yet to test it.
-
@jemerson93 said in Issue imaging with Surface Pro:
I am back to the issue with the long erasing MBR/GPT partitions
Well that tells me the kernel patch I applied didn’t address the slow gpt partition creation (same issue with FOS 4.17.0)
@tom-elliott The nic was enabled by adding
{REALTEK_USB_DEVICE(VENDOR_ID_MICROSOFT, 0x0927)}to
drivers/net/usb/r8152.c@jemerson93 To your adding other usb nics. The answer is sure, all you need to do is patch the linux kernel source from http://www.kernel.org and then compile the linux kernel.
-
@george1421 George I’ll look into that for other USB nics (my Linux knowledge is not the greatest but growing)
I can deal with the longer erasing mbr/gpt partition for those specific devices (hoping newer kernels may resolve it)
Thanks again for the help! So greatly appreciated.
-
@george1421 Also I’m not sure how to change this to solved.
-
@jemerson93 The mbr/gpt issue needs to be resolved, period. The truth may be this slow creation process may be a ‘feature’ of 4.17.x kernel and not a bug. I can tell you this issue is still on the developers plate (which is getting overloaded at the moment). Please give them a bit to get back from holiday and back in business.
