Hi Rudolf
> Hmm thats strange. You should see in syslog the message from the patch and you
> should be able to modprobe the 792 driver without the isaset. Can you see
> the message in the log from my patch?
Do you mean to look for the message "PCI: Canceling ASUS hide and seek
played with SMBus monitoring chip\n" from drivers/pci/quirks.c in
/var/log/message?
I do NOT find any message from the patch when I load the i2c-i801/w83792d/
eeprom without isaset. Is it because I'm using "ssh" to the Linux?
> If not can you put some printks around to see where is problem? Thanks.
> We need to know:
> 1) if our patch was activated
> 2) if it works same way as isaset
Where should I put these "printks"? You'd better give me more information
about it.
> Maybe the "trick" disabled the EEPROM part of the bus.
> Can you please try with clean boot:
Yes, you are right, I find that the eeprom module works well if I do NOT
do the "isaset" trick. But at this time, the 792 module does NOT work!
[root at CFLi ~]# modprobe i2c-i801
[root at CFLi ~]# modprobe eeprom
[root at CFLi ~]# sensors
eeprom-i2c-0-55
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 256
eeprom-i2c-0-51
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 256
==================================================================
Here is some of the debug message:
(1) clean reboot
(2) modprobe i2c-i801
(3) i2cdetect 0
[root at CFLi ~]# 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 08 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 44 XX XX XX XX XX XX XX XX XX XX XX
50: XX 51 XX XX XX 55 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
(4) isaset .... (put here the trick line)
i2cdetect 0
[root at CFLi ~]# isaset -y -f 0x04b9 0x08
[root at CFLi ~]# 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 08 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 2f
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX 44 XX XX XX XX XX XX 4b XX XX XX 4f
50: XX XX XX XX 54 55 XX XX XX XX XX XX XX XX XX XX
60: XX 61 XX XX XX XX XX XX XX XX XX XX XX XX XX XX
70: XX 71 XX XX XX XX XX XX
(5) i2cdump 0 0x55
[root at CFLi ~]# i2cdump 0 0x55
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x55, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
(6) i2cdump 0 0x55 c
[root at CFLi ~]# i2cdump 0 0x55 c
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x55, mode byte consecutive read
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
(7) modprobe eeprom
sensors
[root at CFLi ~]# modprobe eeprom
[root at CFLi ~]# sensors
eeprom-i2c-0-55
Adapter: SMBus I801 adapter at 0400
Unknown EEPROM type (255).
eeprom-i2c-0-54
Adapter: SMBus I801 adapter at 0400
Unknown EEPROM type (255).
(8) modprobe your792driver
sensors
[root at CFLi ~]# modprobe w83792d
[root at CFLi ~]# sensors
w83792d-i2c-0-2f
Adapter: SMBus I801 adapter at 0400
VCoreA: +1.33 V (min = +0.00 V, max = +2.04 V)
VCoreB: +0.35 V (min = +0.00 V, max = +2.04 V)
VIN0: +3.28 V (min = +0.00 V, max = +4.08 V)
VIN1: +3.18 V (min = +0.00 V, max = +4.08 V)
VIN2: +1.52 V (min = +0.00 V, max = +4.08 V)
VIN3: +2.50 V (min = +0.00 V, max = +4.08 V)
5VCC: +5.08 V (min = +0.00 V, max = +6.12 V)
5VSB: +4.92 V (min = +0.00 V, max = +6.12 V)
VBAT: +3.02 V (min = +0.00 V, max = +4.08 V)
Fan1: 0 RPM (min = 0 RPM, div = 128)
Fan2: 0 RPM (min = 0 RPM, div = 2)
Fan3: 0 RPM (min = 0 RPM, div = 128)
Fan4: 0 RPM (min = 0 RPM, div = 128)
Fan5: 0 RPM (min = 0 RPM, div = 128)
Fan6: 0 RPM (min = 0 RPM, div = 2)
Fan7: 0 RPM (min = 0 RPM, div = 128)
Temp1: +40.0????C (high = +127.0????C, hyst = +0.0????C)
Temp2: +59.0????C (high = +43.0????C, hyst = +38.0????C) ALARM
Temp3: -32.0????C (high = +45.0????C, hyst = +40.0????C) ALARM
chassis: Chassis is normal.
eeprom-i2c-0-55
Adapter: SMBus I801 adapter at 0400
Unknown EEPROM type (255).
eeprom-i2c-0-54
Adapter: SMBus I801 adapter at 0400
Unknown EEPROM type (255).
(9) i2cdump 0 0x55 c
[root at CFLi ~]# i2cdump 0 0x55 c
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-0, address 0x55, mode byte consecutive read
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
(10)
[root at CFLi ~]# rmmod w83792d
[root at CFLi ~]# rmmod eeprom
[root at CFLi ~]# rmmod i2c-i801
[root at CFLi ~]# isaset -y -f 0x04b9 0x00 <---here is 0x00 instead of 0x08 !!
[root at CFLi ~]# isadump -f 0x04b9
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address range 0x400 to 0x4ff.
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: 40 00 04 00 ab ff 00 00 00 44 00 00 00 00 07 07
10: 00 00 00 00 10 00 5c 00 00 00 00 00 00 00 00 00
20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
80: c0 31 a4 1b ff ff 00 01 00 00 00 00 00 00 00 03
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 c0 31 00 00
b0: 00 0c 00 03 00 00 00 00 00 00 00 00 00 00 00 00
c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
d0: a0 0a ff ff ff ff ff ff ff ff ff ff ff ff ff ff
e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
[root at CFLi ~]# modprobe i2c-i801
[root at CFLi ~]# modprobe eeprom
[root at CFLi ~]# modprobe w83792d
[root at CFLi ~]# sensors <--- the eeprom can work but 792 NOT!
eeprom-i2c-0-55
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 256
eeprom-i2c-0-51
Adapter: SMBus I801 adapter at 0400
Memory type: DDR SDRAM DIMM
Memory size (MB): 256
Then do you know how to solve this problem? So that both the eeprom and
792 modules can work at the same time.
Thanks
Best Regards
Chunhao
> -----Original Message-----
> From: Rudolf Marek [mailto:r.marek at sh.cvut.cz]
> Sent: 2005???4???12??? 5:20
> To: PI14 HUANG0
> Cc: sensors at Stimpy.netroedge.com
> Subject: Re: Ask for some information about motherboard ASUS NCLV-D
>
> Huang0 at Winbond.com.tw wrote:
> > Hi Rudolf
> >
> > I tested your patch "hide_and_seek_2" under linux-2.6.11 under this
> motherboard
> > ASUS NCLV-D, the 792 driver for linux-2.6 can work if I execute "isaset -y
> -f 0x04b9 0x08" at first,
> even if the eeprom modules is loaded. But the eeprom
> > modules can NOT get the memory information.
>
> Hmm thats strange. You should see in syslog the message from the patch and you
> should
> be able to modprobe the 792 driver without the isaset. Can you see the message
> in the log
> from my patch?
>
> If not can you put some printks around to see where is problem? Thanks.
> We need to know:
>
> 1) if our patch was activated
> 2) if it works same way as isaset
>
> > I remember that under linux-2.4 on this motherboard, the 792 driver can NOT
> > work if eeprom modules is loaded.
>
> yes it was because the i2c-i801 did not handle correctly the i2c-block reads,
> this is already
> fixed in CVS.
>
> > [root at localhost linux-2.6.11]# sensors
> > w83792d-i2c-0-2f
> > Adapter: SMBus I801 adapter at 0400
> > VCoreA: +1.33 V (min = +1.40 V, max = +1.60 V) ALARM
> > VCoreB: +0.35 V (min = +1.40 V, max = +1.60 V) ALARM
> > VIN0: +3.28 V (min = +3.20 V, max = +3.39 V)
> > VIN1: +3.17 V (min = +3.09 V, max = +3.30 V)
> > VIN2: +1.51 V (min = +1.39 V, max = +1.49 V) ALARM
> > VIN3: +2.50 V (min = +2.59 V, max = +2.64 V) ALARM
> > 5VCC: +5.08 V (min = +4.73 V, max = +5.23 V)
> > 5VSB: +4.92 V (min = +4.73 V, max = +5.23 V)
> > VBAT: +3.01 V (min = +2.85 V, max = +3.14 V)
> > Fan1: 0 RPM (min = 0 RPM, div = 128)
> > Fan2: 1448 RPM (min = 1500 RPM, div = 4) ALARM
> > Fan3: 0 RPM (min = 0 RPM, div = 128)
> > Fan4: 0 RPM (min = 0 RPM, div = 128)
> > Fan5: 0 RPM (min = 0 RPM, div = 128)
> > Fan6: 0 RPM (min = 0 RPM, div = 2)
> > Fan7: 0 RPM (min = 0 RPM, div = 128)
> > Temp1: +37.0????C (high = +42.0????C, hyst = +37.0????C)
> > Temp2: +57.0????C (high = +43.0????C, hyst = +38.0????C) ALARM
> > Temp3: -32.0????C (high = +45.0????C, hyst = +40.0????C) ALARM
> > chassis: Chassis is normal.
> >
> > eeprom-i2c-0-55
> > Adapter: SMBus I801 adapter at 0400
> > Unknown EEPROM type (255).
> >
> > eeprom-i2c-0-54
> > Adapter: SMBus I801 adapter at 0400
> > Unknown EEPROM type (255).
> >
>
> Hmm again some more problems...
>
> Maybe the "trick" disabled the EEPROM part of the bus.
> Can you please try with clean boot:
>
> modprobe i2c-i801 (I hope it is this driver)
>
> i2cdetect 0
> isaset .... (put here the trick line)
> i2cdetect 0
>
> Afterwards if you still can see address 0x54 and 0x55
> can you do:
> i2cdump 0 0x55
> i2cdump 0 0x55 c
> modprobe eeprom
> sensors
> modprobe your792driver
> sensors
> i2cdump 0 0x55 c
>
> If you cannot see addresses 54 55 as "responsive - no XX" than it means the
> trick switched the bus. And because
> the quirk did not work and you did it manualy than eeprom driver cant get data
> because the chip is "away"
>
> thanks
>
> regards
>
> Rudolf
===========================================================================================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??.
