Topics created by Interrupt

@george1421 said in issue with netcard of dock gen2 of lenovo l390:

@JJ-Fullmer The r8152.c from the torvalds github site failed to compile on 4.19.65, I’m suspecting its for a later release of linux. The version from the torvalds site was 1.10.10. The version in 4.19.65 was 1.9.9 of the realtek driver.

I was able to compile the realtek driver from the wget github site. This version is 2.12. Here is a link to that kernel with the 2.12 driver built in. I also enabled the usb-c code in the kernel that appears to have not been set. I don’t know if its relevant, but it should be on for other applications. https://drive.google.com/open?id=1wZwwOwbEr0nR3mnPLKg7AsulwJaGhO0A

Download this as bzImageRT (watch your case) and copy it to the ipxe directory with the other kernel images. Manually register the host and then in the host definition add in bzImageRT as the kernel for that host. Then pxe boot into FOS Linux debug mode to see if the network adapter inits correctly with this updated driver.

@Interrupt Give this solution a try, download the kernel @george1421 made and set it on that host. It worked for me with the lenovo usb-c ethernet adapter, it stands to reason it will work for the dock too.

Threads with the same original issue:
https://forums.fogproject.org/topic/8711/host-won-t-image-automatically-after-full-host-registration-and-inventory
https://forums.fogproject.org/topic/8721/no-imaging-after-host-registration
https://forums.fogproject.org/topic/8669/host-registration-doesn-t-start-image

THe slots are correct, for the time they check in.

Basically, you are playing against a clock. When one system checks in, followed by another, the queue number should change. 0 before me, typically, means that there is one system ahead of it and when that one system completes it will begin moving forward.

But lets say you’re imaging 10 systems, and have 5 in queue. It’s fully possibly two systems complete, while the other five are still in queue. One might say 0 before me already, and the others in the proper order saying 1, 2, 3, 4 etc…

But when those 2 systems complete, now there’s 2 open slots, but they’re not ready to be used quite yet. So two of the 5 systems might end up saying “0 before me”, and as soon as they can, they will start the tasking.

Also remember that there is a timeout for wait time. This is so systems waiting in line can continue on even if another system that was tasked before it becomes unusable. If we only kept in track, anything behind that one system might never get completed because they’re all waiting for that one system to complete. So some of the numbers are a bit odd.

It’s also possible that both systems checked in at more or less the same time. So both systems might say the same thing simply because there’s not a nice way to actually determine who was first or second. Partly because statements to the SQL server may take longer from one system to another (even though they’re doing the same thing).

@Wayne-Workman

Thx Wayne
I’ll give it a try 🙂

@Interrupt said:

I updated to the new SVN (3587) and the problem is gone.
MAC addresses are now imported from the CSV. Thanks!

Thx for the report 😉

Thank you Tom! Works like a charm