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.
fedora core 2 kernel 2.4.22-1.2115, i downloaded 2.6.7 kernel compiled with no problem, vmlinuz-2.6.7 is at /boot grub.conf is automatically changed as well. but when i start the system on new kernel, the screen truns into pitch black nothing else, no error, nothing.
I then made a new soft link System.map to System.map-2.6.7, tried , still same problem.
I thoguht the make install after all these make modules, make modules_install will give me dual boot, but sth went wrong, i compiled again still same result.
anyone done dual boot kernels on fedora can give me some instructions please
$ make oldconfig
$ make menuconfig (and configure whatever I want and remove things that I don't want)
$ make all
$ make modules_install
$ make install
I to was having trouble compiling the 2.6.7 kernel in fedora core 2. I went to do make xconfig picked what i wanted and didnt want. I than compiled using the rest of the commands and when i went to boot the new kernel it would freeze and not go any further than saying loading swap partition. So i than recompiled the kernel with the default selected and just changed my processor type and added firewire support. I than did the rest of the commands and rebooted the machine to load the new kernel. Everything worked with the defualts, only issue is that my module folder is a whopping 310 megs and not 39 megs as my reg. kernel was. If anyone has any suggestions please help us out.
I've messed around compiling and recomiling the kernel a bunch of times. My suggestion, for what it's worth, is to get the latest FEDORA kernel from Red Hat (source too). They are in RPM format, and all you have to do is install them like this:
RPM -ivh [kernel name].rpm
I would recommend you do not use:
RPM -Uvh
The "U" means "Upgrade" as opposed to the "i" which means "install". You want to keep your old kernel in case there are problems with the new one. Generally speaking though, if you use kernel upgrades from Red Hat as opposed to vanilla kernels built and compiled by you, then you won't have any problems.
If you're just wanting to tinker and learn, then by all means do what you're doing. It is very "trial and error" type work though, and you will likely break things.
i need source , coz i need to patch it up with epia patch on my epia board.
i changed processor type from nehemian to c3 still same problem , on boot, nothing shows.
Originally posted by taoweijia i need source , coz i need to patch it up with epia patch on my epia board.
i changed processor type from nehemian to c3 still same problem , on boot, nothing shows.
Are you using a Red Hat kernel or just a generic kernel from kernel.org?
Red Hat kernels are optimized and work better on a Red Hat system. If you are running Fedora Core 2, then I suggest only using 2.6.x kernels from Red Hat for Fedora Core 2.
You need to go into your /boot/grub/grub.conf and change your "root=LABEL=/" to "root=(where your / is).
You can find out where your / is by doing a "fdisk -l".
Are you guys remembering to "/sbin/mkinitrd /boot/initrd-2.6.7.img 2.6.7"?
Secondly, make sure you're doing stuff in the right order, etc. Here is a good guide for that.
Finally (and most likely), those of you not being able to boot have deselected some important option in the configuration for your kernel. Do like garretwp and start with the default fedora configurations (found in "/usr/src/linux-kernel-version/configs/"). Copy one of these to your new kernel source directory as .config, then when you go through the configuration the first time, only change a few things that you're *sure* about. If it works, go through a second compile and select less. And so on. Good luck.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.