FedoraThis forum is for the discussion of the Fedora Project.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Ok i think what i did is probably a simple fix with a little guiding to get me straightened out. Ok i did another FC2 fresh install, getting good at that. I decided instead of downloading a new kernel i was just going to do it with my little flashing icon, UP2DATE. Ok everything seemed to go well, wow what a new kernel version !. Well i am a tweaker and afer updating a kernel i like to go in and trim out the fat, get it nice and small. Normally i have no problem, but where is the source to this thing ??? Ok next step was to go download the kernel, which was like 2.6.8.1 something or another and unzip it into /usr/src then make my link. I then did all of the normal
make xconfig
make bzImage
make modules
make modules_install
make install
Well after this reading my old instructions the /boot files looked odd, is that because they were done with Up2date ?? My grub looked like this after all was said and done.
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda2
# initrd /initrd-version.img
#boot=/dev/hda
default=2
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
title Fedora Core (2.6.8.1)
root (hd0,0)
kernel /vmlinuz-2.6.8.1 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.8.1.img
title Fedora Core (2.6.8-1.521)
root (hd0,0)
kernel /vmlinuz-2.6.8-1.521 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.8-1.521.img
title Fedora Core (2.6.5-1.358)
root (hd0,0)
kernel /vmlinuz-2.6.5-1.358 ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.5-1.358.img
Ok the problem is the one marked 2.6.8-1.521 is the one i am on now, the 2.6.8.1 gives me a kernel panic VFS something or another error right after boot. I could care which one works as long as i can do my tweaking, i am a tweak junkie.
I don't usually do make install, I just copy bzImage to /boot/. Last time I remember doing a make install I ended up with LILO. Anyway, at least you're booting into grub right?
Anyway, try this for your grub entry:
title Fedora Core (2.6.8.1)
root (hd0,0)
kernel /vmlinuz-2.6.8.1 root=/dev/hdxx
Distribution: RH, FC 1-6, F 7-21, Debian, LinuxPPC, Knoppix, Ubuntu, Yellow Dog
Posts: 176
Rep:
I remember having the same problem after tweaking. Turned out that I had to turn on RAM disk support for initrd (it is off by default in 2.6.8.x and later versions of the kernels).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.