| 1 |
Except for many unimplemented things (listed in the TODO file), there may be |
|---|
| 2 |
true bugs too. If you experience any problems not listed here, do not hesitate |
|---|
| 3 |
to mail us (see http://www.lm-sensors.org/wiki/FeedbackAndSupport). |
|---|
| 4 |
But read this file and doc/FAQ first, please! |
|---|
| 5 |
|
|---|
| 6 |
============================================================================ |
|---|
| 7 |
These are current problems with specific programs and drivers. |
|---|
| 8 |
In general, please don't send us mail telling us you have the |
|---|
| 9 |
same problem!! Do send us mail if you have a fix!! |
|---|
| 10 |
|
|---|
| 11 |
|
|---|
| 12 |
================================ |
|---|
| 13 |
Asus boards - as99127f support (w83781d driver) |
|---|
| 14 |
|
|---|
| 15 |
Several problems. Asus will not release a datasheet. |
|---|
| 16 |
Support was developed - and tweaked - with experimentation and user feedback. |
|---|
| 17 |
These will not be fixed unless we get a datasheet. |
|---|
| 18 |
If you have problems, please lobby Asus to release a datasheet. |
|---|
| 19 |
Unfortunately, several others have done so, without success. |
|---|
| 20 |
Please do not send mail to us asking for better as99127f support. |
|---|
| 21 |
We have done the best we can without a datasheet. |
|---|
| 22 |
The changes we do make to please some people generally makes |
|---|
| 23 |
things worse for people with other types of motherboard. |
|---|
| 24 |
Please do not send mail to the author or the sensors group asking for |
|---|
| 25 |
a datasheet or ideas on how to convince Asus. |
|---|
| 26 |
See doc/chips/w83781d for more information. |
|---|
| 27 |
|
|---|
| 28 |
================================ |
|---|
| 29 |
i2c/smbus lockup (i2c-piix4 and i2c-ali15x3 drivers) |
|---|
| 30 |
|
|---|
| 31 |
Sometimes the i2c bus will get hung and the driver can't un-hang it. |
|---|
| 32 |
If this is caused by a hung sensor chip (mtp008 and w83781d chips may |
|---|
| 33 |
be culprits), only a reboot or even power cycle will clear it |
|---|
| 34 |
(if the SDRAM eeproms are on the hung i2c bus, the machine probably won't |
|---|
| 35 |
boot until the power is cycled). |
|---|
| 36 |
If there are bugs in the i2c bus drivers, or improvements we can make to |
|---|
| 37 |
error recovery, we don't know what they are. |
|---|
| 38 |
|
|---|
| 39 |
On the ASUS P5A motherboard, there are several reports that |
|---|
| 40 |
the SMBus will hang and this can only be resolved by |
|---|
| 41 |
powering off the computer. It appears to be worse when the board |
|---|
| 42 |
gets hot, for example under heavy CPU load, or in the summer. |
|---|
| 43 |
There may be electrical problems on this board. |
|---|
| 44 |
On the P5A, the W83781D sensor chip is on both the ISA and |
|---|
| 45 |
SMBus. Therefore the SMBus hangs can generally be avoided |
|---|
| 46 |
by accessing the W83781D on the ISA bus only. |
|---|
| 47 |
|
|---|
| 48 |
================================ |
|---|
| 49 |
IBM Thinkpad laptops and sensors-detect |
|---|
| 50 |
See the file README.thinkpad |
|---|
| 51 |
|
|---|
| 52 |
|
|---|
| 53 |
================================ |
|---|
| 54 |
mtp008 support |
|---|
| 55 |
|
|---|
| 56 |
This chip does not always respond, as evidenced by 'XX' fields |
|---|
| 57 |
in i2cdump. Results in non-detection by sensors-detect and/or |
|---|
| 58 |
the mtp008 driver, or periodic bad readings. |
|---|
| 59 |
Cause unknown - perhaps a bug in the chip, or the chip |
|---|
| 60 |
not meeting the i2c specifications. |
|---|
| 61 |
|
|---|
| 62 |
|
|---|
| 63 |
================================ |
|---|
| 64 |
sis5595 (sis5595 and i2c-sis5595 drivers) |
|---|
| 65 |
|
|---|
| 66 |
These drivers latch on to many non-sis5595 chips which |
|---|
| 67 |
do not support sensors, i2c bus, or both. |
|---|
| 68 |
This is because SiS uses the same PCI ID for several different chips. |
|---|
| 69 |
This will have to be fixed by us to recognize these other chips. |
|---|
| 70 |
|
|---|
| 71 |
Right now, the driver tries |
|---|
| 72 |
writing the base addresses (using the force_addr=0x.... parameter to modprobe), |
|---|
| 73 |
it does not work for some machines (dmesg message is "force address failed"). |
|---|
| 74 |
Either some chips do not support sensors, or there is some undocumented |
|---|
| 75 |
lock bit for the base address registers. |
|---|
| 76 |
|
|---|
| 77 |
Also, the temperature reading in sis5595 is usually wrong. |
|---|
| 78 |
Different formulas are required for different versions of |
|---|
| 79 |
the chip and different motherboards. |
|---|
| 80 |
|
|---|
| 81 |
================================ |
|---|
| 82 |
bus drivers (all) |
|---|
| 83 |
|
|---|
| 84 |
Rmmod'ing a bus driver when the /proc directory for a chip |
|---|
| 85 |
driver on that bus is in use may cause a kernel oops, because |
|---|
| 86 |
the chip driver gets removed too. See ticket #331 for details. |
|---|
| 87 |
Not likely to happen. No obvious way to fix. |
|---|
