Red Hat custom Kernel compilation mini-How-To for Red Hat 8-9
Red HatThis forum is for the discussion of Red Hat Linux.
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.
Originally posted by gonniff
And at reboot, I select the new-kernel from the list of two kernels.
This then either ends in a kernel panic or it loads, but gives failure messages about it not supporting reiserfs, ext3, etc.
I would have thought that doing the make oldconfig would have taken the settings for the default, working kernel and then let me just proceed to build a copy of it.
Can anyone shed light on where I've gone wrong?
PS - I've done this with an installation of SuSE 8.2, but mkinitrd failed to run.
I went through all the other steps and rebooted to the new kernel option and it panicked.
But when I went back to /etc/lilo.conf and included the path for the working initrd image, it booted fine and runs fine.
If I understand correctly, you are trying to compile a 2.4.8 kernel?? You want to do a kenel downgrade??
In any case you should have no problem compiling the kenrel, but the problem regarding the panics seems to me like you have enabled some EXPERIMENTAL driver into the kenrel or in the modules. If you are using the LowLatency patch, you may need to re-nice some of the services the kernel starts, otherwise they will seg-fault. What does the panic say?? does it give any info at all (a dump core or something?) You may have hit a kernel bug rather than a compilation per se problem.
For the ReiserFS and EXT3 problem: Did you enabled support for those FS in the FS section? either as modules or into the kernel?
In the example above, I have stated to compile drivers for only the emu10k1 based card (in this case my card), the oss option is to add oss compatibilty to the driver (to play virtually any games) and the sequencer option is to activate MIDI support.
After you install you will see that the channels are muted, you unmute the channes by running the alsamixer command, but before that, make sure you run the makesnddevices script from the driver top level direcotry, otherwise the mixer will not be able to start. Another thing, you can add the alsasound init script to your init sequence, by
chkconfig --add alsasound
Then start it by:
service alsasound start
PS: Check the alsa-project page for refferences on specific card model and the modules options for modules.conf!!!, this is very important!
I have no experience with source rpm's for ALSA. I've always installed it from tarball, it allows (or at least, that is what I think) more control over the the compilation, like the fact that I wouldn't want the whole bunch of drivers compiled in, or to let me add or remove certain feature (like MIDI or AC97). So I'd rather download a newer rpm or simply install the latest sources. It'd be nice to have the guys from freshrpms to lend us the .spec file so we could build the rpms from within the already compiled code in the pure sources.