Mageia forum

[burak@localhost ~]$ su
Password:
[root@localhost burak]# sensors-detect
Stopping lm_sensors (via systemctl): [ OK ]
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: System manufacturer System Product Name
# Board: ASUSTeK Computer INC. P8H67-M EVO

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital 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): yes
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 `Nuvoton NCT6776F Super IO Sensors' Success!
(address 0x290, driver `w83627ehf')
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

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
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

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): no
Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): yes
Copy prog/init/lm_sensors.service to /lib/systemd/system
and run 'systemctl enable lm_sensors.service'
for initialization at boot time.
[root@localhost burak]#

I've tried to do what it says at the end, but couldn't. Have installed various sensors monitors (applets and s-karamba widgets) without success, though lm-sensors seems to be running in MCC.

well, and what is the output of

Code: Select all: sensors

?

[burak@localhost ~]$ sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
[burak@localhost ~]$

That was to expect, in the output of sensors-detect was only one sensor marked "success"

Found `Nuvoton NCT6776F Super IO Sensors' Success!

All other sensors of your mobo(if ever present)seem to be unknown to lm_sensors, what should be displayed in the monitors in this case?

I used to enter these same commands in ubuntu distros and after rebooting I can see the temperatures in Xsensors or Xfce sensors applet.

TabletHater wrote:I used to enter these same commands in ubuntu distros and after rebooting I can see the temperatures in Xsensors or Xfce sensors applet.

and the version of lm_sensors is identical to the version of mageia's lm_sensors? The output of sensors-detect is the same or is it different? Maybe you should open a bug report.

Well, sorry I don't know anything about the versions, but the output of the sensors-detect is different. I haven't seen those last lines before. Thanks anyway.

I've just reactivated my mageia installation an run "sensors-detect" and "sensors" the output looks like this

Code: Select all: [root@kre001 alfred]# sensors-detect # sensors-detect revision 5861 (2010-09-21 17:21:05 +0200) # System: To Be Filled By O.E.M. To Be Filled By O.E.M. # Board: ASRock ALiveXFire-eSATA2.. This program will help you determine which kernel modules you need to load to use lm_sensors most effectively. It is generally safe and recommended to accept the default answers to all questions, unless you know what you're doing. Some south bridges, CPUs or memory controllers contain embedded sensors. Do you want to scan for them? This is totally safe. (YES/no): 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): 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 W83627EHF/EF/EHG/EG Super IO Sensors' Success! (address 0x290, driver `w83627ehf') 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 Some systems (mainly servers) implement IPMI, a set of common interfaces through which system health data may be retrieved, amongst other things. We first try to get the information from SMBIOS. If we don't find it there, we have to read from arbitrary I/O ports to probe for such interfaces. This is normally safe. Do you want to scan for IPMI interfaces? (YES/no): Probing for `IPMI BMC KCS' at 0xca0... No Probing for `IPMI BMC SMIC' at 0xca8... No Some hardware monitoring chips are accessible through the ISA I/O ports. We have to write to arbitrary I/O ports to probe them. This is usually safe though. Yes, you do have ISA I/O ports even if you do not have any ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): Lastly, we can probe the I2C/SMBus adapters for connected hardware monitoring devices. This is the most risky part, and while it works reasonably well on most systems, it has been reported to cause trouble on some systems. Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-piix4' for device 0000:00:14.0: ATI Technologies Inc SB600/SB700/SB800 SMBus Module i2c-dev loaded successfully. Next adapter: NVIDIA i2c adapter (i2c-0) Do you want to scan it? (YES/no/selectively): Next adapter: NVIDIA i2c adapter (i2c-1) Do you want to scan it? (YES/no/selectively): Client found at address 0x49 Probing for `National Semiconductor LM75'... No Probing for `Dallas Semiconductor DS75'... No Probing for `National Semiconductor LM77'... No Probing for `Dallas Semiconductor DS1621/DS1631'... No Probing for `National Semiconductor LM73'... No Probing for `National Semiconductor LM92'... No Probing for `National Semiconductor LM76'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Probing for `EDID EEPROM'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x51 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x52 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Client found at address 0x53 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... No Next adapter: NVIDIA i2c adapter (i2c-2) Do you want to scan it? (YES/no/selectively): Client found at address 0x4c Probing for `National Semiconductor LM75'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Analog Devices ADT7466'... No Probing for `Andigilog aSC7511'... No Probing for `Dallas Semiconductor DS1621/DS1631'... No Probing for `Analog Devices ADM1021'... No Probing for `Analog Devices ADM1021A/ADM1023'... No Probing for `Maxim MAX1617'... Success! (confidence 3, driver `adm1021') Probing for `Maxim MAX1617A'... No Probing for `Maxim MAX1668'... No Probing for `Maxim MAX1805'... No Probing for `Maxim MAX1989'... No Probing for `Maxim MAX6655/MAX6656'... No Probing for `TI THMC10'... No Probing for `National Semiconductor LM84'... No Probing for `Genesys Logic GL523SM'... No Probing for `Onsemi MC1066'... No Probing for `Maxim MAX1618'... No Probing for `Maxim MAX1619'... No Probing for `National Semiconductor LM82/LM83'... No Probing for `National Semiconductor LM90'... No Probing for `National Semiconductor LM89/LM99'... No Probing for `National Semiconductor LM86'... No Probing for `Analog Devices ADM1032'... No Probing for `Maxim MAX6654'... No Probing for `Maxim MAX6690'... No Probing for `Maxim MAX6657/MAX6658/MAX6659'... No Probing for `Maxim MAX6648/MAX6649/MAX6692'... Success! (confidence 8, driver `lm90') Probing for `Maxim MAX6680/MAX6681'... No Probing for `Maxim MAX6695/MAX6696'... No Probing for `Winbond W83L771W/G'... No Probing for `Winbond W83L771AWG/ASG'... No Probing for `Texas Instruments TMP401'... No Probing for `Texas Instruments TMP411'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP423'... No Probing for `Texas Instruments AMC6821'... No Probing for `National Semiconductor LM63'... No Probing for `Fintek F75363SG'... No Probing for `National Semiconductor LM73'... No Probing for `Maxim MAX6633/MAX6634/MAX6635'... No Probing for `Analog Devices ADT7461'... No Probing for `Analog Devices ADT7481'... No Probing for `Fintek F75383S/M'... No Probing for `SMSC EMC1403'... No Probing for `SMSC EMC1404'... No Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-3) Do you want to scan it? (yes/NO/selectively): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `w83627ehf': * ISA bus, address 0x290 Chip `Winbond W83627EHF/EF/EHG/EG Super IO Sensors' (confidence: 9) Driver `lm90': * Bus `NVIDIA i2c adapter ' Busdriver `nvidia', I2C address 0x4c Chip `Maxim MAX6648/MAX6649/MAX6692' (confidence: 8) Driver `k8temp' (autoloaded): * Chip `AMD K8 thermal sensors' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (YES/no): Laden der Sensor-Module: Starten des Sensor-Dämons: [ OK ] Unloading i2c-dev... OK

