A question when test W83792D driver on another motherboard

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jean

We tried the command "isaset -y -f 0x4b9 0x08", and find that the w83792d driver
can "work" now when run "sensors" after load the 792 module, but we meet some
other problems:
1* All of the voltage/fan/temperature measured values are fixed, they
do NOT change at all. The voltage/fan/temperature limits can NOT be set either.
Here is the output message of "sensors", please refer it.
Do you ever meet such similar problem before? Our 792 driver for Windows
can work well.
******************  output of "sensors"  ************************
w83792d-i2c-0-2f
Adapter: SMBus I801 adapter at 0400
VCoreA:    +2.05 V  (min =  +2.04 V, max =  +2.04 V)       ALARM
VCoreB:    +2.05 V  (min =  +2.04 V, max =  +2.04 V)       ALARM
VIN0:      +4.09 V  (min =  +4.08 V, max =  +4.08 V)       ALARM
VIN1:      +4.09 V  (min =  +4.08 V, max =  +4.08 V)       ALARM
VIN2:      +4.09 V  (min =  +4.08 V, max =  +4.08 V)       ALARM
VIN3:      +4.09 V  (min =  +4.08 V, max =  +4.08 V)       ALARM
5VCC:      +6.14 V  (min =  +6.12 V, max =  +6.12 V)       ALARM
5VSB:      +6.12 V  (min =  +6.12 V, max =  +6.12 V)
VBAT:      +4.08 V  (min =  +4.08 V, max =  +4.08 V)
Fan1:        0 RPM  (min =    0 RPM, div = 1)
Fan2:        0 RPM  (min =    0 RPM, div = 1)
Fan3:        0 RPM  (min =    0 RPM, div = 4080)
Fan4:        0 RPM  (min =    0 RPM, div = 255)
Fan5:        0 RPM  (min =    0 RPM, div = 255)
Fan6:        0 RPM  (min =    0 RPM, div = 255)
Fan7:        0 RPM  (min =    0 RPM, div = 255)
Temp1:    +255.0??XC  (high = +255.0??XC, hyst = +255.0??XC)
Temp2:    +255.5??XC  (high = +255.5??XC, hyst = +255.5??XC)
Temp3:    +255.5??XC  (high = +255.5??XC, hyst = +255.5??XC)
ERROR: Can't get Chassis data!

2* When I rmmod the w83792d module, and insmod it again, the 792 driver
will NOT work any more: I get nothing from "sensors". I'm sure that the
0x04b9 is still "0x08", it does NOT change. Then we have to reboot the
Linux to make 792 driver "work" again. :-(

Btw, the "sensors-detect" still can NOT find the 792 chip after I run
"isaset -y -f 0x4b9 0x08".


Thanks
Best Regards

Chunhao
2005-03-02


> -----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??.



[Index of Archives]     [Linux Kernel]     [Linux Hardware Monitoring]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux