* [lm-sensors] Asus a8v problems.
@ 2006-01-18 19:17 Patric
2006-01-19 4:22 ` Mark M. Hoffman
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: Patric @ 2006-01-18 19:17 UTC (permalink / raw)
To: lm-sensors
Hi,
I seem to have some problems with lm-sensors here.
First, it seems like in some revision of lm-sensors i lost the ability
to see the RAM that was installed in the system (see the i2cdump later).
I know this worked before, but i'm not shure what version of lm-sensors
it was ten.
The problem that i'm having is that i dont seem to be able to control
fan3. Speeds and everything is correct, but if i just do an echo 0 >pwm3
the fan still does not stop. fan1 and 2 (and pwm1 and 2) works
perfectly. Any hints of what to look at would be a great help, or if you
know that there is some problems like this. (did not find any matching
entrys in the bug-tracker)
Just got the latest daily snapshot of the lm-sensors today but some
stuff seem to still be missing, so lets collect some info.
---------------------------------------------------------
# sensors-detect revision 1.412 (2006/01/17 07:34:49)
Use driver `i2c-viapro' for device 00:11.0: VIA Technologies VT8237
South Bridge
Probe succesfully concluded.
Next adapter: SMBus Via Pro adapter at 0400
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2f
Probing for `Winbond W83791SD'... Success!
(confidence 3, driver `not-a-sensor')
Client found at address 0x48
Client found at address 0x49
Client at address 0x50 can not be probed - unload all client drivers first!
Client at address 0x51 can not be probed - unload all client drivers first!
Client at address 0x52 can not be probed - unload all client drivers first!
Client at address 0x53 can not be probed - unload all client drivers first!
Client found at address 0x61
Probing for `SMBus 2.0 ARP-Capable Device'... Success!
(confidence 1, driver `smbus-arp')
Client found at address 0x69
Do you want to scan for Super I/O sensors? (YES/no):
Probing for `Winbond W83627THF Super IO Sensors'
Success... found at address 0x0290
First address at 0x2f
# 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: 00 00 00 00 00 00 00 00 00 82 00 00 01 00 00 ff .........?..?...
10: 00 00 7f 00 00 10 00 00 00 00 00 00 00 00 00 80 ..?..?.........?
20: 10 05 0f bf 05 05 05 7d ff ff ff 7e 68 00 00 ed ???????}...~h..?
30: b0 00 00 20 10 10 20 10 00 00 20 20 80 02 ff ff ?.. ?? ?.. ??..
40: 01 30 20 00 00 00 00 50 2f 10 01 44 01 95 80 5c ?0 ....P/??D???\
50: ff ff ff ff ff ff 00 80 72 70 ff 00 00 00 05 ff .......?rp....?.
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 ff 01 ff 00 00 00 00 01 01 01 01 3c 3c 0a 0a ?.?.....????<<??
90: 00 00 00 01 ff 00 00 00 01 01 3c 00 00 00 01 01 ...?....??<...??
a0: ff ff ff 00 00 00 00 00 18 ff 6b 18 00 ff ff ff ........?.k?....
b0: bf 00 05 ff 00 06 20 04 00 09 ff ff 84 00 ff ff ?.?..? ?.?..?...
c0: 7d 80 00 4b 00 50 00 ff 7d 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: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................
f0: ff ff 00 ff 00 01 00 ff ff 02 ff 00 00 10 ff 1d .....?...?...?.?
next address at 0x48
# i2cdump 0 0x48
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 0x48, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
10: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
20: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
30: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
40: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
50: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
60: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
70: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
80: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
90: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
a0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
b0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
c0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
d0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
e0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
f0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
next one at 0x49
# i2cdump 0 0x49
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 0x49, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
10: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
20: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
30: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
40: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
50: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
60: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
70: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
80: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
90: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
a0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
b0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
c0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
d0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
e0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
f0: 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 7d 00 4b 50 }.KP}.KP}.KP}.KP
next ones at 0x50-0x53 these seem to be the missing info about the ram
in the system:
# i2cdump 0 0x50
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 0x50, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 80 08 07 0d 0b 02 40 00 04 50 70 00 82 08 00 01 ??????@.?Pp.??.?
10: 0e 04 10 01 02 20 f0 60 70 75 70 3c 28 3c 28 80 ????? ?`pup<(<(?
20: 60 60 40 40 00 00 00 00 00 37 46 1e 28 50 00 00 ``@@.....7F?(P..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bd ...............?
40: 7f 7f 9e 00 00 00 00 00 01 56 53 31 47 42 34 30 ???.....?VS1GB40
50: 30 43 33 20 20 20 20 20 20 20 20 00 00 00 00 00 0C3 .....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
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 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
# i2cdump 0 0x51
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 0x51, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 80 08 07 0d 0b 02 40 00 04 50 70 00 82 08 00 01 ??????@.?Pp.??.?
10: 0e 04 10 01 02 20 f0 60 70 75 70 3c 28 3c 28 80 ????? ?`pup<(<(?
20: 60 60 40 40 00 00 00 00 00 37 46 1e 28 50 00 00 ``@@.....7F?(P..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 bd ...............?
40: 7f 7f 9e 00 00 00 00 00 01 56 53 31 47 42 34 30 ???.....?VS1GB40
50: 30 43 33 20 20 20 20 20 20 20 20 00 00 00 00 00 0C3 .....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
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 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
# i2cdump 0 0x52
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 0x52, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01 ??????@.?P`.??.?
10: 0e 04 08 01 02 20 00 60 70 75 75 3c 28 3c 28 40 ????? .`puu<(<(@
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 55 00 00 ``@@.....7F((U..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 88 ...............?
40: 7f 7f 9e 00 00 00 00 00 01 56 53 35 31 32 4d 42 ???.....?VS512MB
50: 34 30 30 20 20 20 20 20 20 20 20 00 00 00 00 00 400 .....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
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 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
# i2cdump 0 0x53
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 0x53, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: 80 08 07 0d 0a 02 40 00 04 50 60 00 82 08 00 01 ??????@.?P`.??.?
10: 0e 04 08 01 02 20 00 00 00 00 00 3c 28 3c 28 40 ????? .....<(<(@
20: 60 60 40 40 00 00 00 00 00 37 46 28 28 55 00 00 ``@@.....7F((U..
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ce ...............?
40: 7f 7f 9e 00 00 00 00 00 01 56 53 35 31 32 4d 42 ???.....?VS512MB
50: 34 30 30 20 20 20 20 20 20 20 20 00 00 00 00 00 400 .....
60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
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 00 00 00 00 ................
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
So at 0x49 at those ram-info entrys we see to have the string describing
the memory-modules. (yes, i got 2x1Gb and 2x512Mb)
amd ~ # 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 2f
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 48 49 XX XX XX XX XX XX
50: UU UU UU UU XX XX XX XX XX XX XX XX XX XX XX XX
60: XX 61 XX XX XX XX XX XX XX 69 XX XX XX XX XX XX
70: XX XX XX XX XX XX XX XX
# i2cdetect -l
i2c-0 smbus SMBus Via Pro adapter at 0400 Non-I2C
SMBus adapter
NOTE!!
I'm currently switched to the BAD, but better than nothing, Q-fan
function in bios to reduce the noicelevel a little bit. Everything still
looks the same from the "sensors" point of view, and i can see that pwm1
seems to have been reduced by the qfan function.
Hope you can help me, or point me in the right direction.
Regards,
Patric
^ permalink raw reply [flat|nested] 4+ messages in thread
* [lm-sensors] Asus a8v problems.
2006-01-18 19:17 [lm-sensors] Asus a8v problems Patric
@ 2006-01-19 4:22 ` Mark M. Hoffman
2006-01-20 3:53 ` Mark M. Hoffman
2006-01-23 23:17 ` Patric
2 siblings, 0 replies; 4+ messages in thread
From: Mark M. Hoffman @ 2006-01-19 4:22 UTC (permalink / raw)
To: lm-sensors
Hi Patric:
* Patric <pakar at imperialnet.org> [2006-01-18 20:17:51 +0100]:
> I seem to have some problems with lm-sensors here.
> First, it seems like in some revision of lm-sensors i lost the ability
> to see the RAM that was installed in the system (see the i2cdump later).
> I know this worked before, but i'm not shure what version of lm-sensors
> it was ten.
That's a feature, not a bug. ;) Seriously though, we've decided that
memory/SPD display was useful neither for sensors(1) nor libsensors(3).
You can get the same info (and much more) using the perl script
decode-dimms.pl which is in the lm-sensors package also.
I see now, this is not mentioned in the CHANGES file. I'll fix that.
> The problem that i'm having is that i dont seem to be able to control
> fan3. Speeds and everything is correct, but if i just do an echo 0 >pwm3
> the fan still does not stop. fan1 and 2 (and pwm1 and 2) works
> perfectly. Any hints of what to look at would be a great help, or if you
> know that there is some problems like this. (did not find any matching
> entrys in the bug-tracker)
> [...]
> Probing for `Winbond W83627THF Super IO Sensors'
> Success... found at address 0x0290
Using the command 'echo 0 > pwm3' should depend on the kernel driver only.
What kernel version are you using? What version were you using the last
time that worked? Also, can you please send the output from sensors(1) ?
> [...]
Regards,
--
Mark M. Hoffman
mhoffman at lightlink.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* [lm-sensors] Asus a8v problems.
2006-01-18 19:17 [lm-sensors] Asus a8v problems Patric
2006-01-19 4:22 ` Mark M. Hoffman
@ 2006-01-20 3:53 ` Mark M. Hoffman
2006-01-23 23:17 ` Patric
2 siblings, 0 replies; 4+ messages in thread
From: Mark M. Hoffman @ 2006-01-20 3:53 UTC (permalink / raw)
To: lm-sensors
Hi Patric:
Please reply to the list also.
> >* Patric <pakar at imperialnet.org> [2006-01-18 20:17:51 +0100]:
> >>I seem to have some problems with lm-sensors here.
> >>First, it seems like in some revision of lm-sensors i lost the ability
> >>to see the RAM that was installed in the system (see the i2cdump later).
> >>I know this worked before, but i'm not shure what version of lm-sensors
> >>it was ten.
> Mark M. Hoffman wrote:
> >That's a feature, not a bug. ;) Seriously though, we've decided that
> >memory/SPD display was useful neither for sensors(1) nor libsensors(3).
> >You can get the same info (and much more) using the perl script
> >decode-dimms.pl which is in the lm-sensors package also.
> >
> >I see now, this is not mentioned in the CHANGES file. I'll fix that.
* Patric <pakar at imperialnet.org> [2006-01-19 07:05:02 +0100]:
> Ah, that's why i was a bit confused. =)
> The decode-dimms.pl works even better..
I'm glad you like it.
> >>The problem that i'm having is that i dont seem to be able to control
> >>fan3. Speeds and everything is correct, but if i just do an echo 0 >pwm3
> >>the fan still does not stop. fan1 and 2 (and pwm1 and 2) works
> >>perfectly. Any hints of what to look at would be a great help, or if you
> >>know that there is some problems like this. (did not find any matching
> >>entrys in the bug-tracker)
> >
> >
> >>[...]
> >
> >
> >>Probing for `Winbond W83627THF Super IO Sensors'
> >> Success... found at address 0x0290
> >
> >
> >Using the command 'echo 0 > pwm3' should depend on the kernel driver only.
> >What kernel version are you using? What version were you using the last
> >time that worked? Also, can you please send the output from sensors(1) ?
> >
> >
>
> Well, it seems never to have worked, but i just had to install a new fan
> that is much too loud at max speed.
>
> The kernels that i was running at the time i wrote my last mail i was
> running 2.6.15 with a few patches and now i have upgraded to the latest
> mm-kernel 2.6.16-mm1-rc1. And i have been running 2.6.13 and 2.6.14
> before that.
> If there are there any updates for the w83627hf driver that has not yet
> been introduced into the mm-kernel i'm happy to give those a try.
>
> $ sensors
> w83627thf-isa-0290
> Adapter: ISA adapter
> VCore: +1.26 V (min = +0.64 V, max = +0.70 V) ALARM
> +12V: +11.43 V (min = +10.82 V, max = +13.19 V)
> +3.3V: +3.31 V (min = +3.14 V, max = +3.47 V)
> +5V: +5.12 V (min = +4.75 V, max = +5.25 V)
> -12V: +6.06 V (min = -10.80 V, max = -13.18 V) ALARM
> V5SB: +5.08 V (min = +4.76 V, max = +5.24 V)
> VBat: +2.78 V (min = +2.40 V, max = +3.60 V)
> Case Fan: 0 RPM (min = 998 RPM, div = 8) ALARM
> CPU Fan: 1344 RPM (min = 1328 RPM, div = 4)
> Top Fan: 2636 RPM (min = 1328 RPM, div = 4)
> M/B Temp: +25 C (high = +50 C, hyst = +32 C) sensor =
> thermistor
> CPU Temp: +29.5 C (high = +52 C, hyst = +47 C) sensor =
> thermistor
> Pwr Temp: +17.0 C (high = +80 C, hyst = +75 C) sensor =
> thermistor
> vid: +0.675 V (VRM Version 2.4)
> alarms:
> beep_enable:
> Sound alarm enabled
>
> "Case Fan" in this case should be 0 due too the low temp, but the
> problematic fan is the one called "Top Fan".
>
> fan3 looks ok here, and the speed changes slightly also so it does not
> just read a static value.
Some boards have fan headers that are wired to +12V instead of using
the hwmon chip PWM output, even though the speed detection signal is
there. One of my boards is like that (Asus P4C800E-Deluxe); probably
yours is too. Sorry.
Regards,
--
Mark M. Hoffman
mhoffman at lightlink.com
^ permalink raw reply [flat|nested] 4+ messages in thread
* [lm-sensors] Asus a8v problems.
2006-01-18 19:17 [lm-sensors] Asus a8v problems Patric
2006-01-19 4:22 ` Mark M. Hoffman
2006-01-20 3:53 ` Mark M. Hoffman
@ 2006-01-23 23:17 ` Patric
2 siblings, 0 replies; 4+ messages in thread
From: Patric @ 2006-01-23 23:17 UTC (permalink / raw)
To: lm-sensors
Mark M. Hoffman wrote:
>
> Some boards have fan headers that are wired to +12V instead of using
> the hwmon chip PWM output, even though the speed detection signal is
> there. One of my boards is like that (Asus P4C800E-Deluxe); probably
> yours is too. Sorry.
>
That's just to bad... Could not find any information about my a8v, but i
think it's quite evil of them to call the board fully "cool'n'quiet"
compatible as they say. In my eyes that would mean to be able to control
all fans connected to the mainboard. :(
If i ever do an win-install of this system i will do a test just to
verify that it's not controllable. But it's probably gonna take 10-20
years for me to loose my mind and install windows on this system :)
(pwm3 is the connector that's between the cpu-socket and the rear-io
connector if you don't want to wait for me and want to try it yourself. =)
Well well, got myself a manual controller and put it on the least useful
fan. And never again Asus without checking stuff like this before.
Thanks for the assistance, even if i had to get angry because of Asus :)
/Patric
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2006-01-23 23:17 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-01-18 19:17 [lm-sensors] Asus a8v problems Patric
2006-01-19 4:22 ` Mark M. Hoffman
2006-01-20 3:53 ` Mark M. Hoffman
2006-01-23 23:17 ` Patric
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.