Fujitsu Lifebook U7511 PXE Boot

[Travi]

@sebastian-roth said in Fujitsu Lifebook U7511 PXE Boot:

@travi said in Fujitsu Lifebook U7511 PXE Boot:

Exactly, its showing only the loopback.

What do you mean by that? In the pixture we clearly see eno1 and obviously an IP address on that network interface. Why do you mask the IPs? Security by obscurity (Bruce Schneier)!?

Edit: Wait a second, why do we see Dell in that picture while this topic is about the Fujitsu Lifebook U7511?? You need to run those commands on the Fujitsu Lifebook U7511 and post a picture of the output here!!!

Sorry for masking the IPs. I was trying on 2 different PCs to see the difference between both and have posted the wrong one.

[george1421]

@travi Well that is good (and bad) you posted the wrong picture because it should have been working on that old network adapter.

@Sebastian-Roth Good catch on the system swap.

Network adapter [8086:15fb] first appeared in linux kernel 5.5. So the current kernels offered by FOG should work.

From your latest picture it appears that FOS Linux is seeing the network adapter because it has a device name [enp0s31f6]. But ip a s is not giving us an ip address.

I still don’t understand why in your initial picture you are getting “No network interface found” and yet we see it listed in ip a s. It not having an ip address at the moment, we can test for.

At the fos linux prompt where its telling you it had the network driver but no IP address. If you are booting this fresh get to the fos linux command prompt and then wait 30 seconds then run this command: /sbin/udhcpc -i enp0s31f6 --now and see if it picks up an IP address. Lets see if time fixes what is wrong.

[Travi]

@george1421 Strange, now its getting an IP

[george1421]

@travi Ok since you are in debug mode just key in reboot the debug task is still activated on the FOG server so it should just reboot you into debug mode again. As soon as you reach the command prompt key in ip a s and see if you have an IP address. If no, wait 30 seconds and then issue the /sbin/udhcpc -i enp0s31f6 --now to see if time for sure fixes it.

If the answer is YES to time fixing the network problem, lets look into the network switch. This issue above is sometimes an indication of standard spanning tree being used on the building network switch, where one of the fast spanning tree protocols should be used (portfast, fast-STP, RSTP, MSTP, or whatever your switch mfg calls it). Another simple test for a spanning tree issue is to put one of those dumb/unmanaged inexpensive switches between the building network switch and the pxe booting computer. If that inexpensive switch fixes the problem, then it is for sure a spanning tree issue.

[Travi]

@george1421

I will put one switch between the Building one and let you know if this fixes the issue.
Thank you for your quick reply and your help.

[george1421]

@travi Well hold off for a minute. If you are able to get an IP address right away (as shown in the picture) then its working fine.

Why are we getting that message about network adapter not being found.

With this same exact computer on this same exact network cable let do this.

Go into the FOG UI and delete the current task. Then reschedule a new task with this computer, but this time without debug enable. Does this image correctly now?

I’m having doubt to why this failed.

[Sebastian Roth]

@george1421 said in Fujitsu Lifebook U7511 PXE Boot:

If you are able to get an IP address right away (as shown in the picture) then its working fine.

Well I don’t think it’s right away. In the picture we see it fail on the first manual try…

[Travi]

@george1421 said in Fujitsu Lifebook U7511 PXE Boot:

@travi Well hold off for a minute. If you are able to get an IP address right away (as shown in the picture) then its working fine.

Why are we getting that message about network adapter not being found.

With this same exact computer on this same exact network cable let do this.

Go into the FOG UI and delete the current task. Then reschedule a new task with this computer, but this time without debug enable. Does this image correctly now?

I’m having doubt to why this failed.

I did this, unfortubalety it’s not working, I get the same error. Tomorrow I will try to boot with a USB Network adapter to see if this will fix this issue.

Thanks

[Sebastian Roth]

@Travi Did you look into the things George mentioned before? Switch configuration (spanning tree), testing with a dumb mini switch in between?

[Travi]

@sebastian-roth Issue hase been fixed by using the 5.15.19 kernel. Many thanks @george1421 and @Sebastian-Roth for the quick support.