DebianThis forum is for the discussion of Debian Linux.
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've got a strange problem when compiling my own 2.6.3 kernel: my method is making a debian package of it with make-kpkg buildpackage -rev full1 kernel_image. After that I install the image with dpkg-i kernel-image-2.6.3_full1_i386.deb. It installs and updates grub automatically. When I try to boot on it it fails, giving the message:
VFS: Cannot open root device "hda7" or unknown block (0,0)
Please append a correct "root=" boot option
kernel panic: VFS: Unable to mount root fs on unknown-block (0,0)
I've taken a look at my menu.lst file in /boot/grub, and the entry for my new kernel doesn't have a line about initrd. In /boot/grub/ there isn't even a initrd.img for the new kernel. For the other kernels (2.6 and 2.4, which I didn't compile myself) there is.
At first I had disabled a lot of modules with "make menuconfig". This time I didn't change anything with "make menuconfig", but it hasn't solved the problem at all.
You either need to use --with-initrd I think it is called in the compile line or select as builtin the module for your / file system when you compile. If you are using ide-scsi for burning you will not want to use the 2.6.3 at all there is a bug in it that froze my computer solid and I am pretty sure that it caused the file corruption in my reiserfs as well, 2.6.4-rc3 solved both problems at least no file corruption so far and it wants to burn again so thats a good sign.
Originally posted by HappyTux You either need to use --with-initrd I think it is called in the compile line or select as builtin the module for your / file system when you compile.
Yea he will need to compile the file system of his "/" but also he will need IDE support if he is using a IDE HDD and also the IDE chipset he is using if he will not be using a initrd. You should also turn off initrd support if it is checked as this may cause a similiar problem as before(it did for me).
If you are using ide-scsi for burning you will not want to use the 2.6.3
No need to use ide-scsi no more for burning. ATAPI devices work without it. Well mine did.