LinuxQuestions.org
Support LQ: Use code LQ3 and save $3 on Domain Registration
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 11-01-2004, 02:06 PM   #1
Xavius
Member
 
Registered: Mar 2004
Posts: 107

Rep: Reputation: 15
unable to boot!!!!! kernel panic error


My Slackware Box was working perfectly with kernel 2.4

then I installed the kernel 2.6.7 from CD 2, following the instructions found on the web and on the Slackware docs too.

I have updated LILO, apparently without problems, adding a new entry for Linux with 2.6.7 kernel

after the reboot, I choosed Linux with kernel 2.6.7 and it worked good (I have some problems with the sound server but... i was only testing the 2.6.7 kernel, so i wasn't worried about it)

reboot again,

choose the usual Linux entry (with kernel 2.4)
(that wasn't modified at all)

ERROR: kernel panic, unable to mount Root FS

WHAT's happened???????????

I mean: if it was working before and I have not modified it, and i have followed all the instructions, why it's broken now?

thanks a lot!
 
Old 11-01-2004, 02:21 PM   #2
secesh
Senior Member
 
Registered: Sep 2004
Location: Savannah, GA
Distribution: Ubuntu, Gentoo, Mythbuntu, ClarkConnect
Posts: 1,154

Rep: Reputation: 47
given that 1) you did not recompile your 2.4 kernel, and 2) you did not change the filesystem, i would say you mucked up lilo.conf, let's see it in here--
 
Old 11-01-2004, 02:32 PM   #3
Xavius
Member
 
Registered: Mar 2004
Posts: 107

Original Poster
Rep: Reputation: 15
Post

thanks for your attention secesh

1) no changes and/or recompilations with kernel 2.4

2) no changes at all with filesystems.......

Installing the Kernel 2.6.7, of course, I have added a new entry in the LILO config file, but I have unchanged the other sections. I have only added a new entry... that's all
 
Old 11-01-2004, 02:32 PM   #4
Cedrik
Senior Member
 
Registered: Jul 2004
Distribution: Slackware
Posts: 2,140

Rep: Reputation: 242Reputation: 242Reputation: 242
Maybe the kernel 2.6.7 install did change the vmlinuz symlink in /boot that points to the kernel,
ie :

before :
vmlinuz -> vmlinuz-2.4.26

After:
vmlinuz -> vmlinuz-2.6.7

If it is that, just change the 2.4.26 lilo entry so that boot with vmlinuz-2.4.26 instead of just
vmlinuz.

Last edited by Cedrik; 11-01-2004 at 02:33 PM.
 
Old 11-01-2004, 04:32 PM   #5
Xavius
Member
 
Registered: Mar 2004
Posts: 107

Original Poster
Rep: Reputation: 15
Thanks a lot Cedrik

You was right! (and your solution works ok)

thanks
 
Old 11-01-2004, 07:20 PM   #6
mcd
Member
 
Registered: Aug 2003
Location: Boulder, CO
Distribution: Slackware, RHEL, CentOS
Posts: 825

Rep: Reputation: 33
the whole idea of having the symlink vmlinuz seems unneccessary to me, to be honest. isn't it clearer and simpler to just use the name of the kernel image you want to boot in lilo.conf? does anyone know the history behind this tradition? the only time i can see it coming in useful is to have only two entries in lilo.conf like this:

image = /boot/vmlinuz-2.4.26
label = stable
read only

image = /boot/vmlinuz
label = unstable
read only


and then have vmlinuz point to whichever unstable kernel you feel like testing that day. it could theoretically save you the trouble of changing the lilo.conf file, but instead you have the trouble of constantly changing the symlink. also, would that even work? i seem to remember not being able to boot a new kernel after trying something like that...but it was late at night after recompiling for like the third time, so i don't know if it was due to that or not.
 
  


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
Kernel 2.4 in Zipslack (Waring: unable to open an initial console | Kernel Panic...) kurtamos Linux - General 2 05-10-2006 12:58 PM
Weird Kernel Panic and boot error Daegalus Slackware 6 01-19-2005 04:59 PM
VFS: Kernel panic error at boot (2.6.10) deveraux83 Slackware 2 12-30-2004 01:36 AM
booting error: Kernel Panic: vfs: unable to mount root fs on 01:01 eam Linux - General 2 01-26-2004 08:48 PM
error:"kernel panic: VFS: Unable to mount root fs":-( shyguy Linux - Newbie 1 07-23-2001 04:03 PM


All times are GMT -5. The time now is 09:27 PM.

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