[lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Hello to all,
I'm new to lm-sensors.

I'm writing because I need help to configure lm-sensors to work on an 
old Asus TUSL2-C motherboard. I read a lot of documentation on 
lm-sensors website and wiki and I did some searches with Google, however 
I can't understand what I'm doing wrong.

First of all, I'm using a Linux distribution based on Debian Squeeze: 
precisely, it's OpenMediaVault 0.4. "uname -a" shows:
Linux openmediavault 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 
i686 GNU/Linux
and "sensors -v" shows:
sensors version 3.1.2 with libsensors version 3.1.2

I installed lm-sensors with "apt-get install lm-sensors". Then, I 
launched "sensors-detect". The problem is: no sensor is found. The only 
relevant output is given at the end:

---
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801BA ICH2

Sorry, no sensors were detected.
---

So, if I understand it correctly, the i2c-i801 driver is found and 
queried, but no sensors are found there.
I then made some researches on the Internet and found the following 
information.

At:
http://lists.lm-sensors.org/pipermail/lm-sensors/2005-March/011402.html
a user says that lm-sensors works with Asus TUSL2-C. I also found out 
the example configuration file at:
http://www.lm-sensors.org/browser/lm-sensors/trunk/etc/sensors.conf.eg?rev)64
which mentions the TUSL2-C: for it the AS99127F chip should apply.
Then, if I look at:
http://www.lm-sensors.org/wiki/Devices
I actually find that the AS99127F chip is supported by the w83781d 
driver since kernel 2.5.67, however the sensors-detect program shows this:
Probing for `Winbond W83781D' at 0x290...                   No

Further searching brings this:
http://www.lm-sensors.org/ticket/1317
which seems to say that it's a known issue that no sensors are found on 
the TUSL2-C. It also says to see the FAQ, but the FAQ doesn't say 
anything in particular for this motherboard or for that chip.

I then tried the following:
- run "modprobe w83781d", then run "sensors": still "No sensors found"
- created a file named "asus.conf" under /etc/sensors.d (it's not clear 
to me if the custom configuration file in /etc/sensors.d can be named as 
I like, or if I must give it a specific name...) and put in it all the 
contents from sensors.conf.eg related to the AS99127F chip, then run 
"sensors" or even "sensors -c /etc/sensors.d/asus.conf" (do I need to 
specify the config location??): still "No sensors found"

I don't know what else to try! :-(

Thanks in advance,
Mauro.

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Andrey Repin]

Greetings, Mauro Molinari!

> I'm writing because I need help to configure lm-sensors to work on an
> old Asus TUSL2-C motherboard. I read a lot of documentation on 
> lm-sensors website and wiki and I did some searches with Google, however 
> I can't understand what I'm doing wrong.

Have you tried downloading newer sensors-detect script from the website?

> First of all, I'm using a Linux distribution based on Debian Squeeze: 
> precisely, it's OpenMediaVault 0.4. "uname -a" shows:
> Linux openmediavault 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 
> i686 GNU/Linux
> and "sensors -v" shows:
> sensors version 3.1.2 with libsensors version 3.1.2

> I installed lm-sensors with "apt-get install lm-sensors". Then, I 
> launched "sensors-detect". The problem is: no sensor is found. The only 
> relevant output is given at the end:

> ---
> Do you want to probe the I2C/SMBus adapters now? (YES/no):
> Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801BA ICH2

> Sorry, no sensors were detected.
> ---

> So, if I understand it correctly, the i2c-i801 driver is found and 
> queried, but no sensors are found there.
> I then made some researches on the Internet and found the following 
> information.

> At:
> http://lists.lm-sensors.org/pipermail/lm-sensors/2005-March/011402.html
> a user says that lm-sensors works with Asus TUSL2-C. I also found out 
> the example configuration file at:
> http://www.lm-sensors.org/browser/lm-sensors/trunk/etc/sensors.conf.eg?rev)64
> which mentions the TUSL2-C: for it the AS99127F chip should apply.
> Then, if I look at:
> http://www.lm-sensors.org/wiki/Devices
> I actually find that the AS99127F chip is supported by the w83781d 
> driver since kernel 2.5.67, however the sensors-detect program shows this:
> Probing for `Winbond W83781D' at 0x290...                   No

> Further searching brings this:
> http://www.lm-sensors.org/ticket/1317
> which seems to say that it's a known issue that no sensors are found on 
> the TUSL2-C. It also says to see the FAQ, but the FAQ doesn't say 
> anything in particular for this motherboard or for that chip.

> I then tried the following:
> - run "modprobe w83781d", then run "sensors": still "No sensors found"
> - created a file named "asus.conf" under /etc/sensors.d (it's not clear 
> to me if the custom configuration file in /etc/sensors.d can be named as 
> I like, or if I must give it a specific name...) and put in it all the 
> contents from sensors.conf.eg related to the AS99127F chip, then run 
> "sensors" or even "sensors -c /etc/sensors.d/asus.conf" (do I need to 
> specify the config location??): still "No sensors found"

> I don't know what else to try! :-(


--
WBR,
Andrey Repin (hell-for-yahoo@umail.ru) 27.12.2012, <00:11>

Sorry for my terrible english...


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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Il 26/12/2012 21:11, Andrey Repin ha scritto:
>> I'm writing because I need help to configure lm-sensors to work on an
>> old Asus TUSL2-C motherboard. I read a lot of documentation on
>> lm-sensors website and wiki and I did some searches with Google, however
>> I can't understand what I'm doing wrong.
>
> Have you tried downloading newer sensors-detect script from the website?

Hi Andrey, thanks for your help!
I just downloaded the latest version of sensors-detect from here:
http://www.lm-sensors.org/wiki/iwizard/NoSensorsDetected

Some progress is made compared to the version I have in my Linux 
distribution, because the latest script says:

Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0x5953
     (logical device 9 has address 0x290, could be sensors)

However, later it still says:
Probing for `National Semiconductor LM78' 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

And finally again:
Sorry, no sensors were detected.

So, it seems like something is present at 0x290, but nothing lm-sensors 
can detect. The strange thing is that from what I read on the Internet 
(as stated in my previous mail message), my mainboard (Asus TUSL2-C) 
should actually have a AS99127F chip, supported by the w83781d driver.

Please note I have the following warning message at boot:
[   10.092229] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) 
-> IRQ 17
[   10.092243] ACPI: I/O resource 0000:00:1f.3 [0xe800-0xe80f] conflicts 
with ACPI region SM00 [0xe800-0xe806]
[   10.092291] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver

However I did some research on the Internet and found out that this 
should not be a problem and simply means that the native driver is not 
used, because an AHCI interface to the i801 SMBus device is available. 
Actually, the sensors-detect correctly queries that device:
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801BA ICH2
but it still doesn't find any sensor there, however I don't think this 
is in any way related to my problem.

Any suggestion?

Mauro

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Hi to all,
I see that many have come back from the holidays! :-P
Maybe someone has some more suggestions to help me with my case? :-)

Thanks in advance,
Mauro.

P.S.: my last mail follows for convenience.

Il 26/12/2012 21:11, Andrey Repin ha scritto:
>> I'm writing because I need help to configure lm-sensors to work on an
>> old Asus TUSL2-C motherboard. I read a lot of documentation on
>> lm-sensors website and wiki and I did some searches with Google, however
>> I can't understand what I'm doing wrong.
>
> Have you tried downloading newer sensors-detect script from the website?

Hi Andrey, thanks for your help!
I just downloaded the latest version of sensors-detect from here:
http://www.lm-sensors.org/wiki/iwizard/NoSensorsDetected

Some progress is made compared to the version I have in my Linux 
distribution, because the latest script says:

Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found unknown chip with ID 0x5953
     (logical device 9 has address 0x290, could be sensors)

However, later it still says:
Probing for `National Semiconductor LM78' 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

And finally again:
Sorry, no sensors were detected.

So, it seems like something is present at 0x290, but nothing lm-sensors 
can detect. The strange thing is that from what I read on the Internet 
(as stated in my previous mail message), my mainboard (Asus TUSL2-C) 
should actually have a AS99127F chip, supported by the w83781d driver.

Please note I have the following warning message at boot:
[   10.092229] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) 
-> IRQ 17
[   10.092243] ACPI: I/O resource 0000:00:1f.3 [0xe800-0xe80f] conflicts 
with ACPI region SM00 [0xe800-0xe806]
[   10.092291] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver

