LinuxQuestions.org
Review your favorite Linux distribution.
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 06-11-2003, 02:29 AM   #1
KrYpToN
Member
 
Registered: Aug 2002
Location: England
Distribution: Gentoo
Posts: 38

Rep: Reputation: 15
Exclamation Kernel Panic


Hi guys, need some help please. When I boot into Linux I get:

Kernel Panic: VFS: unable to mount root fs on 03:01

Here is my lilo.conf

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
message = /boot/boot_message.txt
prompt
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# VESA framebuffer console @ 1024x768x256
vga = 773
# End LILO global section
# Linux bootable partition config begins
image = /boot/beta
root = /dev/hda1
label = Beta
read-only
image = /boot/vmlinuz.old
root = /dev/hda1
label = Slack.old
read-only



# Linux bootable partition config ends

(I took out the commented vga sections)

The path to the 'beta' kernel is correct (I can still boot into the Slack.old kernel)

This is with Kernel 2.4.20

Any help would be much appreciated,

Thanks,
 
Old 06-11-2003, 06:50 AM   #2
je_fro
Member
 
Registered: Nov 2002
Location: /texas/austin/home/desk
Distribution: Gentoo
Posts: 341

Rep: Reputation: 30
What is the filesystem?

And did you enable support for it in the kernel?
Did you copy /usr/src/linux/arch/i386/boot/bzImage /boot/Beta ?
 
Old 06-11-2003, 07:12 AM   #3
chakkerz
Member
 
Registered: Dec 2002
Location: Brisbane, Australia
Distribution: a few...
Posts: 654

Rep: Reputation: 32
propably the file system, for instance if your partitions are in reiser format, and forgot to compile reiser support into the kernel.

another possibility is that you disabled VFS support in the kernel, though i think that error looks differently.

I got a very similar message when i used the "bare" kernel that is supplied on the CD and it wanted the kernel on a floppy ... but you look like you recompiled a new kernel. So just go in, check the options (prolly make xconfig) and
make dep clean bzImage
make modules
make modules_install
copy arch...
copy System.map
lilo (don't forget to do that, or else you get a kernel panic also)
 
Old 06-11-2003, 07:45 AM   #4
KrYpToN
Member
 
Registered: Aug 2002
Location: England
Distribution: Gentoo
Posts: 38

Original Poster
Rep: Reputation: 15
Ok, these are the steps I took to build it:

$ make menuconfig (configured everything in there including file systems etc etc)
$ make dep
$ make clean
$ make bzImage
$ make modules
$ make modules_install

I then edited my lilo.conf file in /etc, then typed:
$ lilo
to update it

I then rebooted

There must be something very small wrong because I can use a previously compiled kernel that I made from the same source and I only changed a couple of things.

It tells me to look at the 'root =' parameter in lilo.conf, but I have and it points to the correct image.

Thanks for your help so far,
 
Old 06-11-2003, 08:03 AM   #5
chakkerz
Member
 
Registered: Dec 2002
Location: Brisbane, Australia
Distribution: a few...
Posts: 654

Rep: Reputation: 32
ok, but did you copy the file in arch/i386/boot/bzImage to /boot/newKernelImage
and System.map to /boot/System.mapNewKernelImage

(you need to do that before you run lilo)

And my first guess is still that you disabled LVM in "Multidevice Support (RAID and LVM) ... though just looking at the config thing it doesn't make sense anymore ... so i think i'm really wrong on that one. Check the filesystems section though.
 
Old 06-11-2003, 08:29 AM   #6
KrYpToN
Member
 
Registered: Aug 2002
Location: England
Distribution: Gentoo
Posts: 38

Original Poster
Rep: Reputation: 15
Yeah, I did copy both of the files across the files across, and yes I think I disabled multidevice support . I'll try that when I get home and see what happens, thanks again for your help,
 
Old 06-12-2003, 06:35 AM   #7
chr
LQ Newbie
 
Registered: May 2003
Location: Reunion Island
Distribution: RedHat 6.2 , RedHat9.0, Slackware9.0
Posts: 10

Rep: Reputation: 0
May be you must use mkinitrd to create a RamDisk image.
Then u must give the path of the image in /etc/lilo.conf. (an entry which looks something like 'initrd=/path/to/ramdisk' in lilo.conf - cf man lilo.conf)
 
Old 06-12-2003, 07:28 AM   #8
KrYpToN
Member
 
Registered: Aug 2002
Location: England
Distribution: Gentoo
Posts: 38

Original Poster
Rep: Reputation: 15
Sorted it now guys thanks . I just copyed the default kernel source back into Linux-2.4.20 and I just used that with caution :P

Thanks for all your help ,
 
  


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 2.4 in Zipslack (Waring: unable to open an initial console | Kernel Panic...) kurtamos Linux - General 2 05-10-2006 12:58 PM
kernel panic: try passing init= option to kernel...installation with Red Hat 9 kergen Linux - Hardware 1 09-30-2004 03:28 AM
Kernel panic puts me in a panic theeeg Linux - Software 2 07-31-2004 04:46 PM
kernel panic (narius panic) narius Linux - Newbie 3 06-20-2002 03:56 PM
Kernel panic making me panic! Linux_N0oby Linux - Software 19 05-29-2002 12:31 AM

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

All times are GMT -5. The time now is 03:56 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