FedoraThis forum is for the discussion of the Fedora Project.
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 been using Fedora literally since the first day it was released. I have always compiled my own kernels and have never had any problems. I downloaded the latest 2.6.2-1 kernel and wanted to recompile add reiserfs support, add OSS drivers and remove ALSA drivers, etc. The problem is that during the boot process, the PC freezes at the "Mounting Partitions" part of the install. Any suggestions? Thanks
Have you tried putting in the true path to the partition in /etc/fstab. I've had some trouble with the LABEL= statement that the newer versions of redhat use. Instead of LABEL=/ try just putting in say /dev/hda1 or what ever the partition is that you're trying to use. That usually clears it up for me.
Sorry, the PC freezes when it is "Mounting Local filesystems". All of the other partitions are reiserfs and I have compiled in reiserfs. Works fine with the 220.127.116.11 kernel but the latest is giving me lots of problems. Didn't work with the 18.104.22.168 kernel either.
I've been running into a similar issue. I'm using Arjanv's 2.6.2 kernel and compiled it used the following:
xconfig, make ; make modules_install
Upon completion, I reboot using the new kernel, and I get the following:
VFS: Cannot open root device "LABEL=/" 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)
The parameters in my grub menu are the same as my 2.6.1 kernel which is working fine. Any idea what suddenly changed in 2.6.2? Did I leave a step out? I read the earlier post on changing LABEL=/ to /dev/hda1, but I'm unsure of where exactly I should change that....thanks in advance for the help...=)
This file is responsible for pointing the raw device say /dev/hda1 to a mount point. / for example. Except in Redhat and Fedora they use the disk labels instead of the raw device.
If you're up and running and you open a shell just type in 'mount' and you'll see the raw mappings.
/dev/hda2 on / type ext3 (rw)
none on /proc type proc (rw)
usbdevfs on /proc/bus/usb type usbdevfs (rw)
/dev/hda1 on /boot type ext3 (rw)
none on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/hda5 on /home type ext3 (rw)
none on /dev/shm type tmpfs (rw)
/dev/cdrom on /mnt/cdrom type iso9660 (ro,nosuid,nodev,user=matt)
You can see that on my system /dev/hda2 is mounted on /
What always seems to screw up when I'm compiling a new kernel is that stupid LABEL=/ statement in the /etc/fstab file. So I just type mount find out what the true device is and not the LABEL and I replace the entry in my /etc/fstab file. It would look like this.
/dev/hda2 / ext3 defaults 1 1
Also grub often has a LABEL=/ entry that you may want to change to the raw device. This entry would be in /boot/grub/grub.conf
and would look something like this
I am using a Debian system and I had literaly the same error messages as ckozlowski
when I decided to upgrade to the 2.6.2 kernel. I duno much but what helped in my situation was to use *only* ext2 file system and to disable the ext3 journal file system whatsoever. This may sound strange since ext3 is supposed to be backwards compatible but that's what helped me get going...
I followed your directions and it worked great. Oddly enough though, when I went to compile a custom kernel, it didn't work. But Arjanv's stock kernel worked fine once your instructions were taken into account. Thanks much!
Journal File System = JFS right? Odd, I think I might have disabled support for that or something. Sounds familiar, I think I heard about something being incompatable with it and 2.6 (along with ReiserFS?) I'm just shooting from the hip here. I'm not sure what to say to that, since I'm working ok with 2.6 and ext3 now. But then again I've never worked with Debian before..I'll keep that note though. Thanks!