Description of problem: cpu temperature and fan speeds not available in ksensors Version-Release number of selected component (if applicable): ksensors.x86_64 0.7.3-42.fc30 lm_sensors.x86_64 3.5.0-3.fc30 lm_sensors-libs.x86_64 3.5.0-3.fc30 qt5-qtsensors.x86_64 5.12.4-1.fc30 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: there are not choices to show cpu temperature or fan speeds in ksensors sensors-detect does not detect any sensors for this motherboard
KSensors can only show what lm_sensors (or hddtemp) reports. If lm_sensors does not report anything, that's an lm_sensors issue.
If lm_sensors doesn't report anything, that's really a kernel issue ;). But seriously now, support for AMD 3700X is not yet in the mainline kernel. It should appear in the 5.4 release, however. New kernel releases appear in Fedora predictably, so there's no point in filing a kernel bug for this. sensors-detect should detect the CPU, though. I fixed that upstream recently. I'll reuse this bug to fix this in Fedora. Also, sensors-detect should detect the board's Super IO chip, if there's any. Is there a Super IO chip? What's the part number?
how would find out the super io chip ? ----------------------- here is the output from sensors detect [root@rsmpc ~]# sensors-detect --auto # sensors-detect revision $Revision$ # System: Micro-Star International Co., Ltd. MS-7C37 [3.0] # Board: Micro-Star International Co., Ltd. X570-A PRO (MS-7C37) # Kernel: 5.2.7-200.fc30.x86_64 x86_64 # Processor: AMD Ryzen 7 3700X 8-Core Processor (23/113/0) Running in automatic mode, default answers to all questions are assumed. 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... 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 16h thermal sensors... No AMD Family 17h thermal sensors... No AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 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/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found unknown chip with ID 0xd451 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): 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): Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (YES/no/selectively): Client found at address 0x4a 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/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... 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 Client found at address 0x4c Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Analog Devices ADT7466'... No Probing for `Andigilog aSC7511'... No Probing for `Analog Devices ADM1021'... No Probing for `Analog Devices ADM1021A/ADM1023'... No Probing for `Global Mixed-mode Technology G781'... 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 MAX6642'... 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'... No 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 TMP400'... No Probing for `Texas Instruments TMP401'... No Probing for `Texas Instruments TMP411A'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP423'... No Probing for `Texas Instruments TMP431'... No Probing for `Texas Instruments TMP432'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Texas Instruments TMP442'... No Probing for `Texas Instruments TMP451'... No Probing for `Texas Instruments AMC6821'... No Probing for `National Semiconductor LM95235'... No Probing for `National Semiconductor LM95245'... No Probing for `National Semiconductor LM63'... No Probing for `National Semiconductor LM96163'... 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 ADT7461A, ON Semiconductor NCT1008'... No Probing for `NXP/Philips SA56004'... No Probing for `Analog Devices ADT7481'... No Probing for `Fintek F75383S/M'... No Probing for `SMSC EMC1002'... No Probing for `SMSC EMC1023'... No Probing for `SMSC EMC1033'... No Probing for `SMSC EMC1043'... No Probing for `SMSC EMC1046'... No Probing for `SMSC EMC1053'... No Probing for `SMSC EMC1063'... No Probing for `SMSC EMC1072'... No Probing for `SMSC EMC1073'... No Probing for `SMSC EMC1074'... No Probing for `SMSC EMC1402'... No Probing for `SMSC EMC1403'... No Probing for `SMSC EMC1404'... No Probing for `SMSC EMC1422'... No Probing for `SMSC EMC1423'... No Probing for `SMSC EMC1424'... No Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) 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'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x52 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) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (YES/no/selectively): Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2) Do you want to scan it? (YES/no/selectively): Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3) Do you want to scan it? (YES/no/selectively): Next adapter: NVIDIA i2c adapter 4 at 2d:00.0 (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: NVIDIA i2c adapter 6 at 2d:00.0 (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: NVIDIA i2c adapter 7 at 2d:00.0 (i2c-6) Do you want to scan it? (yes/NO/selectively): Sorry, no sensors were detected. Either your system has no sensors, or they are not supported, or they are connected to an I2C or SMBus adapter that is not supported. If you find out what chips are on your board, check https://hwmon.wiki.kernel.org/device_support_status for driver status.
FEDORA-2019-caf20de424 has been submitted as an update to Fedora 30. https://bodhi.fedoraproject.org/updates/FEDORA-2019-caf20de424
FEDORA-2019-29eae8df8b has been submitted as an update to Fedora 29. https://bodhi.fedoraproject.org/updates/FEDORA-2019-29eae8df8b
You can find it by inspecting the board. sensors-detect also detects it in this case: Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found unknown chip with ID 0xd451 So the chip is Nuvoton NCT6797D. I've updated Fedora's lm_sensors to detect both the AMD sensors and the Super IO. Please try it out. The current kernel should already support NCT6797D. sensors-detect should now load the nct6775 driver and readings from the Super IO should then be available through 'sensors'.
i tested this on fedora 30 and had the following output from sensors-detect [root@rsmpc ~]# sensors-detect # sensors-detect revision $Revision$ # System: Micro-Star International Co., Ltd. MS-7C37 [3.0] # Board: Micro-Star International Co., Ltd. X570-A PRO (MS-7C37) # Kernel: 5.2.7-200.fc30.x86_64 x86_64 # Processor: AMD Ryzen 7 3700X 8-Core Processor (23/113/0) 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): y 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 16h thermal sensors... No AMD Family 17h thermal sensors... Success! (driver `k10temp') AMD Family 15h power sensors... No AMD Family 16h power sensors... No Intel digital thermal sensor... No Intel AMB FB-DIMM thermal sensor... No Intel 5500/5520/X58 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): y Probing for Super-I/O at 0x2e/0x2f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... No Trying family `ITE'... No Probing for Super-I/O at 0x4e/0x4f Trying family `National Semiconductor/ITE'... No Trying family `SMSC'... No Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes Found `Nuvoton NCT6797D Super IO Sensors' Success! (address 0xa20, driver `nct6775') 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): y 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): y 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): y Using driver `i2c-piix4' for device 0000:00:14.0: AMD KERNCZ SMBus Module i2c-dev loaded successfully. Next adapter: SMBus PIIX4 adapter port 0 at 0b00 (i2c-0) Do you want to scan it? (yes/NO/selectively): y Client found at address 0x4a 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/ADT7420'... No Probing for `Analog Devices ADT7411'... No Probing for `Maxim MAX6642'... No Probing for `Texas Instruments TMP435'... 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 Client found at address 0x4c Probing for `National Semiconductor LM75'... No Probing for `National Semiconductor LM75A'... No Probing for `Dallas Semiconductor DS75'... No Probing for `Analog Devices ADT7466'... No Probing for `Andigilog aSC7511'... No Probing for `Analog Devices ADM1021'... No Probing for `Analog Devices ADM1021A/ADM1023'... No Probing for `Global Mixed-mode Technology G781'... 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 MAX6642'... 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'... No 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 TMP400'... No Probing for `Texas Instruments TMP401'... No Probing for `Texas Instruments TMP411A'... No Probing for `Texas Instruments TMP421'... No Probing for `Texas Instruments TMP422'... No Probing for `Texas Instruments TMP423'... No Probing for `Texas Instruments TMP431'... No Probing for `Texas Instruments TMP432'... No Probing for `Texas Instruments TMP435'... No Probing for `Texas Instruments TMP441'... No Probing for `Texas Instruments TMP442'... No Probing for `Texas Instruments TMP451'... No Probing for `Texas Instruments AMC6821'... No Probing for `National Semiconductor LM95235'... No Probing for `National Semiconductor LM95245'... No Probing for `National Semiconductor LM63'... No Probing for `National Semiconductor LM96163'... 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 ADT7461A, ON Semiconductor NCT1008'... No Probing for `NXP/Philips SA56004'... No Probing for `Analog Devices ADT7481'... No Probing for `Fintek F75383S/M'... No Probing for `SMSC EMC1002'... No Probing for `SMSC EMC1023'... No Probing for `SMSC EMC1033'... No Probing for `SMSC EMC1043'... No Probing for `SMSC EMC1046'... No Probing for `SMSC EMC1053'... No Probing for `SMSC EMC1063'... No Probing for `SMSC EMC1072'... No Probing for `SMSC EMC1073'... No Probing for `SMSC EMC1074'... No Probing for `SMSC EMC1402'... No Probing for `SMSC EMC1403'... No Probing for `SMSC EMC1404'... No Probing for `SMSC EMC1422'... No Probing for `SMSC EMC1423'... No Probing for `SMSC EMC1424'... No Client found at address 0x50 Probing for `Analog Devices ADM1033'... No Probing for `Analog Devices ADM1034'... No Probing for `SPD EEPROM'... Yes (confidence 8, not a hardware monitoring chip) 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'... Yes (confidence 8, not a hardware monitoring chip) Client found at address 0x52 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) Next adapter: SMBus PIIX4 adapter port 2 at 0b00 (i2c-1) Do you want to scan it? (yes/NO/selectively): y Next adapter: SMBus PIIX4 adapter port 3 at 0b00 (i2c-2) Do you want to scan it? (yes/NO/selectively): y Next adapter: SMBus PIIX4 adapter port 4 at 0b00 (i2c-3) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 4 at 2d:00.0 (i2c-4) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 6 at 2d:00.0 (i2c-5) Do you want to scan it? (yes/NO/selectively): y Next adapter: NVIDIA i2c adapter 7 at 2d:00.0 (i2c-6) Do you want to scan it? (yes/NO/selectively): y Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `nct6775': * ISA bus, address 0xa20 Chip `Nuvoton NCT6797D Super IO Sensors' (confidence: 9) Driver `k10temp': * Chip `AMD Family 17h thermal sensors' (confidence: 9) Do you want to overwrite /etc/sysconfig/lm_sensors? (YES/no): y Unloading i2c-dev... OK I started ksensors after removing the ~/.kde/share/config/ksensorsrc file and it showed many sensors Thank you
i removed the ~/.kde/share/config/ksensorsrc file because ksensors did not show the new sensors after i updated lm_sensors. after it was deleted and kmsensors was run again the new sensors appeared
Indeed, KSensors likes to hardcode the sensors it found in its config file, so after running sensors-detect, you may have to delete the config file to get the newly detected sensors to show up in the UI.
would it be possible to update ksensors to add the ability to update its config file?
Theoretically, everything is possible, but in practice, I don't think it is reasonably doable. It is not clear how to detect that the configuration needs to be refreshed. And to be honest, I am glad that this application last released 15 years ago still works at all.
lm_sensors-3.5.0-6.fc30 has been pushed to the Fedora 30 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-caf20de424
lm_sensors-3.5.0-2.fc29 has been pushed to the Fedora 29 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-29eae8df8b
lm_sensors-3.5.0-6.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
lm_sensors-3.5.0-2.fc29 has been pushed to the Fedora 29 stable repository. If problems still persist, please make note of it in this bug report.