Latest LQ Deal: Linux Power User Bundle
Go Back > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Slackware This Forum is for the discussion of Slackware Linux.


  Search this Thread
Old 11-28-2003, 02:53 PM   #1
Registered: Sep 2003
Location: Newfoundland, Canada
Distribution: Slackware 9.0
Posts: 44

Rep: Reputation: 15
Newly compiled 2.6-test11 Does not boot

Hello! The last time I compiled a Kernel we were still in the 2.2.x series so it's been a really long time. The more recent distributions I've tried I haven't needed to recompile the Kernel. So it's been years...

Anyway I was curious after reading about some of the improvments in 2.6.x so I downloaded the 2.6.test11, set the config options as best as I knew how, and compiled it. I did Lilo and edited the lilo config and all the usual stuff. Right now I'm running on my old kernel. But the 2.6.x one gives this message during bootup:

VFS: Cannot open root device "302" or hda2
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on hda2

Here is part of my /etc/lilo.conf:

image = /boot/vmlinuz.old
root = /dev/hda2
label = slack.old

image = /boot/vmlinuz
root = /dev/hda2
label = Linux

The first (2.4) kernel boots fine but the second (2.6.x) gives the above error.

Any suggestions on how to fix this? Thank you
Old 11-28-2003, 05:11 PM   #2
LQ Guru
Registered: Feb 2003
Location: Blue Ridge Mountain
Distribution: Linux Mint 17, Debian 8
Posts: 7,863

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
One possibility is that you have some kernel module set to m when it should be set to y. Every module that you need to access /dev/hda2 must be set to y. This includes such things as the file system type module (ext2, ext3, etc.) the drivers for your IDE controller, hard disk, and whatever. If one of these modules is set to m then the bootable kernel has no way to access /lib/modules to read in the loadable module.

Be prepared. Create a LifeBoat CD.

Steve Stites
Old 12-05-2003, 04:25 PM   #3
Registered: Sep 2003
Location: Newfoundland, Canada
Distribution: Slackware 9.0
Posts: 44

Original Poster
Rep: Reputation: 15
Everything I thought I needed I set to Y. I didn't purposely set anything on M. I also later tried compiling with many extra filesystems and IDE drivers etc that I'm pretty sure I didn't need -- but tried just in case -- and it didn't help.

Anyone have any other suggestions?
Old 12-26-2003, 12:18 AM   #4
LQ Newbie
Registered: Nov 2002
Posts: 2

Rep: Reputation: 0
I had the same problem but I was using a debian (unstable) 2.6 kernel. I resolved my problem by adding initrd=/initrd.img to my lilo.conf. Of course, my initrd was already created and sitting in / so I would assume you'll have to make it. Anyway, that fixed it for me.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Newly Compiled Linux does not seem to Boot binarybob0001 Linux - Newbie 2 12-02-2004 07:05 PM
newly compiled kernel, boot fails class_struggle Linux - Newbie 2 07-30-2004 09:10 AM
Newly compiled 2.6/ Key repeating? merlinn31 Slackware 3 03-19-2004 04:15 PM
uh-oh; boot problem in newly compiled 2.6.0 kernel with GRUB tombomb300 Linux - Newbie 10 01-28-2004 11:58 AM
Problem with newly compiled 2.4.22 kernel Xero720 Slackware 2 09-06-2003 12:23 PM > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:19 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration