@george1421 Just an FYI - according to Netgear none of their unmanaged switches do any sort of STP. But who knows. When I bought this I did notice they have a very similar looking switch that is managed.

I’ll get another cheap one and see if that solves the issue.

Thanks again for the help and the great project. This has been a great tool to me over many many years.

@Sebastian-Roth Excellent! Deploying now.

That’s really frustrating that a crappy NIC and cheap switch can cause such a headache.

I’m so used to having so many devices and tools at my disposal. Now, not so much.

Stone knives and bear skins…

Thanks George and Sebastian for all your help. I’m just trying to make one small step forward.

@george1421 Okay, that makes sense.

And yes, it did not get an address and then got one fine at the udhcpc command.

So, aside from “fixing” this problem - since I can get to the command line with an address and ping the server is there a way now for me to manually run the scripts to deploy the image I want?

I only have a handful of laptops I need to image at this point.

Later, I can try another network switch and see if I get different results.

@george1421 Hi,

Okay, did the deploy an image with debug.

When I got the the prompt I issued the udhcpc command and it got an address just fine. Correct subnet and everything.

lspci showed the correct device for what we are working with.

ip addr show shows two interfaces:

lo and enp2s0 and the working interface has the correct address from the DHCP pool, correct broadcast, etc.

I can ping the FOG server’s address from the target host at the command line.

@george1421 Hi - here is what I did:

The target host is not registered (never has been - new install) so instead I renamed bzImage to bzImage-old and renamed bzImageRT to bzImage.

Got into the menu and got the same result - no DHCP on that interface.

If I need to do that differently please let me know.

JF

@george1421 Also, I should add that this is all a fresh install on another laptop.

I did change the IP addressing after I did the initial install. But I believe I made all the correct changes and then ran the installer again.

Initially PXE boot wasn’t working at all due to the address change. But I went through all the wiki steps and now PXE works. Until I get to the kernel loading a NIC driver.

@george1421 Hi - here are the details I have:

#1 I am at my second home and all I have is one unmanaged Netgear switch.

#2 The adapter is a Realtek PCIe FE Family Controller

Vendor = 10EC
Device = 8136

Using the online PCI database I get this for the vendor and device numbers:

RTL810xE PCI Express Fast Ethernet controller

According to what I can find online this NIC has been supported since kernel version 2.9.16. So it isn’t new.

???

One update:

I just tried an Acer Aspire E3-111 and got the same result.

Different interface name (enp3s0 instead of enp2s0) but same result.

So I’m guessing I must have something configured wrong someplace.

Hi,

I am running FOG 1.5.8 with kernel 4.19.118 (both 64 and 32 bit)

I am trying to image a Dell Inspiron 15 3576.

I can PXE boot the laptop fine, it connects, I get the menu, and then after I pick something it boots to Linux and I get this error:

Starting enp2s0 interface and waiting for the link to come up
No link detected on enp2s0 for 35 seconds, skipping it.
Failed to get an IP via DHCP! Tried on interfaces(s): enp2s0
Please check your network setup and try again!
Press enter to continue

I cannot get past this with this laptop.

I checked all the settings I could think of.
I updated the kernel to the most recent.
I cannot find anything in the logs to help.

If anyone has an idea where to point me I’d much appreciate it.

Thanks,

JF

[quote=“Uncle Frank, post: 42045, member: 28116”]So is this causing the problem in your case??

[B]By the way, which version of FOG are you running, Jeff??[/B][/quote]

Uhh, I hate to admit it, but yes, my target disk was just slightly smaller than my original image. Interestingly, one reason I was confused and having issues after attempting to deploy an image was because FOG partitioned the disk with the desired size for the image. So when I ran a disk partitioning utility to check it the first thing I saw was an error because a partition was created beyond the limits of the disk. Weird it is even able to do that and not just error out.

So, replacing the target disk with a larger one resolved the issue for me. I need to go back and recreate my original image using a much smaller disk.

Running FOG 1.2.0

My suggestion for an added feature would be to do some sanity check for disk size and give some sort of feedback to the user if a target disk is too small.

Thanks for the help and the excellent cloning solution!

JF