[lm-sensors] ali1563 problems

[lm-sensors] ali1563 problems

[Jo Lodewyckx]

Hello,

 

 

I'm using an asrock K8-upgrade 1698 motherboard in my server.

I wanted to use lm_sensors on it but run into some problems.

 

Sensors detect seems to detect my sensors correct but sensors gives me an
error:

 

regawebdev jo # sensors

Can't access procfs/sysfs file

Unable to find i2c bus information;

For 2.6 kernels, make sure you have mounted sysfs and libsensors

was compiled with sysfs support!

For older kernels, make sure you have done 'modprobe i2c-proc'!

 

Relevant Lspci info:

 

regawebdev jo # lspci

00:00.0 Host bridge: ALi Corporation M1689 K8 Northbridge [Super K8 Single
Chip]

00:01.0 PCI bridge: ALi Corporation AGP8X Controller

00:02.0 PCI bridge: ALi Corporation M5249 HTT to PCI Bridge

00:03.0 ISA bridge: ALi Corporation M1563 HyperTransport South Bridge (rev
70)

00:03.1 Bridge: ALi Corporation M7101 Power Management Controller [PMU]

01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX
400] (rev a1)

 

Kernel: 2.6.14-hardened-r6

Sensors version: sensors version 2.10.0 with libsensors version 2.10.0

 

Lsmod:

 

Module                  Size  Used by

i2c_dev                 9968  0

w83627hf               28394  0

hwmon_vid               2475  1 w83627hf

eeprom                  6884  0

i2c_isa                 4548  1 w83627hf

i2c_ali1563             6992  0

i2c_core               19325  5 i2c_dev,w83627hf,eeprom,i2c_isa,i2c_ali1563

 

i2c-detect -l:

i2c-0   smbus           SMBus ALi 1563 Adapter @ 0400           Non-I2C
SMBus adapter

 

i2c-detect 0:

 

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: UU UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX

60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX

70: XX XX XX XX XX XX XX XX

 

Dmesg:

 

ali1563: SMBus control = 0403

ali1563_probe: Returning 0

 

some other relevant info:

regawebdev linux # cat /etc/mtab | grep sysfs
sysfs /sys sysfs rw 0 0

 

regawebdev linux # grep 'SYSFS' /usr/src/linux/.config
CONFIG_SYSFS=y

 

regawebdev linux # grep 'I2C' /usr/src/linux/.config
# I2C support
CONFIG_I2C=m
CONFIG_I2C_CHARDEV=m
# I2C Hardware Bus support
CONFIG_I2C_ALI1535=m
CONFIG_I2C_ALI1563=m
CONFIG_I2C_ALI15X3=m
CONFIG_I2C_ISA=m

 

Relevant sensors detect output:

 

We will now try to load each adapter module in turn.
Load `i2c-ali1563' (say NO if built into your kernel)? (YES/no):
Module loaded succesfully.
Load `rivatv' (say NO if built into your kernel)? (YES/no):
FATAL: Module rivatv not found.
Loading failed... skipping.
** Note: rivatv module is available at  <http://rivatv.sourceforge.net/>
http://rivatv.sourceforge.net/
If you have undetectable or unsupported adapters, you can have them
scanned by manually loading the modules before running this script.

