I can't boot 2008.0_beta2 with the "Gentoo [no framebuffer]" kernel on the single machine I tested. I get the following messages and an interrupted boot:
>> Determining root device...
!! Could not find the root block device in .
Please specify another value...
The "Gentoo" kernel option doesn't have this problem.
I'm sure more info is needed. Please tell me what you need so I can provide it, ok?
Some extra info:
The "Determining root device" message appears right after ">> Activating mdev".
It's a i386 machine with a regulat PATA drive.
I experienced the same problem on a 2.6GHz Intel dual-core quad-cpu with 4 GB ram and 5 TB SATA disk. It has a new LG Blu Ray drive that interfaces over SATA. It uses an ASUS motherboard, no add-on boards. See Gentoo Forums at:
for more details.
Is this still an issue with the 2008.0 final release?
I've just tested. The 2008.0 final release seems to be ok.
Thanks for testing.
Sorry for the incomplete info.
The x86 disk is ok but the amd64 still has the problem.
Same here with amd64 minimal 2008.0 gentoo-nofb CD.
Just changing the hardware from "All" to "AMD64" to make the issue clearer.
So I'm seeing this issue on my fresh AMD64 install.
I can't say I'm especially motivated to resolve this. I think my return to gentoo may be experiencing an abrupt end.
This problem could be related to http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8959d300a79c1b70526cdf9e00485262cf8d979f.
Booting with mem=2048M works for me.
AFAIK this boot disk problem is solved as per 23/06/2009 version.
Where can one get an up-to-date install-amd64-minimal that is signed (see bug #277319)?
(In reply to comment #12)
> Where can one get an up-to-date install-amd64-minimal that is signed (see bug
http://distfiles.gentoo.org/releases/amd64/autobuilds/current-iso/ or through one of the mirrors.
(In reply to comment #11)
> AFAIK this boot disk problem is solved as per 23/06/2009 version.
I'm closing this bug then.
If the issue returns, feel free to reopen the bug.
*** Bug 232595 has been marked as a duplicate of this bug. ***