Syslinux - Jun 2005 - hanging pxelinux.0 and menu.c32 on Dell 1850

Hello all.

I've got this weird problem. If I try to boot a simple menu using
syslinux's (v 3.09) pxelinux.0 and menu.c32 -files my Dell 1850 loses
the keyboard / hangs straight after loading menu.c32. The machine has to
be powered off completely.

I did some research and got it working by using menu.c32 v3.09 and
pxelinux.0 v3.07 -combo.

It seems that from version 3.08 on something has changed on pxelinux.0
file which affects this particular system (Dell 1850).

I think the developers can find the problem by diff'ing correct
sourcefiles so I won't post my config right now.

BR,

-Mikko Kurkela

Mikko Kurkela wrote:
> 
> I think the developers can find the problem by diff'ing correct
> sourcefiles so I won't post my config right now.
> 
You're wrong.

It would also be good if you could tell exactly which prerelease broke 
the setup.

	-hpa

Hello.

3.08-pre2 is the latest one that works. I tested all from 3.08-pre11 to
3.08-pre2 (including 3.08 of course).

My pxelinux.cfg/default is as follows:

---------------------------------------------------

DEFAULT menu.c32
PROMPT 0
MENU TITLE PXE BOOT MENU
MENU MASTER PASSWD xxx
MENU PASSWD yyy


#base infra server
LABEL infrabase
    MENU LABEL ^Infra base - no service configs
    kernel RH4ES/vmlinuz
    append initrd=RH4ES/initrd.img ramdisk_size=268235456 console=tty0
ks=ftp://xxx.xxx.xxx.xxx/pub/rh4/kickstart/infra/xxx.cfg ksdevice=eth0


#the base ks skeleton
LABEL base
    MENU LABEL ^Base RH4 - plain RH4
    kernel RH4ES/vmlinuz
    append initrd=RH4ES/initrd.img ramdisk_size=268235456 console=tty0
ks=ftp://xxx.xxx.xxx.xxx/pub/rh4/kickstart/yyy.cfg ksdevice=eth0


#plain red hat 4
LABEL plain
    MENU LABEL RH4 ^manual install
    kernel RH4ES/vmlinuz
    append initrd=RH4ES/initrd.img ramdisk_size=268235456 console=tty0

#full manual installation
LABEL rh4dosboot
        MENU LABEL  RH4 m^anual install - specify all kernel options
manually
        kernel memdisk
        append initrd=RH4ES/diskboot.img

#LABEL local
#       MENU LABEL ^Local boot - boot from local harddrive
#       LOCALBOOT 0

----------------------------------------------------------

Hope this helps.

BR,

-m-




 
>>>"H. Peter Anvin" <hpa at zytor.com> 06/27/05 10:23
pm >>>
Mikko Kurkela wrote: 
> 
>I think the developers can find the problem by diff'ing correct 
>sourcefiles so I won't post my config right now. 
> 
 
You're wrong. 
 
It would also be good if you could tell exactly which prerelease broke 
the setup. 
 
-hpa