Several problems with Surface Pro 4
-
@Tom-Elliott I’m speculating that either the surface pro has some yet unknown pci bridge or usb bridge or keyboard controller. That is getting in the way. Do you know of a way (other than lspci) to identify/list unknown hardware?
-
@george1421
lshwlsusblspcidmesgPersonally, 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.
-
Btw, could succesfully up- and download an image for SP4!
-
@jhuesser Great to hear! Would be awesome if you could provide the information Tom asked as well.
-
@jhuesser Can you summarize exactly what is needed for the Surface Pro 4 please? This thread is really, really long - and we need a summary that is reproducible and clear.
-
From what I gather:
Not working: keyboard in FOS engine, NIC in debug mode?
Working: iPXE menu, capture/deploy
Needed: has_usb_nic=1 kernel parameter. intel7156.efi or realtek7156.efi (or other 7156 ipxe bootfile depending on your USB NIC)
Please add/modify as needed.
-
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 harddiskREFIND_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... okUse
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=1to 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
lshwlsusblspcidmesgPersonally, 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?
-
@jhuesser So the NIC can get DHCP in debug_mode now?
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?
Yes
Should i execute dmesg on a ubuntu bootet on the SP4 or in the FOS Engine?
I think either works, but likely more convenient to boot ubuntu to transfer the output. Make sure the keyboard dock is connected on boot so the information is collected.
-
@Quazz Will do it tomorrow, right now the Surface is getting imaged, and it takes a bit long (old USB HUB)
-
@jhuesser said:
Should i execute dmesg on a ubuntu bootet on the SP4 or in the FOS Engine?
Both will give us some good information although I think that running those on the FOG system would give us a better idea what works and what not.
-
@Tom-Elliott
Not sure if you got the keyboard issue figured out or what drivers / patches you added, but I have successfully used this in the past for SP4
https://github.com/cransom/surface-pro-3-nixos/blob/master/multitouch.patch -
@jdd49 I’ve saved this on my bookmarks list and updated the kernels to have the reflected patch changes within the current 4.7.1 kernels.
Thanks for posting.
-
#wiki worthy
-
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”)
-
Just a small update:
In my solution post i wrote, that I’ve used
intel7156.efias bootfile. Just tried to image again and iPXE couldn’t get a DHCP address. So now I usedipxe7156.efiand it seems to work fine. -
@jhuesser Just note that the xxx7156.* binaries will be gone in the next release as iPXE project has fixed the issue and we decided to remove those binaries. So you need to change your DHCP server to serve
ipxe.efiwhen the next FOG version is released and you want to upgrade.Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
@sebastian-roth Probably a good idea to include that in the announcement when it comes.
-
@sebastian-roth Thank you, will keep that in mind.
-
@sebastian-roth rc12? the fun fact, i spoke today with a collegue because he asked me why i serve 7156.*
-
@x23piracy Missing since RC10 - see here: https://github.com/FOGProject/fogproject/tree/1.5.0-RC-10/packages/tftp
@Tom-Elliott We should definitely put up a big note for the final 1.5 release.
