LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
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 05-02-2011, 10:57 PM   #1
Tribulation
Member
 
Registered: Jun 2008
Distribution: Slackware
Posts: 129

Rep: Reputation: 27
Slackware 13.37 Kernel Panic


I installed Slackware 13.37 today, fresh install. I added the generic 2.6.37.6 kernel to lilo, rebooted, and ran with it. I transferred some stuff to my hard drive and installed a few things, reboot again and now I can't boot up with my kernel of choice (but I can with the huge kernel). It stops during the boot process and says

Code:
[1.785238] No filesystem could mount root, tried: romfs
[1.785342] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
[1.785417] Pid: 1, comm: swapper Not tainted 2.6.37.6 #2
After that is a line that says Call Trace and several lines after that with stuff that makes no sense to me and that I don't feel like typing out, but will if it is relevant. I've never experienced a Kernel panic before, any ideas on how to solve this problem would be much appreciated.
 
Old 05-02-2011, 11:06 PM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,670

Rep: Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786
you need to create initrd if you want to use generic kernel
see /boot/README.initrd for more detail
 
Old 05-02-2011, 11:11 PM   #3
genericflounder
LQ Newbie
 
Registered: Jan 2010
Posts: 8

Rep: Reputation: 0
Quote:
Originally Posted by willysr View Post
you need to create initrd if you want to use generic kernel
see /boot/README.initrd for more detail

The man page for mkinitrd is incredibly helpful as well.
 
Old 05-02-2011, 11:15 PM   #4
Tribulation
Member
 
Registered: Jun 2008
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 27
Quote:
Originally Posted by willysr View Post
you need to create initrd if you want to use generic kernel
see /boot/README.initrd for more detail
I did, but I guess I'll use it again and see what happens..
 
Old 05-02-2011, 11:24 PM   #5
Tribulation
Member
 
Registered: Jun 2008
Distribution: Slackware
Posts: 129

Original Poster
Rep: Reputation: 27
Well I ran the mkinitrd command again and it's working again... Wonder what happened before..
 
Old 05-02-2011, 11:31 PM   #6
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,670

Rep: Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786Reputation: 1786
probably missing or incorrect parameter
 
  


Reply



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 panic on boot with new SATA drive Slackware 12 kernel: 2.6.21.5 theapodan Linux - Hardware 3 05-18-2009 03:02 PM
kernel panic: kernel-2.6.24.3 + alsa-1.0.16(or15) + Slackware-12 ludist Slackware 1 03-07-2008 09:14 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:14 AM.

Main Menu
Advertisement
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
Open Source Consulting | Domain Registration