No, I never use genkernel and I use modules only for things I need once
a year (loop, ramdisk, ... ) or things which can't be built into the
kernel.
Just now I tried the vanilla kernel. Let's see what the reboot brings
up.
Regards
Frank
On Tue, 2006-08-22 at 10:16 +1200, Nick Rout wrote:
On
On Sun, 20 Aug 2006 12:16:01 -0700
Richard Fish wrote:
On 8/20/06, frank [EMAIL PROTECTED] wrote:
Has anyone an Idea? I don't have further :(
Since the kernel is being found it is not a grub setup problem.
Either:
a. The filesystem drivers are not compiled into your kernel. You said
what about fstab?Mirek2006/8/20, frank [EMAIL PROTECTED]:
Just a bit more info, I've rebooted into the new system. Here's thewhole message:...VFS: Cannot open root device hda3 or unknown-block(0,0)Please append a correct root= boot option
Kernel panic - not syncing: VFS: Unable to mount root fs
Mirek Dvořák [EMAIL PROTECTED] writes:
what about fstab?
Mirek
Is fstab relevant at this point? As surely /etc/fstab cannot be read
until after the root ('/') filesystem is mounted, and this is what is
failing.
--
gentoo-user@gentoo.org mailing list
Graham Murray wrote:
Mirek Dvořák [EMAIL PROTECTED] writes:
what about fstab?
Mirek
Is fstab relevant at this point? As surely /etc/fstab cannot be read
until after the root ('/') filesystem is mounted, and this is what is
failing.
Did you try to boot without the root= option?
--
Well, I didn't see any reason to try this. The kernel should know where
the root filesystem lives.
I've tried it just now:
The panic is the same. The only difference is that the unknown device is
(hd3,3).
I've even tried to set root=(hd0,2) (I know, this is NOT what ``info
grub'' says) :o(
Just
On 8/20/06, frank [EMAIL PROTECTED] wrote:
Has anyone an Idea? I don't have further :(
Since the kernel is being found it is not a grub setup problem.
Either:
a. The filesystem drivers are not compiled into your kernel. You said
you configured them...are they built in (=y) or as modules
7 matches
Mail list logo
