From: Mauro Molinari <mauromol@tiscali.it>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C
Date: Thu, 27 Dec 2012 11:29:08 +0000 [thread overview]
Message-ID: <50DC3104.3040608@tiscali.it> (raw)
In-Reply-To: <50DB2017.8010403@tiscali.it>
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
next prev parent reply other threads:[~2012-12-27 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 16:04 [lm-sensors] Help to make lm-sensors work with an Asus TUSL2-C Mauro Molinari
2012-12-26 20:11 ` Andrey Repin
2012-12-27 11:29 ` Mauro Molinari [this message]
2013-01-08 13:34 ` Mauro Molinari
2013-01-08 13:50 ` Jean Delvare
2013-01-08 14:54 ` Mauro Molinari
2013-01-08 15:16 ` Mauro Molinari
2013-01-08 15:18 ` Jean Delvare
2013-01-08 15:22 ` Jean Delvare
2013-01-11 18:03 ` Mauro Molinari
2013-01-11 18:59 ` Guenter Roeck
2013-01-11 20:08 ` Mauro Molinari
2013-01-11 20:55 ` Jean Delvare
2013-01-11 22:23 ` Guenter Roeck
2013-01-11 23:11 ` Mauro Molinari
2013-01-12 2:34 ` Guenter Roeck
2013-01-22 8:29 ` Mauro Molinari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50DC3104.3040608@tiscali.it \
--to=mauromol@tiscali.it \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.