040ee119 error on boot

Tribble

So, you’re saying that the issue would only appear when a PXE booting device using Undionly.kpxe is directly attached to a managed switch with STP enabled. And that adding an unmanaged, Non-STP switch as an intermediary between the PC and the managed switch can prevent the problem because iPXE communicates directly with the switch for DHCP? Therefore since the PC is not “directly” communicating with a switch that has STP enabled, there is less delay establishing a connection with the DHCP server.

Now, I will admit that i do notice a shorter time to pick up DHCP when i have the intermediary switch in place, but i never realized that switches had anything to do with DHCP packets and requests other than routing them to the correct ports.

I won’t be able to get on those switches until possibly friday due to our DR testing schedule, but i’ll be sure to let you know what happens. I know we haven’t done much if any customizing to those managed switches from their default state, so STP being enabled is certainly possible.

Tom Elliott

[quote=“Tribble, post: 29175, member: 17221”]So, you’re saying that the issue would only appear when a PXE booting device using Undionly.kpxe is directly attached to a managed switch with STP enabled. And that adding an unmanaged, Non-STP switch as an intermediary between the PC and the managed switch can prevent the problem because iPXE communicates directly with the switch for DHCP? Therefore since the PC is not “directly” communicating with a switch that has STP enabled, there is less delay establishing a connection with the DHCP server.[/quote]

The intermediary switch just makes the connection between your DHCP server and the FOG Server so things can still boot.

iPXE does not communicate directly with the switch for DHCP. PXE boot’s, get’s DHCP and then loads the undionly.kpxe file. After this point, to use the “new” protocols within iPXE, ipxe requests it’s own dhcp information. The timeout between PXE and iPXE is vastly skewed. iPXE must wait for proxyDHCP address, then if those “timeout” it requests regular DHCP. Mind you these are in the milisecond to second intervals of “waiting”. The STP “blocks” the DHCP address during this time, unintentionally.

STP works like this:
Establish that there is a link on the port. Clear the port, enable forwarding to the port, PXE doesn’t mind all of this and will ‘wait’ for a much longer time to get DHCP. This isn’t all bad, BUT, when iPXE is re-requesting dhcp, STP ‘blocks’ the connection by, disabling and resetting the port, re-open the port, re-forward the port. Sometimes, this action causes a longer delay than what iPXE is expecting so iPXE DHCP requests ‘timeout’.

[quote=“Tribble, post: 29175, member: 17221”]Now, I will admit that i do notice a shorter time to pick up DHCP when i have the intermediary switch in place, but i never realized that switches had anything to do with DHCP packets and requests other than routing them to the correct ports.

I won’t be able to get on those switches until possibly friday due to our DR testing schedule, but i’ll be sure to let you know what happens. I know we haven’t done much if any customizing to those managed switches from their default state, so STP being enabled is certainly possible.[/quote]

bveiga

hi i´m getting the error “could not start: download operation not supported” but this only happens in one domain, in the others we have the same server with no problems,the switches are equals on both domains(cisco), can anybody help me please?
best regards

Bruno

[url=“/_imported_xf_attachments/0/905_fog.png?:”]fog.png[/url]

Wolfbane8653

[quote=“bveiga, post: 29369, member: 24091”]hi i´m getting the error “could not start: download operation not supported” but this only happens in one domain, in the others we have the same server with no problems,the switches are equals on both domains(cisco), can anybody help me please?
best regards

Bruno[/quote]

This is not the iPXE “0x040ee119 error” please make a new thread.

RipAU

Hi,

Not sure if this helps at all, but I am finding even when building from the master iPXE source with the iPXE script that I am getting the same error, but when I forgot to add the option for CONSOLE_VESAFB into the build, all of a sudden I could boot my ipxe.kkpxe file in my DNSMasq server. As soon as I built it back in the error returned

The resulting menu is ugly but it does boot.
Not sure if this helps or not?

Cheers,

Buddy

Ripau which error?

RipAU

