| View previous topic :: View next topic |
| Author |
Message |
superwutze
Tux's lil' helper
Joined: 09 Dec 2004
Posts: 137
Location: Europe/Vienna
|
 Posted: Sat Apr 09, 2005 5:27 pm Post subject: lm-sensors w83627hf chip on kernels > 2.6.9 [SOLVED] |
 |
|
hello!
maybe someone noticed this too: since kernels greater than 2.6.9 the w83627hf chip won't detect anymore. i have a lot of servers running on tyan barebones which feature that chip and on all it is the same behaviour. on some there are different chips also which work still, but the w83627hf fails on all. it simply is not detected.
| Code: | okinawa andreas $ sensors
No sensors found! |
i read some threads which say something about executing isaset before inserting the module but that doesn't work either.
| Code: | okinawa andreas # isaset 0x295 0x296 0x4a 0x89
WARNING! Running this program can cause system crashes, data loss and worse!
I will write value 0x89 to address 0x4a of chip with address register 0x295
and data register 0x296.
Continue? [Y/n] Y
Data mismatch, wrote 0x89, read 0x44 back. |
beside that i don't want that as a module, i have them always compiled into the kernel.
some ideas anyone?
thanks in advance,
andy
_________________
bill who? micro what?
Last edited by superwutze on Wed Apr 13, 2005 12:16 pm; edited 1 time in total |
|
| Back to top |
|
 |
pgolik
Tux's lil' helper
Joined: 24 Nov 2004
Posts: 125
Location: Warsaw, Poland
|
| Posted: Sat Apr 09, 2005 7:29 pm Post subject: |
|
|
Try upgrading to lm_sensors-2.9.0, it's ~amd64, but stable for me. Solved a similar problem with the it87 sensor.
Pawel |
|
| Back to top |
|
|
superwutze
Tux's lil' helper
Joined: 09 Dec 2004
Posts: 137
Location: Europe/Vienna
|
| Posted: Sun Apr 10, 2005 1:33 pm Post subject: |
|
|
already tried prior to the 1st post, sorry, still 'no sensors found!'
_________________
bill who? micro what? |
|
| Back to top |
|
|
jsnorman
Tux's lil' helper
Joined: 24 Feb 2005
Posts: 131
|
| Posted: Mon Apr 11, 2005 5:03 pm Post subject: |
|
|
There is a known bug about this. Disable PnPACPI in your kernel config.
From Jean Delvare:
"Check /proc/ioports, see if something holds part of the 0x290-0x297 range. If there is something, try to recompile a kernel with CONFIG_PNPACPI disabled. This is a known and reported problem waiting for a solution:
http://bugme.osdl.org/show_bug.cgi?id=4014
The cause is IMHO a broken BIOS (or ACPI data thereof), so ideally the motherboard manufacturers would fix their BIOS and the problem would go. But I might be wrong."
Jeff |
|
| Back to top |
|
|
superwutze
Tux's lil' helper
Joined: 09 Dec 2004
Posts: 137
Location: Europe/Vienna
|
| Posted: Wed Apr 13, 2005 12:15 pm Post subject: |
|
|
thanks!!! that did it!!
_________________
bill who? micro what? |
|
| Back to top |
|
|
|
Gentoo on AMD64
