[syslinux] Syslinux vmlinuz name limitation?

[Bogdan Radulescu]

Hello Geert,

Here is my config:

PROMPT 0
TIMEOUT 100
DEFAULT xconf

LABEL xconf
KERNEL /boot/vmlinuz-nx08
APPEND initrd=/boot/initrd-nx08.gz ramdisk_size=7120 root=/dev/ram0 rw

LABEL linux
KERNEL /boot/vmlinuz
APPEND initrd=/boot/initrd.gz ramdisk_size=7120 root=/dev/ram0 rw


"xconf" doesn't work and "linux" works just fine.

Bogdan



--- On Mon, 7/21/08, Geert Stappers <stappers at stappers.nl> wrote:

> From: Geert Stappers <stappers at stappers.nl>
> Subject: Re: [syslinux] Syslinux vmlinuz name limitation?
> To: syslinux at zytor.com
> Date: Monday, July 21, 2008, 1:28 PM
> Op 20-07-2008 om 23:41 schreef Bogdan Radulescu:
> > Hello,
> >
> > I'm using syslinux-3.70 and apparently it
> doesn't allow me to use
> > different names for vmlinuz and initrd.gz.
> 
> I used last saturday succesfully the name 'lua.c32'
> 
> > If I use a name like vmlinuz-nx08 in the config file
> syslinux seem to be
> > reloading everytime I try to boot. If I use vmlinuz
> and initrd-nx08.gz
> > syslinux complains that it can't find the file
> even though it's there. I
> > also tested this from the boot prompt and the menu and
> the same seems
> > to be happening.
> >
> > When I use the standard vmlinuz and initrd.gz names
> everything works
> > just fine.
> >
> > Syslinux seems to be going forward nicely and I really
> enjoy when I
> > see it gets significant improvements quite often.
> >
> > I don't know if anyone else experienced the
> problems I have but I
> > thought that you should know about it. If you need
> additional info
> > I'd be glad to supply it.
> 
> Please provide your syslinux conf file.
> 
> > One more thing. I'm installing syslinux from linux
> on a USB drive and
> > as a MBR I use mbr.bin
> >
> > Best regards, Bogdan
> 
> 
> Cheers
> Geert Stappers
> 
> _______________________________________________
> 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.