skunk ... T2500 (core duo) and the config for 3.6.2 (geek-sources). Note that acpi_cpufreq is blacklisted in /etc/modprobe.d/blacklist.conf and that /etc/modprobe.d/phc-intel.conf is removed/commented.

amen... thank you anyway
if somebody has a clue about what can be wrong, just knock...
as i said the only thing that changes is the kernel version: working till 3.4.14 and not working starting from 3.5.2
thank you.

skunk ... the only thing I can think of is the rules that the documentation for phc-intel suggests to add to /etc/modprobe.d/phc-intel.conf ... I noticed myself that at some point these stopped working and so I commented the rules and added 'blacklist acpi_cpufreq' (also cpufreq_stats if you have it) to /etc/modprobe.d/blacklist.conf. So I would check there and make sure that no rules are in place (other than the blacklisting).

skunk wrote:

as i said the only thing that changes is the kernel version: working till 3.4.14 and not working starting from 3.5.2

It was probably about 3.5.2 when I noticed the suggested phc-intel.conf caused some issues.

skunk ... the only thing I can think of is the rules that the documentation for phc-intel suggests to add to /etc/modprobe.d/phc-intel.conf ... I noticed myself that at some point these stopped working and so I commented the rules and added 'blacklist acpi_cpufreq' (also cpufreq_stats if you have it) to /etc/modprobe.d/blacklist.conf. So I would check there and make sure that no rules are in place (other than the blacklisting).

skunk wrote:

as i said the only thing that changes is the kernel version: working till 3.4.14 and not working starting from 3.5.2

It was probably about 3.5.2 when I noticed the suggested phc-intel.conf caused some issues.

this is just grasping at straws, but you could unmerge
phc-intel and then build the module manually from
the phc-intel sources; maybe there will be some hint
from the result ..._________________.... there is nothing - absolutely nothing - half so much worth
doing as simply messing about with Linux ...
(apologies to Kenneth Graeme)

there is no /etc/modprobe.d/phc-intel.conf file on my system and the only modprobe rule related to this is the blacklisting of acpi_cpufreq...

skunk ... I just want to make sure, you had said as much above but I thought perhaps you had read the reference to /etc/modprobe.d and thought of blacklist.conf, and perhaps not considered the phc-intel.conf. Thats why I said that would be the only thing that comes to mind, and you should check.

I can not remember 3.4 or 3.5, the kernel implements auto module load function. So you dont have to use modprobe. But you know phc-intel and acpi_cpufreq can not be loaded at the same time. So you have to change one line of kernel source

i13m ... interesting, but in my case I have both acpi_cpufreq and phc-intel as modules (with the former blacklisted) and phc-intel is loaded without any change having been made to the kernel. This has been the case all through 3.4.x, 3.5.x and now 3.6.x.

tried, but unfortunately it doesn't work...
the phc-intel module doesn't even get loaded, however after boot i can modprobe it, but again, no phc* files are created...
i went back to acpi-cpufreq removing it from /etc/modprobe.d/blacklist.conf and i noted it doesn't get automatically loaded after reboot (which was happening before and because of this i'd to blacklist it).
i wonder if this behavior has something to do with my phc issue...

For those willing to test latest RC kernels (also might be helpful to maintainer) and be able to use phc-intel here is a slightly updated patch for PHC-intel to build against 3.11-rc linux kernels. Tested on my Dell Latitude E6400 with Core 2 Duo P8600 CPU for more than a week already.

If you are as lazy as me, and don't want to modify the .ebuild, just replace the original phc-intel-0.3.2.12.1-r5-3.7.patch with the file below and re-digest the .ebuild.

For those willing to test latest RC kernels (also might be helpful to maintainer) and be able to use phc-intel here is a slightly updated patch for PHC-intel to build against 3.11-rc linux kernels. Tested on my Dell Latitude E6400 with Core 2 Duo P8600 CPU for more than a week already.

If you are as lazy as me, and don't want to modify the .ebuild, just replace the original phc-intel-0.3.2.12.1-r5-3.7.patch with the file below and re-digest the .ebuild.