Hi Jean > This is a typical output when the SMBus is stuck. Reads will return -1, > which is then misinterpreted as 0xff and results in the output above. > > Side notes: > 1* You should check your code for fan clock dividers. It is very > suspicious that you get different values and some of them are NOT > possible divider values. > 2* The chassis data error is probably not related so you should check > your code too (either sensors, or libsensors, or the driver itself). OK, I will check my codes after a while. > When does your windows driver exactly write 0x08 to 0x4b9? Once when you > load the driver? Or before every register read? 792 windows driver write 0x08 to 0x4b9 before loading the driver, instead of before every register read. > > I'm sure that the 0x04b9 is still "0x08", it does NOT change. > How do you know for sure? I use "isadump -y -f 0x04b9" to check the value. > Also, do you know the value at 0x4b9 before you write 0x08? If you know, > try writing this value again, then 0x08 again, and see if it temporarily > gives you access to the chip again. I tried it just now, but in vain, I still can NOT access to the chip, I still have to reboot the Linux to access to the chip. If you have more suggestion about this problem, please tell us, I'd like to try it here. Btw, Is there any guys who are going to backport the i2c-ali1563.c from linux-2.6 to linux-2.4? We still can not run 792 driver on another motherboard with the Ali M1563 chipset. If there is some evolution on it, please tell us. :-) Thanks Best Regards Chunhao 2005-03-03 ===========================================================================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original author of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such person, please kindly reply the sender indicating accordingly and delete all copies of it from your computer and network server immediately. We thank you for your cooperation. It is advisable that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email that does not relate to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.===========================================================================================If your computer is unable to decode Chinese font, please ignore the following message. They essentially repea! t the English statement above.???H???????t?????q?l???]???????K?????T, ?????v???o?H?H???w?????H?H???\????. ?????z???D?Q???w?????H?H???]???????]?b???g???v?????????U???????H??, ???z?i?????o?H?H?????Y?N?H???q?q???P???????A???????H????. ?????z???X?@, ?????????P??. ?S??????, ???????g???v?????????????q?l?????K???T???????O?Q?Y???T????. ?H???P?????q?l???~?L???????e,???o?????????q?l?????????N??.
