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.
I have a true dedicated server (not KVM) hosted remotely running Fedora. It originally had 11, but I recently live upgraded it to 12 (rather successfully, I might add). However, the hosting provider installs custom kernels on all their machines... they don't require you to keep it, but it is installed by default for "stability/optimization reasons".
It's a fairly generic, 2.6.13.5 kernel, however I cannot get the machine to boot a different one. I have vmlinuz-2.6.31.6-145.fc12.x86_64 installed as well as the matching initramfs, and they are the only entries in grub.conf. I've even moved the old kernel (a bzImage) into a different folder... but it STILL boots it, which leads me to believe that it isn't *really* reboot when I do 'shutdown -r now'.
I am assuming that (above) is a typo and should be 2.6.31.5. Personally I would go look for this issue as a articfact of doing an yum upgrade rather than the clean install, as is officially suggested. I cannot tell you how many yum upgrades I have wiped and done a clean install, just to see all the issues go away. 9/10 there is also a noticeable speed increase (config files that do not crash things but they do not run properly either).
If it is not a typo you potential have a huge can of worms. There are a ton of changes that have been made between 2.6.13 and 2.6.31.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.