@Wayne-Workman This absolutely worked like a charm. Found that MAC was still in the hostMAC table, deleted it, and Bob’s your uncle. Really appreciate it Wayne! I’d love to update to the latest SVN but we’re in the middle of our busy time building and deploying images so it will likely have to wait until the fall. Thanks again!

@george1421 Thanks george, that did the trick.

@george1421 Thanks george, that did the trick.

@george1421 Thanks, I’ll look into that. No need to provide the custom kernel info if that isn’t what I need.

@george1421 Sure, we had new ProBook 750 G8s arrive that we could boot with. Here’s where we stalled at: https://photos.app.goo.gl/EbG6kTro1eAJStR67

Tried all the latest kernels and had no luck.

Hi folks,

I’m trying to build a custom kernel based on the steps here, but when I get to the makefile steps I’m getting some error 127 stuff popping up. I’m well out of my depth here so I could be doing something completely wrong, just looking for some friendly advice. Screenshot:

https://photos.app.goo.gl/uJVA2YjcNBxW14hf8

Thanks!

I can report that both using the USB3 key method and enabling VMD worked for us as well. Great finds!

@sebastian-roth said in HP ProBook 640 G8 imaging extremely slowly:

@Dungody Thanks for the update and pictures! Definitely looks like you deploy to the NVMe driver. I still can’t see why a USB key plugged into the ProBook would make a difference. Though it sounds like it does.

In the picture I notice that you have partclone version 0.2.89. In FOG 1.5.9 we use the newer partclone 0.3.13. So I am wondering which version of FOG you use and if that is also playing a role here.

@Jacob-Gallant Would you want to give that a try as well?

I’d be happy to test this (and @diegotiranya storage controller settings) when I can, but we’ve been locked down due to COVID where I am so I can’t get back into the office in the near term. Looks like you have a few other testers now though! Glad I’m not the only one haha.

@sebastian-roth Thanks, I appreciate your efforts!

@sebastian-roth Thanks again Sebastian, here is the results of that command. Unfortunately we see the same network performance issues with this kernel.

https://photos.app.goo.gl/6Ur7aNkjF92MEKAi6

@sebastian-roth Here you are. https://photos.app.goo.gl/uJJKgG4PSPHY8kQJ6

@sebastian-roth Hey Sebastian, the mtu size was 1500 when I ran than command. Unfortunately when I used the patched kernel I received a “no network interfaces found” error, did I miss a step?

https://photos.app.goo.gl/ieBtBtrgCReWB8BU6