You are not logged in.
Hi all,
I run regular (once or twice a week) updates. Before updating a couple of days ago, lm_sensors and fancontrol were working fine on my AMD socket FM2 system. lm_sensors would show all the various temperatures and I could control fan speed.
For some reason, after the update, lm_sensors only show k10_temp and I'm not able to control any fan speed. Furthermore, find /sys -name '*pwm*' returns nothing.
Here is my pacman log:
# egrep '04-(10|11|12|13)' /var/log/pacman.log
[2013-04-10 01:30] [PACMAN] Running 'pacman -Syuw --noconfirm linux linux-headers'
[2013-04-10 01:30] [PACMAN] synchronizing package lists
[2013-04-10 01:30] [PACMAN] starting full system upgrade
[2013-04-11 01:30] [PACMAN] Running 'pacman -Syuw --noconfirm linux linux-headers'
[2013-04-11 01:30] [PACMAN] synchronizing package lists
[2013-04-11 01:30] [PACMAN] starting full system upgrade
[2013-04-12 01:30] [PACMAN] Running 'pacman -Syuw --noconfirm linux linux-headers'
[2013-04-12 01:30] [PACMAN] synchronizing package lists
[2013-04-12 01:30] [PACMAN] starting full system upgrade
[2013-04-12 03:14] [PACMAN] Running 'pacman -Syu'
[2013-04-12 03:14] [PACMAN] synchronizing package lists
[2013-04-12 03:14] [PACMAN] starting full system upgrade
[2013-04-12 03:14] [ALPM-SCRIPTLET] Generating locales...
[2013-04-12 03:14] [ALPM-SCRIPTLET] en_CA.UTF-8... done
[2013-04-12 03:14] [ALPM-SCRIPTLET] en_DK.UTF-8... done
[2013-04-12 03:14] [ALPM-SCRIPTLET] Generation complete.
[2013-04-12 03:14] [PACMAN] upgraded glibc (2.17-4 -> 2.17-5)
[2013-04-12 03:14] [PACMAN] upgraded binutils (2.23.2-1 -> 2.23.2-2)
[2013-04-12 03:14] [PACMAN] upgraded libcap (2.22-3 -> 2.22-4)
[2013-04-12 03:14] [PACMAN] upgraded libldap (2.4.34-1 -> 2.4.35-1)
[2013-04-12 03:14] [PACMAN] upgraded python-distribute (0.6.34-1 -> 0.6.36-1)
[2013-04-12 03:14] [PACMAN] upgraded systemd (200-1 -> 201-1)
[2013-04-12 03:14] [PACMAN] upgraded systemd-sysvcompat (200-1 -> 201-1)
[2013-04-13 03:17] [PACMAN] Running 'pacman -Syu'
[2013-04-13 03:17] [PACMAN] synchronizing package lists
[2013-04-13 03:17] [PACMAN] starting full system upgrade
[2013-04-13 03:17] [PACMAN] Running 'pacman -Syu'
[2013-04-13 03:17] [PACMAN] synchronizing package lists
[2013-04-13 03:17] [PACMAN] starting full system upgrade
[2013-04-13 03:17] [PACMAN] Running 'pacman -S catalyst-utils'
[2013-04-12 03:32] [PACMAN] Running 'pacman -S rrdtool'
[2013-04-12 03:32] [PACMAN] installed rrdtool (1.4.7-5)
[2013-04-12 03:33] [PACMAN] Running 'pacman -Sc --noconfirm'
[2013-04-12 16:56] [PACMAN] Running 'pacman -Syu'
[2013-04-12 16:56] [PACMAN] synchronizing package lists
[2013-04-12 16:56] [PACMAN] starting full system upgrade
[2013-04-12 16:59] [PACMAN] Running 'pacman -Syy'
[2013-04-12 16:59] [PACMAN] synchronizing package lists
[2013-04-12 16:59] [PACMAN] Running 'pacman -Sy'
[2013-04-12 16:59] [PACMAN] synchronizing package lists
[2013-04-12 16:59] [PACMAN] Running 'pacman -Syy'
[2013-04-12 16:59] [PACMAN] synchronizing package lists
[2013-04-12 17:00] [PACMAN] Running 'pacman -Syu'
[2013-04-12 17:00] [PACMAN] synchronizing package lists
[2013-04-12 17:00] [PACMAN] starting full system upgrade
[2013-04-12 17:00] [PACMAN] installed libbsd (0.4.2-1)
[2013-04-12 17:00] [PACMAN] upgraded libwbclient (3.6.13-1 -> 4.0.5-1)
[2013-04-12 17:00] [PACMAN] upgraded cifs-utils (5.9-1 -> 6.0-1)
[2013-04-12 17:00] [PACMAN] upgraded libkolabxml (0.8.3-2 -> 0.8.4-1)
[2013-04-12 17:00] [PACMAN] upgraded libkolab (0.4.1-1 -> 0.4.2-1)
[2013-04-12 17:00] [PACMAN] installed tevent (0.9.18-1)
[2013-04-12 17:00] [PACMAN] installed ldb (1.1.15-1)
[2013-04-12 17:00] [PACMAN] upgraded smbclient (3.6.13-1 -> 4.0.5-1)
[2013-04-12 17:00] [ALPM-SCRIPTLET] Major upgrade from samba 3.x to 4.x,
[2013-04-12 17:00] [ALPM-SCRIPTLET] please read the Samba4 migration guide:
[2013-04-12 17:00] [ALPM-SCRIPTLET] http://wiki.samba.org/index.php/Samba4/samba3upgrade/HOWTO
[2013-04-12 17:00] [PACMAN] upgraded samba (3.6.13-1 -> 4.0.5-1)
[2013-04-12 17:00] [PACMAN] upgraded sqlite (3.7.16.1-1 -> 3.7.16.2-1)
[2013-04-12 17:25] [PACMAN] Running 'pacman -Syu'
[2013-04-12 17:25] [PACMAN] synchronizing package lists
[2013-04-12 17:25] [PACMAN] starting full system upgrade
Last edited by solarwind (2013-04-13 08:44:43)
Offline
I'm noticed the same issue after systemd and systemd-sysvcompat update. lm_sensors failed to start.
systemd[1]: Unit lm_sensors.service entered failed state
systemd[1]: lm_sensors.service: main process exited, code=exited, status=1/FAILURE
Downgrade to systemd and systemd-sysvcompat of previous version (200) solve the issue.
Offline
I'm noticed the same issue after systemd and systemd-sysvcompat update. lm_sensors failed to start.
systemd[1]: Unit lm_sensors.service entered failed state systemd[1]: lm_sensors.service: main process exited, code=exited, status=1/FAILURE
Downgrade to systemd and systemd-sysvcompat of previous version (200) solve the issue.
Thanks, that solved it. Been having so many problems with Arch lately. The bugs are getting ridiculous.
Never had this many problems when we stuck to simple init scripts.
Offline
Hey Guys,
I am having same problem, also AMD FM2 set-up. Still quite a newbie to arch - how exactly do I go about "Downgrade to systemd and systemd-sysvcompat of previous version (200)"?
I would appreciate your response, as I had a fan-control service controlling the speed of my fan and now it runs on maximum pwm.... which makes a lot of noise...
Cheers,
Radbeefbaron
Offline
Run sensors-detect (as root), and note the kernel module for your missing sensors, then modprobe them and see if that brings your sensors back to life. If yes, add it to /etc/modules-load.d/
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# Board: ASRock FM2A85X-ITX
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):
Module cpuid loaded successfully.
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):
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):
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.
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: AMD Hudson-2 SMBus
Module i2c-dev loaded successfully.
Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
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 `Nuvoton NCT6776F Super IO Sensors' (confidence: 9)
Do you want to overwrite /etc/conf.d/lm_sensors? (YES/no):
Unloading i2c-dev... OK
Unloading cpuid... OK
I am pretty sure it was it87 before, but when I now try modprobe i get: ERROR: could not insert 'it87': No such device.
Offline
how exactly do I go about "Downgrade to systemd and systemd-sysvcompat of previous version (200)"?
To downgrade the packages
for x86_64 system
pacman -U /var/cache/pacman/pkg/systemd-200-1-x86_64.pkg.tar.xz /var/cache/pacman/pkg/systemd-sysvcompat-200-1-x86_64.pkg.tar.xz
for x86 system
pacman -U /var/cache/pacman/pkg/systemd-200-1-i686.pkg.tar.xz /var/cache/pacman/pkg/systemd-sysvcompat-200-1-i686.pkg.tar.xz
And then add
IgnorePkg = systemd systemd-sysvcompat
to
/etc/pacman.conf
Last edited by shyn (2013-04-13 15:51:01)
Offline
Thanks @ shyn, that worked like a charm. My fan is finally down to a bearable level
Offline