@sebastian-roth Thank you, will keep that in mind.

Just a small update:

In my solution post i wrote, that I’ve used intel7156.efi as bootfile. Just tried to image again and iPXE couldn’t get a DHCP address. So now I used ipxe7156.efi and it seems to work fine.

I needed to register the host manually and set the has_usb_nic=1 option in the host settings, try this after updating fog.

This is the output of the dmesgcommand, once in Ubuntu on the SP4 and once in FOS.

(I wanted to upload it here, Got an error “You have not enough privileges”)

dmesg output on google drive

@Quazz Will do it tomorrow, right now the Surface is getting imaged, and it takes a bit long (old USB HUB)

Here are the steps wich resolved the issues:

@jhuesser said in Several problems with Surface Pro 4:

• If i select an entry the display just goes dark, nothing happens

Use intel7156.efi

• If i select Boot from harddisk REFIND_EFI starts, i need to press a key and then windows tries to boot but get stuck at the windows logo. (no problem if i boot without pxe)

Use intel7156.efi

• If a task is assigned it get stuck at

bzImage... ok
init.xz... ok

Use intel7156.efi

• Perform Full Host Registration and Inventory & Quick registration doesn’t work (Select menu entry -> screen goes dark; Quick registration -> chainload failed).

manually add the host and add has_usb_nic=1 to the host settings. (also for dhcp error in FOS)

@jhuesser said in Several problems with Surface Pro 4:

@george1421 It doesn’t recognize the keyboard at this point. (…)

Use an USB-Keyboard with an USB-Hub

@Sebastian-Roth Am I right, if i used the USB keyboard at the beginning, there is no need to modify the initrd to remove the keyboard interaction?

@Tom-Elliott said in Several problems with Surface Pro 4:

@george1421 lshw lsusb lspci dmesg

Personally, dmesg will probably be of more use as even if the kernel doesn’t have drivers we should see the device in the list on load up.

Should i execute dmesg on a ubuntu bootet on the SP4 or in the FOS Engine?

Btw, could succesfully up- and download an image for SP4!

@george1421 It’s the surface pro 4 with the smallest computer power.https://www.microsoft.com/surface/en-us/devices/surface-pro-4#techspec-block the one with the Intel Core m3

I’ve one booted the ubuntu live USB stick. It didn’t recognized the keyboard (and the touchscreen, but that’s not important for FOG i guess).

@Tom-Elliott I’ve used an USB-Keyboard with an USB-Hub and it works!

if i register the other surface with the full host registration i still need the keyboard to enter the details, but as i said with the USB Keyboard it’s fine just as @Sebastian-Roth said in chat. Currently I’m uploading the image, hope that works, so marking this as solved

Thank you all for your help!

I’ve looked into it with @Sebastian-Roth We’ve modifyed the initrd to remove the keyboard interaction (pressing enter to continue). After that the Surface continues with the boot and starts the debut upload task, but because the keyboard doesn’t get recognized, I can’t start the fog script…

@Sebastian-Roth I’m not quite sure. It seems that FOS doesn’t regocnize the NIC and the keyboard. I don’t know how FOS exactly works, but after r8182 2-1:1.0 eth0 v1.08.5 should there be more? Because after replug the nic it stops there.

@Tom-Elliott nope, it isn’t working…

@Tom-Elliott Thank you very much! Downloaded the new kernels from the update kernel site, unfurtunally I’ve got the same error as above.

@Sebastian-Roth Yeah, but after r8152 .. eth0 nothing happens. The keyboard also doesn’t get recognized if i don’t pull out anything. The keyboard is connected via the Surface connector. If i pull it out and plug it in again it says:

usb 1-7: new full-speed USB device number 3 using xhci_hcd

So now I have Running Version 1.3.0-RC-8 SVN Revision: 5949. Created a upload-debug task. The image of the output is below. If i pull out the usb nix and putting it back in, it recognize, that somethig is pulled in, but pressing enter doesn’t work at any time.

@Tom-Elliott I’m on RC-7 so i will update tomorrow, thank you!

@Tom-Elliott So no need to install the kernel here?

@Sebastian-Roth said in Several problems with Surface Pro 4:

@jhuesser Now I see. From what I remember (check out this post) the cdc_ether kernel module is not working nicely and therefore Tom and I decided to through it out kernel config.

@Sebastian-Roth Hi, so should i download the kernel you posted here?

@Sebastian-Roth said in Several problems with Surface Pro 4:

(check out this post)

As well read through this and see if your DHCP config is fine.

Should be correct. I can’t enable the config through the whole subnet, so i enter it manually for every host.

@Sebastian-Roth Thank you. Will have a deeper look into it at work on monday.

@Sebastian-Roth

I receive this output:

ubuntu-gnome@ubuntu-gnome:~$ lsusb
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 003 Device 004: ID 045e:07c6 Microsoft Corp. 
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c046 Logitech, Inc. RX1000 Laser Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ubuntu-gnome@ubuntu-gnome:~$ dmesg | tail
[   24.138016] cdc_ether 3-1.1:2.0 enx5882a88c3afd: renamed from eth0
[   24.169228] IPv6: ADDRCONF(NETDEV_UP): enx5882a88c3afd: link is not ready
[   24.169330] cdc_ether 3-1.1:2.0 enx5882a88c3afd: kevent 12 may have been dropped
[   24.169334] cdc_ether 3-1.1:2.0 enx5882a88c3afd: kevent 12 may have been dropped
[   24.169949] cdc_ether 3-1.1:2.0 enx5882a88c3afd: kevent 12 may have been dropped
[   24.170093] cdc_ether 3-1.1:2.0 enx5882a88c3afd: kevent 12 may have been dropped
[   24.170115] cdc_ether 3-1.1:2.0 enx5882a88c3afd: kevent 12 may have been dropped
[   25.990587] e1000e: eno1 NIC Link is Down
[   42.564105] cdc_ether 3-1.1:2.0 enx5882a88c3afd: kevent 12 may have been dropped
[   42.564191] cdc_ether 3-1.1:2.0 enx5882a88c3afd: kevent 12 may have been dropped
ubuntu-gnome@ubuntu-gnome:~$ 

I think the network stuff is right. With the same cable / ports etc. I’m able to image the desktop cable. Just put the USB nic in between the surface and the cable and the error shows up…