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.
So this seems like a rather dumb problem but it's starting to a bit concerning.
Two days ago I booted me system and udev decided for no appearent reason, that it no longer liked any of my modules. I tried fixing the problem for a while then I realized there was a good reason I installed multiple partitions.
So, I made a Crunchbang install usb, and planned to only replace /, /boot, and the bootloader.
I had trouble immediately, which I had never had before. It booted fine and started the install process but when it began searching for data on the "cd" it couldn't find it. This was easy enough to fix by just opening a shell and mounting /dev/sdc at /cdrom. After that, fixing the partitions worked flawlessly, but when I went to install grub it wasn't able to load data off the cd. I tried the same thing again with no luck.
Now I'm trying to just use a grub bootloader to boot but once again I'm having trouble. I've done this before a while back and don't remember having any trouble. I'm using "super_grub_disk", and trying to manually load the kernel.
I thought I remember the correct order of commands being root,boot, and initrd.
Root is no longer a command though. I tried legacy_kernel, xnu_kernel, and xnu_kernel64 however none of them will load it. I know I'm typing it in correctly because I am using tab to retrieve the full name of the kernel. Is there another command that I should be using to load the kernel?
btw this system doesn't have a cd-rom so burning an install cd isn't an option.
Thanks Spiky0011, that worked, unfortunately I still get a kernel panic. It says it can't find my root partition at (hd0,0) even though I'm using (hd1,8)
I've tried it with and without including the ramfs....
The strangest part is that I just got this laptop like 6 months ago, I didn't have any trouble with the same installer last time.