Mod Edit: This is a very common problem, made this one sticky and changed the title from 'Lilo boot problem' to 'Job control & attempt to access beyond end of device' - tomkEdit: Unstuck, as the solution is now in the handbook. --Maedhros

Hi,

I installed Gentoo 2004 according to the instructions online.
When I boot I end up getting the following message:

Found the problem. 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 entirely. Is this a genkernel all misinterpretation?

Hello, I had the same problem using lilo. Was a simple fix by just adding:

Code:

ramdisk=8192

to my lilo.conf

If you are stuck at BusyBox just boot up with the Gentoo LiveCD, follow the documentation to mount your root partition, boot partition, and proc, then chroot and edit the conf. Then type 'lilo' to save the changes and your system should boot.

OK... my issue was related to using a large drive (greater than 32GB)
but not having the Auto-Geometry Resizing Support" enabled at
the makeconfig step. This is on an IDE disk. I would guess that SCSI
disks do not have this option.

Yea I am having the same problem. Except I installed my Gentoo installation on my secondary hard drive so all my errors are hdb blah blah blah. I have tried with the ramdisk at 8096 and even at 16192, but nothing works.
The full error says:

Yea I am having the same problem. Except I installed my Gentoo installation on my secondary hard drive so all my errors are hdb blah blah blah. I have tried with the ramdisk at 8096 and even at 16192, but nothing works.
The full error says:

Is this not the common case of teh /etc/fstab was not updated?
i.e. the "ROOT".
I did this too the first time thinking like I was using Red Hat and
DiskDruid (which, in later releases) would write disk labels onto the
partitions during the fdisk phase. Then if you moved the disk to a
different controller it would still be able to find the "ROOT" partition.
But i think your case might be the former common error I mention.

I'm getting the exact same busy box message and error lines. I tried adding the ramdisk line...and my config file looks very similar to those posted...very generic.
Now, instead of getting the errors...I get a big blank screen once I past the kernel selection...no command line...nothing. I'm not sure what to try from this point...everything just seems to stop. I can feel the HDD rotating and other than that...nothing else I can detect and the computer is completely unresponsive. this is the 3rd time in 48 hours I've hit this problem...unfortuantely I'm not (yet) smart enough to understand how to get past this...

Since hitting this minor delay...I've decided to redo everything...I've been using Stage 3 and Genkernel...but now I'm trying Stage 1 and I'll manually config everything...what I noticed first off...was that now, instead of booting into SMP so I could use the 2.6 kernel (and thinking that was all there was to it!)...but having it show me later that I was on 2.4!? I now understand where I am able to install gentoo-dev-sources 2.6.7-r8...so I've solved my "why isn't this 2.6 kernel installing? I picked it with SMP!" ( my repedative reinstallations (besides wasting time) have indeed brought me more knowledge about gentoo in particular.

I'll be sure to add the ramdisk line in when I get to that piece...I'm hoping this goes better this time...I'm currently emerge gentoo-dev-sources...wish me LUCK and please...if you all have any tips beyond the ramdisk tip...I would appreciate it, I'm expecting to see the problem again...but my fingers are crossed.

The "blk: queue..." line appears when I boot up too. But IT ISN'T HALTING. It just takes a while for it to get past whatever it is doing at that point. The first few times I thought it was hanging but I was wrong.

one thing I did to get past that....go to make menuconfig (as well as have it in your grub config)...in there you have a selection for ramdisk...make sure you update the value there too. it got me past that annoying problem