* [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3
@ 2010-04-16 23:36 Marc
2010-04-17 0:01 ` Jeff Rickman
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Marc @ 2010-04-16 23:36 UTC (permalink / raw)
To: lm-sensors
Hi...
Runnig Rehat Fedora Core 12 with an Asus k8n-dre motherboard. It has a NVIDE nFORCE Professional 2200 Chip as well as a Winbond W83627THF-A super i/o chip. The linux kernel is kernel-2.6.32.11-99.fc12.x86_64. Using lm_sensors-3.1.1-3.fc12.x86_64
When I run sensors-detect I get the following
Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): y
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... Success!
(driver `k8temp')
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
Intel Core family thermal sensor... No
Intel Atom thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No
Some Super I/O chips contain embedded 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):
Some Super I/O chips contain embedded 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): y
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
Found `Winbond W83627THF/THG Super IO Sensors'
(but not activated)
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Everything else returns a no until...
Next adapter: SMBus nForce2 adapter at 4c40 (i2c-0)
Do you want to scan it? (YES/no/selectively):
Nothing in the summary about it.
The k8temp works fine. I get temperatures.
k8temp-pci-00c3
Adapter: PCI adapter
Core0 Temp: +35.0°C
Core1 Temp: +36.0°C
k8temp-pci-00cb
Adapter: PCI adapter
Core0 Temp: +36.0°C
Core1 Temp: +37.0°C
But no fan speeds or anything else because when I attempt to load the w83627hf modules I get the following:
FATAL: Error inserting w83627hf (/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627hf.ko): No such device
Here is the lsmod
Module Size Used by
fuse 57189 2
hwmon_vid 2091 0
eeprom 4947 0
i2c_dev 7529 0
sunrpc 193819 1
cpufreq_ondemand 8793 2
powernow_k8 14706 2
freq_table 3947 2 cpufreq_ondemand,powernow_k8
ip6t_REJECT 4222 10
nf_conntrack_ipv6 18504 7
ip6table_filter 2791 1
ip6_tables 16760 1 ip6table_filter
ipv6 279463 32 ip6t_REJECT,nf_conntrack_ipv6
uinput 7228 0
amd64_edac_mod 15481 0
tg3 101698 0
i2c_nforce2 6819 0
i2c_core 26876 3 eeprom,i2c_dev,i2c_nforce2
edac_core 39581 4 amd64_edac_mod
edac_mce_amd 7746 1 amd64_edac_mod
k8temp 3735 0
raid1 19043 2
dm_multipath 14558 0
ata_generic 3467 0
pata_acpi 3395 0
floppy 54666 0
pata_amd 11269 4
sata_nv 20834 3
When I load the w83627ehf I get:
FATAL: Error inserting w83627ehf (/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627ehf.ko): No such device
When I try the w83781d it loads lsmod shows the following:
Module Size Used by
w83781d 28749 0
fuse 57189 2
hwmon_vid 2091 1 w83781d
eeprom 4947 0
i2c_dev 7529 0
sunrpc 193819 1
cpufreq_ondemand 8793 2
powernow_k8 14706 2
freq_table 3947 2 cpufreq_ondemand,powernow_k8
ip6t_REJECT 4222 10
nf_conntrack_ipv6 18504 7
ip6table_filter 2791 1
ip6_tables 16760 1 ip6table_filter
ipv6 279463 32 ip6t_REJECT,nf_conntrack_ipv6
uinput 7228 0
amd64_edac_mod 15481 0
tg3 101698 0
i2c_nforce2 6819 0
i2c_core 26876 4 w83781d,eeprom,i2c_dev,i2c_nforce2
edac_core 39581 4 amd64_edac_mod
edac_mce_amd 7746 1 amd64_edac_mod
k8temp 3735 0
raid1 19043 2
dm_multipath 14558 0
ata_generic 3467 0
pata_acpi 3395 0
floppy 54666 0
pata_amd 11269 4
sata_nv 20834 3
Running sensor-detect again produces original results and nothing is loaded into the /etc/sysconfig/lm_sensors, So starting lm_sensors gives me a warning telling me its not configured.
Same result as directly above when I load the w83791d drive, hav\ing removed the other, including the w83792d, w83793, w83l785ts, w83l786ng, wm831x-hwmon and wm8350-hwmon. The lsmod stays the same as above except that the driver is relplace at the same position with the new driver.
Tried various combinations and permutations and nothing.
Any help would appreciated, and apologizes if it has already been dealt with.
Regards and thanks...
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3
2010-04-16 23:36 [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3 Marc
@ 2010-04-17 0:01 ` Jeff Rickman
2010-04-28 11:41 ` Jean Delvare
2010-05-05 2:48 ` Marc
2 siblings, 0 replies; 7+ messages in thread
From: Jeff Rickman @ 2010-04-17 0:01 UTC (permalink / raw)
To: lm-sensors
> Hi...
>
> Runnig Rehat Fedora Core 12 with an Asus k8n-dre motherboard. It has a
> NVIDE nFORCE Professional 2200 Chip as well as a Winbond W83627THF-A super
> i/o chip. The linux kernel is kernel-2.6.32.11-99.fc12.x86_64. Using
> lm_sensors-3.1.1-3.fc12.x86_64
>
> When I run sensors-detect I get the following
>
> Some south bridges, CPUs or memory controllers contain embedded sensors.
> Do you want to scan for them? This is totally safe. (YES/no): y
> Silicon Integrated Systems SIS5595... No
> VIA VT82C686 Integrated Sensors... No
> VIA VT8231 Integrated Sensors... No
> AMD K8 thermal sensors... Success!
> (driver `k8temp')
> AMD Family 10h thermal sensors... No
> AMD Family 11h thermal sensors... No
> Intel Core family thermal sensor... No
> Intel Atom thermal sensor... No
> Intel AMB FB-DIMM thermal sensor... No
> VIA C7 thermal sensor... No
> VIA Nano thermal sensor... No
>
> Some Super I/O chips contain embedded 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):
>
> Some Super I/O chips contain embedded 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): y
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
> Found `Winbond W83627THF/THG Super IO Sensors'
> (but not activated)
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
> Trying family `ITE'... No
>
> Everything else returns a no until...
>
> Next adapter: SMBus nForce2 adapter at 4c40 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
>
> Nothing in the summary about it.
>
> The k8temp works fine. I get temperatures.
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp: +35.0°C
> Core1 Temp: +36.0°C
>
> k8temp-pci-00cb
> Adapter: PCI adapter
> Core0 Temp: +36.0°C
> Core1 Temp: +37.0°C
>
> But no fan speeds or anything else because when I attempt to load the
> w83627hf modules I get the following:
>
> FATAL: Error inserting w83627hf
> (/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627hf.ko):
> No such device
>
> Here is the lsmod
>
> Module Size Used by
> fuse 57189 2
> hwmon_vid 2091 0
> eeprom 4947 0
> i2c_dev 7529 0
> sunrpc 193819 1
> cpufreq_ondemand 8793 2
> powernow_k8 14706 2
> freq_table 3947 2 cpufreq_ondemand,powernow_k8
> ip6t_REJECT 4222 10
> nf_conntrack_ipv6 18504 7
> ip6table_filter 2791 1
> ip6_tables 16760 1 ip6table_filter
> ipv6 279463 32 ip6t_REJECT,nf_conntrack_ipv6
> uinput 7228 0
> amd64_edac_mod 15481 0
> tg3 101698 0
> i2c_nforce2 6819 0
> i2c_core 26876 3 eeprom,i2c_dev,i2c_nforce2
> edac_core 39581 4 amd64_edac_mod
> edac_mce_amd 7746 1 amd64_edac_mod
> k8temp 3735 0
> raid1 19043 2
> dm_multipath 14558 0
> ata_generic 3467 0
> pata_acpi 3395 0
> floppy 54666 0
> pata_amd 11269 4
> sata_nv 20834 3
>
> When I load the w83627ehf I get:
> FATAL: Error inserting w83627ehf
> (/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627ehf.ko):
> No such device
>
> When I try the w83781d it loads lsmod shows the following:
> Module Size Used by
> w83781d 28749 0
> fuse 57189 2
> hwmon_vid 2091 1 w83781d
> eeprom 4947 0
> i2c_dev 7529 0
> sunrpc 193819 1
> cpufreq_ondemand 8793 2
> powernow_k8 14706 2
> freq_table 3947 2 cpufreq_ondemand,powernow_k8
> ip6t_REJECT 4222 10
> nf_conntrack_ipv6 18504 7
> ip6table_filter 2791 1
> ip6_tables 16760 1 ip6table_filter
> ipv6 279463 32 ip6t_REJECT,nf_conntrack_ipv6
> uinput 7228 0
> amd64_edac_mod 15481 0
> tg3 101698 0
> i2c_nforce2 6819 0
> i2c_core 26876 4 w83781d,eeprom,i2c_dev,i2c_nforce2
> edac_core 39581 4 amd64_edac_mod
> edac_mce_amd 7746 1 amd64_edac_mod
> k8temp 3735 0
> raid1 19043 2
> dm_multipath 14558 0
> ata_generic 3467 0
> pata_acpi 3395 0
> floppy 54666 0
> pata_amd 11269 4
> sata_nv 20834 3
>
> Running sensor-detect again produces original results and nothing is
> loaded into the /etc/sysconfig/lm_sensors, So starting lm_sensors gives me
> a warning telling me its not configured.
>
> Same result as directly above when I load the w83791d drive, hav\ing
> removed the other, including the w83792d, w83793, w83l785ts, w83l786ng,
> wm831x-hwmon and wm8350-hwmon. The lsmod stays the same as above except
> that the driver is relplace at the same position with the new driver.
>
> Tried various combinations and permutations and nothing.
>
> Any help would appreciated, and apologizes if it has already been dealt
> with.
>
> Regards and thanks...
>
>_______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>
Looking at my "stock" FC12 boxes I see:
# ls /lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83*
/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627ehf.ko
/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627hf.ko
/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83781d.ko
/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83791d.ko
/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83792d.ko
/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83793.ko
/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83l785ts.ko
/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83l786ng.ko
What modules does "sensors-detect" say it is trying to load? The actual
output is important.
What is the output of "/var/log/messages" after the module loading errors
occur? That info could be valuable.
Perhaps the SuperIO chip is actually being detected but there is no kernel
module support for it? Others more wise than me will know that answer.
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3
2010-04-16 23:36 [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3 Marc
2010-04-17 0:01 ` Jeff Rickman
@ 2010-04-28 11:41 ` Jean Delvare
2010-05-05 2:48 ` Marc
2 siblings, 0 replies; 7+ messages in thread
From: Jean Delvare @ 2010-04-28 11:41 UTC (permalink / raw)
To: lm-sensors
Hi Marc,
On Fri, 16 Apr 2010 16:36:34 -0700 (PDT), Marc wrote:
> Hi...
>
> Runnig Rehat Fedora Core 12 with an Asus k8n-dre motherboard. It has a NVIDE nFORCE Professional 2200 Chip as well as a Winbond W83627THF-A super i/o chip. The linux kernel is kernel-2.6.32.11-99.fc12.x86_64. Using lm_sensors-3.1.1-3.fc12.x86_64
>
> When I run sensors-detect I get the following
>
> Some south bridges, CPUs or memory controllers contain embedded sensors.
> Do you want to scan for them? This is totally safe. (YES/no): y
> Silicon Integrated Systems SIS5595... No
> VIA VT82C686 Integrated Sensors... No
> VIA VT8231 Integrated Sensors... No
> AMD K8 thermal sensors... Success!
> (driver `k8temp')
> AMD Family 10h thermal sensors... No
> AMD Family 11h thermal sensors... No
> Intel Core family thermal sensor... No
> Intel Atom thermal sensor... No
> Intel AMB FB-DIMM thermal sensor... No
> VIA C7 thermal sensor... No
> VIA Nano thermal sensor... No
>
> Some Super I/O chips contain embedded 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):
>
> Some Super I/O chips contain embedded 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): y
> Probing for Super-I/O at 0x2e/0x2f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
> Found `Winbond W83627THF/THG Super IO Sensors'
> (but not activated)
This typically means that the vendor decided to not use the embedded
hardware monitoring features of the Super I/O chip, either because they
aren't interested in monitoring at all, or because they have included a
dedicated monitoring chip on the board. You can tell between these two
cases by looking for monitoring in the BIOS setup screen.
> Probing for Super-I/O at 0x4e/0x4f
> Trying family `National Semiconductor'... No
> Trying family `SMSC'... No
> Trying family `VIA/Winbond/Nuvoton/Fintek'... No
> Trying family `ITE'... No
>
> Everything else returns a no until...
>
> Next adapter: SMBus nForce2 adapter at 4c40 (i2c-0)
> Do you want to scan it? (YES/no/selectively):
Note that the nForce2 and later have 2 SMBus channels, and apparently
sensors-detect found only one. This could mean that ACPI requested the
other one. Please search for kernel log messages as the i2c-nforce2
driver is being loaded.
>
> Nothing in the summary about it.
>
> The k8temp works fine. I get temperatures.
> k8temp-pci-00c3
> Adapter: PCI adapter
> Core0 Temp: +35.0째C
> Core1 Temp: +36.0째C
>
> k8temp-pci-00cb
> Adapter: PCI adapter
> Core0 Temp: +36.0째C
> Core1 Temp: +37.0째C
>
> But no fan speeds or anything else because when I attempt to load the w83627hf modules I get the following:
>
> FATAL: Error inserting w83627hf (/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627hf.ko): No such device
This is expected if the device is disabled.
>
> Here is the lsmod
>
> Module Size Used by
> fuse 57189 2
> hwmon_vid 2091 0
> eeprom 4947 0
> i2c_dev 7529 0
> sunrpc 193819 1
> cpufreq_ondemand 8793 2
> powernow_k8 14706 2
> freq_table 3947 2 cpufreq_ondemand,powernow_k8
> ip6t_REJECT 4222 10
> nf_conntrack_ipv6 18504 7
> ip6table_filter 2791 1
> ip6_tables 16760 1 ip6table_filter
> ipv6 279463 32 ip6t_REJECT,nf_conntrack_ipv6
> uinput 7228 0
> amd64_edac_mod 15481 0
> tg3 101698 0
> i2c_nforce2 6819 0
> i2c_core 26876 3 eeprom,i2c_dev,i2c_nforce2
> edac_core 39581 4 amd64_edac_mod
> edac_mce_amd 7746 1 amd64_edac_mod
> k8temp 3735 0
> raid1 19043 2
> dm_multipath 14558 0
> ata_generic 3467 0
> pata_acpi 3395 0
> floppy 54666 0
> pata_amd 11269 4
> sata_nv 20834 3
>
> When I load the w83627ehf I get:
> FATAL: Error inserting w83627ehf (/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627ehf.ko): No such device
This is a different driver, for a device you don't have, so it wasn't
expected to load.
>
> When I try the w83781d it loads lsmod shows the following:
> Module Size Used by
> w83781d 28749 0
> fuse 57189 2
> hwmon_vid 2091 1 w83781d
> eeprom 4947 0
> i2c_dev 7529 0
> sunrpc 193819 1
> cpufreq_ondemand 8793 2
> powernow_k8 14706 2
> freq_table 3947 2 cpufreq_ondemand,powernow_k8
> ip6t_REJECT 4222 10
> nf_conntrack_ipv6 18504 7
> ip6table_filter 2791 1
> ip6_tables 16760 1 ip6table_filter
> ipv6 279463 32 ip6t_REJECT,nf_conntrack_ipv6
> uinput 7228 0
> amd64_edac_mod 15481 0
> tg3 101698 0
> i2c_nforce2 6819 0
> i2c_core 26876 4 w83781d,eeprom,i2c_dev,i2c_nforce2
> edac_core 39581 4 amd64_edac_mod
> edac_mce_amd 7746 1 amd64_edac_mod
> k8temp 3735 0
> raid1 19043 2
> dm_multipath 14558 0
> ata_generic 3467 0
> pata_acpi 3395 0
> floppy 54666 0
> pata_amd 11269 4
> sata_nv 20834 3
The w83781d driver is an hybrid driver supporting both ISA and I2C
devices. For this reason is always loads, even when no supported device
was found. This driver is for old systems, it won't help you.
>
> Running sensor-detect again produces original results and nothing is loaded into the /etc/sysconfig/lm_sensors, So starting lm_sensors gives me a warning telling me its not configured.
You should at least get the k8temp driver.
>
> Same result as directly above when I load the w83791d drive, hav\ing removed the other, including the w83792d, w83793, w83l785ts, w83l786ng, wm831x-hwmon and wm8350-hwmon. The lsmod stays the same as above except that the driver is relplace at the same position with the new driver.
Loading random drivers is not recommended.
>
> Tried various combinations and permutations and nothing.
>
> Any help would appreciated, and apologizes if it has already been dealt with.
On a recent Asus desktop board, I suspect that you have to use the
asus_atk0110 driver for (ACPI-based) monitoring. It is even supposed to
load automatically.
Please search your kernel logs for the exact errors when loading the
i2c-nforce2 and w83627hf drivers (you can unload them and reload them
to trigger the messages again.)
Please also look for messages about resource conflicts between ACPI and
native drivers, such as:
ACPI: I/O resource nForce2_smbus [0x700-0x73f] conflicts with ACPI region SM00 [0x700-0x73f]
ACPI: Device needs an ACPI driver
Please also try loading the asus_atk0110 driver manually, and see what
happens. Report the messages from the kernel logs if there are any.
--
Jean Delvare
http://khali.linux-fr.org/wishlist.html
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3
@ 2010-04-28 12:24 Luca Tettamanti
2010-05-06 19:23 ` Luca Tettamanti
2010-05-07 8:07 ` Luca Tettamanti
0 siblings, 2 replies; 7+ messages in thread
From: Luca Tettamanti @ 2010-04-28 12:24 UTC (permalink / raw)
To: lm-sensors
On Wed, Apr 28, 2010 at 1:41 PM, Jean Delvare <khali@linux-fr.org> wrote:
>> Runnig Rehat Fedora Core 12 with an Asus k8n-dre motherboard.
[...]
> On a recent Asus desktop board, I suspect that you have to use the
> asus_atk0110 driver for (ACPI-based) monitoring. It is even supposed to
> load automatically.
[...]
> Please also try loading the asus_atk0110 driver manually, and see what
> happens. Report the messages from the kernel logs if there are any.
It it doesn't work please send me a copy of the DSDT and if possible
enable HWMON_DEBUG_CHIP.
Luca
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3
2010-04-16 23:36 [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3 Marc
2010-04-17 0:01 ` Jeff Rickman
2010-04-28 11:41 ` Jean Delvare
@ 2010-05-05 2:48 ` Marc
2 siblings, 0 replies; 7+ messages in thread
From: Marc @ 2010-05-05 2:48 UTC (permalink / raw)
To: lm-sensors
Thanks for the advice Jeff... But it didn't work. I updated all the software, including a new sensors_detect and such and still the exact same results as I described. retried various things and no luck at all!
Can any one else provide some guidance on this, as to what if anything can be done to get lm_sensor to work.
Thanks in advance for any and all assistance.
Regards,
Marc
--- On Fri, 4/16/10, Jeff Rickman <jrickman@myamigos.us> wrote:
> From: Jeff Rickman <jrickman@myamigos.us>
> Subject: Re: [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3
> To: "Marc" <digitelp@yahoo.com>
> Date: Friday, April 16, 2010, 8:15 PM
>
> > Hi...
> >
> > Runnig Rehat Fedora Core 12 with an Asus k8n-dre
> motherboard. It has a
> > NVIDE nFORCE Professional 2200 Chip as well as a
> Winbond W83627THF-A super
> > i/o chip. The linux kernel is
> kernel-2.6.32.11-99.fc12.x86_64. Using
> > lm_sensors-3.1.1-3.fc12.x86_64
> >
> > When I run sensors-detect I get the following
> >
> > Some south bridges, CPUs or memory controllers contain
> embedded sensors.
> > Do you want to scan for them? This is totally safe.
> (YES/no): y
> > Silicon Integrated Systems SIS5595...
>
> No
> > VIA VT82C686 Integrated Sensors...
>
> No
> > VIA VT8231 Integrated Sensors...
>
> No
> > AMD K8 thermal sensors...
>
> Success!
> > (driver `k8temp')
> > AMD Family 10h thermal sensors...
>
> No
> > AMD Family 11h thermal sensors...
>
> No
> > Intel Core family thermal sensor...
>
> No
> > Intel Atom thermal sensor...
>
> No
> > Intel AMB FB-DIMM thermal sensor...
>
> No
> > VIA C7 thermal sensor...
>
> No
> > VIA Nano thermal sensor...
>
> No
> >
> > Some Super I/O chips contain embedded 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):
> >
> > Some Super I/O chips contain embedded 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):
> y
> > Probing for Super-I/O at 0x2e/0x2f
> > Trying family `National Semiconductor'...
>
> No
> > Trying family `SMSC'...
>
> No
> > Trying family `VIA/Winbond/Nuvoton/Fintek'...
> Yes
> > Found `Winbond W83627THF/THG Super IO Sensors'
> > (but not activated)
> > Probing for Super-I/O at 0x4e/0x4f
> > Trying family `National Semiconductor'...
>
> No
> > Trying family `SMSC'...
>
> No
> > Trying family `VIA/Winbond/Nuvoton/Fintek'...
> No
> > Trying family `ITE'...
>
> No
> >
> > Everything else returns a no until...
> >
> > Next adapter: SMBus nForce2 adapter at 4c40 (i2c-0)
> > Do you want to scan it? (YES/no/selectively):
> >
> > Nothing in the summary about it.
> >
> > The k8temp works fine. I get temperatures.
> > k8temp-pci-00c3
> > Adapter: PCI adapter
> > Core0 Temp: +35.0°C
> > Core1 Temp: +36.0°C
> >
> > k8temp-pci-00cb
> > Adapter: PCI adapter
> > Core0 Temp: +36.0°C
> > Core1 Temp: +37.0°C
> >
> > But no fan speeds or anything else because when I
> attempt to load the
> > w83627hf modules I get the following:
> >
> > FATAL: Error inserting w83627hf
> >
> (/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627hf.ko):
> > No such device
> >
> > Here is the lsmod
> >
> > Module
> Size Used by
> > fuse
> 57189 2
> > hwmon_vid
> 2091 0
> > eeprom
> 4947 0
> > i2c_dev
> 7529 0
> > sunrpc
> 193819 1
> > cpufreq_ondemand 8793
> 2
> > powernow_k8
> 14706 2
> > freq_table
> 3947 2 cpufreq_ondemand,powernow_k8
> > ip6t_REJECT
> 4222 10
> > nf_conntrack_ipv6 18504 7
> > ip6table_filter
> 2791 1
> > ip6_tables
> 16760 1 ip6table_filter
> > ipv6
> 279463 32 ip6t_REJECT,nf_conntrack_ipv6
> > uinput
> 7228 0
> > amd64_edac_mod
> 15481 0
> > tg3
> 101698 0
> > i2c_nforce2
> 6819 0
> > i2c_core
> 26876 3 eeprom,i2c_dev,i2c_nforce2
> > edac_core
> 39581 4 amd64_edac_mod
> > edac_mce_amd
> 7746 1 amd64_edac_mod
> > k8temp
> 3735 0
> > raid1
> 19043 2
> > dm_multipath
> 14558 0
> > ata_generic
> 3467 0
> > pata_acpi
> 3395 0
> > floppy
> 54666 0
> > pata_amd
> 11269 4
> > sata_nv
> 20834 3
> >
> > When I load the w83627ehf I get:
> > FATAL: Error inserting w83627ehf
> >
> (/lib/modules/2.6.32.11-99.fc12.x86_64/kernel/drivers/hwmon/w83627ehf.ko):
> > No such device
> >
> > When I try the w83781d it loads lsmod shows the
> following:
> > Module
> Size Used by
> > w83781d
> 28749 0
> > fuse
> 57189 2
> > hwmon_vid
> 2091 1 w83781d
> > eeprom
> 4947 0
> > i2c_dev
> 7529 0
> > sunrpc
> 193819 1
> > cpufreq_ondemand 8793
> 2
> > powernow_k8
> 14706 2
> > freq_table
> 3947 2 cpufreq_ondemand,powernow_k8
> > ip6t_REJECT
> 4222 10
> > nf_conntrack_ipv6 18504 7
> > ip6table_filter
> 2791 1
> > ip6_tables
> 16760 1 ip6table_filter
> > ipv6
> 279463 32 ip6t_REJECT,nf_conntrack_ipv6
> > uinput
> 7228 0
> > amd64_edac_mod
> 15481 0
> > tg3
> 101698 0
> > i2c_nforce2
> 6819 0
> > i2c_core
> 26876 4
> w83781d,eeprom,i2c_dev,i2c_nforce2
> > edac_core
> 39581 4 amd64_edac_mod
> > edac_mce_amd
> 7746 1 amd64_edac_mod
> > k8temp
> 3735 0
> > raid1
> 19043 2
> > dm_multipath
> 14558 0
> > ata_generic
> 3467 0
> > pata_acpi
> 3395 0
> > floppy
> 54666 0
> > pata_amd
> 11269 4
> > sata_nv
> 20834 3
> >
> > Running sensor-detect again produces original results
> and nothing is
> > loaded into the /etc/sysconfig/lm_sensors, So starting
> lm_sensors gives me
> > a warning telling me its not configured.
> >
> > Same result as directly above when I load the w83791d
> drive, hav\ing
> > removed the other, including the w83792d, w83793,
> w83l785ts, w83l786ng,
> > wm831x-hwmon and wm8350-hwmon. The lsmod stays the
> same as above except
> > that the driver is relplace at the same position with
> the new driver.
> >
> > Tried various combinations and permutations and
> nothing.
> >
> > Any help would appreciated, and apologizes if it has
> already been dealt
> > with.
> >
> > Regards and thanks...
> >
> >
> > _______________________________________________
> > lm-sensors mailing list
> > lm-sensors@lm-sensors.org
> > http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
> >
>
> You may need to update your version of LM_Sensors...
>
> Here is what I have on my FC12 x86_64 box running
> 2.6.32.11-99.fc12.x86_64:
>
> lm_sensors.x86_64
> 3.1.2-1.fc12
> lm_sensors-libs.x86_64
> 3.1.2-1.fc12
>
> Unfortunately I do not have your SuperIO chip in my
> system.
>
>
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3
2010-04-28 12:24 Luca Tettamanti
@ 2010-05-06 19:23 ` Luca Tettamanti
2010-05-07 8:07 ` Luca Tettamanti
1 sibling, 0 replies; 7+ messages in thread
From: Luca Tettamanti @ 2010-05-06 19:23 UTC (permalink / raw)
To: lm-sensors
On Wed, May 5, 2010 at 4:48 AM, Marc <digitelp@yahoo.com> wrote:
> Thanks for the advice Jeff... But it didn't work. I updated all the software,
> including a new sensors_detect and such and still the exact same results
> as I described. retried various things and no luck at all!
Enable HWMON_DEBUG_CHIP and recompile asus_atk0110 if you can; also
send me a copy of the DSDT.
Luca
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3
2010-04-28 12:24 Luca Tettamanti
2010-05-06 19:23 ` Luca Tettamanti
@ 2010-05-07 8:07 ` Luca Tettamanti
1 sibling, 0 replies; 7+ messages in thread
From: Luca Tettamanti @ 2010-05-07 8:07 UTC (permalink / raw)
To: lm-sensors
On Fri, May 7, 2010 at 6:48 AM, Marc <digitelp@yahoo.com> wrote:
> Thanks for the response, but fortunately, I found the solution and its one
> that your group ought to be telling others about.
It's not that we're hiding it, it's even mentioned in the FAQ.
> For later kernels, 2.6.32 the ACPI has gotten very strict and will not permit
> older drivers to function. Â To get around all that I added acpi_enforce_resources=lax
> to the kernel load and it did the trick.
Yes, I'm aware of this (I wrote the patch that enabled strict
validation by default). This is not the preferred solution though,
you'll revert to having two drivers touching the same hardware without
coordination.
The real bug here is that asus_atk0110 - which uses the monitoring
interface provided by Asus - is not working correctly on your board.
Luca
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2010-05-07 8:07 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-16 23:36 [lm-sensors] asus_atk0110 Not Activated in lm_sensors-3.1.1-3 Marc
2010-04-17 0:01 ` Jeff Rickman
2010-04-28 11:41 ` Jean Delvare
2010-05-05 2:48 ` Marc
-- strict thread matches above, loose matches on Subject: below --
2010-04-28 12:24 Luca Tettamanti
2010-05-06 19:23 ` Luca Tettamanti
2010-05-07 8:07 ` Luca Tettamanti
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.