However I did some research on the Internet and found out that this 
should not be a problem and simply means that the native driver is not 
used, because an AHCI interface to the i801 SMBus device is available. 
Actually, the sensors-detect correctly queries that device:
Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801BA ICH2
but it still doesn't find any sensor there, however I don't think this 
is in any way related to my problem.

Any suggestion?

Mauro

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Jean Delvare]

On Tue, 08 Jan 2013 14:34:55 +0100, Mauro Molinari wrote:
> Some progress is made compared to the version I have in my Linux 
> distribution, because the latest script says:
> 
> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
> Found unknown chip with ID 0x5953
>      (logical device 9 has address 0x290, could be sensors)

Very strange, I wouldn't expected an unknown Super-I/O chip on such an
old board. Can you find the chip's name by visual inspection of the
board or from the documentation?

> However, later it still says:
> Probing for `National Semiconductor LM78' 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
> 
> And finally again:
> Sorry, no sensors were detected.
> 
> So, it seems like something is present at 0x290, but nothing lm-sensors 
> can detect. The strange thing is that from what I read on the Internet 
> (as stated in my previous mail message), my mainboard (Asus TUSL2-C) 
> should actually have a AS99127F chip, supported by the w83781d driver.
> 
> Please note I have the following warning message at boot:
> [   10.092229] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) 
> -> IRQ 17
> [   10.092243] ACPI: I/O resource 0000:00:1f.3 [0xe800-0xe80f] conflicts 
> with ACPI region SM00 [0xe800-0xe806]
> [   10.092291] ACPI: If an ACPI driver is available for this device, you 
> should use it instead of the native driver
> 
> However I did some research on the Internet and found out that this 
> should not be a problem and simply means that the native driver is not 
> used, because an AHCI interface to the i801 SMBus device is available. 
> Actually, the sensors-detect correctly queries that device:
> Using driver `i2c-i801' for device 0000:00:1f.3: Intel 82801BA ICH2
> but it still doesn't find any sensor there, however I don't think this 
> is in any way related to my problem.

