| 2 | | true bugs too. If you experience any problems, do not hesitate to mail |
|---|
| 3 | | sensors@stimpy.netroedge.com. But read the documentation first, please! |
|---|
| | 2 | true bugs too. If you experience any problems not listed here, |
|---|
| | 3 | do not hesitate to mail sensors@stimpy.netroedge.com. |
|---|
| | 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 | ================================ |
|---|
| | 30 | i2c/smbus lockup (i2c-piix4 and i2c-ali15x3 drivers) |
|---|
| | 31 | |
|---|
| | 32 | Sometimes the i2c bus will get hung and the driver can't un-hang it. |
|---|
| | 33 | If this is caused by a hung sensor chip (mtp008 and w83781d chips may |
|---|
| | 34 | be culprits), only a reboot or even power cycle will clear it |
|---|
| | 35 | (if the SDRAM eeproms are on the hung i2c bus, the machine probably won't |
|---|
| | 36 | boot until the power is cycled). |
|---|
| | 37 | If there are bugs in the i2c bus drivers, or improvements we can make to |
|---|
| | 38 | error recovery, we don't know what they are. |
|---|
| | 39 | |
|---|
| | 40 | |
|---|
| | 41 | ================================ |
|---|
| | 42 | IBM Thinkpad laptops and sensors-detect |
|---|
| | 43 | See the file README.thinkpad |
|---|
| | 44 | |
|---|
| | 45 | |
|---|
| | 46 | ================================ |
|---|
| | 47 | mtp008 support |
|---|
| | 48 | |
|---|
| | 49 | This chip does not always respond, as evidenced by 'XX' fields |
|---|
| | 50 | in i2cdump. Results in non-detection by sensors-detect and/or |
|---|
| | 51 | the mtp008 driver, or periodic bad readings. |
|---|
| | 52 | Cause unknown - perhaps a bug in the chip, or the chip |
|---|
| | 53 | not meeting the i2c specifications. |
|---|
| | 54 | |
|---|
| | 55 | |
|---|
| | 56 | ================================ |
|---|
| | 57 | sis5595 (sis5595 and i2c-sis5595 drivers) |
|---|
| | 58 | |
|---|
| | 59 | Writing the base addresses (using the force_addr=0x.... parameter to modprobe) |
|---|
| | 60 | does not work for some machines (dmesg message is "force address failed"). |
|---|
| | 61 | Either some chips do not support sensors, or there is some undocumented |
|---|
| | 62 | lock bit for the base address registers. |
|---|
| | 63 | |
|---|
| | 64 | Also, the temperature reading in sis5595 is usually wrong. |
|---|
| | 65 | Different formulas are required for different versions of |
|---|
| | 66 | the chip and different motherboards. |
|---|
| | 67 | |
|---|
| | 68 | ================================ |
|---|
| | 69 | bus drivers (all) |
|---|
| | 70 | |
|---|
| | 71 | Rmmod'ing a bus driver when the /proc directory for a chip |
|---|
| | 72 | driver on that bus is in use may cause a kernel oops, because |
|---|
| | 73 | the chip driver gets removed too. See ticket #331 for details. |
|---|
| | 74 | Not likely to happen. No obvious way to fix. |
|---|
| | 75 | |
|---|
| | 76 | |
|---|
| | 77 | ============================================================================ |
|---|
| | 78 | Following are old problems with older kernels. |
|---|
| | 79 | |
|---|
