TigerMP (2460) and lm_sensors, anybody care?

otheos

unread,

Dec 4, 2001, 7:51:17 PM12/4/01

to

to share your experiences?

I have it running, but can't tell if I can trust the values.

Euan Kirkhope

unread,

Dec 5, 2001, 2:54:27 PM12/5/01

to

Before I bought my fanless coolers (the have fans suspended on a bracket
connnected to the PCI screws) CPU 1 was always at least 5 deg C higher than
CPU 0! Now they are still the same temperature, but the difference has
gone, they both sit at 49-51 deg C (XP 1600+'s).

What program you using?

MBM has a bug where the CPU temps aren't available unless you go into the
bios then exit WITHOUT saving. The other program K7TT.exe only monitors the
CPU temps, but doesn't require the bios trick.

IMHO the TYAN implementation is a mess, and the lack of bios monitoring (for
auto shutdown) is insane.

regards

Euan Kirkhope
"otheos" <othe...@clara.net> wrote in message
news:1007513479.30499.1@eurus...

sehh

unread,

Dec 5, 2001, 3:34:52 PM12/5/01

to

On Wed, 05 Dec 2001 00:51:17 +0000, otheos wrote:

>to share your experiences?
>I have it running, but can't tell if I can trust the values.

Do you mean that you've got CPU0/1 temps and
FAN1/2/3 speeds all in one go?

Which of the two health monitor chips are you using? both?

How did you manage to enable them all without going
into the BIOS on every boot?

--
sehh

otheos

unread,

Dec 5, 2001, 8:43:35 PM12/5/01

to

Was not very simple but finally got it.

You need:
/sbin/modprobe i2c-dev
/sbin/modprobe i2c-amd756
/sbin/modprobe w83781d init=0

Make sure you use init=0 otherwise the system will freeze. Also getting the
new lm_sensors from the CVS and patching/recompiling the kernel works
better (didn't mention anything though).

Now when you run sensors you'll get 77C for the CPU's. but if you change
the sensor type at /etc/sensors.conf under the:

chip "w83782d-*" "w83783s-*" "w83627hf-*"

#like this:

set sensor1 2
set sensor2 2
set sensor3 2

and then run sensors -s (to read the changes) and then sensors again,
you'll see all fans and CPU temps + the Northbridge readings. Voltages are
more complex (apart for CPUs) as the calculation method needs tuning.

BTW, how did you manage to revive your board after that failed flash?

Garglemonster

unread,

Dec 8, 2001, 7:20:22 AM12/8/01

to

>>>>> "otheos" == otheos <othe...@clara.net> writes:

otheos> Was not very simple but finally got it. You need:
otheos> /sbin/modprobe i2c-dev /sbin/modprobe i2c-amd756
otheos> /sbin/modprobe w83781d init=0
otheos> Make sure you use init=0 otherwise the system will
otheos> freeze.

hmm, i don't use the init=0 bit and my machine doesn't hang.

otheos> Voltages are more complex (apart for CPUs) as the
otheos> calculation method needs tuning.

you know it... i gave up on those.

g.m.

--
gargle...@my-deja.com

Used staples are good with SOY SAUCE!

Stephane Du Pasquier

unread,

Dec 19, 2001, 6:37:39 PM12/19/01

to

Garglemonster wrote:

>>>>>>"otheos" == otheos <othe...@clara.net> writes:
>>>>>>
>
> otheos> Was not very simple but finally got it. You need:
> otheos> /sbin/modprobe i2c-dev /sbin/modprobe i2c-amd756
> otheos> /sbin/modprobe w83781d init=0
> otheos> Make sure you use init=0 otherwise the system will
> otheos> freeze.
>
> hmm, i don't use the init=0 bit and my machine doesn't hang.

I don't seem to need it either (2.4.16, patched with lm_sensors-2.6.2
and i2c-2.6.2, 2x non-MP 1200's)

> otheos> Voltages are more complex (apart for CPUs) as the
> otheos> calculation method needs tuning.
>
> you know it... i gave up on those.

me too, for now.

S.