[syslinux] problems with 2880 linux floppy image

[Patty O'Reilly]

I had two pieces of hardware on which to test a linux floppy image and
the only way I was able to boot my image was to break it appart and
dump vmlinuz and initrd into the /tftpboot directory.
                                                                                
Finally, I got my hands on another computer and the image file booted 
fine. My syslinux.cfg looks something like this:
                                                                                
label myimage
   kernel memdisk
   append initrd=myimage.img
                                                                                
My question is whether there is support for UNDI/PXE in linux. The
original machine I stuggled with had an Intel UNDI PXE-2.0 NIC. I
tried the keeppxe option on my append line but this didn't work. I've
tried serveral different versions of syslinux without success. Am I
wasting my time trying to load linux on these UNDI machines via
memdisk?

--patty

On Mon, 3 Nov 2003, Patty O'Reilly wrote:

> Date: Mon, 3 Nov 2003 15:20:00 -0800 (PST)
> From: Patty O'Reilly <oreilly at qualcomm.com>
> To: syslinux at zytor.com
> Subject: Re: [syslinux] problems with 2880 linux floppy image
> 
> I referenced the syslinux.zytor web page to help create my
> syslinux.cfg file. It looks something like the following:
> 
> label myimage
> 	kernel memdisk
> 	append initrd=myimage.img
> 
> My dhcp/tftp server are configured similar to the recommendations
> found under pxelinux at syslinux.zytor.com.
> 
> The file myimage.img is a fat filesystem which contains vmlinuz,
> initrd.img, and syslinux.cfg. I used syslinux to creat the boot
> boot loader on the image file. The client simply hangs when it trys to
> boot the image file. There are no error messages.
> 
> Does it matter whether you run syslinux on the filesystem before or
> after it is populated? Any suggestions on how to troubleshoot this?
> 
> Thanks,
> 
> --patty
> 
>  On Sat, 1 Nov 2003, H. Peter Anvin wrote:
> 
> > Date: Sat, 01 Nov 2003 15:31:57 -0800
> > From: H. Peter Anvin <hpa at zytor.com>
> > To: H. Peter Anvin <hpa at zytor.com>
> > Cc: Patty O'Reilly <oreilly at qualcomm.com>, syslinux at zytor.com
> > Subject: Re: [syslinux] problems with 2880 linux floppy image
> >
> > H. Peter Anvin wrote:
> > > Patty O'Reilly wrote:
> > >
> > >>
> > >> The client boots memdisk but fails to boot the 2880 floppy image. In
> > >> fact, it also fails to boot the stock RH bootdisk.img which is 1440 K.
> > >> The last message on the client is "Loading boot sector... booting..."
> > >> and it hangs. I can tell from the output on the client's screen and
> > >> network sniffing that the client receives the image and is aware of
> > >> its size.
> > >>
> > >
> > > You can't boot Linux using MEMDISK, since it wants to talk to the
> > > hardware directly.
> > >
> >
> > Actually, come to think of it, you should be able to boot a syslinux
> > disk image with memdisk.  It's probably not a good idea, however... if
> > nothing else you will lose those megabytes of memory.
> >
> > 	-hpa
> >
> _______________________________________________
> 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.
>