sis5595

sis5595

[Nicolas]

Hello,

I am using 2.6.0-test1,
and I launched "sensors-detect",
it told me I have an sis5595.
So I began to port the 2.4.21 sis5595 driver to 2.6 kernel.
Here are the beginning of my work, but I am stuck here :
i2c_detect doesn't call sis5595_detect.

I don't know if it is because I haven't the good hardware or
if I made a mistake. I seems I have something at adress 8008, but I don't
have enougth experience in developping kernel drivers so I gived up,
and I send you my work.

Regards.

Nicolas Parpandet.

You can reply me on linux@1g6.biz

ul 15 23:41:17 hal9003 kernel: sis5595.o: version 2.7.0 (20021208)
Jul 15 23:41:17 hal9003 kernel: sis5595.o: before imposter
Jul 15 23:41:17 hal9003 kernel: sis5595.o: after imposter
Jul 15 23:41:17 hal9003 kernel: sis5595.o: after pci_read_config_word
Jul 15 23:41:17 hal9003 kernel: sis5595.o: addr 8008 force_addr 0
Jul 15 23:41:17 hal9003 kernel: sis5595.o: before i2c_add_driver
Jul 15 23:41:17 hal9003 kernel: sis5595.o: not class 2 1 0
Jul 15 23:41:17 hal9003 kernel: i2c_detect: is_isa 0
Jul 15 23:41:17 hal9003 kernel: i2c_detect: begin i2c_detect 0 to 7f
Jul 15 23:41:17 hal9003 kernel: i2c_detect: for addr 0
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sis5595.c
Type: text/x-csrc
Size: 28747 bytes
Desc: not available
Url : http://lists.lm-sensors.org/pipermail/lm-sensors/attachments/20030716/beed2bbe/sis5595.bin

sis5595

[Jean Delvare]

> I am using 2.6.0-test1,
> and I launched "sensors-detect",
> it told me I have an sis5595.
> So I began to port the 2.4.21 sis5595 driver to 2.6 kernel.
> Here are the beginning of my work, but I am stuck here :
> i2c_detect doesn't call sis5595_detect.

There are many, many SiS chipsets that are misdetected as SiS5595. I
suggest you begin with trying lm_sensors on a 2.4 kernel, so you'll see
if it works on your system. What's more, libsensors and most userspace
tools do not exist

> I don't know if it is because I haven't the good hardware or
> if I made a mistake. I seems I have something at adress 8008, but I
> don't have enougth experience in developping kernel drivers so I gived
> up, and I send you my work.

Your porting is wrong. In 2.5/2.6, sensor modules export their values
using sysfs, not procfs. And I guess you started with an old version of
sis5595.c, because many things I see in "your" code has been removed
from our times ago. If you really want to port the driver, please see
with Greg how to do this correctly.

-- 
Jean Delvare
http://www.ensicaen.ismra.fr/~delvare/

sis5595

[Nicolas]

Hello,

kernel 2.4 doesn't work on my computer 
(no networking because sis648/sis900),

The procfs stuffs are /* commented */,
I looked at differencies in via686a.c and it87.c betweens 2.4 and 2.6
 to port sis5595.c, so if
via686a/it87 aren't good in 2.6 ... :(,
I lost my time.

have a look : 
[root@hal9003 SiS 5595]# uname -a
Linux hal9003.1g6.biz 2.6.0-test1 #15 mar jui 15...
[root@hal9003 SiS 5595]# pwd
/sys/bus/i2c/drivers/SiS 5595  (apparently not totally wrong)

[root@hal9003 proc]# find /proc -iname "*sis*"
/proc/ide/sis

