Hi Jean, Rudolf
I tried the command you gave me, but failed, I still can not find the 792 chip,
The detect result of sensors-detect is same as the one I sent you before,
I also tried the "i2cdetect", the result is attached in this mail, it's
a little different from the original one I sent you before.
I also tried to load 792 module, but 792 output data can not be found when I
run "sensors".
Here are my questions:
1. Are you sure that I should try "isaset -y -f 0x04b9 0x08" instead of
"i2cset"?
2. Is there any other method I can try? Because we want to solve this problem
so much!
[root at localhost lm_sensors-2.9.0]# i2cdetect 0
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0.
I will probe address range 0x03-0x77.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: XX XX XX XX XX XX XX XX XX XX XX XX XX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX
Thanks
Best Regards
Chunhao
2005-03-01
> -----Original Message-----
> From: Jean Delvare [mailto:khali at linux-fr.org]
> Sent: 2005??2??28?? 16:35
> To: PI14 HUANG0
> Cc: LM Sensors; PI10 LHHsu; PI14 DZSHEN; PI13 CFLi
> Subject: RE: A question when test W83792D driver on another motherboard
>
>
> Hi Chunhao,
>
> > When it has been confirmed that it is ASUS motherboard, write the value
> > 0x08 into the port 0x04b9.
> > (...)
> > Then, do you have any idea on how to solve the problem we meet?
> > If do, please tell me, I'd like to test it on this motherboard.
>
> Just try "isaset -y -f 0x4b9 0x08". That should do the trick Asus
> recommends.
>
> If you confirm that the W83792D then appears on the SMBus (as probed by
> sensors-detect or i2cdetect) then we'll have to integrate the trick.
> For 2.6 there is a place dedicated to this (pci/quirks.c). For 2.4 there
> is none so we'll just document the fact that isaset must be run prior
> to loading the smbus driver, or integrate the operation into the smbus
> driver itself (shouldn't be too hard).
>
> I still wonder what device is at 0x4b9. According to the snapshot of
> /proc/ioports you sent, your linux system doesn't know about it.
>
> Thanks,
> --
> Jean Delvare
===========================================================================================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??.
