Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
06-04-2009, 11:10 PM
|
#1
|
|
Member
Registered: Apr 2008
Distribution: Slackware 13.1 ,slackware-current
Posts: 141
Rep:
|
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.
|
|
|
|
06-04-2009, 11:13 PM
|
#2
|
|
Senior Member
Registered: Jul 2004
Location: Phoenix, Arizona
Distribution: LFS-Version SVN-20091202, Arch 2009.08
Posts: 1,466
Rep:
|
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
|
|
|
|
06-04-2009, 11:28 PM
|
#3
|
|
Senior Member
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,335
Rep: 
|
I made the same mistake once. I configured ext3 as a module when it needs to be built in to the kernel.
|
|
|
|
06-04-2009, 11:30 PM
|
#4
|
|
Member
Registered: Dec 2006
Distribution: Slackware
Posts: 507
Rep:
|
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.
|
|
|
|
06-05-2009, 07:18 AM
|
#5
|
|
Member
Registered: Apr 2008
Distribution: Slackware 13.1 ,slackware-current
Posts: 141
Original Poster
Rep:
|
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??
|
|
|
|
06-05-2009, 07:39 AM
|
#6
|
|
Senior Member
Registered: Mar 2004
Location: Prince Rupert, B.C., Canada
Distribution: Slackware, FreeBSD
Posts: 3,656
|
This is an excellent kernel compile guide:
Building a Linux Kernel from source
|
|
|
|
06-05-2009, 07:41 AM
|
#7
|
|
Senior Member
Registered: Mar 2005
Location: Kentucky
Distribution: Slackware64-current
Posts: 1,335
Rep: 
|
Edit lilo.conf again.
root=/dev/sda8 should be:
root = /dev/sda8
Then re-run lilo and see if it gives an error.
|
|
|
|
06-05-2009, 09:35 AM
|
#8
|
|
Senior Member
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 1,868
|
Quote:
Originally Posted by yuchankit
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
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
|
|
|
|
06-05-2009, 12:53 PM
|
#9
|
|
Member
Registered: Apr 2008
Distribution: Slackware 13.1 ,slackware-current
Posts: 141
Original Poster
Rep:
|
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.
|
|
|
|
06-06-2009, 03:04 AM
|
#10
|
|
LQ Newbie
Registered: Oct 2006
Posts: 14
Rep:
|
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.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 04:03 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|