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 usually run mkinitrd in /boot, in this case I do not need to use full paths. <kernel> refers to the kernel binary, in your case vmlinuz-220.127.116.11y, <initrd> to the name you would like to give the ramdisk, e.g. initrd-18.104.22.168y (SUSE naming). If you run mkinitrd from outside /boot, the command could look like this:
I'm sure you are getting tired of walking me thru this, but I really do appreciate it.
Created the initrd file correctly, I think.
Error popped up that modules.dep may need to be updated. I may have jumped the gun, but I tried to reboot with the new kernel and got nothing. No errors, no nothing. After I selected the net kernel, screen went blank and nothing else happened. I did reconfigure the menu.lst file to include the new kernel image and initrd file.That is the only difference from the old configuration.
Sorry, I went home yesterday, but I see you still had help
Not mounting rootfs can have several causes:
1. rootfs could not be found due to false parameters in the bootloader
2. rootf could not be mounted because the HDD controller driver or the filesystem driver was not present at that stage. This could either be a unreadable ramdisk (you should see if the kernel reads the ramdisk) or that the driver was not included into ramdisk.
Did you see whether the HDD was recognised and the initrd properly loaded?
I think the more interesting part comes thereafter. Are the drivers (e.g. reiserfs) loaded from ramdisk, are the drives properly recognised.
BTW: did you upgrade the package mkinitrd before? Have a look here, if not: http://www.linuxforums.org/forum/top...tml&highlight=