The above message means that sensors-detect knows which driver should
be used for the ICH2 SMBus. That doesn't mean the driver did
successfully bind to the device. And if device binding failed (as the
log messages pasted above suggest) then scanning isn't possible.

The AS99127F is an SMBus chip. Please boot with
acpi_enforce_resources=lax and run sensors-detect again, it should find
your AS99127F chip then.

-- 
Jean Delvare

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Hi Jean,
thank you for your help.

Il 08/01/2013 14:50, Jean Delvare ha scritto:
>> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
>> Found unknown chip with ID 0x5953
>>       (logical device 9 has address 0x290, could be sensors)
>
> Very strange, I wouldn't expected an unknown Super-I/O chip on such an
> old board. Can you find the chip's name by visual inspection of the
> board or from the documentation?

The documentation (manual) just speaks about an "Asus ASIC" hardware.
I will visually inspect the mainboard as soon as possible (I can't right 
now).

> The above message means that sensors-detect knows which driver should
> be used for the ICH2 SMBus. That doesn't mean the driver did
> successfully bind to the device. And if device binding failed (as the
> log messages pasted above suggest) then scanning isn't possible.
>
> The AS99127F is an SMBus chip. Please boot with
> acpi_enforce_resources=lax and run sensors-detect again, it should find
> your AS99127F chip then.

Well, strange enough, I added the acpi_enforce_resources=lax to the 
Kernel boot options, as dmesg demonstrates:
[    0.000000] Kernel command line: 
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 
root=UUID=7034614e-0226-481e-99cb-9fe0789f0a57 ro quiet nomodeset 
acpi_enforce_resources=lax

