On Friday 11 January 2008, Adam wrote: > >> [EMAIL PROTECTED] ~]$ sudo modprobe coretemp > >> FATAL: Error inserting coretemp > >> (/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.k > >>o.g z): No such device > > > > It's hard to know what's missing. Maybe the logs will give the humans > > a hint. Have a look at the end of /var/log/dmesg, /var/log/messages, and > > /var/log/syslog right after trying to load the module. ['tail -n 25 > > /var/log/messages' will give you the last 25 lines of /var/log/messages, > > for instance.] Perhaps even try seeing what other log might have a > > message in it with 'zfgrep coretemp /var/log/*' > > Aha! /var/log/messages and /var/log/syslog both include: > > Jan 11 17:18:00 eris sudo: adam : TTY=pts/1 ; PWD=/home/adam ; > USER=root ; COMMAND=/sbin/modprobe -v coretemp > 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."
Well, it's "unknown" in terms of the *coretemp* module.
From Linux-2.6.23.12/drivers/hwmon/coredump.c:
=-=-=-=-=-=-=
/* supported CPU not found, but report the unknown
family 6 CPU */
if ((c->x86 == 0x6) && (c->x86_model > 0xf))
printk(KERN_WARNING DRVNAME ": Unknown CPU "
"model %x\n", c->x86_model);
=-=-=-=-=-=-=
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.
> > Sometimes ACPI itself has some temperature measurements available.
> > For instance, I measure my P4's CPU temperature via:
> >
> > cat /proc/acpi/thermal_zone/THRM/temperature
>
> 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.
If you want to find files that start with a "." I'd use:
find . -name ".*"
which will start finding files starting in the current directory. When I
run that in my own home directory I get quite a list, and quite a few ".git"
directories. :-)
> Thanks for the link! It's been downloaded and added to my "to read"
> list. Right now I'm going through "Upgrading and Repairing PCs, 18th
> edition" to learn about the hardware in my new system -- things like
> SATA and DDR2 RAM are new to me.
That makes sense. I read one of those "Upgrading and Repairing PCs" books
a few years ago also. It's mostly good info for background understanding.
> Michael Muller wrote:
> > Jim Doherty gave a good talk on this subject way back in 2003, you can
> > view the presentation info at http://mhvlug.org/MonthlyMeetings/2003/05.
> > I think it would be worthwhile for the LUG to have another talk on kernel
> > building.
>
> That was nearly five years ago. I think updated presentations on some
> of the older topics could be useful.
Yeah, I find that certain topics commonly get periodic talks, and it
generally seems like a good thing, and there's usually new things to keep
people that had heard the earlier talks from getting bored.
-- Chris
--
Chris Knadle
[EMAIL PROTECTED]
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ 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
