Caution: If the last supported CPU model was x0F (decimal 15), I would
suspect that the next model that you need to support is decimal 16 (x10),
not hex 16 (x16). It's easy to mix these things up, so if and when you get
the revised coretemp module built and loaded, you /may/ need to change
your x16 to x10 to get it to work. Just a thought... something to be on
the lookout for, unless the manufacturer's documentation clearly states that
it's x16 (not decimal 16).
Adam wrote:
>> So at present in the current "stable" vanilla kernel, the "Family 6" CPUs
>> with model numbers > 15 [hex 0xf] are currently "Unknown". And
>> with 'cat /proc/cpuinfo' you can see both the "cpu family" number as well as
>> the "model" number to verify that that's what you have.
>>
>>
>
> /* check if family 6, models e, f, 16 */
> if ((c->cpuid_level < 0) || (c->x86 != 0x6) ||
> !((c->x86_model == 0xe) || (c->x86_model == 0xf) ||
> (c->x86_model == 0x16))) {
>
> The check for 0x16 is the new part, and I changed coretemp.c. Is there
> a relatively simple way to compile just the coretemp module? I tried
> compiling it as if it were a standalone program, and of course that failed.
>
_______________________________________________
Mid-Hudson Valley Linux Users Group http://mhvlug.org
http://mhvlug.org/cgi-bin/mailman/listinfo/mhvlug
Upcoming Meetings (6pm - 8pm) MHVLS Auditorium
Feb 6 - DBUS
Mar 5 - Setting up a platform-independent home/small office network using
Linux