However, the "conflict" message is still displayed:
[   10.478084] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) 
-> IRQ 17
[   10.478099] ACPI: I/O resource 0000:00:1f.3 [0xe800-0xe80f] conflicts 
with ACPI region SM00 [0xe800-0xe806]
[   10.478105] ACPI: This conflict may cause random problems and system 
instability
[   10.478110] ACPI: If an ACPI driver is available for this device, you 
should use it instead of the native driver

Nonetheless, now the sensors-detect script does find something:
Probing for `Asus AS99127F (rev.1)'...                      Success!
     (confidence 8, driver `w83781d', other addresses: 0x48 0x49)
[...]
Driver `w83781d':
   * Bus `SMBus I801 adapter at e800'
     Busdriver `i2c_i801', I2C address 0x2d (and 0x48 0x49)
     Chip `Asus AS99127F (rev.1)' (confidence: 8)

So, first question: am I forced to use the acpi_enforce_resources=lax 
option to use lm_sensors on my system? No other option? (I read this is 
not optimal)

Now, the sensors-detect script downloaded from 
http://www.lm-sensors.org/wiki/iwizard/NoSensorsDetected asks me to 
create /etc/sysconfig/lm_sensors: I reply "YES" and then I try to run 
"sensors", but it says it does not find any sensors. However, it does 
work after I run "modprobe w83781d".

So, second question: what is /etc/sysconfig/lm_sensors for? I do have 
/etc/init.d/lm-sensors in my system (it's a Debian-based distribution) 
but even if I do a "/etc/init.d/lm-sensors restart", I still need to 
"modprobe w83781d" before being able to use "sensors". Maybe there's 
some Debian-specific way to do the same thing (instead of using 
/etc/sysconfig/lm_sensors)?

Finally, among the output of sensors I find:
CPU Temp:     +5.5°C  (high = +100.0°C, hyst = +92.0°C)
which sounds quite funny. I think this has something to do with the 
configuration. I created the file /etc/sensors.d/asus.conf, by copying 
the example configuration file and uncommenting the sections that are 
meant for Asus TUSL2-C. But I'm not sure that this file is taken into 
consideration.

Third question: is this asus.conf taken by sensors? Or do I have to 
specify a command-line parameter to sensors in order to take it? I read 
the documentation on the lm_sensors wiki and the man page, but it's not 
clear to me whether configuration files in /etc/sensors.d should have 
specific names or whether any any name is ok (and configuration files 
are all automatically found and used by sensors command).

Thanks again,
Mauro

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Il 08/01/2013 14:50, Jean Delvare ha scritto:
>> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
>> Found unknown chip with ID 0x5953
>>       (logical device 9 has address 0x290, could be sensors)
>
> Very strange, I wouldn't expected an unknown Super-I/O chip on such an
> old board. Can you find the chip's name by visual inspection of the
> board or from the documentation?

The visual inspection on the board confirmed it has an Asus AS99127F 
chip. I don't think I have any other thermal sensor on the board... I 
just have a Pentium III 1000EB (Coppermine) CPU, an ancient nVidia Riva 
TNT AGP card, a Realtek Gigabit LAN card and two Silicon Image 3512 SATA 
controllers. Any idea on what that Super-I/O chip might be?

Mauro.

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Jean Delvare]

Hi Mauro,

On Tue, 08 Jan 2013 15:54:27 +0100, Mauro Molinari wrote:
> Hi Jean,
> thank you for your help.
> 
> Il 08/01/2013 14:50, Jean Delvare ha scritto:
> >> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
> >> Found unknown chip with ID 0x5953
> >>       (logical device 9 has address 0x290, could be sensors)
> >
> > Very strange, I wouldn't expected an unknown Super-I/O chip on such an
> > old board. Can you find the chip's name by visual inspection of the
> > board or from the documentation?
> 
> The documentation (manual) just speaks about an "Asus ASIC" hardware.
> I will visually inspect the mainboard as soon as possible (I can't right 
> now).

"Asus ASIC" most certainly refers to the AS99127F, which isn't a
Super-I/O chip. I think you'll see another chip on the board when you
get to inspect it.

