Chris Knadle wrote:
>> Jan 11 17:18:00 eris kernel: coretemp: Unknown CPU model 16
>>
>> I think this tells me something useful, but I'm not yet sure what.
>> AFAIK my CPU's an ordinary Intel Celeron 420; I don't see why I should
>> get "unknown CPU model."
>>
[snip]
> 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.
>
[EMAIL PROTECTED] ~]$ cat /proc/cpuinfo | head -4
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 22
Okay, that explains things. I actually managed to find the patch for
coretemp.c for my kernel, which is:
/* 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.
>> I looked through all of /proc and /sys and didn't find anything that
>> seemed relevant. OTOH the script I wrote to search recursively only
>> looked at 'visible' directories and files. Is there any way to have
>> something like "for FOO in *" in a bash script also return files and
>> directories that start with a period?
>>
> It may be that it's required to load an ACPI module to get the above to
> show up; not sure.
>
[EMAIL PROTECTED] ~]$ sudo modprobe acpi
FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/arch/i386/kernel/cpu/cpufreq/acpi-cpufreq.ko.gz):
No such device
> If you want to find files that start with a "." I'd use:
> find . -name ".*"
>
It took me a bit of tinkering, but once I replaced
for Y in $1/*
with
for Y in `find -P $1 -maxdepth 1 -mindepth 1 -name "*"`
my recursive script was able to look through everything (both hidden and
not) in the /proc and /sys directories, and I didn't find anything
resembling a thermal measurement. (If anyone wants my script, just ask
and I'll post it to the list. It's quick and dirty but it works.)
Thanks again for all your help with my seemingly endless series of
questions!
Adam
_______________________________________________
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
