* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
@ 2006-05-23 13:25 Rod Morison
2006-05-23 21:21 ` Rudolf Marek
` (9 more replies)
0 siblings, 10 replies; 11+ messages in thread
From: Rod Morison @ 2006-05-23 13:25 UTC (permalink / raw)
To: lm-sensors
I am stuck with what it certainly a config problem. I've got lm_sensors
2.10.0 running fine on a SuperMicro PDSMA mobo under 2.6.16 kernel.
However, under 2.4.19 (required for the embedded project I'm on), I'm
missing sensors for one of the chips. I'm using the same sensors.conf
and modules.conf/modprobe.conf settings.
In the 2.4 kernel case I get some eeprom/ram listings off the I801 bus,
instead of the w83792d chip I'm expecting.
Can anyone point me in the right direction to reconcile the difference...
2.6 kernel driver list and sensors output:
sm1:~ # lsmod
Module Size Used by
joydev 27520 0
st 55332 0
sr_mod 33060 0
xt_pkttype 18560 3
ipt_LOG 23168 9
xt_limit 19328 9
w83627hf 45328 0
eeprom 24464 0
w83792d 46872 0
w83781d 53156 0
hwmon_vid 19200 2 w83627hf,w83781d
hwmon 19848 3 w83627hf,w83792d,w83781d
i2c_isa 22272 2 w83627hf,w83781d
af_packet 55820 2
edd 26760 0
button 24224 0
battery 27272 0
ac 22152 0
ip6t_REJECT 22272 3
xt_tcpudp 19968 5
ipt_REJECT 22272 3
xt_state 18816 12
iptable_mangle 19584 0
iptable_nat 25220 0
ip_nat 35884 1 iptable_nat
iptable_filter 19712 1
ip6table_mangle 19072 0
ip_conntrack 75164 3 xt_state,iptable_nat,ip_nat
nfnetlink 23496 2 ip_nat,ip_conntrack
ip_tables 30792 3 iptable_mangle,iptable_nat,iptable_filter
ip6table_filter 19584 1
ip6_tables 32328 2 ip6table_mangle,ip6table_filter
x_tables 31368 10
xt_pkttype,ipt_LOG,xt_limit,ip6t_REJECT,xt_tcpudp,ipt_REJECT,xt_state,iptable_nat,ip_tables,ip6_tables
ipv6 328736 19 ip6t_REJECT
apparmor 72352 0
aamatch_pcre 30720 1 apparmor
loop 32528 0
dm_mod 77616 0
i2c_i801 25876 0
shpchp 62368 0
e1000 130744 0
uhci_hcd 48544 0
ehci_hcd 47624 0
ide_cd 57248 0
cdrom 52392 2 sr_mod,ide_cd
i2c_core 40192 6
w83627hf,eeprom,w83792d,w83781d,i2c_isa,i2c_i801
pci_hotplug 45056 1 shpchp
i8xx_tco 24616 0
usbcore 150312 3 uhci_hcd,ehci_hcd
floppy 82984 0
parport_pc 56680 1
lp 29768 0
parport 56716 2 parport_pc,lp
reiserfs 241280 2
fan 21896 0
thermal 32272 0
sg 52264 0
processor 50280 1 thermal
3w_9xxx 50180 3
piix 27652 0 [permanent]
sd_mod 34176 4
scsi_mod 163888 5 st,sr_mod,sg,3w_9xxx,sd_mod
ide_disk 32896 0
ide_core 165764 3 ide_cd,piix,ide_disk
sm1:~ # sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +0.14 V (min = +1.38 V, max = +1.54 V) ALARM
VCore 2: +0.14 V (min = +1.38 V, max = +1.54 V) ALARM
+3.3V: +0.14 V (min = +3.14 V, max = +3.46 V) ALARM
+5V: +5.19 V (min = +4.73 V, max = +5.24 V)
+12V: +0.55 V (min = +10.82 V, max = +13.19 V) ALARM
-12V: -14.17 V (min = -13.18 V, max = -10.88 V) ALARM
-5V: -7.26 V (min = -5.25 V, max = -4.75 V) ALARM
V5SB: +5.54 V (min = +4.73 V, max = +5.24 V) ALARM
VBat: +0.00 V (min = +2.40 V, max = +3.60 V) ALARM
fan1: 0 RPM (min = 2848 RPM, div = 2) ALARM
fan2: 0 RPM (min = 2848 RPM, div = 2) ALARM
fan3: 0 RPM (min = 1328 RPM, div = 8) ALARM
temp1: +124?C (high = -5?C, hyst = -3?C) sensor =
thermistor ALARM
temp2: +124.0?C (high = +80?C, hyst = +75?C) sensor =
thermistor ALARM
temp3: +124.0?C (high = +80?C, hyst = +75?C) sensor =
thermistor ALARM
vid: +1.462 V (VRM Version 10.0)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled
w83792d-i2c-0-2f
Adapter: SMBus I801 adapter at 1100
VCoreA: +1.33 V (min = +1.40 V, max = +1.60 V) ALARM
VCoreB: +1.53 V (min = +1.40 V, max = +1.60 V)
VIN0: +3.29 V (min = +3.20 V, max = +3.39 V)
VIN1: +3.01 V (min = +3.09 V, max = +3.30 V) ALARM
VIN2: +0.52 V (min = +1.39 V, max = +1.49 V) ALARM
VIN3: +3.12 V (min = +2.59 V, max = +2.64 V) ALARM
5VCC: +5.02 V (min = +4.73 V, max = +5.23 V)
5VSB: +4.88 V (min = +4.73 V, max = +5.23 V)
VBAT: +3.20 V (min = +2.85 V, max = +3.14 V) ALARM
Fan1: 0 RPM (min = 712 RPM, div = 8) ALARM
Fan2: 0 RPM (min = 712 RPM, div = 8) ALARM
Fan3: 7336 RPM (min = 712 RPM, div = 8)
Fan4: 0 RPM (min = 712 RPM, div = 8) ALARM
Fan5: 0 RPM (min = 712 RPM, div = 8) ALARM
Fan6: 5625 RPM (min = 712 RPM, div = 8)
ERROR: Can't get FAN7 data!
Temp1: +34.0?C (high = +50.0?C, hyst = +0.0?C)
Temp2: +41.0?C (high = +80.0?C, hyst = +75.0?C)
Temp3: +28.5?C (high = +80.0?C, hyst = +75.0?C)
chassis: Chassis intrusion detection ALARM
sm1:~ #
--------------------------------------------------------------------------------------
2.4 kernel driver list and sensors output
2.4.19# lsmod
Module Size Used by Tainted: P
w83627hf 14104 0 (unused)
smbus-arp 4816 0 (unused)
i2c-isa 804 0 (unused)
i2c-i801 4828 0 (unused)
eeprom 3500 0 (unused)
w83781d 19196 0 (unused)
i2c-proc 5988 0 [w83627hf smbus-arp eeprom w83781d]
i2c-core 14276 0 [w83627hf smbus-arp i2c-isa i2c-i801
eeprom w83781d i2c-proc]
e1000 98896 1
2.4.19# sensors
eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 1100
Memory type: DDR2 SDRAM DIMM
Memory size (MB): 512
eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 1100
Memory type: DDR2 SDRAM DIMM
Memory size (MB): 512
w83627hf-isa-0290
Adapter: ISA adapter
in0: +0.00 V (min = +3.28 V, max = +3.68 V)
in1: +0.00 V (min = +3.28 V, max = +3.68 V)
in2: +0.00 V (min = +2.82 V, max = +3.79 V)
in3: +3.09 V (min = +4.08 V, max = +4.08 V)
in4: +0.00 V (min = +4.08 V, max = +4.08 V)
in5: +0.00 V (min = +4.08 V, max = +4.08 V)
in6: +0.00 V (min = +4.08 V, max = +4.08 V)
in7: +3.31 V (min = +4.08 V, max = +4.08 V)
in8: +0.00 V (min = +4.08 V, max = +4.08 V)
fan1: 0 RPM (min = 2848 RPM, div = 2)
fan2: 0 RPM (min = 2848 RPM, div = 2)
fan3: 0 RPM (min = 0 RPM, div = 8)
temp1: +127 C (high = -1 C, hyst = -1 C) sensor =
thermistor
temp2: +127.0 C (high = +80 C, hyst = +75 C) sensor =
thermistor ALARM
temp3: +127.0 C (high = +80 C, hyst = +75 C) sensor =
thermistor ALARM
vid: +3.500 V (VRM Version 8.2)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled
arp-i2c-0-61
Adapter: SMBus I801 adapter at 1100
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
@ 2006-05-23 21:21 ` Rudolf Marek
2006-05-24 8:32 ` Rod Morison
` (8 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Rudolf Marek @ 2006-05-23 21:21 UTC (permalink / raw)
To: lm-sensors
Hello,
Rod Morison wrote:
> I am stuck with what it certainly a config problem. I've got lm_sensors
> 2.10.0 running fine on a SuperMicro PDSMA mobo under 2.6.16 kernel.
> However, under 2.4.19 (required for the embedded project I'm on), I'm
> missing sensors for one of the chips. I'm using the same sensors.conf
> and modules.conf/modprobe.conf settings.
>
As for the 2.4 version I cannot see that you have loaded the w83792d kernel module.
Please try the modprobe w83792d
and then sensors
regards
Rudolf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
2006-05-23 21:21 ` Rudolf Marek
@ 2006-05-24 8:32 ` Rod Morison
2006-05-24 8:45 ` Yuan Mu
` (7 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Rod Morison @ 2006-05-24 8:32 UTC (permalink / raw)
To: lm-sensors
Rudolf Marek wrote:
> Hello,
>
> As for the 2.4 version I cannot see that you have loaded the w83792d
> kernel module.
>
> Please try the modprobe w83792d
> and then sensors
You're right. Now I'm fairly sure I have all the sensor bus/chip drivers
loaded under 2.4 that are loaded in the 2.6 kernel, but still I'm
missing the w83792d-i2c-0-2f information. Is it possible that I need to
load the w83792d driver with some option settings?
Am I missing something else?
2.4.19: lsmod
Module Size Used by Tainted: P
i2c-dev 3776 0 (unused)
w83627hf 14104 0 (unused)
smbus-arp 4816 0 (unused)
w83792d 11988 0 (unused)
i2c-isa 804 0 (unused)
i2c-i801 4828 0 (unused)
vrdvx 51460 4
vrdsp 1234848 2
vrsfd 74096 14 [vrdvx vrdsp]
vrmem 9760 2
eeprom 3500 0 (unused)
w83781d 19196 0 (unused)
i2c-proc 5988 0 [w83627hf smbus-arp w83792d eeprom
w83781d]
i2c-core 14276 0 [i2c-dev w83627hf smbus-arp w83792d
i2c-isa i2c-i801 eeprom w83781d i2c-proc]
e1000 98896 1
2.4.19: sensors
eeprom-i2c-0-50
Adapter: SMBus I801 adapter at 1100
Memory type: DDR2 SDRAM DIMM
Memory size (MB): 512
eeprom-i2c-0-52
Adapter: SMBus I801 adapter at 1100
Memory type: DDR2 SDRAM DIMM
Memory size (MB): 512
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1: +0.00 V (min = +3.33 V, max = +3.66 V)
VCore 2: +0.00 V (min = +3.33 V, max = +3.66 V)
+3.3V: +0.00 V (min = +3.14 V, max = +3.46 V)
+5V: +5.19 V (min = +4.74 V, max = +5.24 V)
+12V: +0.00 V (min = +10.83 V, max = +13.19 V)
-12V: -14.91 V (min = -13.16 V, max = -10.90 V)
-5V: -7.71 V (min = -5.26 V, max = -4.76 V)
V5SB: +5.56 V (min = +4.74 V, max = +5.24 V)
VBat: +0.00 V (min = +2.40 V, max = +3.60 V)
fan1: 0 RPM (min = 2848 RPM, div = 2)
fan2: 0 RPM (min = 2848 RPM, div = 2)
fan3: 0 RPM (min = 0 RPM, div = 8)
temp1: +127 C (high = -1 C, hyst = -1 C) sensor =
thermistor
temp2: +127.0 C (high = +80 C, hyst = +75 C) sensor =
thermistor ALARM
temp3: +127.0 C (high = +80 C, hyst = +75 C) sensor =
thermistor ALARM
vid: +3.500 V (VRM Version 8.2)
alarms: Chassis intrusion detection ALARM
beep_enable:
Sound alarm disabled
arp-i2c-0-61
Adapter: SMBus I801 adapter at 1100
2.4.19:
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060524/0671b176/attachment.html
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
2006-05-23 21:21 ` Rudolf Marek
2006-05-24 8:32 ` Rod Morison
@ 2006-05-24 8:45 ` Yuan Mu
2006-05-24 14:13 ` Rod Morison
` (6 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Yuan Mu @ 2006-05-24 8:45 UTC (permalink / raw)
To: lm-sensors
Rod Morison wrote:
> Rudolf Marek wrote:
>> Hello,
>>
>> As for the 2.4 version I cannot see that you have loaded the w83792d
>> kernel module.
>>
>> Please try the modprobe w83792d
>> and then sensors
> You're right. Now I'm fairly sure I have all the sensor bus/chip drivers
> loaded under 2.4 that are loaded in the 2.6 kernel, but still I'm
> missing the w83792d-i2c-0-2f information. Is it possible that I need to
> load the w83792d driver with some option settings?
>
> Am I missing something else?
>
Is there Any information about w83792d in "/proc/sys/dev/sensors" ?
Any messages when load the driver?
Best Regards
Yuan Mu
=============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
` (2 preceding siblings ...)
2006-05-24 8:45 ` Yuan Mu
@ 2006-05-24 14:13 ` Rod Morison
2006-05-24 15:07 ` Rudolf Marek
` (5 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Rod Morison @ 2006-05-24 14:13 UTC (permalink / raw)
To: lm-sensors
Yuan Mu wrote:
>
> Is there Any information about w83792d in "/proc/sys/dev/sensors" ?
> Any messages when load the driver?
>
No, nothing in /proc, but the driver load message appears
relavent...What does the w83792d load error mean, ("Subclients have same
address") and how do I figure out the address for the force_subclients
param?
(What is a "subclient", anyway? Any docs on that anywhere?)
May 24 07:06:54 ImageServer kernel: dmi_scan.o version 2.10.0 (20060214)
May 24 07:06:54 ImageServer kernel: dmi_scan.o: SM BIOS found
May 24 07:06:54 ImageServer kernel: i2c-piix4.o version 2.10.0 (20060214)
May 24 07:06:54 ImageServer kernel: i2c-i801 version 2.10.0 (20060214)
May 24 07:06:54 ImageServer kernel: i2c-isa.o version 2.10.0 (20060214)
May 24 07:06:54 ImageServer kernel: w83781d.o version 2.10.0 (20060214)
May 24 07:06:55 ImageServer kernel: w83792d version 2.10.0 (20060214)
May 24 07:06:55 ImageServer kernel: w83792d: Subclients have the same
address (0x48)! Use force_subclients.
May 24 07:06:55 ImageServer kernel: w83792d.o: Subclient 1 registration
at address 0x48 failed.
May 24 07:06:55 ImageServer kernel: w83627hf.o version 2.10.0 (20060214)
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
` (3 preceding siblings ...)
2006-05-24 14:13 ` Rod Morison
@ 2006-05-24 15:07 ` Rudolf Marek
2006-05-25 6:57 ` Rod Morison
` (4 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Rudolf Marek @ 2006-05-24 15:07 UTC (permalink / raw)
To: lm-sensors
Hello,
I remember I did some patch for 2.6 kernel for this.
Maybe it is missing for 2.4?
Anyway please supply output of following:
modprobe i2c-dev
i2cdetect 0
i2cdump 0 0x2f
I have the motherboard with this chip thanks to ASUS and Winbond so I can help you.
> May 24 07:06:54 ImageServer kernel: dmi_scan.o version 2.10.0 (20060214)
> May 24 07:06:54 ImageServer kernel: dmi_scan.o: SM BIOS found
> May 24 07:06:54 ImageServer kernel: i2c-piix4.o version 2.10.0 (20060214)
> May 24 07:06:54 ImageServer kernel: i2c-i801 version 2.10.0 (20060214)
> May 24 07:06:54 ImageServer kernel: i2c-isa.o version 2.10.0 (20060214)
> May 24 07:06:54 ImageServer kernel: w83781d.o version 2.10.0 (20060214)
> May 24 07:06:55 ImageServer kernel: w83792d version 2.10.0 (20060214)
> May 24 07:06:55 ImageServer kernel: w83792d: Subclients have the same
> address (0x48)! Use force_subclients.
> May 24 07:06:55 ImageServer kernel: w83792d.o: Subclient 1 registration
> at address 0x48 failed.
> May 24 07:06:55 ImageServer kernel: w83627hf.o version 2.10.0 (20060214)
This means that there was some misprogramming done by BIOS which put two other
sublients to same addr. The subclients are legacy LM75 like chips emulated by
w83792d.
Please let me know if
modprobe w83792d force_subclients=0,0x2f,0x4a,0x4b
Will work. the first 0 is the bus number. (I assume it as 0, please change it
for i2cdump too if it is different)
This also assumes that 0x4A and 0x4B are empty (very likely)
The cmd parameter was taken from 2.6 kernel Documentation/hwmon/w83792d file. I
belive we have similar for 2.4 in lm-sensors package.
Anyway, hope this helps. Plus let us know the output of dumps so I can reproduce
and eventually fix the driver.
Regards
Rudolf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
` (4 preceding siblings ...)
2006-05-24 15:07 ` Rudolf Marek
@ 2006-05-25 6:57 ` Rod Morison
2006-05-25 21:25 ` Rudolf Marek
` (3 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Rod Morison @ 2006-05-25 6:57 UTC (permalink / raw)
To: lm-sensors
Rudolf Marek wrote:
> Hello,
>
> I remember I did some patch for 2.6 kernel for this.
>
> Maybe it is missing for 2.4?
>
I'm building 2.10.0 for the 2.4 kernel from source. For 2.6 kernel I'm
using the Suse supplied build (opensuse 10.1 distro).
> Anyway please supply output of following:
>
> modprobe i2c-dev
> i2cdetect 0
> i2cdump 0 0x2f
>
>
Here's the output:
ImageServer#/tmp: ./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 0c 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 2d XX 2f
30: 30 XX 32 XX XX XX XX XX XX XX XX XX XX XX XX XX
40: XX XX XX XX 44 XX XX XX 48 49 XX XX XX XX XX XX
50: UU XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX
60: 60 61 62 63 64 XX XX XX XX 69 XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX
ImageServer#/tmp: ./i2cdump 0 0x2f
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 0x2f, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 01 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ??..............
10: 00 00 64 64 b2 00 00 38 00 ff 00 00 05 00 e0 b3 ..dd?..8....?.??
20: ab c0 cd bd 1f c4 d1 22 18 ff 19 d2 82 ce a9 e2 ???????"?.??????
30: b9 ce a8 2f 13 d9 b1 cc a7 32 00 ed ed ed 39 bf ???/?????2.???9?
40: 03 00 20 57 7f ff ff 33 2f 13 88 c0 45 ff 80 5c ?. W?..3/???E.?\
50: ff ff ff ff ff ff ff ff 7a 20 ff 33 33 01 05 7f ........z .33???
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: 01 8f ff 8f 00 00 00 50 11 ff ff ff 3c 00 0a 0a ??.?...P?...<.??
90: 00 00 00 01 8f ff 00 00 11 ff 3c 00 bf 01 01 ff ...??...?.<.???.
a0: 01 01 01 8f 8f 8f 8f ff 37 40 30 a0 ff ff 00 00 ???????.7 at 0?....
b0: cb cb ff ff cc a7 e2 b9 ff 1e ff ed ed ed 41 ff ??..????.?.???A.
c0: 2c 80 00 4b 00 50 00 ff 1e 80 00 4b 00 50 00 ff ,?.K.P..??.K.P..
d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
e0: 8b ff 8b 28 3c 50 28 3c 50 28 3c 50 ff ff ff ff ?.?(<P(<P(<P....
f0: ff ff 80 ff 00 05 00 7f ff 02 ff 00 00 00 00 ff ..?..?.?.?......
ImageServer#/tmp: lsmod
Module Size Used by Tainted: P
w83627hf 14104 0 (unused)
w83792d 11988 0 (unused)
w83781d 19196 0 (unused)
i2c-isa 804 0 (unused)
i2c-i801 4828 0
eeprom 3500 0 (unused)
i2c-proc 5988 0 [w83627hf w83792d w83781d eeprom]
i2c-dev 3776 0
i2c-core 14276 0 [w83627hf w83792d w83781d i2c-isa
i2c-i801 eeprom i2c-proc i2c-dev]
vrdvx 51460 4
vrdsp 1234848 2
vrsfd 74096 14 [vrdvx vrdsp]
vrmem 9760 2
e1000 98896 1
ImageServer#/tmp:
> This means that there was some misprogramming done by BIOS which put two other
> sublients to same addr. The subclients are legacy LM75 like chips emulated by
> w83792d.
>
>
But why would 2.6 distro work and 2.4 not work for w83792d-i2c-0-2f if
it was a BIOS problem?
> Please let me know if
> modprobe w83792d force_subclients=0,0x2f,0x4a,0x4b
>
>
Nope, still didn't get w83792d-i2c-0-2f to appear. Thanks for the help!
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
` (5 preceding siblings ...)
2006-05-25 6:57 ` Rod Morison
@ 2006-05-25 21:25 ` Rudolf Marek
2006-05-25 22:42 ` Rod Morison
` (2 subsequent siblings)
9 siblings, 0 replies; 11+ messages in thread
From: Rudolf Marek @ 2006-05-25 21:25 UTC (permalink / raw)
To: lm-sensors
> But why would 2.6 distro work and 2.4 not work for w83792d-i2c-0-2f if
> it was a BIOS problem?
>> Please let me know if
>> modprobe w83792d force_subclients=0,0x2f,0x4a,0x4b
modprobe w83792d force_subclients=0,0x2f,0x4b,0x4c
Sorry this should at least theoreticaly work. The driver has some flaw. I will
fix it in the weekend.
If the force does not work please use following before loading driver:
i2cset 0 0x2f 0x4a 0x43
modprobe w83792d
regards
Rudolf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
` (6 preceding siblings ...)
2006-05-25 21:25 ` Rudolf Marek
@ 2006-05-25 22:42 ` Rod Morison
2006-05-26 6:18 ` Rudolf Marek
2006-05-31 15:09 ` Rudolf Marek
9 siblings, 0 replies; 11+ messages in thread
From: Rod Morison @ 2006-05-25 22:42 UTC (permalink / raw)
To: lm-sensors
Yes,
modprobe w83792d force_subclients=0,0x2f,0x4b,0x4c
works like a champ!
So that I can learn from this, how would I (or how did you) figure out
the subclient addresses from the i2cdump?
Thanks again!
Rod
Rudolf Marek wrote:
>> But why would 2.6 distro work and 2.4 not work for w83792d-i2c-0-2f
>> if it was a BIOS problem?
>>> Please let me know if
>>> modprobe w83792d force_subclients=0,0x2f,0x4a,0x4b
>
> modprobe w83792d force_subclients=0,0x2f,0x4b,0x4c
>
> Sorry this should at least theoreticaly work. The driver has some
> flaw. I will fix it in the weekend.
>
> If the force does not work please use following before loading driver:
> i2cset 0 0x2f 0x4a 0x43
> modprobe w83792d
>
> regards
> Rudolf
>
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
` (7 preceding siblings ...)
2006-05-25 22:42 ` Rod Morison
@ 2006-05-26 6:18 ` Rudolf Marek
2006-05-31 15:09 ` Rudolf Marek
9 siblings, 0 replies; 11+ messages in thread
From: Rudolf Marek @ 2006-05-26 6:18 UTC (permalink / raw)
To: lm-sensors
Rod Morison wrote:
> Yes,
>
> modprobe w83792d force_subclients=0,0x2f,0x4b,0x4c
>
> works like a champ!
>
> So that I can learn from this, how would I (or how did you) figure out
> the subclient addresses from the i2cdump?
>
The driver has flaw when the w83792d subclients are disabled. This was fixed for
2.6 but forgotten for 2.4. Moreover it likes to have both subclients on specific
addr ranges. Plus I had to select addresses where no device is present.
I will fix the driver hopefuly in the weekend.
Regards
Rudolf
^ permalink raw reply [flat|nested] 11+ messages in thread
* [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
` (8 preceding siblings ...)
2006-05-26 6:18 ` Rudolf Marek
@ 2006-05-31 15:09 ` Rudolf Marek
9 siblings, 0 replies; 11+ messages in thread
From: Rudolf Marek @ 2006-05-31 15:09 UTC (permalink / raw)
To: lm-sensors
Hello,
Please apply this fix which should fix it:
http://www.lm-sensors.org/changeset/4031?format=diff&new@31
Regards
Rudolf
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2006-05-31 15:09 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-05-23 13:25 [lm-sensors] w83792d works under 2.6 kernel, but not 2.4 kernel Rod Morison
2006-05-23 21:21 ` Rudolf Marek
2006-05-24 8:32 ` Rod Morison
2006-05-24 8:45 ` Yuan Mu
2006-05-24 14:13 ` Rod Morison
2006-05-24 15:07 ` Rudolf Marek
2006-05-25 6:57 ` Rod Morison
2006-05-25 21:25 ` Rudolf Marek
2006-05-25 22:42 ` Rod Morison
2006-05-26 6:18 ` Rudolf Marek
2006-05-31 15:09 ` Rudolf Marek
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.