@sebastian-roth

Sweet. The default setting for the loglevel is 4. Taking it down to 3 no longer produces those USB errors. Thank you. The computer does register and I can image but those USB errors were extremely annoying. Seems like this will suppress those messages and works just fine now.

@m144 Thanks for that. OMG, how many new USB devices are there just by plugging into the dock. Yeah the ID 045e:07c6 seems about right. Though this has been added to the kernel (official and our custom build one) source code long ago.

Re-reading what you said before I feel this is a really hard one to nail down. Seems like we have the driver right in the kernel and it does come up with an IP part of the time but not always. Not really sure where to go from here. Hmmmmm

I can now confirm that the Lenovo Mini-Ethernet Extension Adapter (p/n: sc10a39882bb, fru: 04x6435) also works in both UEFI and Legacy network boot.

@george1421 It is a HP Prodesk 400 Mini G3 MFR part# 2RN27UT#ABA
The nvme was manually added, not something that comes with it.
But the Intel Optane setting was new to me, and this wasn’t my first prodesk 400 mini g3. But they did just change the mfr part # for this configuration and stop sending out the old one, so it’s probably related to this.

From what I read briefly about the intel optane feature, it’s a part of the 7th gen intel core cpus chipset or requires it or something like that.

@kotazzu said in HP Prodesk 600 G3 mini:

No problems when imaging Win10, just Ubuntu.

Sorry but that doesn’t make any sense!

Intel I219LM as ethernet card. […] Fog 1.2 , latest kernel installed.

Upgrade to FOG 1.4.4 and it should work all fine!

@imagingmaster21 That is probably a bit overkill for the FOG server. But as they say more is always better.

Just make sure you order it with an array controller that is compatible with linux. The cheap windows only raid controllers (SXXX series adapters) won’t work with linux, so don’t even try if you are installing linux on bare metal.

@sebastian-roth said in Linux kernel:

Just not sure if it’s worth sending it around the world as I am located in Germany.

His org could just buy you one and have it shipped to you. Of course you are deserving of much more than a crap hardware model, Sebastian. 🙂

@george1421
I got it fixed, seems to be working.

@smcadm Seems like google is your friend here - see this:

Updating the Bios firmware has done the trick and PXE boot is working now…

I really don’t understand what’s wrong with HP notebook’s firmware?! We’ve see the weirdest things happening (fatally wrong initialized registers would cause the linux kernel to freeze when booting on the HP x2 210 devices - they send us a patched firmware more than a year ago but have not released a patched firmware officially yet…). So to make a long story short, I really wouldn’t wonder if PXE booting is going to work for you after firmware upgrade.

#wiki worthy

@Psycholiquid thank you for the pictures and steps! I will get them included into the wiki when I can. @moderators and @testers if you have wiki access, you can help too!

@abrowning just for clarity, there is an issue between the linux kernel, uefi mode, and Dell systems using the intel sata adapter when the sata adapter is in “raid-on” mode. Switching the sata adapter to achi mode will (mask) the issue. This is a documented linux kernel issue and not specifically a fog issue. Commercial linux distributions suffer from the same issue.

NOTE: I moved all the posts about testing the iPXE binaries: https://forums.fogproject.org/topic/10789/boot-file-testing-for-sr

@Tywyn As suggested try updating the machine’s firmware or disabling ACPI in the linux kernel. For the later add acpi=off as kernel parameter in the host’s settings and see if the messages are gone. As George already said, those messages shouldn’t be a show stopper.

@kandresen Which part was it? Just for those that might find the thread in the future.

@george1421
Yeah… I understand the whole meeting thing. Sucks to start working on something and constantly get pulled away on other less interesting things.

I’ll look at that article and see what I can do to integrate it into my processes.

Will report back when I have more information to share.

@sebastian-roth

Hi sorry, I couldn’t answer any sooner.
“Nevertheless we ought to try out using the SNP binary (debug enabled - DEBUG=snp:3,nii:3 to start with). So find 01_snp.efi here. Just give it a try and post pictures or video. Make sure when you take those to place the camera or phone on a stack of books in front of the screen so we have a good picture.”

Here you go, not much to say from my side but here goes: video

Thanks!

@Crixx Did you get to take a picture of the error yet?

@joesay You are welcome! Feel free to ask again and even open new threads if you run into issues again. We will try to help and get things fixed!

@mrcur Great!! rEFInd is a great boot loader (once you tell it where to and not to look).

What’s the contents of that system’s image d1.fixed_size_partitions.

What’s the contents of:

cat /images/<imagename>/d1.fixed_size_partitions cat /images/<imagename>/d1.partitions cat /images/<imagename>/d1.minimum.partitions

This, too me, sounds liek the image was captured before our tests for “fixed” partitions became a little more proper and it resized something that was expected to be fixed size. What partition was it giving this issue on?