Code: Select all: [root@kre001 alfred]# sensors k8temp-pci-00c3 Adapter: PCI adapter Core0 Temp: +16.0°C Core0 Temp: +15.0°C Core1 Temp: +16.0°C Core1 Temp: +17.0°C w83627ehf-isa-0290 Adapter: ISA adapter Vcore: +1.32 V (min = +0.00 V, max = +1.74 V) in1: +1.31 V (min = +1.02 V, max = +0.98 V) ALARM AVCC: +3.31 V (min = +2.98 V, max = +3.63 V) +3.3V: +3.31 V (min = +2.98 V, max = +3.63 V) in4: +1.69 V (min = +0.46 V, max = +1.51 V) ALARM in5: +1.67 V (min = +2.04 V, max = +1.27 V) ALARM in6: +1.90 V (min = +1.00 V, max = +1.32 V) ALARM 3VSB: +3.30 V (min = +2.98 V, max = +3.63 V) Vbat: +3.28 V (min = +2.70 V, max = +3.30 V) in9: +1.66 V (min = +1.76 V, max = +1.50 V) ALARM fan1: 0 RPM (min = 897 RPM, div = 32) ALARM fan2: 2083 RPM (min = 912 RPM, div = 8) fan3: 0 RPM (min = 7031 RPM, div = 32) ALARM fan5: 0 RPM (min = 981 RPM, div = 32) ALARM temp1: +25.0°C (high = -97.0°C, hyst = -6.0°C) ALARM sensor = thermistor temp2: +23.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor temp3: +23.5°C (high = +80.0°C, hyst = +75.0°C) sensor = thermistor cpu0_vid: +0.000 V