Sorry I jumped ahead of myself.
I was getting the error 0x040ee119 error when using the iPXE files from Toms website. ([url]https://mastacontrola.com/ipxe/[/url])

But what I did notice was that if I leave the CONSOLE_VESAFB out of the build and write my own iPXE script into the embedded ipxe.kkpxe file it seems to boot with my laptops. (Dell E5410)

[CODE]#!ipxe
ifopen net0
dhcp
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac ${net0/mac}
param arch ${arch}
chain http://10.0.0.253/fog/service/ipxe/boot.php##params
[/CODE]

if I use the following fog iPXE script it seems to fail with that error.

[CODE]#!ipxe
sync --timeout 500
dhcp || reboot
chain default.ipxe || exit[/CODE]

I don’t mean to derail this thread if I’m not posting into the right place.

:edit:

I was using my own server as well as [url]https://rom-o-matic.eu/[/url] to make the files with the embedded script options.

Tom Elliott

[quote=“RipAU, post: 29482, member: 24459”]Sorry I jumped ahead of myself.
I was getting the error 0x040ee119 error when using the iPXE files from Toms website. ([url]https://mastacontrola.com/ipxe/[/url])

But what I did notice was that if I leave the CONSOLE_VESAFB out of the build and write my own iPXE script into the embedded ipxe.kkpxe file it seems to boot with my laptops. (Dell E5410)

[CODE]#!ipxe
ifopen net0
dhcp
cpuid --ext 29 && set arch x86_64 || set arch i386
params
param mac ${net0/mac}
param arch ${arch}
chain http://10.0.0.253/fog/service/ipxe/boot.php##params
[/CODE]

if I use the following fog iPXE script it seems to fail with that error.

[CODE]#!ipxe
sync --timeout 500
dhcp || reboot
chain default.ipxe || exit[/CODE]

I don’t mean to derail this thread if I’m not posting into the right place.

:edit:

I was using my own server as well as [url]https://rom-o-matic.eu/[/url] to make the files with the embedded script options.[/quote]

Interesting,

Basically your compiled script is what the default.ipxe script does.

I’ll make a modification to the ipxescript and put those undionly.kpxe.

Can somebody test and see if it helps?

Tom Elliott

Rebuilt, only change based on suspicion of the issue would be removing the sync --timeout command from the default.ipxe.

link to try:
[url]http://mastacontrola.com/ipxe/latest[/url]

My suspicion is it’s not a CONSOLE_VESAFB problem, but that your CPU’s don’t like the sync command. We don’t really need it anymore, it was when we KNEW it was a timing issue and an attempt to delay that timing. Hopefully my theory’s correct and will work now.

Buddy

Will check it against my environment to see if it helps me. Will post back tonight.

RipAU

Ok just tested with each file in --> [url]http://mastacontrola.com/ipxe/latest/[/url]

I’m finding the ipxe.kkpxe still has error 040ee119 but the undionly.kkpxe had an error with default.ipxe error 3d126001 (Dell OptiPlex 755 and Dell Latitude E5410)
I didn’t get the error code for the rest of the files but I can re-test and write them down if needed.

Buddy

Just tested them all as well. undionly.pxe throws it in a boot loop (but still gets error (op not sup)- flashes really fast). ipxe.pxe does something new (see image below). The rest just did the operation not supported. The ipxe.pxe error doesn’t make a lot of sense though as seen in second pic the path is correct.

[url=“/_imported_xf_attachments/0/913_ScreenShot535.png?:”]ScreenShot535.png[/url][url=“/_imported_xf_attachments/0/914_ScreenShot536.png?:”]ScreenShot536.png[/url]

Buddy

The above was off a dell 390. Just tested them all on hp 8300 elite:

unidonly.pxe - - puts it into a boot loop

All others = operation not supported.

RipAU

Hi guys, as a quick workaround till the iPXE issues are working I posted this in another post.
Might help a few people?

[url]http://fogproject.org/forum/threads/ipxe-issues-work-around.10727/[/url]

Cheers,

Buddy

Thank you I will try this in the morning. Getting late now. I will let you know.

Tom Elliott

[url]http://www.fogproject.org/wiki/index.php/Building_undionly.kpxe[/url]

If you want to give this a shot!

Tom Elliott

If you’re still having issues with that try this:
[url]http://fogproject.org/wiki/index.php/Chainloading_PXE_to_iPXE_using_pxelinux.0[/url]

K3nnyfr

Just did that fix, having now “booting from san device 0x00” then nothing happens…

Tom Elliott

K3nnyfr, change the boot exit style from sanboot to exit or grub and let me know if that helps you out.

K3nnyfr

We’ve messed up totally, we’ve started reinstall completly the OS (Debian) + FOG in 1.0.1.
You can delete my post, we’ll see that next Thurdsay (Week-end + day off + 2 days of meetings)

Thanks for your help !!

040ee119 error on boot

251

11.7k

17.2k

154.7k