Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
HI
this is my 3rd day ..n i m still stuck with kernel panic ... i hav search n tried every possible solution but nothing worked ...
i hav upgraded my kernel from 2.4.X(default in Slackware 10.2) to kernel 2.6.17.6 ... i m using ext3 fs n enabled ext3 fs in the kernel as builtin(no as module) ... now when i compile n install my kernel ... n reset it .. booom .... a kernel panic error...
u can see my system detail below ....
Code:
VFS: Cannot open root device "303" or unknown_block(3,3)
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on unknown_block(3,3)
u can see my lilo.conf
Code:
# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
timeout = 300
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/bzImage
root = /dev/hda3
label = Linux
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
This sort of error almost always comes from one of two things, the filesystem or hard disk support. Since you've compiled in the file system, its likely you didn't compile in support for your hard disk drive (in Device Drivers > ATA/ATAP/MFM/RLL support). Again, this needs to be in the kernel and not as a module.
Hm. Googling on that error was surprisingly uninformative. I'm going to guess that this has something to do with the intial RAM disk support. Check in Device Drivers > Block Devices that you have RAM Disk support and Initial RAM Filesystem are built into the kernel. For RAM disks, I use the defaults for number of RAM disks (16) and RAM disk size (4096). You'll probably want to check on enabling loopback device support as long as your there.
The item I've bolded you should delete. It's linking to the config file for the kernel you're not using. I have made this mistake before. If it doesn't work you can always relink it after.
Just in case... make a slackware boot disk in case you get funky problems that won't let you go back and relink that old config... but I've never needed that. Never hurts to be careful
That's the only reason I can think of why the kernel is having an I/O sync error.
With your new kernel you should either compile the .config file into the kernel or put it into /boot with your kernel. The kernels that don't have the config file compiled in will look for a file "config" and if it's different than what you compiled with it will complain like a child.
okz .. here is update ...
i have notice the two lines about kernel panic
Code:
attempt to access beyoud end of device
hda2: rw=16, want=8, limit=2
Kernel Panic - not syncing: I/0 error reading memory image
i dont know y my kernel is finding .. hda2 .. i dont hav any partition hda2 .. u can see my FSTAB above i had posted....i think this is Lilo problem ..... now how could i disabled it ?? ...
It probably isn't a LILO problem since this is specific to this kernel, and given the lilo.conf entry you posted, it would affect ALL kernels.
To be honest, I'm kind of stumped. One thing to try would be to load one of the 2.6.x stock kernels from Slackware (have a look in testing for 2.6.13). If that works, you can swipe the .config from that kernel, then run make oldconfig for your 2.6.17.6. If that works, then you can start adjusting the config until it better meets your needs.
The only other question I'd have is whether or not you have vfat compiled into the kernel?
The only reason I ask is that your hda2 is actually an extended partition which is the sum total of hda5 and hda6 which are logical partitions. If it's complaining about hda2, then it might not know that it's an extended partition or doesn't recognize the type. This is a problem because the logical (hda5, hda6) partitions occur in the space that would be hda2... which exists before your root partition (hda3). If it can't figure out your logical partitions, then it probably can't figure out where hda2 (hda5 + hda6) ends and hda3 begins. Since your Slackware with the 2.4 kernel works fine I can only assume that the kernel your compiling sees the partitions but has no clue what they are and doesn't want to do anything for fear of overwriting data.
It's just a thought. I hope it works for you because I'm out of ideas.
i guess i m also having the same problem .. where i think in daniel's problem the 01:00 is the device(partition) with major 1 n minor 0 ..
in the second link u can see that dainel has solved the problem by setting ram_disk in grub .. i dont know how to do it with lilo .... need suggestiosn...
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.