[syslinux] memdisk issue with gpxelinux.0

[Miller, Shao]

I have seen problems running memdisk from gPXE before, but usually they
were "superfloppy" images.  Anything with 2,880 512-byte sectors has
always worked for me.  Maybe this is something worth posting to the gPXE
discussion mailing list, Pierre.  If you are in dire need, you can still
plug PXELINUX into the process as middle-man for memdisk and find
success.  - Shao

-----Original Message-----
From: syslinux-bounces at zytor.com [mailto:syslinux-bounces at zytor.com] On
Behalf Of H. Peter Anvin
Sent: Sunday, April 26, 2009 18:50
To: For discussion of Syslinux and tftp-hpa
Subject: Re: [syslinux] memdisk issue with gpxelinux.0

Pierre wrote:
> Ramdisk at 0xdfb00000, length 0x0016bd50
> 
> The floppy image is correct and its size is 1440 K (1474560 bytes) not
> 1455 K as indicated above
> 
> I have the same results on 2 servers whith different architectures
> 
> Can someone tell me about the exceedings 15696 bytes (and what mistake
> I have made) ?
> 

This sounds like a gPXE issue; clearly it is reporting the wrong length
to MEMDISK (length 0x0016bd50 = 1490256 rather than 1474560).

Since the length is wrong, MEMDISK gets the geometry wrong, too.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.

_______________________________________________
Syslinux mailing list
Submissions to Syslinux at zytor.com
Unsubscribe or set options at:
http://www.zytor.com/mailman/listinfo/syslinux
Please do not send private replies to mailing list traffic.