Hello.
We've been using a very old version of SYS-/PXELINUX, 3.36, going by the
proven "if it works, don't break it" philosophy. We us it mostly
to load
floppy disk images to kick off OS installations.
Unfortunately we've recently had some PXE menu problems (USB keyboard
stopped working) for a certain Fujitsu PC model, and decided to upgrade
to the latest version, i e 3.84. All seemed well until we got reports
about problems with Dell OptiPlex GX280.
I've done some testing and everything works well until version 3.62.
After the floppy image has been loaded and it starts executing DOS 7.0
(Win98), there are several error messages about DOS memory. GDISK also
can't run, complaining about DOS memory.
This problem can be reproduced with the following:
- Dell OptiPlex GX280, BIOS version A08 (the latest/last).
- pxelinux.0 version 3.62 (or later).
- Menu.c32 (I can use menu.c32 from 3.62 with pxelinux.0 from 3.61).
Menu example:
KERNEL memdisk
APPEND keeppxe initrd=images/install/w98_aterm_xp_current.IMZ
I haven't seen this problem on any other machine model (3.62 or later
versions).
We're stuck with a bunch of old GX280's for the rest of the year, after
that they will be replaced. As long as we do not experience problems
with any of our other PC models (17 at the moment), version 3.61 is fine
for us (we use memdisk from 3.84 for ISO support), but the ideal
situation would be if our GX280:s could use 3.84 (or later). Since the
problem seems to be in pxelinux.0, we can't simply add another menu item
for GX280.
Any ideas?
Cheers,
Daniel Lindgren
On 01/11/2010 07:05 AM, Lindgren Daniel wrote:> > Any ideas? >Since you have a working and a non-version version, it would be useful if you could determine which prerelease broke things: http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/Obsolete/ or, equivalently, if you're familiar with "git" you can do a "git bisect". That would help immensely in narrowing down the problem. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.
> Menu example: > > ? ? KERNEL memdisk > ? ? APPEND keeppxe > initrd=images/install/w98_aterm_xp_current.IMZ >Add 'raw' to memdisk and see if it helps: KERNEL memdisk APPEND keeppxe initrd=images/install/w98_aterm_xp_current.IMZ raw - Gert Hulselmans
> Since you have a working and a non-version version, it would > be useful if you could determine which prerelease broke things: > > http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/Obsolete/ >Done, the problem appears with pxelinux.0 version 3.62-pre7. Cheers, Daniel
On 01/12/2010 03:06 AM, Lindgren Daniel wrote:>> Since you have a working and a non-version version, it would >> be useful if you could determine which prerelease broke things: >> >> http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/Obsolete/ >> > > Done, the problem appears with pxelinux.0 version 3.62-pre7. >Yep, definitely the putting labels in high memory stuff. Could you run "memdump.c32" and send me the output? -hpa
On 01/12/2010 01:28 PM, H. Peter Anvin wrote:> On 01/12/2010 03:06 AM, Lindgren Daniel wrote: >>> Since you have a working and a non-version version, it would >>> be useful if you could determine which prerelease broke things: >>> >>> http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/Obsolete/ >>> >> >> Done, the problem appears with pxelinux.0 version 3.62-pre7. >> > > Yep, definitely the putting labels in high memory stuff. Could you run > "memdump.c32" and send me the output? >Called "meminfo.c32" in newer versions... -hpa
> > > > Done, the problem appears with pxelinux.0 version 3.62-pre7. > > > > Yep, definitely the putting labels in high memory stuff. > Could you run "memdump.c32" and send me the output?See attached screen dump. Cheers, Daniel -------------- next part -------------- A non-text attachment was scrubbed... Name: dell_gx280_meminfo.PNG Type: image/png Size: 22924 bytes Desc: dell_gx280_meminfo.PNG URL: <http://www.zytor.com/pipermail/syslinux/attachments/20100114/a22088e8/attachment.png>