Post-Installation Errors Gentoo (2004.1)

wolverineman85 · 05-17-2004, 06:10 PM

I have a Dell Inspiron 8200 and I installed Gentoo (2004.1) onto a firewire HDD. For the kernel (gentoo-kernel 2.4.25), I used genkernel. I got GRUB installed and working, but when I boot into gentoo i got the following error:

Code:

/bin/sh: Can't open dofirewire
Kernel panic: Attempted to kill init!

My config for Gentoo GRUB is as follows:

Code:

root (hd0,2)
kernel /kernel-2.4.25-gentoo-r2 root=/dev/ram0 init=/linuxrc real_root=/dev/sda2 dofirewire
initrd /initrd-2.4.25-gentoo-r2

So then I took out the dofirewire command and I ran into the following message:

Code:

BusyBox v1.00-pre7 (2004.05.16-17:48+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/bin/sh: can't access tty; job control turned off
attempt to access beyond end of device
01:00: rw=0, want=4171, limit=4096
attempt to access beyond end of device
01:00: rw=0, want=4171, limit=4096
/ #

and when I type in help, I get this on the screen:

Code:

. : alias bg break cd chdir continue eval exec exit export false
fg hash help jobs kill let local pwd read readonly return set
shift times trap true type ulimit umask unalias unset wait

Where should I go from here? Any help would be much appreciated.

MerePeer · 06-15-2004, 11:12 AM

2.4.25 requires a ramdisk that is larger than 4096 at boot, setting it in grub.conf to 8192 (ramdisk_size=8192) fixed the problem for me.

smgoosen · 06-06-2005, 10:27 AM

Hi MerePeer,

Excuse me if I sound ignorant, I am a true Linux newbie (plus it's a Monday).

I have Suse w/ 2.6.4-52 and Redhat w/ 2.4.20-8 on two different disks in my system.

Using SuSe menu.lst at boot. Booting SuSe is fine.

Booting Redhat with SuSe "loader" (green w/ SuSe logo in upper right corner)
seems to work. But when I boot Redhat w/ the Redhat "loader" (black background
w/ Penguin at top), I get en error message.

I'm getting the same message as wolverineman85:

kernel: attempt to access beyond end of device
kernel: 01:00: rw=0, want=4258, limit=4096

as soon as boot starts. Sounds like the ramdisk size problem you descibe. Could
you give me the location of the file (/boot/grub/grub.conf on Redhat or /etc/grub.conf
on SuSe) and the exact location within the file to put the ramdisk_size variable you
mention for my situation?

Thanks!