You don't get it do you?

CSSU THUMB comes with its own kernel, which is KP50 with the necessary patches to make it able to run thumb2-compiled code without crashing.

Meaning (in simple words): it's EITHER cssu-thumb OR kp50. Not both.

I understand that you have problems that somehow "require" kp50, even if kp50 is actually "included" in the cssu-thumb kernel.

Well, say thanks to the brainfvcked debian package system. We have to live with it though.

Now, if e.g. CLEVEN says it needs kp50 no-matter-what then go to the cleven developer and tell him to relax the requirements (I don't know what's worse, the debian package system or the debian package authors, probably an entangled combination of both).

Anyway, to make it short: if you want to EXPERIMENT with cssu-thumb then I'd suggest to stick to it, and ignore any other programs that may not work with it. If you want a "functioning" system (by whatever definition of function you may have, e.g. "cleven must work") then please don't experiment anymore with cssu-thumb until it stops being an experiment. Then (hopefully) the various kernel-maintainers and the various-I-depend-on-this-kernel-package-maintainers will get together and think of a system to make this work nicely (e.g. "provides: thumb2, overclocking, etc.").

Add.: didn't notice @misiak's post above (http://talk.maemo.org/showpost.php?p...&postcount=241). Read that too, twice.