> 
> > The above message means that sensors-detect knows which driver should
> > be used for the ICH2 SMBus. That doesn't mean the driver did
> > successfully bind to the device. And if device binding failed (as the
> > log messages pasted above suggest) then scanning isn't possible.
> >
> > The AS99127F is an SMBus chip. Please boot with
> > acpi_enforce_resources=lax and run sensors-detect again, it should find
> > your AS99127F chip then.
> 
> Well, strange enough, I added the acpi_enforce_resources=lax to the 
> Kernel boot options, as dmesg demonstrates:
> [    0.000000] Kernel command line: 
> BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 
> root=UUID=7034614e-0226-481e-99cb-9fe0789f0a57 ro quiet nomodeset 
> acpi_enforce_resources=lax
> 
> However, the "conflict" message is still displayed:

Yes, that's what lax does. Pass acpi_enforce_resources=no if you don't
want to see the warning.

> [   10.478084] i801_smbus 0000:00:1f.3: PCI INT B -> GSI 17 (level, low) 
> -> IRQ 17
> [   10.478099] ACPI: I/O resource 0000:00:1f.3 [0xe800-0xe80f] conflicts 
> with ACPI region SM00 [0xe800-0xe806]
> [   10.478105] ACPI: This conflict may cause random problems and system 
> instability
> [   10.478110] ACPI: If an ACPI driver is available for this device, you 
> should use it instead of the native driver
> 
> Nonetheless, now the sensors-detect script does find something:
> Probing for `Asus AS99127F (rev.1)'...                      Success!
>      (confidence 8, driver `w83781d', other addresses: 0x48 0x49)
> [...]
> Driver `w83781d':
>    * Bus `SMBus I801 adapter at e800'
>      Busdriver `i2c_i801', I2C address 0x2d (and 0x48 0x49)
>      Chip `Asus AS99127F (rev.1)' (confidence: 8)
> 
> So, first question: am I forced to use the acpi_enforce_resources=lax 
> option to use lm_sensors on my system? No other option? (I read this is 
> not optimal)

On such an old system, I doubt there is any other solution. I also
don't expect any problem with acpi_enforce_resources=lax or no. After
all, "no" is the behavior the kernel had back then.

> Now, the sensors-detect script downloaded from 
> http://www.lm-sensors.org/wiki/iwizard/NoSensorsDetected asks me to 
> create /etc/sysconfig/lm_sensors: I reply "YES" and then I try to run 
> "sensors", but it says it does not find any sensors. However, it does 
> work after I run "modprobe w83781d".
> 
> So, second question: what is /etc/sysconfig/lm_sensors for? I do have 
> /etc/init.d/lm-sensors in my system (it's a Debian-based distribution) 
> but even if I do a "/etc/init.d/lm-sensors restart", I still need to 
> "modprobe w83781d" before being able to use "sensors". Maybe there's 
> some Debian-specific way to do the same thing (instead of using 
> /etc/sysconfig/lm_sensors)?

Don't use the script you downloaded, use the one provided by Debian
instead, and everything will be fine. The only reason for using the
latest version is for very recent hardware, which isn't your case at
all.

> Finally, among the output of sensors I find:
> CPU Temp:     +5.5°C  (high = +100.0°C, hyst = +92.0°C)
> which sounds quite funny. I think this has something to do with the 
> configuration. I created the file /etc/sensors.d/asus.conf, by copying 
> the example configuration file and uncommenting the sections that are 
> meant for Asus TUSL2-C. But I'm not sure that this file is taken into 
> consideration.
>
> Third question: is this asus.conf taken by sensors? Or do I have to 
> specify a command-line parameter to sensors in order to take it? I read 

It should be taken into consideration, yes. If you don't see any
effect, this may mean that you got the "chip" line wrong so the whole
section is ignored for your chip.

> the documentation on the lm_sensors wiki and the man page, but it's not 
> clear to me whether configuration files in /etc/sensors.d should have 
> specific names or whether any any name is ok (and configuration files 
> are all automatically found and used by sensors command).

Any name is OK (for now.)

-- 
Jean Delvare

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Jean Delvare]

