I thought of that and that's why I reinstall the kernel and I patched it with the patch from kernel.org, i.e 2.6.0-bk. The problem with that was that the kernel could not load any module. The reason , I believe, was that the kernel was 2.6.0-bk but in the /lib/module folder I had only the 2.6.0 folder. How did you solve this problem?
Anyway, I tried to patch the kernel with the alsa patch and it did not work. (I was getting the message that I posted in my previous email.)
BTW, to patch the kernel I used patch --dry-run -p1 -i patch.file
If you used the --dry-run option with both patches, then nothing got patched at all - only tests have been performed, and you still have the plain vanilla kernel and the 2.6.0 modules folder. You might also see that from the Makefile in the upper kernel source directory. I bet, at the top it reads:
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 0
EXTRAVERSION =
After a successfully performed bk3 patch, the fourth line should read something like:
EXTRAVERSION = bk3
So please, no dry-run after its test has shown that the patching would be ok.
Klaus
------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
