040ee119 error on boot
-
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,
-
Ripau which error?
-
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=“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?
-
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.
-
Will check it against my environment to see if it helps me. Will post back tonight.
-
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. -
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]
-
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.
-
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,
-
Thank you I will try this in the morning. Getting late now. I will let you know.
-
[url]http://www.fogproject.org/wiki/index.php/Building_undionly.kpxe[/url]
If you want to give this a shot!
-
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] -
Just did that fix, having now “booting from san device 0x00” then nothing happens…
-
K3nnyfr, change the boot exit style from sanboot to exit or grub and let me know if that helps you out.
-
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 !!
-
Finally managed to get around to looking at those switches. Disabled Spanning Tree Protocol, and they now boot correctly.
Thanks Tom.
-
[quote=“Tribble, post: 29689, member: 17221”]Finally managed to get around to looking at those switches. Disabled Spanning Tree Protocol, and they now boot correctly.
Thanks Tom.[/quote]
Just poking fun.[quote=“Wolfbane8653, post: 29152, member: 3362”]Tribble check out this: [url]http://fogproject.org/forum/threads/nothing-is-working.10598/page-2#post-28305[/url]
I’m sure that the Dell Powerconnects have Spanning Tree Protocol (STP) enabled by default. Please confirm that these have be disabled.
Also there seems to be a portfast function as well. With portfast being disabled it would interfere with iPXE and not PXE[/quote]
-
Hello,
Did I miss where the 0x040ee119 error final solution was? I am trying on an HP 15T. I have tried the “latest” and “default good” on the mastacontroler page, tried the symlink ln -s pxelinux.0.old undionly.kpxe method. None have worked.My Fog box is working. I can connect with Dell Optiplex, Lenvova E545 no problem, upload/download images, just can’t boot to pxe with the HP 15T.
-
I am having the exact same problem as DanielR - Getting error 0x040ee119 on our Acer 1830 fleet, however both our Acer B113 & Acer 3830 fleets are working fine.
If DanielR is still around, did you fix the issue?
We have tested the default files with Fog 1.1.2, as well as the files available on Tom’s site under both “Latest 5Jun” and “e0478 3Jun”.
Any suggestions?[url=“/_imported_xf_attachments/1/1170_Fog 03 kpxe.jpg?:”]Fog 03 kpxe.jpg[/url]
