Waiting sounds wise- no use in messing up your current setup.
However, if you really wanted to see if it will apply, what you could try is copying your stock MDK kernel sources directory from /usr/src to it's own directory in /home. (Compiling there is much safer than doing it as root in /usr/src, especially for people like me still learning).Then make a backup of your .config file, and cd in a console (as user) to the new directory in /home where you copied the MDK kernel sources to, and run mrproper. Then, try applying the Hz patch. If it applies OK, do a make xconfig and load the copy of your stock .config file into xconfig., Then change the value of the Hz line to =1000Hz, and save and exit.
VERY IMPORTANT:Check the makefile extra version line at the top of the file to see if it added the -ck2 extra version when the patch applied, otherwise if you do choose to install this kernel and the name (version) is the same, it will overwrite your original modules directory, and not create a new -ck2 version. In your case, that would be a disaster.
Then you can (as user) do:
make dep make clean make bzImage make modules
If you get through these with no error outs, you are probably OK, and will then know the patch probably didn't cause any problem. Up to this point, nothing you have done could possibly affect your current kernel setup.
If you want to actually install, su to root and do:
make modules_install
This will put a new modules directory in /lib/modules with the new -ck2 version name, leaving the original untouched.
I never do the usual final "make install" to call the kernel script after that if I'm not compiling in /usr/src. I did that once, and had huge problems. I manually copy System.map and bzImage to /boot, naming them to reflect the extra version, like System.map-2.4.21-ck2, and bzImage-2.4.21-ck2. I then edit lilo, and since I don't use an initrd file for the new kernel, I delete the initrd line in the new kernel's lilo stanza, so it looks like:
image=/boot/bzImage-2.4.21-ck3 label=2421ck3 root=/dev/hda10 append="devfs=mount hdc=ide-scsi acpi=off quiet" vga=788 read-only
Then save, and run lilo as root.
Of course there's no way to know if doing all this will actually increase system response in a noticable way, even if the patch applies on the MDK kernel, without actually doing it. I can report that all the ck patches I've applied seem to work great on the vanilla 2.4.21.
Well, I was following this thread over the weekend, and so today I went ahead and followed your directions. I installed the multimedia kernel and source, then booted into the Mandrake multimedia kernel to make sure it worked - it did, at least as good as the stock Mandrake kernel.
So, I went ahead and downloaded the patch, and patched the mm kernel source, which I had copied and chowned into $HOME/src/. The patch had two minor failures, which I was able to manually fix (I've never even patched a kernel before, let alone had to manually patch some source code because the patch failed - but it was easy).
I check the Makefile, and sure enough I also had to edit the extra-version info to indicate 'ck2' so I wouldn't blow away my existing multimedia kernel modules.
Everything compiled without errors, so I went ahead and installed the modules and kernel. I am running the patched mm kernel right now, and it performs at least as well as the stock kernel and (unpatched) mm kernel. Not sure how to do any performance benchmarks, but at least nothing is broken!
-- Dave Sherman MCSE, MCSA, CCNA I think animal testing is a terrible idea; they get all nervous and give the wrong answers.
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