On Tue, 08 Jan 2013 16:16:12 +0100, Mauro Molinari wrote:
> Il 08/01/2013 14:50, Jean Delvare ha scritto:
> > Very strange, I wouldn't expected an unknown Super-I/O chip on such an
> > old board. Can you find the chip's name by visual inspection of the
> > board or from the documentation?
> 
> The visual inspection on the board confirmed it has an Asus AS99127F 
> chip. I don't think I have any other thermal sensor on the board... I 
> just have a Pentium III 1000EB (Coppermine) CPU, an ancient nVidia Riva 
> TNT AGP card, a Realtek Gigabit LAN card and two Silicon Image 3512 SATA 
> controllers. Any idea on what that Super-I/O chip might be?

It should be a chip of about the same size as the Asus chip, with
"Winbond" written on it. Probably close to the last PCI slot.

-- 
Jean Delvare

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Il 08/01/2013 14:50, Jean Delvare ha scritto:
>> Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
>> Found unknown chip with ID 0x5953
>>       (logical device 9 has address 0x290, could be sensors)
>
> Very strange, I wouldn't expected an unknown Super-I/O chip on such an
> old board. Can you find the chip's name by visual inspection of the
> board or from the documentation?

Hi Jean!
I looked at the mainboard again as you suggested. The Super I/O chip is 
a Winbond W83627GF-AW.

In fact, I don't see it in the device support list at lm-sensors.org.
Are you interested in more information on this?

-- 

Mauro Molinari
E-mail: mauromol@tiscali.it
ICQ UIN: 10379016
Digital Things Home Space: http://digitalthings.cjb.net
Il Sito più Banale: http://www.poesiamasini.it

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Guenter Roeck]

On Fri, Jan 11, 2013 at 07:03:39PM +0100, Mauro Molinari wrote:
> Il 08/01/2013 14:50, Jean Delvare ha scritto:
> >>Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
> >>Found unknown chip with ID 0x5953
> >>      (logical device 9 has address 0x290, could be sensors)
> >
> >Very strange, I wouldn't expected an unknown Super-I/O chip on such an
> >old board. Can you find the chip's name by visual inspection of the
> >board or from the documentation?
> 
> Hi Jean!
> I looked at the mainboard again as you suggested. The Super I/O chip
> is a Winbond W83627GF-AW.
> 
I think that may be W83627SF, not GF. Datasheet is on the web.
If so, it does not support hardware monitoring.

