Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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 have compiled a kernel from source and am trying to boot with it. (I am using Ubuntu 8.10.) I added a new entry to my grub file by copying a working entry. A snippet of my /boot/grub/menu.lst file is show below.
bzImage is my compiled kernel. I created the initramfs file via the command mkinitramfs -o initramfs `uname -r`.
When I select the custom kernel from the grub boot menu, it outputs a bunch of text and eventually outputs the following:
WARNING: Couldn't open directory /lib/modules/2.6.28: No such file or directory
FATAL: Could not open /lib/modules/2.6.28/modules.dep.temp for writing: No such file or directory
Begin: Waiting for root file system... ...
Gave up waiting for root device. Common problems:
ALERT! /dev/disk/by-uuid/778cb529-8914-451a-97ee-fb2d8ae404ae does not exist. Dropping to a shell!
BusyBox v1.10.2. (Ubuntu 1:1.10.2-1ubuntu6) built-in shell (ash)
My guess is that either:
1) I configured the grub file incorrectly
2) The initramfs file was not properly created
Please help! Thanks in advance.
Last edited by titaniumdecoy; 12-30-2008 at 02:55 AM.
It seems like your ramfs was made without the "device mapper" support, that loads the module dm-mod.ko. You can solve by creating the ramfs file with the right options (I don't know the exact option as I use mkinitrd), or by compiling the device mapper into the kernel itself, not as a module
@Quakeboy02: Thanks, I have spent so long on this method already though I want to give it another shot.
Suit yourself, but using the Ubuntu (Debian) method, there are very few steps that you have to take.
I gave up on using the UUID in grub. So now I have this in my /boot/grub/menu.lst file:
title kernel 2.6.28
kernel /boot/vmlinuz-2.6.28 root=/dev/sda1
Here are the entries in my menu.lst file for 2.6.28. I'm not sure if your issue is that "ro" is missing or not. I have no way of knowing if you added a suffix; in my case "-k8". What is the actual directory name in /lib/modules?
title Debian GNU/Linux, kernel 2.6.28-k8
kernel /boot/vmlinuz-2.6.28-k8 root=/dev/sda1 ro
title Debian GNU/Linux, kernel 2.6.28-k8 (single-user mode)
kernel /boot/vmlinuz-2.6.28-k8 root=/dev/sda1 ro single
Last edited by Quakeboy02; 12-30-2008 at 03:43 PM.
I tried the method suggested by Quakeboy02. I wiped the system to make sure the old kernel was not in the way. I let the Ubuntu (Debian) package system take care of everything for me. In the end, I got the exact same error. I am using defconfig which includes device mapper support.
Glad you got it working! I wish I knew exactly what was wrong. I saw one with similar issues not too long ago, and it was Ubuntu, as well. I suspect that it was the CONFIG_SCSI line that fixed it, but the problem most likely relates somehow to initrd, like you said in your first post. On Debian I am able to get away with CONFIG_SCSI=m.