the version of lm_sensors i'm using:

Code: Select all: # sensors-detect revision 5861 (2010-09-21 17:21:05 +0200)

I'm grateful and this is by far the best support I've seen in the whole planet.

Formerly I've never accepted "the most risky part" (and sensors have always worked in buntus), but this time accepted that too as well as entering much more yes' and this is the damned output (with the same infamous last words):

[burak@localhost ~]$ su
Password:
[root@localhost burak]# sensors-detect
Stopping lm_sensors (via systemctl): [ OK ]
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: System manufacturer System Product Name
# Board: ASUSTeK Computer INC. P8H67-M EVO

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital 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): yes
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 `Nuvoton NCT6776F Super IO Sensors' Success!
(address 0x290, driver `w83627ehf')
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

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
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

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): no
Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): yes
Copy prog/init/lm_sensors.service to /lib/systemd/system
and run 'systemctl enable lm_sensors.service'
for initialization at boot time.
[root@localhost burak]# sensors
No sensors found!
Make sure you loaded all the kernel drivers you need.
Try sensors-detect to find out which these are.
[root@localhost burak]# sensors-detect
# sensors-detect revision 5984 (2011-07-10 21:22:53 +0200)
# System: System manufacturer System Product Name
# Board: ASUSTeK Computer INC. P8H67-M EVO

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no): yes
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital 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): yes
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 `Nuvoton NCT6776F Super IO Sensors' Success!
(address 0x290, driver `w83627ehf')
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

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no): yes
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO): yes
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

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no): yes
Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)
Module i2c-dev loaded successfully.

Next adapter: i915 gmbus disabled (i2c-0)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 gmbus ssc (i2c-1)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 GPIOB (i2c-2)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 gmbus vga (i2c-3)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 GPIOA (i2c-4)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 gmbus panel (i2c-5)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 GPIOC (i2c-6)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 gmbus dpc (i2c-7)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 GPIOD (i2c-8)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 gmbus dpb (i2c-9)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x49
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6642'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)

