Imac 27" ipxe boot

[george1421]

I find its suspicious that it says waiting for link-up on net1? What happened to net0?

Since I am ignorant of this hardware are there two network adapters in this Mac? Did it pick the wrong one to init?

My intuition is telling me this could be a spanning tree issue too or the iPXE kernel doesn’t have the driver for this nic interface.

[Tom Elliott]

@george1421 If I remember correctly, is it quite possible to simply use the ipxe7156.efi file? I don’t know what nic’s will or won’t require that particular bootfile but I think this might be the best place to start.

[george1421]

@Tom-Elliott I agree that iPXE kernel seems to work well with some of this misbehaving hardware (i.e. surface pros for one)

[Seb B]

@george1421

Hi! Net0 is the wireless interface.
It does try to connect net0 but won’t get any further than that which is totally normal.

[Seb B]

@Tom-Elliott
Thanks, I’ll try and give it a try today (it’s morning here).
I’ll keep you informed with the results.

[Seb B]

@Tom-Elliott @george1421
we tried to use ipxe7156.efi, it did load but the error is still here.

the only difference is the response for the other interface which is now

Could not open net0 Input/Output error (http://ipxe.org/1d6a4698)

But the error on the ethernet interface is the same.

[Sebastian Roth]

@Seb-B Please check the LEDs on your switch while this is happening. Are those really ON (link up) all the time? Maybe this is some kind of Spanning Tree issue…

[george1421]

@Sebastian-Roth said in Imac 27" ipxe boot:

@Seb-B Please check the LEDs on your switch while this is happening. Are those really ON (link up) all the time? Maybe this is some kind of Spanning Tree issue…

I thought it might be a spanning tree issue too, but the error is the link is down (assuming the link light is off) and not the link is up but can’t pickup an IP address. Unless those Macs do things funny. But checking the link light is a great idea and not assume that its working.

The link light will wink as the iPXE kernel starts, but should not go out and stay out.

[Tom Elliott]

You might be running into what another person informed me of (which prompted my creating a 10sec delay ipxe file).

So the initial IP comes up from PXE, then hands off to iPXE which has to drop the link and re-open for it to get a dhcp (initial pxe I think is bootp?) that can use different protocols. In some cases the down/up is too fast, and the motherboard essentially hasn’t had time for the device to go down before the system is requesting the new dhcp request. (Leaving the device seeming to be marked in down).

Please try the ipxe.pxe file from the /tftpboot/10secdelay/ folder and see if it at least helps?

[Seb B]

Hi!

We’ve tried using the ipxe.pxe file from /tftpboot/10secdelay/ folder and this error :

Could not open net1: Input/Output error (http://ipxe/org/1d6a4698)

It then restarts the device initialisation and tres net 0 which appears down.

Could it be that the driver for the card is missing from the pxe file?

[Quazz]

@Seb-B Can you try using the snponly.efi files? Try all versions (delay, 7156, regular)

[Seb B]

@Quazz
Hi, we just tried with all snponly files and each time got

Configuring (net0 38:c9:86:12:xx:xx)..............No configuration method succeeded (http://ipxe.org/040ee186)

as a response.

[george1421]

@Seb-B said in Imac 27" ipxe boot:

Well this is a different/interesting error.

This is saying that it can’t get a dhcp address on interface net0. But what is interesting is that it now picks up the mac address of the nic. This tells me that the nic is initializing (!!). Can you confirm what device is 38:c9:86:12:xx:xx

If this was a Dell box, at this point I would say your issue could be related to spanning tree, where the building switch is not using one of the fast spanning tree protocols like RSTP, fast stp, etc.

[Tom Elliott]

If my memory is serving me correctly, there was a similar thread about this in the past, I’ll see if I can dig it up from the abyss. If I am remembering correctly they other person got it working.

[Seb B]

@george1421

Hi,
Yes the mac address of the device is correct.
I don’t think it could be a spanning tree since
a - I a m plugged on a switch port with no spanning tree
b - other iMacs(21.5") on the same port have no problem getting through this step
c - I think using the efi file with the 10sec delay would have worked if this was the case (not sure though)

Once again, I could be wrong but spanning tree issues don’t seem logical to me in this case.

Thanks anyhow.

[george1421]

@Seb-B is the 21.5" iMac an older generation than the 27" iMac?

With the efi kernel that shows the mac address, please install an unmanaged switch between the building switch and the target computer. This is a quick test to see if its a spanning tree/green ethernet issue.

Understand we are now to the point if guessing a bit, since this is not a FOG issue but an iPXE booting issue.

As long as we are guessing, is the firmware up to date on this target computer?

[Seb B]

@george1421

The “working” Imacs are from late 2014 while the “not working” ones are from late 2015.

I’m already plugged on a non manageable switch, that’s what I was trying to tell you in my last reply.
Yes I checked the firmware for the IMac and it is up to date.

As for the guessing, I checked this post and checked the cable integrity just in case but to no avail so far…

[george1421]

@Seb-B On the windows side, we’ve seen newer nic adapters support some more advanced functions (like green ethernet 802.3az) that seems to be causing issues with pxe booting. The unmanaged switch also blocks this type if pre-link protocols (which is good for us).

When you get the error pxe booting does it give you an option to press ‘s’ to get to an ipxe command prompt?

[Seb B]

@george1421

Yes it does, I tried some commands but I’m not really familiar withe the ipxe environment.

[george1421]

@Seb-B OK, its been a while since I had to mess with the iPXE kernel. But the first thing I would try is to get to the iPXE command prompt. Wait 30 seconds and then key in dhcp net0 that will instruct the kernel to try to pick up a dhcp address.

I’m going to have to create a similar issue here in my test lab to see if I can remember the commands to confirm the network adapter is ready. But starting with dhcp after 30 seconds will tell us if there is a timeout involved.