Hi Jaymes,

have checked the manufacturers web-site and the BIOS on the machines is already the latest. As far as the switches go though, because I am having to remove the HDD to image it in another chassis, I have been doing them one at a time. All on the same switch, same port. I still don’t understand why every other unit could be imaged on this LAN cable except the T5760 Acer.

Also it doesn’t explain why one out the twenty works fine and can be imaged in its own chassis, the other nineteen won’t…

Kind Regards,

Frank

Its looking like a possibility that there is some issue with the Acers getting an IP at iPXE handover.

[COLOR=#ff0000]Tom Elliott said: System will only reboot, if it can’t pick up DHCP. 0x040ee119 or something like that.[/COLOR]

It is strange though that I have one unit which PXE’s fine and 19 that will not. They are all on the same BIOS revision, same version of PXE Rom. Only thing I noticed during boot was all the others come up with what appears to be a valid GUID during DHCP. The one that works shows a GUID of all FF’s.

Could this be the reason? Can’t really see how, but it is the only difference between them.

Hi Robin,

the issue I have is with Acers. However, EUFI boot is disabled and has always been disabled because we were working with an older version of FOG. AHCI mode has been set to IDE (equivalent to LEGACY in other BIOS’s). Something in iPXE is not compatible with these laptops for some reason…

Kind Regards,

Frank

Thx Ch3i,

i am not completely surprised HP do something non-standard. We have some Elite series ones which luckily work OK.

This is something different. These laptops used to work with the old FOG 0.29 server fine. It is definitely an issue with the way FOG now uses iPXE. Hopefully Tom et al, will come up with a solution. If secure boot is starting to be an issue also, then something will need to be done about fixing FOG to work with it. More and more newer PC’s and laptops are using this EUFI boot which appears to be hit and miss whether FOG will work or not.

Newer BIOS’s will not even let you “Legacy” boot now which was a workaround to getting an image put onto a computer with FOG.

Hi All,

Have trunked the TFTP files and copied them as suggested by Tom and Robin. This has not changed the situation though. These darn Acer laptops will still not iPXE correctly…

Any further ideas about this issue? Having to remove the hard drives and image them in a chassis that does iPXE.

Hi All,

Thx for the SVN info Robin. So the only way to try out the new trunk KPXE files is to upgrade our fog server?

Tom, I tried ipxe.pxe and seem to be still getting the "Error {some sort of hex error code} {some further text I cannot catch}, so I swapped back to undionly.kpxe, so is trunk the only way to go now?..

Thanks Tom,

I’ll try ipxe.pxe as a bootfile for DHCP.

I am a bit of a noob with Linux. How do obtain and use the files in trunk.

Hi Tom,

No, as I said it only seems to be this particular model of laptop. I took the hard drive out of it, installed in in a different model ACER (P255M) and downloaded an image to it (turned 255 off after imaging complete). I swapped it back to its original chassis booted it and am in the process of updating it ready to capture. Which I am unable to do at the moment and will have to juggle HDD’s to get it uploaded.

Coincidentally we had the issue with infinity loop on everything until we turned on PORTFAST.

The Atheros bootrom seems to pick up an IP because some addresses appear on the screen (again too quick to catch) until it hands over to iPXE. The error message seems a lot faster to disappear when using undionly.kpxe because I only managed to catch it when i switched to undionly.kkpxe so was it because undionly.kkpxe doesn’t exist? Did I use the wrong bootfile name?

Hi All,

I’ve been looking around the forum for answers to this but none that I found fix the problem for me.

It is strange, other hosts work fine. Just seems to be this particular model of laptop. I have tried using undionly.kkpxe as the bootloader in DHCP but get same issue. A long row of dots accumulate after the “Configuring (net0 {MAC Address})” then an error flashes on the screen too quick to read and the laptop reboots. The error message tags itself to the end of the dots. It seems to be "Error {some sort of hex error code} {some further text I cannot catch}. I have tried many times to pause the screen just as it appears but have been unsuccessful. I could try videoing it if you think it may be important to know what the message says.

Originally I thought it may be a dodgy kernel as our old fog server 0.29 used to image these with pxelinux.0 fine. But I downloaded an old “kitchensink” kernel and pointed the host to it but nothing changed. It isn’t getting as far as downloading the kernel files.

I am currently using FOG 1.2.0 on Ubuntu 12.0.4 LTS.

Any ideas or did I miss a post which sorted this?

Hi DoubleD,

I don’t know if there is a broken distro of Apache out there. When you run installfog.sh it runs apt-get to fetche all the bits it needs. It seems to be downloading an apache which does not have the mods enabled or are incomplete for some reason.

Maybe it will get fixed at some point, but at least we have a workaround…