On Wednesday 09 January 2008, Adam wrote: > Porkchop wrote: > > The chip, an IT8718, isn't responsible for whats on each line. Each line > > can be attached to whatever the designer of your motherboard wanted to > > attach it to. You need to find the exact model of mobo and start > > googleing that instead of the chip type. > > The only docs I could find so far on my MB are (IMO) inadequate. There > seem to be common practices for connecting the sensor chip's inputs, and > following those gives reasonable values for all the voltages except the > two I mentioned. I miss the '80s, when you could actually look at the > motherboard schematics to answer things like this.
I wish for the days when electronics manufacturers included schematics,
too. :-( I'm currently having a similiar problem: I have a nice small
computer with no moving parts (an OpenBrick-E) that mysteriously failed and I
want to measure if all of the voltages are right on the board itself. I
haven't had luck finding enough info to be able to do that, though, and it's
now a discontinued product and I can't find a place to have it repaired.
> Chris Knadle 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): Unknown symbol in module, or unknown parameter (see dmesg)
> >
> > My best guess is that modprobe can't determine which of the
> > lower-level device modules are necessary to load, or it's also possible
> > that modprobe knows which one to load but the kernel as delivered by
> > Mandriva didn't include the required module.
>
> Because of several problems, I ended up doing an OS reinstall, and I'm
> back to:
I don't think I know anybody (including myself) that hasn't reinstalled
Linux after some experimentation that hosed it. So you're in good company.
> [EMAIL PROTECTED] ~]$ sudo modprobe coretemp
> FATAL: Error inserting coretemp
> (/lib/modules/2.6.22.15-desktop-1.uc1mdv/kernel/drivers/hwmon/coretemp.ko.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/*'
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
See if that works for your CPU.
> > If you want to fix your 'coretemp' issue, you don't need the source
> > for just the 'coretemp' module, you need the kernel source so that you
> > can recompile either the whole thing, or just the unerlying dependencies
> > that may be missing. You can either get the kernel source from Mandriva
> > which has their patches applied and options removed, or you can get the
> > "vanilla" kernel source from www.kernel.org. If you get the source from
> > kernel.org, I recommend the "full" download of 2.6.23.12, the latest
> > "stable" kernel.
>
> At this point, compiling an entire kernel may be beyond my abilities.
> Rather than go through the instabilities of the past few days, I think
> I'll just leave the core temp a mystery, as there are absolutely no
> signs of any overheating.
Compiling a kernel for yourself to start with is frankly a daunting task.
I'm trying to figure out ways to present how to do it to make it a little
easier -- and that isn't easy, either.
The best recommendation on learning how to do it is the Linux Kernel in a
Nutshell by Greg Kroah-Hartman, which is free for download here -- see the
bottom of the page:
http://www.kroah.com/lkn/
And if you're running Ubuntu or Debian, have a look here for how to build a
kernel such that it's automatically added to the boot menu when it's
installed:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html
And hopefully I'll be able to give a talk on this stuff in a couple of
months, which may or may not help. ;-)
-- 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
