Thanks for offering to help! I'll make this my pet project for a while. :-)
Actually I had not been using acpi_enforce_resources=lax, but I *think* I
am using it now. I included the parameter at boot:
I root@debianstick:~# cat /proc/cmdline
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64
root=UUID=771651f1-c1a2-47af-a7ee-96a0c7bbfc51 ro quiet
acpi_enforce_resources=lax
But at the same time acpi_enforce_resources isn't included when I "Display
all currently available" (I interpret it as "possible with the current
kernel") using sysctl (which might be a bit odd?):
root@debianstick:~# sysctl --all | grep acpi
kernel.acpi_video_flags = 0
Am I doing something wrong when I try to set the acpi_enforce_resources=lax
kernel parameter?
Unfortunately the sensors output looks the same with the
acpi_enforce_resources=lax kernel paremeter, if I am setting it correctly.
The sensors output looks the same both before and after running
sensors-detect again.
My GNU/Linux knowledge has lots of holes. How would I try the asus_atk0110
driver with lm-sensors? I assume (but please correct me) that it simply
means that it's a kernel module which I should load.
I didn't have asus_atk0110 loaded at first:
root@debianstick:~# lsmod | grep asus
asus_wmi 18726 1 eeepc_wmi
sparse_keymap 12760 1 asus_wmi
rfkill 19012 1 asus_wmi
wmi 13243 3 asus_wmi,mxm_wmi,nouveau
And got an error when I tried loading it when using
acpi_enforce_resources=lax as described above:
root@debianstick:~# modprobe asus_atk0110
ERROR: could not insert 'asus_atk0110': Device or resource busy
It had a corresponding syslog entry:
Sep 22 19:50:21 debianstick kernel: [ 8208.492660] asus_atk0110:
Resources not safely usable due to acpi_enforce_resources kernel parameter
Does that mean that acpi_enforce_resources kernel is set to something other
than lax?
I tried modprobe asus_atk0110 after removing the modules coretemp and
w83627ehf from /etc/modules and rebooting while still having
acpi_enforce_resources=lax set as described above, but that didn't help.
However, if I reboot and skip adding the argument
acpi_enforce_resources=lax to the linux... line in Grub it loads. However,
it only gives me this output:
root@debianstick:~# sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +38.0°C (high = +81.0°C, crit = +91.0°C)
Core 0: +37.0°C (high = +81.0°C, crit = +91.0°C)
Core 1: +37.0°C (high = +81.0°C, crit = +91.0°C)
Core 2: +35.0°C (high = +81.0°C, crit = +91.0°C)
Core 3: +39.0°C (high = +81.0°C, crit = +91.0°C)
Core 4: +36.0°C (high = +81.0°C, crit = +91.0°C)
Core 5: +35.0°C (high = +81.0°C, crit = +91.0°C)
nouveau-pci-0100
Adapter: PCI adapter
temp1: +48.0°C (high = +100.0°C, crit = +110.0°C)
If I reboot with all three modules in /etc/modules (asus_atk0110, coretemp
and w83627ehf) I get the same output as without asus_atk0110.
test@debianstick:~$ sensors
coretemp-isa-0000
Adapter: ISA adapter
Physical id 0: +39.0°C (high = +81.0°C, crit = +91.0°C)
Core 0: +35.0°C (high = +81.0°C, crit = +91.0°C)
Core 1: +38.0°C (high = +81.0°C, crit = +91.0°C)
Core 2: +35.0°C (high = +81.0°C, crit = +91.0°C)
Core 3: +37.0°C (high = +81.0°C, crit = +91.0°C)
Core 4: +36.0°C (high = +81.0°C, crit = +91.0°C)
Core 5: +35.0°C (high = +81.0°C, crit = +91.0°C)
nouveau-pci-0100
Adapter: PCI adapter
temp1: +48.0°C (high = +100.0°C, crit = +110.0°C)
nct6776-isa-0290
Adapter: ISA adapter
Vcore: +0.81 V (min = +0.00 V, max = +1.74 V)
in1: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM
AVCC: +3.41 V (min = +2.98 V, max = +3.63 V)
+3.3V: +3.39 V (min = +2.98 V, max = +3.63 V)
in4: +1.01 V (min = +0.00 V, max = +0.00 V) ALARM
in5: +2.04 V (min = +0.00 V, max = +0.00 V) ALARM
3VSB: +3.39 V (min = +2.98 V, max = +3.63 V)
Vbat: +3.34 V (min = +2.70 V, max = +3.63 V)
fan1: 1002 RPM (min = 0 RPM) ALARM
fan2: 1477 RPM (min = 0 RPM) ALARM
fan3: 0 RPM (min = 0 RPM) ALARM
fan4: 0 RPM (min = 0 RPM) ALARM
fan5: 0 RPM (min = 0 RPM) ALARM
SYSTIN: +36.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor
= thermistor
CPUTIN: +41.5°C (high = +80.0°C, hyst = +75.0°C) sensor = CPU
diode
AUXTIN: +31.0°C (high = +80.0°C, hyst = +75.0°C) sensor =
thermistor
PECI Agent 0: +28.0°C
cpu0_vid: +1.708 V
intrusion0: OK
intrusion1: ALARM
I think I have completed step [1] now, if the kernel parameter was set the
right way?
For step [2] I'll try to set a resonable minimum fan speed for the used
fans. It's a bit odd that it says the minimum is 0 but still thinks that
for example fan1 is in ALARM state even though it's RPM is 1002. I also am
a bit curious to how setting the minimum fan speed could help getting the
RPM for the fans with 0 RPM? But of course I'll go further and try that
anyway if I didn't mess something upp setting the kernel parameter talked
about above.
Best regards, Kent
On Sat, Sep 21, 2013 at 7:05 PM, Guenter Roeck <linux@xxxxxxxxxxxx> wrote:
> On 09/21/2013 05:31 AM, Kent Larsson wrote:
>
>> Hi!
>>
>> I have a P9X79 WS motherboard and am having some problems with the
>> nct6776-isa-0290 sensor. I'll start with most serious problem (where
>> Google
>> didn't turn up anything promising), 2 out of 4 fans are reported as 0 RPM,
>> even though they are running.
>>
>> I am running Debian stable which has sensors version 3.3.2 with libsensors
>> version 3.3.2. I am using the latest kernel in Debian stable at the time
>> of
>> writing, uname -a prints:
>> Linux cow 3.2.0-4-amd64 #1 SMP Debian 3.2.46-1+deb7u1 x86_64 GNU/Linux
>>
>> I have executed sensors-detect and loaded the suggested kernel modules.
>> The
>> sensors command prints:
>>
>> ----/ sensors output start /-----
>>
>> coretemp-isa-0000
>> Adapter: ISA adapter
>> Physical id 0: +39.0°C (high = +81.0°C, crit = +91.0°C)
>> Core 0: +35.0°C (high = +81.0°C, crit = +91.0°C)
>> Core 1: +39.0°C (high = +81.0°C, crit = +91.0°C)
>> Core 2: +36.0°C (high = +81.0°C, crit = +91.0°C)
>> Core 3: +37.0°C (high = +81.0°C, crit = +91.0°C)
>> Core 4: +36.0°C (high = +81.0°C, crit = +91.0°C)
>> Core 5: +35.0°C (high = +81.0°C, crit = +91.0°C)
>>
>> nouveau-pci-0100
>> Adapter: PCI adapter
>> temp1: +48.0°C (high = +100.0°C, crit = +110.0°C)
>>
>> nct6776-isa-0290
>> Adapter: ISA adapter
>> Vcore: +0.81 V (min = +0.00 V, max = +1.74 V)
>> in1: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM
>> AVCC: +3.41 V (min = +2.98 V, max = +3.63 V)
>> +3.3V: +3.39 V (min = +2.98 V, max = +3.63 V)
>> in4: +1.01 V (min = +0.00 V, max = +0.00 V) ALARM
>> in5: +2.04 V (min = +0.00 V, max = +0.00 V) ALARM
>> 3VSB: +3.39 V (min = +2.98 V, max = +3.63 V)
>> Vbat: +3.34 V (min = +2.70 V, max = +3.63 V)
>> fan1: 978 RPM (min = 0 RPM) ALARM
>> fan2: 1508 RPM (min = 0 RPM) ALARM
>> fan3: 0 RPM (min = 0 RPM) ALARM
>> fan4: 0 RPM (min = 0 RPM) ALARM
>> fan5: 0 RPM (min = 0 RPM) ALARM
>> SYSTIN: +37.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor =
>> thermistor
>> CPUTIN: +41.5°C (high = +80.0°C, hyst = +75.0°C) sensor = CPU
>> diode
>> AUXTIN: +31.5°C (high = +80.0°C, hyst = +75.0°C) sensor =
>> thermistor
>> PECI Agent 0: +32.0°C
>> cpu0_vid: +1.708 V
>> intrusion0: OK
>> intrusion1: ALARM
>>
>> ----/ sensors output end /-----
>>
>> As you can see there are no "div" in any of the output, which I understand
>> means that changing the divisor won't help?
>>
>> I have screenshots of my BIOS (upgraded to latest version) and an
>> annotated
>> picture of the actual machine inside here:
>> http://forums.debian.net/**viewtopic.php?f=10&t=107523&p=**512640#p512640<http://forums.debian.net/viewtopic.php?f=10&t=107523&p=512640#p512640>
>>
>> That link also contains sensors-detect output and my complete
>> /etc/sensors3.conf as I thought they were a bit too large to post in this
>> message. Let me know if that conclusion was wrong, in which case I'm sorry
>> and I'll paste them here.
>>
>> I am willing to help out any way I can to improve lm-sensors support for
>> my
>> motherboard. It's supposed to be a nice motherboard, so improved
>> compatibility would hopefully be of value for lots of users.
>>
>> Thank you for reading this post! I would greatly appreciate some help as I
>> am pretty dumbfounded when it comes to this problem.
>>
>>
> The NCT6776 does not have fan divisor registers.
>
> Couple of things to try:
>
> 1) Try using the asus_atk0110 driver. ASUS exports environmental data
> through ACPI,
> so that is the preferred method to get the the information for ASUS
> boards.
> [ Which makes me wonder. Do you have "acpi_enforce_resources=lax"
> configured
> your boot command line ? ]
> If that does not work, please send a copy of /sys/firmware/acpi/tables/
> **DSDT.
> 2) Try setting the minimum fan speed to something reasonable. Odd, though,
> that
> the BIOS reports minimum speeds but the driver reports 0.
> 3) Try using other fan connectors. I understand the board has a total of 6
> connectors.
> Since the chip can only monitor a total of 5 fan inputs, it is possible
> that ASUS
> uses a multiplexer to be able to read the speed of two of the fans.
> Since we don't
> know about that, it won't work for us.
> 4) Install and use the driver from https://github.com/groeck/**nct6775<https://github.com/groeck/nct6775>
> .
>
> We can go from there if nothing of the above works. Next step would be to
> dump all
> registers from the SuperIO chip.
>
> Guenter
>
>
_______________________________________________
lm-sensors mailing list
lm-sensors@xxxxxxxxxxxxxx
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