To continue, we need module `i2c-dev' to be loaded.
If it is built-in into your kernel, you can safely skip this.
i2c-dev is already loaded.

We are now going to do the adapter probings. Some adapters may hang halfway
through; we can't really help that. Also, some chips will be double
detected;
we choose the one with the highest confidence value in that case.
If you found that the adapter hung after probing a certain address, you can
specify that address to remain unprobed. That often
includes address 0x69 (clock chip).

Next adapter: SMBus ALi 1563 Adapter @ 0400
Do you want to scan it? (YES/no/selectively):
Client found at address 0x50
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Probing for `DDC monitor'... Failed!
Probing for `Maxim MAX6900'... Failed!
Client found at address 0x51
Probing for `SPD EEPROM'... Success!
(confidence 8, driver `eeprom')
Client found at address 0x69

Some chips are also accessible through the ISA bus. ISA probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan the ISA bus? (YES/no):

Probing for `Winbond W83627HF'
Trying address 0x0290... Success!
(confidence 8, driver `w83781d')

Some Super I/O chips may also contain sensors. Super I/O probes are
typically a bit more dangerous, as we have to write to I/O ports to do
this. This is usually safe though.

Do you want to scan for Super I/O sensors? (YES/no):
Probing for `Winbond W83627HF Super IO Sensors'
Success... found at address 0x0290

 

 

 

Your's sincerely,

 

Jo Lodewyckx

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20060404/d63a04de/attachment-0001.html

[lm-sensors] ali1563 problems

[Rudolf Marek]

Hello,

> /Module                  Size  Used by/
> /i2c_dev                 9968  0/
> /w83627hf               28394  0/
> /hwmon_vid               2475  1 w83627hf/
> /eeprom                  6884  0/
> /i2c_isa                 4548  1 w83627hf/
> /i2c_ali1563             6992  0/
> /i2c_core               19325  5
> i2c_dev,w83627hf,eeprom,i2c_isa,i2c_ali1563/

> 
> /i2c-0   smbus           SMBus ALi 1563 Adapter @ 0400           Non-I2C
> SMBus adapter/
> 

> /     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: UU UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX/
> /60: XX XX XX XX XX XX XX XX XX 69 XX XX XX XX XX XX/
> /70: XX XX XX XX XX XX XX XX/

> *Relevant sensors detect output:*
> 
> / /
> 
> /We will now try to load each adapter module in turn.
> Load `i2c-ali1563' (say NO if built into your kernel)? (YES/no):
> Module loaded succesfully.
> Load `rivatv' (say NO if built into your kernel)? (YES/no):
> FATAL: Module rivatv not found.
> Loading failed... skipping.
> ** Note: rivatv module is available at //http://rivatv.sourceforge.net///
> If you have undetectable or unsupported adapters, you can have them
> scanned by manually loading the modules before running this script.
> 
> To continue, we need module `i2c-dev' to be loaded.
> If it is built-in into your kernel, you can safely skip this.
> i2c-dev is already loaded.
> 
> We are now going to do the adapter probings. Some adapters may hang halfway
> through; we can't really help that. Also, some chips will be double
> detected;
> we choose the one with the highest confidence value in that case.
> If you found that the adapter hung after probing a certain address, you can
> specify that address to remain unprobed. That often
> includes address 0x69 (clock chip).
> 
> Next adapter: SMBus ALi 1563 Adapter @ 0400
> Do you want to scan it? (YES/no/selectively):
> Client found at address 0x50
> Probing for `SPD EEPROM'... Success!
> (confidence 8, driver `eeprom')
> Probing for `DDC monitor'... Failed!
> Probing for `Maxim MAX6900'... Failed!
> Client found at address 0x51
> Probing for `SPD EEPROM'... Success!
> (confidence 8, driver `eeprom')
> Client found at address 0x69
> 
> Some chips are also accessible through the ISA bus. ISA probes are
> typically a bit more dangerous, as we have to write to I/O ports to do
> this. This is usually safe though.
> 


You have no sensor on i2c bus.

> Do you want to scan the ISA bus? (YES/no):
> 
> Probing for `Winbond W83627HF'
> Trying address 0x0290... Success!
> (confidence 8, driver `w83781d')
>
> Some Super I/O chips may also contain sensors. Super I/O probes are
> typically a bit more dangerous, as we have to write to I/O ports to do
> this. This is usually safe though.
> 
> Do you want to scan for Super I/O sensors? (YES/no):
> Probing for `Winbond W83627HF Super IO Sensors'
> Success... found at address 0x0290/

Please can you provide dump of:

isadump 0x295 0x296

Thanks,

Regards
Rudolf

[lm-sensors] ali1563 problems

[Jean Delvare]

> > Do you want to scan the ISA bus? (YES/no):
> > 
> > Probing for `Winbond W83627HF'
> > Trying address 0x0290... Success!
> > (confidence 8, driver `w83781d')
> >
> > Some Super I/O chips may also contain sensors. Super I/O probes are
> > typically a bit more dangerous, as we have to write to I/O ports to do
> > this. This is usually safe though.
> > 
> > Do you want to scan for Super I/O sensors? (YES/no):
> > Probing for `Winbond W83627HF Super IO Sensors'
> > Success... found at address 0x0290/
> 
> Please can you provide dump of:
> 
> isadump 0x295 0x296

And even before that, the contents of /proc/ioports

Kernel 2.6.14 was still affected by the PNP ACPI vs w83627hf issue, we
fixed it only in 2.6.15.
(See http://bugzilla.kernel.org/show_bug.cgi?id@14 for details.)

-- 
Jean Delvare

[lm-sensors] ali1563 problems

[Jo Lodewyckx]

Hi Rudolf,

Here's the isadump:



regawebdev jo # isadump 0x295 0x296
WARNING! Running this program can cause system crashes, data loss and worse!
I will probe address register 0x295 and data register 0x296.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
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: 5b 5c cd bb c7 c7 c8 15 38 35 ff ff 00 ff 00 ed
30: b0 52 3d e1 4b 50 8c 42 79 33 78 4e 3c ff 00 00
40: 01 08 06 00 00 00 00 ff 2d 03 01 44 08 15 80 5c
50: ff ff 00 ff ff ff 00 80 21 70 ff ff 11 00 ff 05
60: 5b 5c cd bb c7 c7 c8 15 38 35 ff ff 00 ff 00 ed
70: b0 52 3d e1 4b 50 8c 42 79 33 78 4e 3c ff 00 00
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: 5b 5c cd bb c7 c7 c8 15 38 35 ff ff 00 ff 00 ed
b0: b0 52 3d e1 4b 50 8c 42 79 33 78 4e 3c ff 00 00
c0: 01 00 00 00 00 00 00 ff 2d 03 01 44 08 15 80 5c
d0: ff ff 00 ff ff ff 00 80 21 70 ff ff 11 00 ff 05
e0: 5b 5c cd bb c7 c7 c8 15 38 35 ff ff 00 ff 00 ed
f0: b0 52 3d e1 4b 50 8c 42 79 33 78 4e 3c ff 00 00

Regards,

Jo


-----Original Message-----
From: Rudolf Marek [mailto:r.marek at sh.cvut.cz] 
Sent: woensdag 5 april 2006 9:51
To: Jo Lodewyckx
Cc: lm-sensors at lm-sensors.org
Subject: Re: [lm-sensors] ali1563 problems


> Do you want to scan the ISA bus? (YES/no):
> 
> Probing for `Winbond W83627HF'
> Trying address 0x0290... Success!
> (confidence 8, driver `w83781d')
>
> Some Super I/O chips may also contain sensors. Super I/O probes are
> typically a bit more dangerous, as we have to write to I/O ports to do
> this. This is usually safe though.
> 
> Do you want to scan for Super I/O sensors? (YES/no):
> Probing for `Winbond W83627HF Super IO Sensors'
> Success... found at address 0x0290/

Please can you provide dump of:

isadump 0x295 0x296

Thanks,

Regards
Rudolf

[lm-sensors] ali1563 problems

[Jo Lodewyckx]

Hello,

The contents of /proc/ioports:


regawebdev proc # cat ioports
0000-001f : dma1
0020-0021 : pic1
0040-0043 : timer0
0050-0053 : timer1
0060-006f : keyboard
0070-0077 : rtc
0080-008f : dma page reg
00a0-00a1 : pic2
00c0-00df : dma2
00f0-00ff : fpu
01f0-01f7 : ide0
0295-0296 : pnp 00:07
03c0-03df : vga+
03f6-03f6 : ide0
0400-040f : i2c-ali1563
0680-06ff : pnp 00:07
0800-083f : 0000:00:03.1
  0800-0803 : PM1a_EVT_BLK
  0804-0805 : PM1a_CNT_BLK
  0808-080b : PM_TMR
  0810-0815 : ACPI CPU throttle
  0818-0827 : GPE0_BLK
  0830-0830 : PM2_CNT_BLK
0cf8-0cff : PCI conf1
e000-efff : PCI Bus #02
  ec00-ec3f : 0000:02:06.0
    ec00-ec3f : e1000
ff00-ff0f : 0000:00:0e.0
  ff00-ff07 : ide0
  ff08-ff0f : ide1



-----Original Message-----
From: Jean Delvare [mailto:khali at linux-fr.org] 
Sent: woensdag 5 april 2006 11:03
To: Jo Lodewyckx
Cc: LM Sensors
Subject: Re: [lm-sensors] ali1563 problems

> > Do you want to scan the ISA bus? (YES/no):
> > 
> > Probing for `Winbond W83627HF'
> > Trying address 0x0290... Success!
> > (confidence 8, driver `w83781d')
> >
> > Some Super I/O chips may also contain sensors. Super I/O probes are
> > typically a bit more dangerous, as we have to write to I/O ports to do
> > this. This is usually safe though.
> > 
> > Do you want to scan for Super I/O sensors? (YES/no):
> > Probing for `Winbond W83627HF Super IO Sensors'
> > Success... found at address 0x0290/
> 
> Please can you provide dump of:
> 
> isadump 0x295 0x296

And even before that, the contents of /proc/ioports

Kernel 2.6.14 was still affected by the PNP ACPI vs w83627hf issue, we
fixed it only in 2.6.15.
(See http://bugzilla.kernel.org/show_bug.cgi?id@14 for details.)

-- 
Jean Delvare

[lm-sensors] ali1563 problems

[Jean Delvare]

Hi Jo,

> The contents of /proc/ioports:
> 
> regawebdev proc # cat ioports
> (...)
> 0295-0296 : pnp 00:07

OK, that's what I suspected then. You have PNP ACPI enabled, and before
2.6.15, the w83627hf driver doesn't work properly with this option
enabled.

Your options are:
1* Upgrade to a 2.6.15+ kernel.
Or:
2* Boot with pnpacpi=off.
Or:
3* Recompile your kernel with CONFIG_PNPACPI disabled.

-- 
Jean Delvare

[lm-sensors] ali1563 problems

[Jo Lodewyckx]

Hi Jean,

Thank you very much!
That was indeed the problem.
I upgraded to the unstable hardened kernel (2.6.16-hardened) and the problem
was solved.

regawebdev jo # sensors
w83627hf-isa-0290
Adapter: ISA adapter
VCore 1:   +1.46 V  (min =  +0.00 V, max =  +0.00 V)       ALARM
VCore 2:   +1.49 V  (min =  +0.00 V, max =  +0.00 V)       ALARM
+3.3V:     +3.28 V  (min =  +3.14 V, max =  +3.47 V)
+5V:       +5.03 V  (min =  +4.76 V, max =  +5.24 V)
+12V:     +12.10 V  (min = +10.82 V, max = +13.19 V)
-12V:      +1.46 V  (min = -13.18 V, max = -10.80 V)       ALARM
-5V:       +2.34 V  (min =  -5.25 V, max =  -4.75 V)       ALARM
V5SB:      +5.64 V  (min =  +4.76 V, max =  +5.24 V)       ALARM
VBat:      +3.25 V  (min =  +2.40 V, max =  +3.60 V)
fan1:     2909 RPM  (min = 2163 RPM, div = 8)
fan2:     3245 RPM  (min = 2812 RPM, div = 8)
fan3:        0 RPM  (min =    0 RPM, div = 2)
temp1:       +26 C  (high =   +51 C, hyst =  +120 C)   sensor = thermistor

temp2:     +31.5 C  (high =   +80 C, hyst =   +75 C)   sensor = thermistor

temp3:     +30.5 C  (high =   +80 C, hyst =   +75 C)   sensor = thermistor

vid:      +0.000 V  (VRM Version 2.4)
alarms:
beep_enable:
          Sound alarm enabled

[lm-sensors] ali1563 problems

[Jean Delvare]

Hi Jo,

> Thank you very much!
> That was indeed the problem.
> I upgraded to the unstable hardened kernel (2.6.16-hardened) and the problem
> was solved.

Great :)

> regawebdev jo # sensors
> w83627hf-isa-0290
> Adapter: ISA adapter
> VCore 1:   +1.46 V  (min =  +0.00 V, max =  +0.00 V)       ALARM
> VCore 2:   +1.49 V  (min =  +0.00 V, max =  +0.00 V)       ALARM

Limits were set to 0 because your VID reads 0 (most probably the pins
aren't wired). You can fix that by changing the configuration lines
in /etc/sensors.conf (section w83627hf-*) not to reference vid anymore:

    set in0_min 1.45 * 0.95
    set in0_max 1.45 * 1.05
    set in1_min 1.5 * 0.95
    set in1_max 1.5 * 1.05

Assuming that your CPU core voltage is 1.45V. in1 is most certainly not
a CPU voltage but rather the AGP voltage (nominal value 1.5V), but
you'll need to compare with what the BIOS or documentation lists to
make sure.

> -12V:      +1.46 V  (min = -13.18 V, max = -10.80 V)       ALARM
> -5V:       +2.34 V  (min =  -5.25 V, max =  -4.75 V)       ALARM

These lines are probably not wired to -12V and -5V. You should comment
out the compute lines for them (in5 and in6) and see if you get
reasonable readings (changing a bit, but not too much). Then, once
again you have to look at what the BIOS or documentation says is
monitored. Once you know, you'll have to adjust the compute lines and
limits accordingly.

> V5SB:      +5.64 V  (min =  +4.76 V, max =  +5.24 V)       ALARM

It's a bit high... Not sure about this one.

> vid:      +0.000 V  (VRM Version 2.4)

Probably not wired, so you could add "ignore vid" to your configuration
file.

The rest looks all OK.

-- 
Jean Delvare