ipxe, boot hdt, com32

[Shraik]

i'am trying to boot Hardware detection tool http://hdt-project.org/

1.
boot from ipxe: (works wonderfully)

pxe->undionly.kpxe->vesamenu.c32
LABEL HDT
KERNEL http://memdisk
INITRD http://hdt-0.5.0.iso
APPEND iso

2. boot from pxe (works wonderfully)

pxe->vesamenu.c32
LABEL HDT
KERNEL /hdt/hdt_0_5_0.c32

3. boot from ipxe com32 module (hangs on start)

pxe->undionly.kpxe->vesamenu.c32
LABEL HDT c32
KERNEL http://hdt_0_5_0.c32
-----
tell me What I'm Doing Wrong in "3" ?

[robinsmidsrod]

I'm actually quite surprised that those http://memdisk URLs actually boot. Those are invalid URLs, as far as I can tell. URLs are usually built up like this: http://name-of-your-server/path/to/file.html. From what I can tell, I'm guessing that syslinux or iPXE is ignoring that http:// prefix and just treating your URLs as relative paths, in which case I would assume they are being downloaded from TFTP.

Have you turned on logging in your tftp server and web server to see which one is actually serving up your file.

With regards to option number 3, the C32 file might be compiled for another version of syslinux than you are booting with. Where did you get your syslinux binaries from?

[Shraik]

"http://memdisk"
Of course, this simplification.
FQDN is http://192.168.1.250/memdisk
---
Syslinux binaries from http://www.kernel.org/pub/linux/utils/boot/syslinux/
I tried version 4.05 and 4.10

(2012-01-14 17:44)robinsmidsrod Wrote:  I'm actually quite surprised that those http://memdisk URLs actually boot.

With regards to option number 3, the C32 file might be compiled for another version of syslinux than you are booting with. Where did you get your syslinux binaries from?