My fstab file looks like this:
/dev/hdb7 / reiserfs
defaults 0 0
/dev/hdb2 none swap sw
0 0
proc /proc proc defaults
0 0
/dev/fd0 /floppy auto user
0 0
/dev/cdrom /cdrom iso9660
noauto,ro,user,unhide 0 0
#/dev/cdrom1 /cdrom1 iso9660
noauto,ro,user,unhide 0 0
/dev/hdb1 /boot ext3 defaults
0 0
/dev/hdb3 /var reiserfs defaults 0
0
/dev/hdb5 /usr reiserfs defaults 0
0
/dev/hdb6 /home reiserfs defaults 0
0
Running the grub commands on the command line gives
error code 16.
The kernel and the initrd files are
vmlinuz-2.4.22-1-686
initrd.img-2.4.22-1-686
I hope this will shed more light on the problem.
Regards,
Anim
> Subject: FW: FW: Kernel panic error
>
>
>
>
> > > From: Jerome R. Acks
> > > [mailto:[EMAIL PROTECTED]
> > > Sent: 24 October 2003 03:47
> > > To: Anim Asante
> > > Cc: [EMAIL PROTECTED]
> > > Subject: Re: Kernel panic error
> > >
> > >
> > > On Wed, Oct 22, 2003 at 11:10:02AM +0100, Anim
> > > Asante wrote:
> > >
> > > > > > I have got a grub menu.lst file with a
> section
> > > of
> > > > > the
> > > > > > file looking like this
> > > > > > ?root (hd1,0)
> > > > > > ?kernel /vmlinuz root=/dev/hdb1
> > > > > > ?boot
> > > > > > ?
> > > > > > When I restart my machine and select this
> > > option,
> > > > > the
> > > > > > boot up process begins up
> > > > > > to a point and it gives the following
> error
> > > > > message:
> > > > > > ?Warning: unable to open an initial
> console.
> > > > > > ?Kernel panic: No init found.
> > > > > > ?Try passing init= option to kernel.
> > >
> > >
> > > > I do not have any problems when I use lilo. I
> am
> > > not
> > > > at my machine at the moment but I will give it
> a
> > > try
> > > > and see what happens.
> > >
> > > Can you post the pertinent section from
> lilo.conf?
> > >
> >
> > The section from lilo.conf is as follows:
> >
> >
> > boot=/dev/hda
> > root=/dev/hdb7
> > install=/boot/boot-menu.b
> > map=/boot/map
> > image=/vmlinuz initrd=/initrd.img
> > label=linux
> > read-only
> >
> > other=/dev/hda1
> > label=windows
>
> If this section in lilo boots your kernel, a
> comparable section in
> grub's menu.lst would be:
>
> title Debian/GNU linux
> root (hd1,6)
> kernel /vmlinuz root=/dev/hdb7
> initrd /initrd.img
> boot
>
> If /vmlinuz and /initrd.img are symlinks to
> /boot/vmlinux-2.4.xxx and
> /boot/initrd.img-2.4.xxx,respectively, you should
> replace them with
> the specific kernel and initrd filenames. The grub
> menu.lst would read:
>
> title Debian/GNU linux
> root (hd1,6)
> kernel /boot/vmlinuz-2.4.xxx root=/dev/hdb7
> initrd /boot/initrd.img-2.4.xxx
> boot
>
> If /boot is in a different partition that /dev/hdb7,
> "root (hd1,6)"
> will need to be changed to match the partition of
> /boot. For example:
> is /boot is /dev/hdb6, the grub menu.lst would be:
>
> title Debian/GNU linux
> root (hd1,5)
> kernel /vmlinuz-2.4.xxx root=/dev/hdb7
> initrd /initrd.img-2.4.xxx
> boot
>
> To be more definitive, you will need to spply more
> info. Post your
> /etc/fstab and the kernel and initrd.img filenames
> in /boot.
>
> If you run grub in a terminal, you can determine the
> appropriate file
> names and root device by using grub's find command.
>
> --
> Jerome
>
>
> ATTACHMENT part 2 application/pgp-signature
name=ATT00018.dat
________________________________________________________________________
Want to chat instantly with your online friends? Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