491         /* Register a new directory entry with module sensors */
    492         device_create_file(&new_client->dev, &dev_attr_fan_input1);
    493         device_create_file(&new_client->dev, &dev_attr_fan_min1);
    494         device_create_file(&new_client->dev, &dev_attr_fan_div1);
    495         device_create_file(&new_client->dev, &dev_attr_fan_input2);
    496         device_create_file(&new_client->dev, &dev_attr_fan_min2);
    497         device_create_file(&new_client->dev, &dev_attr_fan_div2);
    498         //device_create_file(&new_client->dev, &dev_attr_in_input0);
    499         /*
    500         if ((i = i2c_register_entry((struct i2c_client *) new_client,

I didn't know for the misdetection problem, and I just
wanted "cat /sys/..", doesn't mind about libraries...

Regards.

Nicolas.

Le Mercredi 16 Juillet 2003 15:04, vous avez ?crit :
> > I am using 2.6.0-test1,
> > and I launched "sensors-detect",
> > it told me I have an sis5595.
> > So I began to port the 2.4.21 sis5595 driver to 2.6 kernel.
> > Here are the beginning of my work, but I am stuck here :
> > i2c_detect doesn't call sis5595_detect.
>
> There are many, many SiS chipsets that are misdetected as SiS5595. I
> suggest you begin with trying lm_sensors on a 2.4 kernel, so you'll see
> if it works on your system. What's more, libsensors and most userspace
> tools do not exist
>
> > I don't know if it is because I haven't the good hardware or
> > if I made a mistake. I seems I have something at adress 8008, but I
> > don't have enougth experience in developping kernel drivers so I gived
> > up, and I send you my work.
>
> Your porting is wrong. In 2.5/2.6, sensor modules export their values
> using sysfs, not procfs. And I guess you started with an old version of
> sis5595.c, because many things I see in "your" code has been removed
> from our times ago. If you really want to port the driver, please see
> with Greg how to do this correctly.

sis5595

[Mark M. Hoffman]

* Nicolas <linux@1g6.biz> [2003-07-16 16:04:39 +0200]:
> 
> kernel 2.4 doesn't work on my computer 
> (no networking because sis648/sis900),
                         ^^^^^^^^^^^^^

1. As Jean guessed, you don't have a sis5595.  Your port of that module,
even if it loads, is not what you want.

2. The workaround for kernel 2.4 is to load the i2c-sis645 module
*before* you load the sis900 module.

3. In kernel >= 2.5.7x (where x means I can't remember) you want to load
i2c-sis96x instead - sorry for the confusion, but that name is more
accurate.

So I might recommend to you...

Try kernel 2.4 again with I2C and sensors 2.8.0 release so that you can
see what sensors chip you have.  I assure you, it's not sis5595.  Then
see if that chip is supported by kernel 2.6... maybe so, or maybe you'll
want to port that one.

<snip>

Regards,

-- 
Mark M. Hoffman
mhoffman@lightlink.com

[lm-sensors] sis5595

[Jean Delvare]

Hi Ivo,

Now that we got your SiS5595 to work again, maybe you want to spend
some time finding out why the sensors output doesn't match what you
have in your BIOS? If so, please provide the following information:

* Full output of the latest version of sensors-detect (just to make
sure you don't have a _second_ hardware monitoring chip).
* A list of all hardware monitoring information that is listed by your
BIOS. Labels and values, in order.
* Several outputs of "sensors -c /dev/null", 1 minute apart or so.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Ivo Manca]

Hey Jean,

Thanks for helping out, if you need more information, just let me know

> Sensors-detect:
[root@localhost ~]# sensors-detect
# sensors-detect revision 4348 (2007-03-18 02:45:21 -0700)

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

We can start with probing for (PCI) I2C or SMBus adapters.
Do you want to probe now? (YES/no):
Probing for PCI bus adapters...
Use driver `i2c-sis5595' for device 0000:00:01.0: Silicon Integrated Systems 
SIS5595

We will now try to load each adapter module in turn.
Module `i2c-sis5595' already loaded.
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.
Do you want to load `i2c-dev' now? (YES/no):
Module loaded successfully.

We are now going to do the I2C/SMBus adapter probings. Some chips may
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.

Next adapter: SMBus SIS5595 adapter at 0438 (i2c-0)
Do you want to scan it? (YES/no/selectively):

Some chips are also accessible through the ISA I/O ports. We have to
write to arbitrary I/O ports to probe them. This is usually safe though.
Yes, you do have ISA I/O ports even if you do not have any ISA slots!
Do you want to scan the ISA I/O ports? (YES/no): Probing for `National 
Semiconductor LM78' at 0x290...       Success!
    (confidence 6, driver `lm78')
Probing for `National Semiconductor LM78-J' at 0x290...     No
Probing for `National Semiconductor LM79' at 0x290...       No
Probing for `Winbond W83781D' at 0x290...                   No
Probing for `Winbond W83782D' at 0x290...                   No
Probing for `Silicon Integrated Systems SIS5595'...         Success!
    (confidence 9, driver `sis5595')
Probing for `VIA VT82C686 Integrated Sensors'...            No
Probing for `VIA VT8231 Integrated Sensors'...              No
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No

Some Super I/O chips may also contain sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `ITE'...                                      No
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No
Probing for Super-I/O at 0x4e/0x4f
Trying family `ITE'...                                      No
Trying family `National Semiconductor'...                   No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Fintek'...                       No

Some CPUs or memory controllers may also contain embedded sensors.
Do you want to scan for them? (YES/no):
AMD K8 thermal sensors...                                   No
Intel Core family thermal sensor...                         No
Intel AMB FB-DIMM thermal sensor...                         No

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `lm78' (should be inserted):
  Detects correctly:
  * ISA bus, address 0x290
    Chip `National Semiconductor LM78' (confidence: 6)

Driver `sis5595' (should be inserted):
  Detects correctly:
  * ISA bus
    Chip `Silicon Integrated Systems SIS5595' (confidence: 9)

I will now generate the commands needed to load the required modules.
Just press ENTER to continue:

To make the sensors modules behave correctly, add these lines to
/etc/modules.conf:

#----cut here----
# I2C module options
alias char-major-89 i2c-dev
#----cut here----

To load everything that is needed, add this to some /etc/rc* file:

#----cut here----
# Chip drivers
modprobe lm78
modprobe sis5595
# sleep 2 # optional
/usr/bin/sensors -s # recommended
#----cut here----

If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones! You really
should try these commands right now to make sure everything is
working properly. Monitoring programs won't work until the needed
modules are loaded.

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no):
[root@localhost ~]#


> BIOS output:
CPU Temprature                    49` C / 120` F
CPU FAN Speed                   Disconnected
Vcc 5.0V                                5.093V
Vcc 3.3V                                3.382V
Vcc 2.5V                                2,949V
Vcore                                      2,048V

> sensors -c /dev/null
[root@localhost ~]# sensors -c /dev/null
sis5595-isa-0290
Adapter: ISA adapter
in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in2:       +2.75 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +3.62 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
alarms:   Board temperature input (usually LM75 chips) ALARM

[root@localhost ~]# sensors -c /dev/null
sis5595-isa-0290
Adapter: ISA adapter
in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in2:       +2.74 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +3.62 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
alarms:   Board temperature input (usually LM75 chips) ALARM

[root@localhost ~]# sensors -c /dev/null
sis5595-isa-0290
Adapter: ISA adapter
in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in2:       +2.74 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +3.63 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
alarms:   Board temperature input (usually LM75 chips) ALARM

[root@localhost ~]# sensors -c /dev/null
sis5595-isa-0290
Adapter: ISA adapter
in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in2:       +2.74 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +3.62 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
alarms:   Board temperature input (usually LM75 chips) ALARM

[root@localhost ~]# sensors -c /dev/null
sis5595-isa-0290
Adapter: ISA adapter
in0:       +2.86 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in2:       +2.74 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +3.62 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
alarms:   Board temperature input (usually LM75 chips) ALARM

[root@localhost ~]# sensors -c /dev/null
sis5595-isa-0290
Adapter: ISA adapter
in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in2:       +2.74 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +3.62 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
alarms:   Board temperature input (usually LM75 chips) ALARM

--
Removing sis5595 & loading lm78 also gives output?
[root@localhost ~]# rmmod sis5595
[root@localhost ~]# modprobe lm78
[root@localhost ~]# sensors
lm78-isa-0290
Adapter: ISA adapter
VCore 1:   +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
VCore 2:   +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+3.3V:     +2.75 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+5V:       +3.44 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+12V:     +13.74 V  (min =  +0.00 V, max =  +0.00 V)
-12V:      -0.00 V  (min =  -0.00 V, max =  -0.00 V)
-5V:       -0.00 V  (min =  -0.00 V, max =  -0.00 V)
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan3:       -1 RPM  (min =   -1 RPM, div = 2)
temp:     +127.0°C  (high =    +0°C, hyst =    +0°C)
vid:       +3.50 V
alarms:   Board temperature input (LM75)               ALARM

Ivo

----- Original Message ----- 
From: "Jean Delvare" <khali@linux-fr.org>
To: "Ivo Manca" <pinkel@gmail.com>; "LM Sensors" <lm-sensors@lm-sensors.org>
Sent: Thursday 7 June 2007 19:40
Subject: sis5595


> Hi Ivo,
>
> Now that we got your SiS5595 to work again, maybe you want to spend
> some time finding out why the sensors output doesn't match what you
> have in your BIOS? If so, please provide the following information:
>
> * Full output of the latest version of sensors-detect (just to make
> sure you don't have a _second_ hardware monitoring chip).
> * A list of all hardware monitoring information that is listed by your
> BIOS. Labels and values, in order.
> * Several outputs of "sensors -c /dev/null", 1 minute apart or so.
>
> -- 
> Jean Delvare 


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Jean Delvare]

[-- Attachment #1: Type: text/plain, Size: 7008 bytes --]

Hi Ivo,

On Fri, 8 Jun 2007 17:20:10 +0200, Ivo Manca wrote:
> Thanks for helping out, if you need more information, just let me know
> 
> > Sensors-detect:
> Next adapter: SMBus SIS5595 adapter at 0438 (i2c-0)
> Do you want to scan it? (YES/no/selectively):

Nothing on the SMBus.

> Some chips are also accessible through the ISA I/O ports. We have to
> write to arbitrary I/O ports to probe them. This is usually safe though.
> Yes, you do have ISA I/O ports even if you do not have any ISA slots!
> Do you want to scan the ISA I/O ports? (YES/no): Probing for `National 
> Semiconductor LM78' at 0x290...       Success!
>     (confidence 6, driver `lm78')
> Probing for `National Semiconductor LM78-J' at 0x290...     No
> Probing for `National Semiconductor LM79' at 0x290...       No
> Probing for `Winbond W83781D' at 0x290...                   No
> Probing for `Winbond W83782D' at 0x290...                   No
> Probing for `Silicon Integrated Systems SIS5595'...         Success!
>     (confidence 9, driver `sis5595')
> Probing for `VIA VT82C686 Integrated Sensors'...            No
> Probing for `VIA VT8231 Integrated Sensors'...              No
> Probing for `IPMI BMC KCS' at 0xca0...                      No
> Probing for `IPMI BMC SMIC' at 0xca8...                     No
> 
> Some Super I/O chips may also contain sensors. We have to write to
> standard I/O ports to probe them. This is usually safe.
> Do you want to scan for Super I/O sensors? (YES/no):
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `ITE'...                                      No
> Trying family `National Semiconductor'...                   No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Fintek'...                       No
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `ITE'...                                      No
> Trying family `National Semiconductor'...                   No
> Trying family `SMSC'...                                     No
> Trying family `VIA/Winbond/Fintek'...                       No
> 
> Some CPUs or memory controllers may also contain embedded sensors.
> Do you want to scan for them? (YES/no):
> AMD K8 thermal sensors...                                   No
> Intel Core family thermal sensor...                         No
> Intel AMB FB-DIMM thermal sensor...                         No
> 
> Now follows a summary of the probes I have just done.
> Just press ENTER to continue:
> 
> Driver `lm78' (should be inserted):
>   Detects correctly:
>   * ISA bus, address 0x290
>     Chip `National Semiconductor LM78' (confidence: 6)

This is a misdetection, as we know (from the "sensors" output below)
that the SiS5595 hardware monitoring function is mapped to I/O address
0x290. Unfortunately sensors-detect cannot (easily) detect this
address, so we'll have to live with the misdetection for now.

> Driver `sis5595' (should be inserted):
>   Detects correctly:
>   * ISA bus
>     Chip `Silicon Integrated Systems SIS5595' (confidence: 9)

> > BIOS output:
> CPU Temprature                    49` C / 120` F
> CPU FAN Speed                   Disconnected
> Vcc 5.0V                                5.093V
> Vcc 3.3V                                3.382V
> Vcc 2.5V                                2,949V
> Vcore                                      2,048V
> 
> > sensors -c /dev/null
> [root@localhost ~]# sensors -c /dev/null
> sis5595-isa-0290
> Adapter: ISA adapter
> in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in2:       +2.75 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in4:       +3.62 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
> fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
> alarms:   Board temperature input (usually LM75 chips) ALARM

OK. There are some correlations, this isn't that bad.

It seems that your SiS5595 is wired for 1 temperature and 4 voltages,
rather than 5 voltages as the driver detects. I guess that your BIOS
doesn't properly set up the relevant configuration bit when the setup
screen isn't entered. Please look for a BIOS update. If there is none,
or if it doesn't solve the problem, we'll have to add a module
parameter to allow the user to force one of the modes when
autodetection fails.

For now, you can try changing the configuration manually. First, do:
lspci -d 1039:0008 -xxx
This will dump the PCI configuration space of your device. I guess that
bit 7 of register 0x7a will be 0, while it should be 1. You can change
it with:
setpci -d 1039:0008 7a.b=80:80
Check with lspci that the write worked, then reload the sis5595 driver,
it should list 4 voltages and one temperature. Please provide the
output then.

For voltages, the SiS5595 uses a DAC sampling from 0 to 4.08 V. This
means that voltage values of 3.3 V and below are probably connected
directly. This seems to match. in0 would be "Vcc 2.5V" (which BTW, is
way too high!), in1 would be "Vcc 3.3V", and in3 would be "Vcore". This
leaves in2 for "Vcc 5.0V", with a scaling factor we'll have to guess.
The standard +5V formula doesn't appear to work.

For fans, do you have 3-wire fans? Are they connected to headers on
the motherboard? If they are relatively slow, maybe we need to increase
the divider to get a reading.

Lastly, alarms, given that you don't have any other hardware monitoring
chip on this board, I guess this alarm isn't meaningful and should be
ignored.

I attached a preliminary configuration file for your motherboard.
Please give it a try. You can tell "sensors" to use it with the "-c"
flag. Use "-s" to write the limit values to the chip.

What's your CPU? Do you happen to know its nominal vcore?

> Removing sis5595 & loading lm78 also gives output?
> [root@localhost ~]# rmmod sis5595
> [root@localhost ~]# modprobe lm78
> [root@localhost ~]# sensors
> lm78-isa-0290
> Adapter: ISA adapter
> VCore 1:   +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> VCore 2:   +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> +3.3V:     +2.75 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> +5V:       +3.44 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> +12V:     +13.74 V  (min =  +0.00 V, max =  +0.00 V)
> -12V:      -0.00 V  (min =  -0.00 V, max =  -0.00 V)
> -5V:       -0.00 V  (min =  -0.00 V, max =  -0.00 V)
> fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
> fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
> fan3:       -1 RPM  (min =   -1 RPM, div = 2)
> temp:     +127.0°C  (high =    +0°C, hyst =    +0°C)
> vid:       +3.50 V
> alarms:   Board temperature input (LM75)               ALARM

This is all noise, you don't have a LM78. Don't load the lm78 driver.

-- 
Jean Delvare

[-- Attachment #2: sensors-PCChips-M748LMRT.conf --]
[-- Type: text/plain, Size: 771 bytes --]

# lm_sensors configuration file for the PCChips M748LMRT motherboard
# 2007-06-09, Jean Delvare <khali@linux-fr.org>
# Preliminary version. Comments welcome!

chip "sis5595-*"

### Voltages

   label in0 "+2.5V"
   label in1 "+3.3V"
   label in2 "+5.0V"
   label in3 "Vcore"

   # Non-standard scaling resistors are used for +5V, so this is guess
   # work.
   compute in2 @*(1+8.6/10),  @/(1+8.6/10)

   set in0_min 2.5 * 0.90
   set in0_max 2.5 * 1.10
   set in1_min 3.3 * 0.95
   set in1_max 3.3 * 1.05
   set in2_min 5.0 * 0.95
   set in2_max 5.0 * 1.05
   set in3_min 2.0 * 0.95
   set in3_max 2.0 * 1.05

### Fans

   set fan1_div 8
   set fan2_div 8
   set fan1_min 1000
   set fan2_min 1000

### Temperatures

   label temp "CPU Temp"

### Misc

   ignore alarms

[-- Attachment #3: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Ivo Manca]

Hey Jean,

I'm currently not home, so I do not have local acces yet.

> It seems that your SiS5595 is wired for 1 temperature and 4 voltages,
> rather than 5 voltages as the driver detects. I guess that your BIOS
> doesn't properly set up the relevant configuration bit when the setup
> screen isn't entered. Please look for a BIOS update. If there is none,
> or if it doesn't solve the problem, we'll have to add a module
> parameter to allow the user to force one of the modes when
> autodetection fails.

I already flashed my bios to the latest version, a week or so ago. This did 
sadly not fix anything .
I've read the docs concerning this chips, and I also figured out this had to 
be a BIOS error.
I wrote a mail to AMI two weeks ago, concerning their " AMI Desktop client 
manager"  for windows, which is supposed to expose me some more information 
about the hardware. I've lost the CD, and can't find it anywhere on the net. 
However, they've not yet responded.

The manual states:

Hardware Monitoring
¨       Built-in hardware monitoring for CPU temperature and fan speeds
¨       Supports AMI's  Desktop Client Manager (ADCM)

> For now, you can try changing the configuration manually. First, do:
> lspci -d 1039:0008 -xxx
> This will dump the PCI configuration space of your device. I guess that
> bit 7 of register 0x7a will be 0, while it should be 1. You can change

[root@localhost ~]# lspci -d 1039:0008 -xxx
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC 
Bridge) (rev b1)
00: 39 10 08 00 0f 00 00 02 b1 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: f8 0a 0b 80 80 60 90 40 f7 ff 10 0f 11 20 04 01
50: 11 28 02 01 60 00 62 00 a5 12 12 00 d3 8b 00 00
60: 0c 80 43 00 34 c1 40 04 90 02 8c 00 20 1b 00 00
70: 1a 00 00 00 80 00 00 00 ff 00 00 80 00 00 80 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 04 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


> it with:
> setpci -d 1039:0008 7a.b€:80
> Check with lspci that the write worked, then reload the sis5595 driver,
> it should list 4 voltages and one temperature. Please provide the
> output then.

[root@localhost ~]# setpci -d 1039:0008 7a.b€:80
[root@localhost ~]# lspci -d 1039:0008 -xxx
00:01.0 ISA bridge: Silicon Integrated Systems [SiS] SiS85C503/5513 (LPC 
Bridge) (rev b1)
00: 39 10 08 00 0f 00 00 02 b1 00 01 06 00 00 80 00
10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
40: f8 0a 0b 80 80 60 90 40 f7 ff 10 0f 11 20 04 01
50: 11 28 02 01 62 00 62 00 a5 12 12 00 d3 8b 00 00
60: 0c 80 43 00 34 c1 40 04 90 02 8c 00 20 1b 00 00
70: 1a 00 00 00 80 00 00 00 ff 00 80 80 00 00 80 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 04 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

Sensors gives a temprature after removing & loading the module:

[root@localhost ~]# sensors -c /dev/null
sis5595-isa-0290
Adapter: ISA adapter
in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in2:       +2.74 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
temp:       +158°C  (high =   +52°C, hyst =   +52°C)
alarms:   Board temperature input (usually LM75 chips) ALARM

> For voltages, the SiS5595 uses a DAC sampling from 0 to 4.08 V. This
> means that voltage values of 3.3 V and below are probably connected
> directly. This seems to match. in0 would be "Vcc 2.5V" (which BTW, is
> way too high!)
I'm not really suprised by that. This system has been around the family for 
almost a decade now, and the same powersupply is still used. Untill a year 
or two ago, it was actually used quite frequently (1hour/day, minumum), 
after which I adopted it as a linux server (4 hours/day, or so). Now it just 
remains alive for testing and fooling around.
However, there have been troubles with the system since the beginning (CPU 
fried within a month) and the motherboard has gave me quite some headaches 
before. It is actually quite stable now, just very slow.

> , in1 would be "Vcc 3.3V", and in3 would be "Vcore". This
> leaves in2 for "Vcc 5.0V", with a scaling factor we'll have to guess.
> The standard +5V formula doesn't appear to work.

> For fans, do you have 3-wire fans? Are they connected to headers on
> the motherboard? If they are relatively slow, maybe we need to increase
> the divider to get a reading.
As far as I can remember (I'll have to look into it tomorrow), my fan is 
connected directly to the PSU, bypassing the motherboard.

> Lastly, alarms, given that you don't have any other hardware monitoring
> chip on this board, I guess this alarm isn't meaningful and should be
> ignored.

> I attached a preliminary configuration file for your motherboard.
> Please give it a try. You can tell "sensors" to use it with the "-c"
> flag. Use "-s" to write the limit values to the chip.
Thanks!

[root@localhost ivo]# sensors -c sensors-PCChips -s
[root@localhost ivo]# sensors -c sensors-PCChips
sis5595-isa-0290
Adapter: ISA adapter
+2.5V:     +2.96 V  (min =  +2.26 V, max =  +2.75 V)   ALARM
+3.3V:     +3.41 V  (min =  +3.14 V, max =  +3.47 V)
+5.0V:     +5.09 V  (min =  +4.76 V, max =  +5.24 V)
Vcore:     +2.05 V  (min =  +1.90 V, max =  +2.10 V)
fan1:        0 RPM  (min =  998 RPM, div = 8)          ALARM
fan2:        0 RPM  (min =  998 RPM, div = 8)          ALARM
CPU Temp:   +158°C  (high =   +52°C, hyst =   +52°C)

It seems like the +5,0V actually makes complete sense now!  However, what's 
up with the Temp? The default sensors.conf speaks about a vendor.ini. I 
suppose this should be coming with AMI's utility?
I''m not really sure if I understand what's ment with all the computing 
stuff standing there ;)

> What's your CPU? Do you happen to know its nominal vcore?
It's an Intel Celeron 366. According to this page 
(http://www.intel.com/support/processors/celeron/sb/CS-007435.htm#Voltage%20Requirements), 
it is 2,00V.

-- 
Jean Delvare 


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Jean Delvare]

Hi Ivo,

On Sat, 9 Jun 2007 13:56:43 +0200, Ivo Manca wrote:
> Sensors gives a temprature after removing & loading the module:
> 
> [root@localhost ~]# sensors -c /dev/null
> sis5595-isa-0290
> Adapter: ISA adapter
> in0:       +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in1:       +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in2:       +2.74 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> in3:       +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
> fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
> temp:       +158°C  (high =   +52°C, hyst =   +52°C)
> alarms:   Board temperature input (usually LM75 chips) ALARM

Not exactly a good temperature though. According to the driver source,
158°C corresponds to a register value of 127 degree C - which means
saturation. So it's no good.

One possibility that I am only thinking of now, is that the temperature
might be provided by a thermistor and not a diode. In which case it
would make sense that the BIOS leaves in4 as a voltage input. So can
you please revert the PCI configuration change:

setpci -d 1039:0008 7a.b\0:80

Then reload the driver, check the voltage values, then put some load on
the CPU (e.g. md5sum /dev/zero) for several minutes and check if any of
the voltages changed significantly. If one did, then this input might
be connected to a thermistor. Unfortunately, without technical
information from the manufacturer, it will be difficult to find out how
to translate the voltage into a temperature.

> > For fans, do you have 3-wire fans? Are they connected to headers on
> > the motherboard? If they are relatively slow, maybe we need to increase
> > the divider to get a reading.
>
> As far as I can remember (I'll have to look into it tomorrow), my fan is 
> connected directly to the PSU, bypassing the motherboard.

OK, then it's no surprise that you get no reading, neither in the BIOS
no in "sensors". You need a 3-wire fan plugged into the motherboard fan
header to get a speed reading.

> [root@localhost ivo]# sensors -c sensors-PCChips -s
> [root@localhost ivo]# sensors -c sensors-PCChips
> sis5595-isa-0290
> Adapter: ISA adapter
> +2.5V:     +2.96 V  (min =  +2.26 V, max =  +2.75 V)   ALARM
> +3.3V:     +3.41 V  (min =  +3.14 V, max =  +3.47 V)
> +5.0V:     +5.09 V  (min =  +4.76 V, max =  +5.24 V)
> Vcore:     +2.05 V  (min =  +1.90 V, max =  +2.10 V)
> fan1:        0 RPM  (min =  998 RPM, div = 8)          ALARM
> fan2:        0 RPM  (min =  998 RPM, div = 8)          ALARM
> CPU Temp:   +158°C  (high =   +52°C, hyst =   +52°C)
> 
> It seems like the +5,0V actually makes complete sense now!

Well, I crafted the configuration file to make it look good, so it
doesn't mean much ;)

> However, what's 
> up with the Temp? The default sensors.conf speaks about a vendor.ini. I 
> suppose this should be coming with AMI's utility?
> I''m not really sure if I understand what's ment with all the computing 
> stuff standing there ;)

No idea what vendor.ini they're talking about. The computing stuff is
there to account for different thermal diode types, but as I said
above, I don't think you have a thermal diode, so no amount of
computing will give you a temperature value while in4 is in temperature
mode.

> > What's your CPU? Do you happen to know its nominal vcore?
> It's an Intel Celeron 366. According to this page 
> (http://www.intel.com/support/processors/celeron/sb/CS-007435.htm#Voltage%20Requirements), 
> it is 2,00V.

Good, exactly what I put in the config file :)

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Ivo Manca]

Hey Jean,

> Not exactly a good temperature though. According to the driver source,
> 158°C corresponds to a register value of 127 degree C - which means
> saturation. So it's no good.

> One possibility that I am only thinking of now, is that the temperature
> might be provided by a thermistor and not a diode. In which case it
> would make sense that the BIOS leaves in4 as a voltage input. So can
> you please revert the PCI configuration change:

> setpci -d 1039:0008 7a.b\0:80
Done

> Then reload the driver, check the voltage values, then put some load on
> the CPU (e.g. md5sum /dev/zero) for several minutes and check if any of
> the voltages changed significantly. If one did, then this input might
> be connected to a thermistor. Unfortunately, without technical
> information from the manufacturer, it will be difficult to find out how
> to translate the voltage into a temperature.
[root@localhost ivo]# sensors -c sensors-PCChips
sis5595-isa-0290
Adapter: ISA adapter
+2.5V:     +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+3.3V:     +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+5.0V:     +5.09 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
Vcore:     +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +3.55 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM

after md5sum:
[root@localhost ivo]# sensors -c sensors-PCChips
sis5595-isa-0290
Adapter: ISA adapter
+2.5V:     +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+3.3V:     +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+5.0V:     +5.15 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
Vcore:     +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +0.19 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM

Seems like in4 dropped completely?
Wait: it seemed like a flatcable dropped on the fan, and stopped it 
spinning. So I guess +0,19V is suppose to say "Way to hot: you're burning 
your fingers!"? (Since I actually did burn my finger)

But one minute after the fan started spinning again...
[root@localhost ivo]# sensors -c sensors-PCChips
sis5595-isa-0290
Adapter: ISA adapter
+2.5V:     +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+3.3V:     +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+5.0V:     +5.12 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
Vcore:     +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +0.00 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM

And 30 seconds later:
[root@localhost ivo]# sensors -c sensors-PCChips
sis5595-isa-0290
Adapter: ISA adapter
+2.5V:     +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+3.3V:     +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+5.0V:     +5.12 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
Vcore:     +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +4.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM

After a complete cooldown period (30 mins idling)
[root@localhost ivo]# sensors -c sensors-PCChips
sis5595-isa-0290
Adapter: ISA adapter
+2.5V:     +2.96 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+3.3V:     +3.41 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
+5.0V:     +5.09 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
Vcore:     +2.05 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
in4:       +3.42 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
fan1:        0 RPM  (min =   -1 RPM, div = 2)          ALARM
fan2:        0 RPM  (min =   -1 RPM, div = 2)          ALARM


Is there any way to get information from PCCHIPS, or is it just a waste of 
time to request information from them?

> OK, then it's no surprise that you get no reading, neither in the BIOS
> no in "sensors". You need a 3-wire fan plugged into the motherboard fan
> header to get a speed reading.
They are indeed connected directly, so no wonder it's not showing up. I 
don't have any 3-wire fan available anymore, so I can't test that.

> Well, I crafted the configuration file to make it look good, so it
> doesn't mean much ;)
Is there actually any way to see if it is correct, not involving to use a 
multimeter? I lost mine, so I should buy a new one ;p

> No idea what vendor.ini they're talking about. The computing stuff is
> there to account for different thermal diode types, but as I said
> above, I don't think you have a thermal diode, so no amount of
> computing will give you a temperature value while in4 is in temperature
> mode.
True. However, I suppose their AMI utitly _does_ give temperature 
information to windows, however, this is only a guess. I will look through 
all the CD's I own to find if I didnt' accidently overlookad the CD. Have no 
luck yet. However, I was able to download the app for a different 
motherboard, which has mainly refferences to the LM75 chip... I wonder what 
kind of output it will give. Trying to find a windows 98 installation now ;)


> Good, exactly what I put in the config file :)

Thanks,
Ivo 


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Hans de Goede]

Ivo Manca wrote:
> Hey Jean,
> 
>> Well, I crafted the configuration file to make it look good, so it
>> doesn't mean much ;)
> Is there actually any way to see if it is correct, not involving to use a 
> multimeter? I lost mine, so I should buy a new one ;p
>

You can borrow one from me if you want.

Regards,

Hans




_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Jean Delvare]

Hi Ivo,

On Mon, 11 Jun 2007 18:21:13 +0200, Ivo Manca wrote:
> in4:       +3.55 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 
> after md5sum:
> [root@localhost ivo]# sensors -c sensors-PCChips
> (...)
> in4:       +0.19 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 
> Seems like in4 dropped completely?
> Wait: it seemed like a flatcable dropped on the fan, and stopped it 
> spinning. So I guess +0,19V is suppose to say "Way to hot: you're burning 
> your fingers!"? (Since I actually did burn my finger)
> 
> But one minute after the fan started spinning again...
> (...)
> in4:       +0.00 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 
> And 30 seconds later:
> (...)
> in4:       +4.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
> 
> After a complete cooldown period (30 mins idling)
> (...)
> in4:       +3.42 V  (min =  +0.00 V, max =  +0.00 V)   ALARM

Strange. The value changes, so I was probably right that in4 was
connected to a thermal sensor, but OTOH, the values look odd. The
first two and last values suggest that +3.55 V / +3.42 V corresponds to
the normal running temperature, and +0.19 V means the CPU is very hot,
but the 3rd and 4th values don't really fit in that model. Or maybe it
was just too hot and the sensor got confused for some time, I don't
know.

> Is there any way to get information from PCCHIPS, or is it just a waste of 
> time to request information from them?

If the board is 10-year old, it's probably hopeless, but it depends on
how much you want to get it to work and how much time you are ready to
spend on it.

If you can't get additional information, you can label in4 "CPU Temp",
observe the reading over a period of time, and set arbitrary limits
accordingly. Unfortunately we have no way to tell "sensors" that a
voltage input is actually a temperature value.

> > Well, I crafted the configuration file to make it look good, so it
> > doesn't mean much ;)
>
> Is there actually any way to see if it is correct, not involving to use a 
> multimeter? I lost mine, so I should buy a new one ;p

The other possibilities are asking PCChips, or attempting to
disassemble the BIOS.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Hans de Goede]

Jean Delvare wrote:
> Hi Ivo,
> 
> If you can't get additional information, you can label in4 "CPU Temp",
> observe the reading over a period of time, and set arbitrary limits
> accordingly. Unfortunately we have no way to tell "sensors" that a
> voltage input is actually a temperature value.
> 

Is it possible other motherboards manufacturers have done something similar?
Ifso would it be an idea to add a driver flag to rename all the in4 sysfs attr 
to tempX sysfs attr, without changing the way how things are read?

Regards,

Hans

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Ivo Manca]

Hey Jean,

I got response from PCCHIPS, but no luck that way. They simply said 
something along the line of "We don't provide datasheets to End-users and
you can download the drivers from our website", where they obviously are not 
(The AMI utility, it is).
Pitty, but not that surpising..

I also posted a message on GoT (dutch tweakers forum) and someone pointed me 
to "PCCHips Lottery", which is offline right now, but Internet Archive keeps 
a mirror at:
http://web.archive.org/web/20060114065910/http://www.stud.fernuni-hagen.de/q3998142/pcchips/threads.html
Might be a very usefull link to other people with a PCCHIPS mobo.

According to this post:
http://web.archive.org/web/20041227220452/www.stud.fernuni-hagen.de/q3998142/ubb/Forum3/HTML/001138.html
It seems that the motherboard has two temperature sensors, one for the 
Socket 370, one for the Slot 1. I use the 370.

> The JP7 (I think this is the number, is the one in the middle of the 
> motherboard, with 3 pins) chooses which temp sensor will be measured
> (S370 OR Slot1). At least that's my conclusion after some tests...
> If you put the opposite setting on JP7 your motherboard will measure the 
> sensor that is no on your CPU and you will get a "system
> temperature" like measure.
So that's at least something.
I'll have more time next week, and I'll try to see if I can extract some 
more information about the temperature and sensor-readings.

Ivo

P.s. Hans: Thanks for offering your multimeter, however, I'd rather try it 
without one first :).

----- Original Message ----- 
From: "Jean Delvare" <khali@linux-fr.org>
To: "Ivo Manca" <pinkel@gmail.com>
Cc: <lm-sensors@lm-sensors.org>
Sent: Tuesday 12 June 2007 18:25
Subject: Re: sis5595


> Hi Ivo,
>
> On Mon, 11 Jun 2007 18:21:13 +0200, Ivo Manca wrote:
>> in4:       +3.55 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>
>> after md5sum:
>> [root@localhost ivo]# sensors -c sensors-PCChips
>> (...)
>> in4:       +0.19 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>
>> Seems like in4 dropped completely?
>> Wait: it seemed like a flatcable dropped on the fan, and stopped it
>> spinning. So I guess +0,19V is suppose to say "Way to hot: you're burning
>> your fingers!"? (Since I actually did burn my finger)
>>
>> But one minute after the fan started spinning again...
>> (...)
>> in4:       +0.00 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>
>> And 30 seconds later:
>> (...)
>> in4:       +4.03 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>>
>> After a complete cooldown period (30 mins idling)
>> (...)
>> in4:       +3.42 V  (min =  +0.00 V, max =  +0.00 V)   ALARM
>
> Strange. The value changes, so I was probably right that in4 was
> connected to a thermal sensor, but OTOH, the values look odd. The
> first two and last values suggest that +3.55 V / +3.42 V corresponds to
> the normal running temperature, and +0.19 V means the CPU is very hot,
> but the 3rd and 4th values don't really fit in that model. Or maybe it
> was just too hot and the sensor got confused for some time, I don't
> know.
>
>> Is there any way to get information from PCCHIPS, or is it just a waste
>> of
>> time to request information from them?
>
> If the board is 10-year old, it's probably hopeless, but it depends on
> how much you want to get it to work and how much time you are ready to
> spend on it.
>
> If you can't get additional information, you can label in4 "CPU Temp",
> observe the reading over a period of time, and set arbitrary limits
> accordingly. Unfortunately we have no way to tell "sensors" that a
> voltage input is actually a temperature value.
>
>> > Well, I crafted the configuration file to make it look good, so it
>> > doesn't mean much ;)
>>
>> Is there actually any way to see if it is correct, not involving to use a
>> multimeter? I lost mine, so I should buy a new one ;p
>
> The other possibilities are asking PCChips, or attempting to
> disassemble the BIOS.
>
> -- 
> Jean Delvare 


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] sis5595

[Jean Delvare]

Hans,

On Tue, 12 Jun 2007 19:42:29 +0200, Hans de Goede wrote:
> Jean Delvare wrote:
> > If you can't get additional information, you can label in4 "CPU Temp",
> > observe the reading over a period of time, and set arbitrary limits
> > accordingly. Unfortunately we have no way to tell "sensors" that a
> > voltage input is actually a temperature value.
> 
> Is it possible other motherboards manufacturers have done something similar?

Well, it is possible to do this with virtually any voltage input of all
driver. But maybe this is more likely for the in4 of the sis5595
because it can already be used for temperature monitoring (although in
a technically different way.)

> Ifso would it be an idea to add a driver flag to rename all the in4 sysfs attr 
> to tempX sysfs attr, without changing the way how things are read?

Yes, this could be done, shouldn't be too expensive.

A more generic solution would be to implement this in libsensors. For
that we'd need a new sensors.conf directive to change the type of a
given sensor (from voltage to temp in this case). After all, the only
difference is the unit displayed after the value. There are a few
driver which could use this: pc87360, vt8231... which currently export
voltage value as temp* files for thermistor-based measurements.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors