l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 May 02 00:33

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] Kernel upgrade from Sarge (fresh install) 2.4.25 ->2.6.3 or 5
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] Kernel upgrade from Sarge (fresh install) 2.4.25 ->2.6.3 or 5

me@heyjay.com wrote:
VFS - Cannot open root device "hda1" or unknown-block(0,0)
Please append correct "Root=" boot option
Kernel panic: VFS: unable to mount root fs on unknown-block(0,0)
well, this pretty much tells it all.  the kernel panics because it
doesn't know where to find the root of your filesystem.

I sorta got that, I'm just not sure why it can't find the filesystem

I've found, by personal experience, 3 things that cause the root filesystem not to be found or mounted.

1) incorrect "root=/dev/hdxx" entry in your boot loader, as others have pointed out

2) incorrect line in /etc/fstab

3) The necessary parts for your filesystem (e.g. ext3, reiserfs, or even your harddrive drivers) are not properly compiled in your kernel.

The first 2 are obvious, but I'll talk more about the last one. Unless you are using an initrd, you MUST compile support for your harddrive and its filesystem into the kernel directly, i.e. not as modules. This is what I do, and it works. Supposedly, modules are OK when using an initrd, but I haven't taught myself that yet, and it seems unnecessary. Modules are OK, and recommended, for things that come after mounting your root partition, but not before (e.g. usb stuff).

cp /boot/config-2.4.25-1-386 .config
make menuconfig # didn't really do much here except make the processor

whoa there.  you're kidding, right?

you can't just use old .config files like that.  read the kernel
compiling howto and do a search on oldconfig.

I've tried make oldconfig, I've tried using all the defaults, I don't know
what all the options mean (even after reading the help) nor if they apply to

Anyway, I tried using the prebuilt 2.6.5-k7 image and that installed and
booted fine, so I'll use it's config as a starting point, and try again

Yep, all those options can be really confusing and intimidating. But you have the right idea: start by working with a config that is known to work. Good luck! There is something satisfying about compiling your own kernel.

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.