LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 06-04-2009, 11:10 PM   #1
yuchankit
Member
 
Registered: Apr 2008
Distribution: Slackware 13.1 ,slackware-current
Posts: 143

Rep: Reputation: 22
Kernel compile and upgrade failed


I'm using Slackware 12.2,upgrading from original kernel to recent one,which is 2.6.29.4.

I follow all the steps in here to upgrade and recompile the kernel.

But when I booted the new kerne,the following error popped up;

VFS:Cannot open root device "308" or unknown block (3,8)
Please append and correct "root=" boot option;here are the available partitions;

Kernel panic.not syncing:VFS:Unable to mount root fs on unknown block (3.8)

Do you know why the error and how to solve this?Thank you and sorry for my bad English.
 
Old 06-04-2009, 11:13 PM   #2
exvor
Senior Member
 
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,485

Rep: Reputation: 66
I would check your boot managers configuration file if its grub then it would be menu.lst listed normally in /boot/grub/ the root= line is what its complaining about this needs to be the harddisk that you have your / partition


Also its possible you forgot to include in the kernel configuration drivers for your hard drive controllers or file system.

Last edited by exvor; 06-04-2009 at 11:14 PM. Reason: Added more info
 
Old 06-04-2009, 11:28 PM   #3
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,375

Rep: Reputation: 164Reputation: 164
I made the same mistake once. I configured ext3 as a module when it needs to be built in to the kernel.
 
Old 06-04-2009, 11:30 PM   #4
C-Sniper
Member
 
Registered: Dec 2006
Distribution: Slackware
Posts: 507

Rep: Reputation: 33
as mlangdn said, when you recompile your kernel make sure your FS is listed as a built in (<y>) not as a module. If it is built as a module you will need to make an initrd.gz file that will tell the kernel what to load.
 
Old 06-05-2009, 07:18 AM   #5
yuchankit
Member
 
Registered: Apr 2008
Distribution: Slackware 13.1 ,slackware-current
Posts: 143

Original Poster
Rep: Reputation: 22
I recompiled the kernel again,and it shows sign of improvement although I failed to boot them;

VFS:Cannot open root device "308" or unknown block (3,8)
Please append and correct "root=" boot option;here are the available partitions;

sda1
sda2
sda8(My root partition)

Kernel panic.not syncing:VFS:Unable to mount root fs on unknown block (3.8)

These were the steps I did;

1.Edited my lilo.conf,changed root=/dev/hda8 to root=/dev/sda8.
2.Ran lilo,but there were some error that states root=/dev/sda8 is not a valid specification.
3.Rebooted and I found that the root's MBR isn't renewed.

What I need to do now??
 
Old 06-05-2009, 07:39 AM   #6
hitest
Senior Member
 
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, OpenBSD
Posts: 4,163

Rep: Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527Reputation: 527
This is an excellent kernel compile guide:

Building a Linux Kernel from source
 
Old 06-05-2009, 07:41 AM   #7
mlangdn
Senior Member
 
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,375

Rep: Reputation: 164Reputation: 164
Edit lilo.conf again.

root=/dev/sda8 should be:

root = /dev/sda8

Then re-run lilo and see if it gives an error.
 
Old 06-05-2009, 09:35 AM   #8
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 2,548

Rep: Reputation: 422Reputation: 422Reputation: 422Reputation: 422Reputation: 422
Quote:
Originally Posted by yuchankit View Post
I recompiled the kernel again,and it shows sign of improvement although I failed to boot them;

VFS:Cannot open root device "308" or unknown block (3,8)
Please append and correct "root=" boot option;here are the available partitions;

sda1
sda2
sda8(My root partition)

Kernel panic.not syncing:VFS:Unable to mount root fs on unknown block (3.8)

These were the steps I did;

1.Edited my lilo.conf,changed root=/dev/hda8 to root=/dev/sda8.
2.Ran lilo,but there were some error that states root=/dev/sda8 is not a valid specification.
3.Rebooted and I found that the root's MBR isn't renewed.

What I need to do now??
Try to revert it again to root = /dev/hda8 and ran LILO
make sure it worked and then when you boot, press tab or escape to get the LILO prompt and then select the correct kernel and add
Code:
root=/dev/sda8
this will overwrite the root partition should be used to boot the kernel.

The problem with your LILO is because the current kernel you are running doesn't recognize your /dev/sda8, so it complaints. The solution is to use the old value and overwrite it during boot time using above's way
 
Old 06-05-2009, 12:53 PM   #9
yuchankit
Member
 
Registered: Apr 2008
Distribution: Slackware 13.1 ,slackware-current
Posts: 143

Original Poster
Rep: Reputation: 22
Finally,I get to run my shiny new kernel and typing my post using the new kernel.

1.I edited the root = /dev/sda8 to root = /dev/root
2.I finally booted my new kernel,but of course it's not the end of my problems.I forgot to build some important modules,and I rebuild them and I get to run new kernel.

To be frank,this is my first time compiling a new kernel.So far I did not notice increase in performance despite having the kernel shrinked slightly from 4.3 MB to 3.5 MB.But this should be a good experience for me indeed.
 
Old 06-06-2009, 03:04 AM   #10
kurta
LQ Newbie
 
Registered: Oct 2006
Posts: 15

Rep: Reputation: 0
You might not get so much of a boost in speed and such.. but you get better support for more things. But using a newer kernel, and a custom one is something that I see as a good thing anyways.
 
  


Reply


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
Failed to compile kqemu on slack 11.0 + customized 2.6.18 kernel kite Slackware 2 10-14-2006 10:46 AM
kernel 2.6.8 compile error mkinitrd failed mcalizo Linux - Software 0 11-30-2004 01:58 AM
eth0 failed to start after kernel compile andy18 Linux - Networking 3 09-09-2003 09:32 AM
upgrade the kernel failed lzyking Linux - Software 2 02-14-2003 10:37 PM
Help, upgrade kernel and failed boot explorer1979 Linux - General 3 09-26-2002 05:08 PM


All times are GMT -5. The time now is 10:32 AM.

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