Microsoft Surface Pro 4

[george1421]

OK first let me say, I’m too frick’n old to try to work with these things in console mode. That text is damn small, about 4pt in size.

Short form: It werks as advertised. I can pxe boot and register the surface book via the external dock thingy. You must use kernel 4.11.6, the stock kernel that comes with FOG 1.4.4 4.11.0 does not werk. You can tell if you have the older kernel (at least with the surface books is that they onboard keyboard does not function correctly.

At the moment I think the dock’s model number is PF3-00005

The longer form will have to wait until tonight. I have color pictures and logs to post, but no time at the moment.

[mwarner]

@sebastian-roth I got you two PCAP files on a different VLAN with an IP helper on it that captured more information from both the HP and the Surface. Here is a link to a Google Drive folder containing those files. I’ll try to leave them up for future reference to this article.

[Sebastian Roth]

@mwarner I am sorry to say this but the PCAPs don’t show the DHCP answer packets (offer and ack). So it’s missing very essential information.

Have you looked into booting a live Linux OS on the Surface just to see if that can properly bring up the network interface and retrieve an IP via DHCP - see my last post.

[george1421]

@sebastian-roth When I was testing earlier today, I usb booted FOS to skip th pxe boot stuff. I can say right from the start, iPXE did work correctly, but when the linux (FOS) kernel started it would not pick up an IP address, and the on board keyboard would not respond. I plugged in a usb keyboard and I was able to navigate, but the network would not come up.

I played around a bit with the dock and disconnecting it and reconnecting it. The FOS kernel saw those changes. It reported the nic in the dock as a Real tech nic. I can’t remember why I thought to update the kernel other than I was using a USB FOS stick created last may. Once I booted on USB FOS with the 4.11.6 kernel the network ms adapter picked up an ip address. Once that was done I was able to register the target computer.

@mwarner on your fog server linux console, will you navigate to this path: /var/www/html/fog/service/ipxe and once in there key in files bzImage and post back the version number reported?

[mwarner]

@george1421 The command reported back this:

bzImage: Linux kernel x86 boot executable bzImage, version 4.13.4 (root@debian64) #2 SMP Wed Oct 18 15:26:04 EDT 2017, RO-rootFS, swap_dev 0x7, Normal VGA

How can I upgrade to 4.11.6?

[george1421]

@mwarner I got them from the following links.

wget https://fogproject.org/inits/init.xz
wget https://fogproject.org/inits/init_32.xz
wget https://fogproject.org/kernels/bzImage
wget https://fogproject.org/kernels/bzImage32

Just make sure you save your current files before overwriting them

[mwarner]

@george1421 Good news and bad news!

I was able to get the DHCP working using the new inits/kernels. I was able to register the host and run the compatibility settings option just fine.

Unfortunately, I was not able to run a capture task. Below is an image of the result.

I have no clue what could be going on, should I run another tcpdump?

I should also add that there is a substantially long pause between where it says “OK” and where the error starts - I’d say maybe 30-60 seconds.

[george1421]

@mwarner One question, are you booting via the USB stick? If so, you MUST schedule a task on the FOG server before you attempt to boot with usb stick. While the error is a bit cryptic, that is the typically the error.

If you ARE booting via the usb stick, why? I was able to pxe boot the surface book and capture without issue.

[mwarner]

@george1421 I am booting via USB stick. I tried PXE and it didn’t seem to work - same errors as before. I created the task before booting.

[george1421]

@mwarner And so it works now?

The error message basically translates to I tried to deploy an image but there wasn’t anything for me to do (i.e. request type: null [nothing to do]). Same error as before as in your are still deploying the old bzImage from your fog server?

[Edit] Oh I see you updated to fog 1.5.0RC10 a few posts ago. So you should have the latest kernel on your fog server. There may be an issue with the usb boot and fog 1.5.0. I have to look at it, but the developers change (in 1.5.0 to add the ability to deal with http and https installs of fog). That maybe why its returning an invalid null type.

[george1421]

Looking at the code in the grub.cfg file, lets try to update it as such.

change

<snip> ramdisk_size=127000 keymap= web=$myfogip/fog/ boottype=usb

to

<snip>ramdisk_size=127000 keymap= web=http://$myfogip/fog/ boottype=usb

Note the http:// inserted just before $myfogip. You need to do that for every row that has web=$myfogip/fog/ in it.

[mwarner]

@george1421 Yes, the DHCP works now when I use the USB stick. I’d still prefer to go without it, but it can suffice for now.

What do you recommend the next step should be for me? Should I wait for the next stable version of FOG to be released? In the meantime, should I go back to bzImage 4.13.4?

[mwarner]

@george1421 where should this grub.cfg file be located?

[george1421]

@mwarner Grub.cfg is on the usb stick. Its in the boot/grub/grub.cfg path.

[mwarner]

@george1421 Unfortunately that didn’t seem to fix anything. Should I revert my kernel back to 4.13.4?

[george1421]

@mwarner You can or leave it at 4.13.6 since that has proven to work with the surface devices. When 1.5.0 stable is eventually released it will contain that or a later kernel anyway.

I guess I need to look into why 1.5.0RC10 is giving us an issue with USB booting.