> It's similar to what I reported a time ago after a MacOSX-upgrade (Panther). > Benjamin Herrenschmidt recommended to upgrade my 2.4.* kernel which > solved the problem, which, as he explained short, was in some context > with cpufreq. No, the problem must be different. The fix that went into 2.4 was first developped in 2.6 ;) Try adding "printkbtext" to your command line to get some more debug output Ben.