Next adapter: i915 GPIOE (i2c-10)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x49
Probing for `National Semiconductor LM75'... No
Probing for `National Semiconductor LM75A'... No
Probing for `Dallas Semiconductor DS75'... No
Probing for `National Semiconductor LM77'... No
Probing for `Analog Devices ADT7410'... No
Probing for `Dallas Semiconductor DS1621/DS1631'... No
Probing for `Maxim MAX6642'... No
Probing for `National Semiconductor LM73'... No
Probing for `National Semiconductor LM92'... No
Probing for `National Semiconductor LM76'... No
Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
Probing for `NXP/Philips SA56004'... No
Probing for `SMSC EMC1023'... No
Probing for `SMSC EMC1043'... No
Probing for `SMSC EMC1053'... No
Probing for `SMSC EMC1063'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)

Next adapter: i915 gmbus reserved (i2c-11)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x18
Probing for `Analog Devices ADM1021'... No
Probing for `Analog Devices ADM1021A/ADM1023'... No
Probing for `Maxim MAX1617'... No
Probing for `Maxim MAX1617A'... No
Probing for `Maxim MAX1668'... No
Probing for `Maxim MAX1805'... No
Probing for `Maxim MAX1989'... No
Probing for `Maxim MAX6655/MAX6656'... No
Probing for `TI THMC10'... No
Probing for `National Semiconductor LM84'... No
Probing for `Genesys Logic GL523SM'... No
Probing for `Onsemi MC1066'... No
Probing for `Maxim MAX1618'... No
Probing for `Maxim MAX1619'... No
Probing for `National Semiconductor LM82/LM83'... No
Probing for `Maxim MAX6654'... No
Probing for `Maxim MAX6690'... No
Probing for `Maxim MAX6680/MAX6681'... No
Probing for `Maxim MAX6695/MAX6696'... No
Probing for `Texas Instruments AMC6821'... No
Probing for `National Semiconductor LM95245'... No
Probing for `National Semiconductor LM64'... No
Probing for `SMSC EMC1047'... No
Probing for `SMSC EMC1402'... No
Probing for `SMSC EMC1403'... No
Probing for `SMSC EMC1404'... No
Probing for `ST STTS424'... No
Probing for `ST STTS424E'... No
Probing for `NXP SE97/SE97B'... No
Probing for `NXP SE98'... No
Probing for `Analog Devices ADT7408'... No
Probing for `IDT TS3000/TSE2002'... No
Probing for `Maxim MAX6604'... No
Probing for `Microchip MCP98242'... No
Probing for `Microchip MCP98243'... No
Probing for `Microchip MCP9843'... No
Probing for `ON CAT6095/CAT34TS02'... No
Client found at address 0x50
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Probing for `EDID EEPROM'... No
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x52
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... No
Client found at address 0x58
Probing for `Analog Devices ADT7462'... No
Probing for `Andigilog aSC7512'... No
Client found at address 0x5c
Probing for `Analog Devices ADT7462'... No
Probing for `SMSC EMC1072'... No
Probing for `SMSC EMC1073'... No
Probing for `SMSC EMC1074'... No
Client found at address 0x73
Probing for `FSC Poseidon I'... No
Probing for `FSC Poseidon II'... No
Probing for `FSC Scylla'... No
Probing for `FSC Hermes'... No
Probing for `FSC Heimdal'... No
Probing for `FSC Heracles'... No
Probing for `FSC Hades'... No
Probing for `FSC Syleus'... No

Next adapter: i915 gmbus dpd (i2c-12)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: i915 GPIOF (i2c-13)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: DPDDC-B (i2c-14)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: DPDDC-C (i2c-15)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: DPDDC-D (i2c-16)
Do you want to scan it? (YES/no/selectively): yes

Next adapter: SMBus I801 adapter at f040 (i2c-17)
Do you want to scan it? (YES/no/selectively): yes
Client found at address 0x51
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)
Client found at address 0x53
Probing for `Analog Devices ADM1033'... No
Probing for `Analog Devices ADM1034'... No
Probing for `SPD EEPROM'... Yes
(confidence 8, not a hardware monitoring chip)

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `w83627ehf':
* ISA bus, address 0x290
Chip `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)

Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): yes
Copy prog/init/lm_sensors.service to /lib/systemd/system
and run 'systemctl enable lm_sensors.service'
for initialization at boot time.
Unloading i2c-dev... OK

[root@localhost burak]#

Please put next time longer listings within codeblocks. I see you are using revision 5984, are you runnig the beta1 of MGA2? In this case you should post your problem in the approriate subforum.

All right. Do you mean this forum: Testing : Alpha, Beta, RC and Cauldron?

Yes, that's my suggest.

You want to have a look at https://bugs.mageia.org/show_bug.cgi?id=4095

Also no need to start a new thread in cauldron subforum, just report one of your posts
in this thread and request it to be moved to that subforum (and be nice to the moderators

)

Thanks Dok.

Latest updates have solved this on Beta.

Mageia forum

[SOLVED] Can't configure sensors

[SOLVED] Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors

Re: Can't configure sensors