Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i installed debian sarge then dist-up'ed to sid.. then i compiled the new kernel 2.6.6, but it gave me this error:
Kernel panic: VFS: Unable to mount root fs on unknown-block(0,0)
i guess i didn't select the file system settings correctly when compiling the kernel..
how would i go about recompiling it?? i can still select the 2.4 at the grub menu that still works.. i need some advice especially in the lines of how to recompile, if it will write over the existing 2.6.6, and if not how i wiould remove the broken one...
TO recompile a new kernel... well... just the same way you did it the first time :P LOL
OK.... IF you didnt deleted your source files/directories then:
bash:~$ cd /usr/src
(NOTE: create a symlink, use the correct kernel
source folder name, if symlink existed already
remove it and make a new one.)
bash:/usr/src$ ln -s kernel-source-2.4.18 linux
bash:/usr/src$ cd linux
bash:/usr/src/linux$ make xconfig
(reconfigure your kernel)
bash:/usr/src/linux$ fakeroot make-kpkg clean
(lots of cleaning here)
(the value in 'append-to-version' can ve your choice. NO dashes,
all lowercase, keep the dot '.' at the beggining of the value)
bash:/usr/src/linux$ fakeroot make-kpkg --append-to-version=.030401 kernel_image
(enter root pasword)
bash:/usr/src/linux#dpkg -i kernel-image-2.6.5.030401_10.00.Custom_i386.deb
Forgot to give you a couple of tips.
a) DON'T bother with RAMDISK, will give you more troubles than you need, when in fact you dont need it !!!!!!!!!
RMADISK is used in cases where you are installing/booting from a floppy disk or a CD-ROM.
b) Be SURE you have the filesystem compiled IN the kernel and not as module. This is only relevant for the filesystem used in the hard disk where you are booting Linux from.
c) Mouse, keyboard, VGA/VESA support compiled IN the kernel, not as modules.
d) Even if you have a VESA card you DO need the VGA support too !!!
e) Pray to Saint Tux, and make an ice-cube sacrifice to him.
I'm having the same problem, used make-kpkg and all went well, installed the kernel gave /boot/grub/menu.1st a look all is well.
Reboot and BAM!
Kernel Panic: VFS Unable to mount root fs on unknown_block (0,0)
I've read several time to compile the FS into the kernel and not as a module, however I've not read how to do that exactly, I have chosen the File Systems and all the FS have *'s with them, just to cover myself.
Did you read the little HOW-TO link I posted?
What are you using to configure the kernel; xconfig, menuconfig, or config?
I used xconfig, with that front-end, IN the kernel is a 'check' mark, module is a 'dot' mark.
Are trying to use a RAMDISK ?
So, by your post, I asume you are sure the mounting point in '/boot/grub/menu.lst' is correct.
BTW, took me 32 trials to get my first kernel FULLY customized and fully functional. Not everybody is as dumb as me, so probably will take you less than that
ok.. i recompiled with the right fs settings (i use ext3.. and i checked EVERY ext3 setting to * ), and then when i boot up, it still gives me the same error! i'm certain that the new kernel was correctly loaded, as i reconfigured some other settings and those showed up in the boot up before the error. what else could be the problem??
i'm using menuconfig.. so an ASTERICKS would mean it is installed in the kernel..
RAMDISK option was UNchecked
the /boot/grub/menu.lst shows that the settings for the newly compiled kernel are exactly the same as kernel 2.4 which still loads.