From superiotool source:

	{0x595, "W83627SF", {   /* TODO: Not yet in sensors-detect */

I guess that explains why sensors-detect doesn't recognize it.

Guenter

> In fact, I don't see it in the device support list at lm-sensors.org.
> Are you interested in more information on this?
> 
> -- 
> 
> Mauro Molinari
> E-mail: mauromol@tiscali.it
> ICQ UIN: 10379016
> Digital Things Home Space: http://digitalthings.cjb.net
> Il Sito più Banale: http://www.poesiamasini.it
> 
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> 

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Il 11/01/2013 19:59, Guenter Roeck ha scritto:
>> Hi Jean!
>> I looked at the mainboard again as you suggested. The Super I/O chip
>> is a Winbond W83627GF-AW.
>>
> I think that may be W83627SF, not GF. Datasheet is on the web.
> If so, it does not support hardware monitoring.

Well, maybe the serigraphy on the chip is wrong, but it actually says 
GF. I double checked it once again. If you search with Google, you'll 
find some retailers that sell it.

Here is the datasheet for the W83627G-AW (without the "F" - I don't know 
if it may apply or not):
http://pdf1.alldatasheet.com/datasheet-pdf/view/203870/WINBOND/W83627G-AW.html

Mauro.

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Jean Delvare]

On Fri, 11 Jan 2013 10:59:30 -0800, Guenter Roeck wrote:
> On Fri, Jan 11, 2013 at 07:03:39PM +0100, Mauro Molinari wrote:
> > Il 08/01/2013 14:50, Jean Delvare ha scritto:
> > >>Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
> > >>Found unknown chip with ID 0x5953
> > >>      (logical device 9 has address 0x290, could be sensors)
> > >
> > >Very strange, I wouldn't expected an unknown Super-I/O chip on such an
> > >old board. Can you find the chip's name by visual inspection of the
> > >board or from the documentation?
> > 
> > Hi Jean!
> > I looked at the mainboard again as you suggested. The Super I/O chip
> > is a Winbond W83627GF-AW.
> > 
> I think that may be W83627SF, not GF. Datasheet is on the web.
> If so, it does not support hardware monitoring.
> 
> From superiotool source:
> 
> 	{0x595, "W83627SF", {   /* TODO: Not yet in sensors-detect */
> 
> I guess that explains why sensors-detect doesn't recognize it.

The W83627GF seems to exist as well and it is entirely possible that
both have the same ID. The lack of "H" in the names indicates the lack
of hardware monitoring function in these chips.

I have added detection to sensors-detect. Even if the chip has no
hardware monitoring features, identifying it is good, as it clarifies
the situation.

Mauro, feel free to try:
http://dl.lm-sensors.org/lm-sensors/files/sensors-detect

It should now detect your Super-I/O chip. But the change is informative
only, it won't change the driver list for your board.

-- 
Jean Delvare

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Guenter Roeck]

On Fri, Jan 11, 2013 at 09:08:03PM +0100, Mauro Molinari wrote:
> Il 11/01/2013 19:59, Guenter Roeck ha scritto:
> >>Hi Jean!
> >>I looked at the mainboard again as you suggested. The Super I/O chip
> >>is a Winbond W83627GF-AW.
> >>
> >I think that may be W83627SF, not GF. Datasheet is on the web.
> >If so, it does not support hardware monitoring.
> 
> Well, maybe the serigraphy on the chip is wrong, but it actually
> says GF. I double checked it once again. If you search with Google,
> you'll find some retailers that sell it.
> 
> Here is the datasheet for the W83627G-AW (without the "F" - I don't
> know if it may apply or not):
> http://pdf1.alldatasheet.com/datasheet-pdf/view/203870/WINBOND/W83627G-AW.html
> 
That points to the W83627HF/HG datasheet.

Guenter

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Il 11/01/2013 23:23, Guenter Roeck ha scritto:
>> Here is the datasheet for the W83627G-AW (without the "F" - I don't
>> know if it may apply or not):
>> http://pdf1.alldatasheet.com/datasheet-pdf/view/203870/WINBOND/W83627G-AW.html
>>
> That points to the W83627HF/HG datasheet.

Hi Guenter,
actually the first page of the PDF says: W83627HF/F/HG/G
So, it also applies to W83627G, as I said.

Mauro

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Guenter Roeck]

On Sat, Jan 12, 2013 at 12:11:10AM +0100, Mauro Molinari wrote:
> Il 11/01/2013 23:23, Guenter Roeck ha scritto:
> >>Here is the datasheet for the W83627G-AW (without the "F" - I don't
> >>know if it may apply or not):
> >>http://pdf1.alldatasheet.com/datasheet-pdf/view/203870/WINBOND/W83627G-AW.html
> >>
> >That points to the W83627HF/HG datasheet.
> 
> Hi Guenter,
> actually the first page of the PDF says: W83627HF/F/HG/G
> So, it also applies to W83627G, as I said.
> 
Yes, but not really. The device id in that datasheet is different.

Guenter

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

Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C

[Mauro Molinari]

Il 11/01/2013 21:55, Jean Delvare ha scritto:
> The W83627GF seems to exist as well and it is entirely possible that
> both have the same ID. The lack of "H" in the names indicates the lack
> of hardware monitoring function in these chips.
>
> I have added detection to sensors-detect. Even if the chip has no
> hardware monitoring features, identifying it is good, as it clarifies
> the situation.
>
> Mauro, feel free to try:
> http://dl.lm-sensors.org/lm-sensors/files/sensors-detect
>
> It should now detect your Super-I/O chip. But the change is informative
> only, it won't change the driver list for your board.

Hi Jean,
I confirm the detection works with the updated sensors-detect:

Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Winbond W83627SF/GF Super IO'
     (no hardware monitoring capabilities)

Thanks again for your support on this issue.

Mauro.

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