Thanks for the info sylvain. I tried what you suggested and root=/dev/rd/0
did have an effect however didn't solve the problem. When I set my
configuration in this manner:
kernel linux.1
append initrd=linux.2 root=/dev/rd/0
I get this result
Loading linux.1....................
Loading linux.2.........................................................
Ready.
Failed to free base memory, sorry...
Uncompressing and Loading Imaging. Please wait...
OK, booting the kernel.
Kernel panic: I have no root and I want to scream
Note before I had the same result except my kernel panic error was:
Kernel Panic: VFS: Unable to mount root fs on 01:01
Another thing that might help in the trouble shooting is here is what my
logs look like for the tftp server.
Sep 17 13:14:47 bluebruda in.tftpd[18056]: RRQ from 131.202.242.198
filename pxelinux.cfg/default
Sep 17 13:14:47 bluebruda in.tftpd[18057]: RRQ from 131.202.242.198
filename fcs.msg
Sep 17 13:14:52 bluebruda in.tftpd[18059]: RRQ from 131.202.242.198
filename linux.1
Sep 17 13:14:53 bluebruda in.tftpd[18060]: RRQ from 131.202.242.198
filename linux.2
To me everything looks fine... except for this model of IBM 6282-73U I
can't mount the root file system. Where as the exact same setup will work
on other machines.
On Sat, 14 Sep 2002, Sylvain Meilard wrote:
> Hello !
>
> Maybe passing argument root=/dev/ram0 or root=/dev/rd/0 would help ?
> I use isolinux and it works in the isolinux.cfg
>
> sylvain
>
>
> > Message: 3
> > Date: Fri, 13 Sep 2002 14:11:38 -0300 (ADT)
> > From: Geddes <jgeddes at unb.ca>
> > To: syslinux at zytor.com
> > Subject: [syslinux] Unable to mount root fs
> >
> >
> > Hey all,
> >
> > I'am able to use pxelinux to successfully boot a particular kernel
and
> > image on various IBM PC's ex. 6287-41U and 6591-34U. However,
using the same
> > setup (ie. dhcp, tftp, pxelinux.0, pxelinux.cfg, networkcard, bootrom,
> > ram memory) on an IBM 6282-73U my kernel and image decompress fine but
I'am
> > getting a...
> >
> > Kernel Panic: VFS: Unable to mount root fs on 01:01
> >
> > I realize that this may not be problem with pxelinux. I'am hoping
someone might
> > have a solution for this... maybe a kernel option that I can pass.
> >
> > here is an example of my pxelinux.cfg default file:
> >
> > default dlimage
> > prompt 1
> > display fcs.msg
> > timeout 100
> > label mkimage
> > kernel linux.1
> > append initrd=linux.2 lang= text devfs=nomount
PROXYADDR=prox.cs.unb.ca
> > MANUALREBOOT=YES
> > label dlimag
> > kernel linux.1
> > append initrd=linux.2 lang= text devfs=nomount
PROXYADDR=prox.cs.unb.ca
> > MANUALREBOOT=NO
> > label 3c905
> > kernel memdisk
> > append initrd=nw3c905.img
> > label intel
> > kernel memdisk
> > append initrd=intel.img
> > label samba
> > kernel memdisk
> > append initrd=samba.img
> > label local
> > LOCALBOOT 0
> > label modboot
> > kernel memdisk
> > append initrd=modboot.img
> >
>
--
Jeff Geddes, BSc(UNB)
Computer Systems Specialist
University of New Brunswick
Faculty of Computer Science
eMail: jgeddes at unb.ca
office: Rm. E119
phone : (506) 452-6102
fax : (506) 453-3566