Mageia forum

Anyone know when/if the new chipset will be supported with regards lm-sensors ?

I had seen some commits to the kernel list for driver updates/pci id's in the last month just wondered if they would be patched into MG4/5 ?

I did update to sensors 3.3.5 with libsensors version 3.3.5.

Tried mga5 a2 but still dont work.

The cpu temps work fine via coretemp but that's all. No voltages/fan rpm

Any idea anyone?

MB is a Asus Sabertooth z97 mark 1

Check here: http://lm-sensors.org/wiki/Devices
EDIT: Or check the current interim solution from e.g. http://lists.lm-sensors.org/pipermail/l ... 41776.html

That's what you get for buying bleeding-edge chipsets AND wanting to use linux on top with all bells and whistles

doktor5000 wrote:Check here: http://lm-sensors.org/wiki/Devices
EDIT: Or check the current interim solution from e.g. http://lists.lm-sensors.org/pipermail/l ... 41776.html

Tried them all ready mine uses the Nuvoton NCT6791D

lmsensors picks it up but is unable to use it.

I did rebuild the current driver for said chip but still no joy.

doktor5000 wrote:That's what you get for buying bleeding-edge chipsets AND wanting to use linux on top with all bells and whistles

I know! I should know better

I bought a P5Q Asus mobo when they were new, it took about 12 months before I could use the on board raid properly. But the upside is it's still in use some 6 or 7 years later

Hang tight, it will come down the chain at some stage

pete910 wrote:

doktor5000 wrote:Check here: http://lm-sensors.org/wiki/Devices
EDIT: Or check the current interim solution from e.g. http://lists.lm-sensors.org/pipermail/l ... 41776.html

Tried them all ready mine uses the Nuvoton NCT6791D

Did you check the standalone driver on github: https://github.com/groeck/nct6775/ ? And what Mageia version is that?
And also see the thread: http://lists.lm-sensors.org/pipermail/l ... 40401.html

That's the driver I am using/trying . Followed the same info/pages

MGA4 64 bit.

Using the latest lmsensrs too.

doing sensors detect picks it up and all the rest of it but still dont work.

Code: Select all

cat lm_sensors
# Generated by sensors-detect on Tue Sep 16 00:44:10 2014
# This file is sourced by /etc/init.d/lm_sensors and defines the modules to
# be loaded/unloaded.
#
# The format of this file is a shell script that simply defines variables:
# HWMON_MODULES for hardware monitoring driver modules, and optionally
# BUS_MODULES for any required bus driver module (for example for I2C or SPI).

HWMON_MODULES="coretemp nct6775"

driver built fine with no errors. installed and loads fine

Code: Select all

 lsmod | grep nct
nct6775                55431  0
hwmon_vid              12783  1 nct6775

Code: Select all

modinfo nct6775
filename:       /lib/modules/3.12.25-desktop-3.mga4/kernel/drivers/hwmon/nct6775.ko
license:        GPL
description:    NCT6775F/NCT6776F/NCT6779D driver
author:         Guenter Roeck <linux@roeck-us.net>
srcversion:     986CD32F300986B1E71741D
depends:        hwmon-vid
vermagic:       3.12.25-desktop-3.mga4 SMP mod_unload modversions
parm:           force_id:Override the detected device ID (ushort)
parm:           fan_debounce:Enable debouncing for fan RPM signal (ushort)

Typing sensors in the console still only shows CPU.

Code: Select all

sensors
acpitz-virtual-0
Adapter: Virtual device
temp1:        +27.8°C  (crit = +105.0°C)
temp2:        +29.8°C  (crit = +105.0°C)

coretemp-isa-0000
Adapter: ISA adapter
Physical id 0:  +37.0°C  (high = +80.0°C, crit = +100.0°C)
Core 0:         +33.0°C  (high = +80.0°C, crit = +100.0°C)
Core 1:         +37.0°C  (high = +80.0°C, crit = +100.0°C)
Core 2:         +38.0°C  (high = +80.0°C, crit = +100.0°C)
Core 3:         +36.0°C  (high = +80.0°C, crit = +100.0°C)


Something I've missed you thinking?

Nope, best ask upstream on lm-sensors mailing list for further information. Can't really comment more on this topic as I'm not using lm-sensors myself.

Update:

Asus have changed something with there recent BIOS updates which is causing the problem. A user on the LM-sensors ml has found this out. http://www.spinics.net/lists/lm-sensors/msg42336.html

Looking at mine it seems it a address conflict, dmesg is showing this

Code: Select all

ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\_GPE.HWM_) (20131218/utaddress-258)

Only way round it is by putting the line

Code: Select all

acpi_enforce_resources=lax

in gub.

From what I understand that ain't the best solution.

So, kind of solved though more like a work round

Please mark the thread accordingly by editing the topic of the first post and prefix it by [DONE] as there's not much more we can do about this.
Would also be appreciated if you could use a more meaningful thread title, at least mention lm_sensors there please

doktor5000 wrote:Please mark the thread accordingly by editing the topic of the first post and prefix it by [DONE] as there's not much more we can do about this.
Would also be appreciated if you could use a more meaningful thread title, at least mention lm_sensors there please

lol, was thinking of marking done to find that you have commented on it