@george1421 Unfortunately that didn’t seem to fix anything. Should I revert my kernel back to 4.13.4?
Latest posts made by mwarner
-
RE: Microsoft Surface Pro 4
-
RE: Microsoft Surface Pro 4
@george1421 where should this grub.cfg file be located?
-
RE: Microsoft Surface Pro 4
@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?
-
RE: Microsoft Surface Pro 4
@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.
-
RE: Microsoft Surface Pro 4
@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.
-
RE: Multiple Partition Image to Blank Hard Drive
@sebastian-roth Unfortunately it has been lower on my priority list right now, we are undergoing a lot of changes as a business right now. I’ll update ASAP.
-
RE: Microsoft Surface Pro 4
@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?
-
RE: Microsoft Surface Pro 4
@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.
-
RE: Microsoft Surface Pro 4
@sebastian-roth I ran a tcpdump with a different device to see what would happen. I tried using one of our HP desktops and it captured all DHCP and TFTP packets properly as you’d expect, with the same UEFI PXE boot over IPV4 settings as the Surface. If you want to see for yourself, I’ll post the PCAP file but otherwise you can take my word for it: it worked just fine as you’d expect and even did a successful deploy and capture.
I’m not sure what Microsoft is doing with this particular NIC on this dock, but I think that somehow it’s blocking DHCP in PXE boot somehow because that’s the only explanation that I can think of with my current knowledge of networking. As you can see from the PCAP file I posted, the device even has an IP address of 10.241.70.172 upon connection to the FOG server - SOMEHOW - but does not get it via DHCP as there are no DHCP packets. As if it were cached or something. I’m so confused as to how this is even functioning.
Furthermore, if I boot into Windows, the wired connection works just fine - so it’s not a defective dock or anything. It works in Windows, just not in PXE. Absolutely bizarre.
PS: I’ll have to purchase a hub because I don’t believe we have one in house. We have a switch, but not a hub.
-
RE: Microsoft Surface Pro 4
@george1421 Awesome! I’ll be interested to see what you can pull off and if it will help with our case. Unfortunately our docks aren’t USB-C though. We have the Surface Pro 4’s (2-in-1 device) that have a proprietary plug for the dock connection. It’s definitely not USB. Probably why USB NIC option isn’t working.