I have recently bought an haswell system with the B85M-G Mainboard. And its now running the great arch linux distribution.
My problem is, that the the pwm sensors are not correctly recognised while running sensors-detect. So i get the following output:
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): Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found unknown chip with ID 0xc803 (logical device B has address 0x290, could be sensors) Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No
So finally only the Chip `Intel digital thermal sensor' (confidence: 9) is working.
Does anyone know, which additional module i need, if its already existing?
Apparently sensors-detect doesn't know your SuperIO. You can identify this chip by eyeballing and some googling, it should be between 1x1cm and 2x2cm in size and have no heatsink on it. Once you know what it is, you'll be able to look for a Linux driver.
Some ASUS motherboards also have an ACPI interface which provides read-only access to these sensors. In Linux this is supported by the asus_atk0110 module.
First thank you to your fast response.
Thanks to this page: http://forums.hardwarezone.com.sg/hardw … 54140.html i found the chip very fast. I checked also myself. My slightly different board ASUS B85M-G has the same chip:
Nuvoton NCT6791D as the Super I/O Controller.
I found the module for the predecessor chip in the aur https://aur.archlinux.org/packages/nct677x/ . This one will be also included in the upcoming 3.10 kernel, but it looks like also this module does not support my one. This is very sad.
So i think that i have to wait that someone who can develop such a module, gets interest in supporting this chip.
I have a ASUS Z87-PLUS with this chip as well. All the new Z87 ASUS boards seem to use it. I've requested the datasheet from Nuvoton, and assuming they give it to me, I should be able to update the nct6775 driver to support it.
Oh jeah, that would be great! I hope that they give you the datasheet.
Good news, I have a patch written, available at https://github.com/Andaareed/nct6775. Could you try building and loading the module, and then verify that sensors outputs stuff? You should be able to just run "make; sudo modprobe hwmon-vid; sudo insmod nct6775.ko", assuming you have kernel headers installed.
Sorry for the late reply. I was not at home.
The source package is looking for kernel sources in /usr/src/linux-headers-3.9.8-1-ARCH but in my installation the folder exists only without the header part in the name. (Yes i have the linux-headers package installed.) So i symlinked the folder without 'headers' to this location where it is searching for.
The compilation runs great without any warning or error. The both commands after make runs without any output. Checking with lsmod gives the following output:
lsmod | grep nct
nct6775 38886 0
hwmon_vid 3260 1 nct6775
But the output of sensors-detect is still the same as in my first post.
I saw that there is also a section inside the make file for installation. So i did run make install which gives the following output:
cp nct6775.ko /lib/modules/3.9.8-1-ARCH/kernel/drivers/hwmon
depmod -a -F /boot/System.map-3.9.8-1-ARCH 3.9.8-1-ARCH
depmod: FATAL: could not load /boot/System.map-3.9.8-1-ARCH: No such file or directory
make: *** [modules_install] Fehler 1
If you need further information of my system, feel free to write me.
After loading the module does sensors show the new sensors?
Oh jeah, it was my fault. Running sensors after loading the module seems to work pretty fine:
nct6791-isa-0290 Adapter: ISA adapter in0: +0.90 V (min = +0.00 V, max = +1.74 V) in1: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM in2: +3.33 V (min = +0.00 V, max = +0.00 V) ALARM in3: +3.33 V (min = +0.00 V, max = +0.00 V) ALARM in4: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM in5: +2.03 V (min = +0.00 V, max = +0.00 V) ALARM in6: +0.62 V (min = +0.00 V, max = +0.00 V) ALARM in7: +3.41 V (min = +0.00 V, max = +0.00 V) ALARM in8: +3.34 V (min = +0.00 V, max = +0.00 V) ALARM in9: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM in10: +0.22 V (min = +0.00 V, max = +0.00 V) ALARM in11: +0.18 V (min = +0.00 V, max = +0.00 V) ALARM in12: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM in13: +1.02 V (min = +0.00 V, max = +0.00 V) ALARM in14: +0.22 V (min = +0.00 V, max = +0.00 V) ALARM fan1: 0 RPM (min = 0 RPM) fan2: 903 RPM (min = 0 RPM) fan3: 0 RPM (min = 0 RPM) fan4: 0 RPM (min = 0 RPM) fan5: 0 RPM (min = 0 RPM) SYSTIN: +25.0°C (high = +0.0°C, hyst = +0.0°C) ALARM sensor = thermistor CPUTIN: +26.0°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor AUXTIN0: +49.0°C sensor = thermistor AUXTIN1: +106.0°C sensor = thermistor AUXTIN2: +104.0°C sensor = thermistor AUXTIN3: +104.0°C sensor = thermistor PCH_CHIP_CPU_MAX_TEMP: +0.0°C PCH_CHIP_TEMP: +0.0°C PCH_CPU_TEMP: +0.0°C PCH_MCH_TEMP: +0.0°C intrusion0: ALARM intrusion1: ALARM beep_enable: disabled
Which path should i use for the nct6775.ko file, that i can load it at startup with the /etc/modules-load.d/mymodules.conf?
It looks like it installed the driver ok so it would be however you normally load a driver on arch (on Ubuntu I would add nct6775 to /etc/modules).
Yeah okey, now i am using a startup script, which loads the modules as an systemd service.
I have the situation that pwmconfig is not able to controll the cpu fan. (fan2 in dumb before) So i moved my pwm configurable fans to the chassis port and it works like a charm. It is not a problem for me, but i want to describe this problem, for future production release.
I had a ASRock A55 Pro3 M/B which used nct6776, i follow the README.ASRock file from the sources,
isaset -y -f 0x2e 0x87 isaset -y -f 0x2e 0x87 isaset -y 0x2e 0x2f 0x7 0x8 isaset -y 0x2e 0x2f 0xf0 0xb2 isaset -y 0x2e 0x2f 0xf1 0xb3
the CPU Fan finally show up, otherwise it don't.
I have to execute the above code while reboot or just do once?
Sorry for my poor english.