Cooler Control zeigt keine Lüfter an

[digdib]

Oh, jetzt habe ich was durcheinander gebraucht, ich dachte irgendwie, dass @Scully Arch Linux nutzt. Darum hatte ich auch den Link zum AUR genannt. Aber mit deinem Ubuntu kannst du auch deb Pakete installieren. So wie es in der Anleitung auf GitHub steht.

 

[Scully]

Bei Erzeugen des *deb Paketes kommt ein Fehler und es wird kein Paket erzeugt. Somit kann ich den 3.Befehl nicht ausführen?? Jemand eine Idee??

Spoiler: Ausführung mit Fehler

sed: /etc/fedora-release kann nicht gelesen werden: Datei oder Verzeichnis nicht gefunden
git --no-pager log \
--format='nct6687d-dkms (%ad) unstable; urgency=low%n%n * %s%n%n -- %aN <%aE> %aD%n' \
--date='format:%Y%m%d-%H%M%S' \

debian/changelog

sudo apt install -y debhelper dkms
Paketlisten werden gelesen… Fertig
Abhängigkeitsbaum wird aufgebaut… Fertig
Statusinformationen werden eingelesen… Fertig
debhelper ist schon die neueste Version (13.14.1ubuntu5).
dkms ist schon die neueste Version (3.0.11-1ubuntu13).
0 aktualisiert, 0 neu installiert, 0 zu entfernen und 1 nicht aktualisiert.
dpkg-buildpackage -b -rfakeroot -us -uc
dpkg-buildpackage: Warnung: Verwendung eines root-werde-Befehls, obwohl bereits root
dpkg-buildpackage: Information: Quellpaket nct6687d-dkms
dpkg-buildpackage: Information: Quellversion 20241105-084624
dpkg-buildpackage: Information: Quelldistribution unstable
dpkg-buildpackage: Information: Quelle geändert durch Frederic BOLTZ <frederic.boltz@gmail.com>
dpkg-buildpackage: Information: Host-Architektur amd64
dpkg-source --before-build .
fakeroot debian/rules clean
make[1]: Verzeichnis „/root/nct6687d“ wird betreten
dh clean --parallel --with dkms
dh: warning: Compatibility levels before 10 are deprecated (level 8 in use)
dh: error: unable to load addon dkms: Can't locate Debian/Debhelper/Sequence/dkms.pm in @inc (you may need to install the Debian:ebhelper::Sequence::dkms module) (@inc entries checked: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.38.2 /usr/local/share/perl/5.38.2 /usr/lib/x86_64-linux-gnu/perl5/5.38 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl-base /usr/lib/x86_64-linux-gnu/perl/5.38 /usr/share/perl/5.38 /usr/local/lib/site_perl) at (eval 3) line 1.
BEGIN failed--compilation aborted at (eval 3) line 1.

make[1]: *** [debian/rules:6: clean] Fehler 255
make[1]: Verzeichnis „/root/nct6687d“ wird verlassen
dpkg-buildpackage: Fehler: Unterprozess fakeroot debian/rules clean lieferte Exitstatus 2
make: *** [Makefile:75: deb] Fehler 2

 

[Marco01_809]

Hast du die Dependencies aus der README installiert?

apt-get install build-essential linux-headers-$(uname -r) dkms dh-dkms

Can't locate Debian/Debhelper/Sequence/dkms.pm in @inc (you may need to install the Debian::Debhelper::Sequence::dkms module). Das Modul ist wahrscheinlich durch dh-dkms paketiert.

 

[Scully]

@Marco01_809 : jetzt hat es geklappt. Was muss ich jetzt machen?

 

[mytosh]

echo "nct6687" | sudo tee -a /etc/modules-load.d/nct6687.conf

 

[Scully]

Hat leider nicht geholfen, Lüfter können weiterhin nicht gesteuert werden.

 

[digdib]

@Scully

Wurde das Modul auch geladen? Was kommt, wenn du mal folgendes ausführst?

grep -E "nct6687" /proc/modules

Und hast du mal den manuellen Modus versucht, so wie er auf GitHub beschrieben ist? Also erstmal herausfinden, welches Interface über das Modul bereitgestellt wird:

for d in /sys/class/hwmon/*; do echo "$d: $(cat "$d/name")"; done | grep nct6687

Die Ausgabe davon sollte ein Verzeichnisname sein, über den du mittels SysFS auf die Funktionen des Moduls zugreifen kannst. Klingt komplizierter als es ist. In diesem Verzeichnis sollten einige "pwm*_enable" Dateien sein, für jeden erkannten Lüfter eine. Also "pwm1_enable" für den ersten Lüfter und so weiter. In diesen Dateien sollte einfach "99" stehe, das bedeutet einfach automatische Lüftersteuerung.

Ist das bei dir vorhanden?

 

[Scully]

@digdib: Danke, mache ich wenn ich zu Hause bin...

 

[Scully]

@digdib :

grep -E "nct6687" /proc/modules -> keine Ausgabe in irgendeiner Form

for d in /sys/class/hwmon/*; do echo "$d: $(cat "$d/name")"; done | grep nct6687 -> Ergebniss:

/sys/class/hwmon/hwmon3: nct6687

In dem Ordner gibt es diese Dateien - da steht in einigen eine "90" drin, in anderen eine "99" und wieder andere haben "255" oder "128"...

 

[digdib]

Das ist jetzt etwas seltsam, wenn bei der ersten Ausgabe nichts kommt, dann heißt das eigentlich, dass das Modul gar nicht geladen ist!?!

Mach mal ein

sudo modprobe nct6687

kommt da irgend eine Fehlermeldung?

Ansonsten bin ich mir gerade nicht sicher, ob das

echo "nct6687" | sudo tee -a /etc/modules-load.d/nct6687.conf

richtig war. Bei Arch-Distros funktioniert das, bei Ubuntu weiß ich es nicht. Vielleicht solltest du mal folgendes probieren:

sudo sh -c 'echo "nct6687" >> /etc/modules'

 

[Scully]

sudo modprobe nct6687

Ergebniss:
modprobe: ERROR: could not insert 'nct6687': Key was rejected by service

sudo sh -c 'echo "nct6687" >> /etc/modules'

Ergebniss: nix

 

[digdib]

@Scully Kann es sein, dass du Secure Boot an hast? Dann werden selbstgebaute, unsignierte Module nicht geladen und dieser Fehler kommt.

 

[Scully]

@digdib : das abstellen von Secure boot führte zum Erfolg, allerdings zeigt mir Sensors Fehler an:

nct6687-isa-0a20
Adapter: ISA adapter
+12V: 12.05 V (min = -16.58 V, max = +12.08 V)
+5V: 5.11 V (min = +0.00 V, max = +20.48 V)
+3.3V: 3.36 V (min = +0.00 V, max = +4.09 V)
CPU Soc: 704.00 mV (min = +0.00 V, max = +4.09 V)
CPU Vcore: 678.00 mV (min = +0.00 V, max = +4.09 V)
CPU 1P8: 0.00 V (min = +0.00 V, max = +4.09 V)
CPU VDDP: 0.00 V (min = +0.00 V, max = +4.09 V)
DRAM: 1.24 V (min = +0.00 V, max = +8.19 V)
Chipset: 1.15 V (min = +0.00 V, max = +4.09 V)
CPU SA: 900.00 mV (min = +0.00 V, max = +4.09 V)
Voltage #2: 1.53 V (min = +0.00 V, max = +4.09 V)
AVCC3: 3.42 V (min = +0.00 V, max = +4.09 V)
AVSB: 3.36 V (min = +0.00 V, max = +4.09 V)
VBat: 1.06 V (min = +0.00 V, max = +4.09 V)
CPU Fan: 981 RPM (min = 0 RPM)
Pump Fan: 0 RPM (min = 0 RPM)
System Fan #1: 776 RPM (min = 0 RPM)
System Fan #2: 916 RPM (min = 901 RPM)
System Fan #3: 0 RPM (min = 0 RPM)
System Fan #4: 0 RPM (min = 0 RPM)
System Fan #5: 0 RPM (min = 0 RPM)
System Fan #6: 0 RPM (min = 0 RPM)
ERROR: Can't get value of subfeature fan9_input: Kernel interface error
ERROR: Can't get value of subfeature fan9_min: Kernel interface error
fan9: N/A (min = 0 RPM)
ERROR: Can't get value of subfeature fan10_input: Kernel interface error
ERROR: Can't get value of subfeature fan10_min: Kernel interface error
fan10: N/A (min = 0 RPM)
ERROR: Can't get value of subfeature temp1_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp1_crit: Kernel interface error
CPU: +33.5°C (low = +0.0°C)
(high = +255.5°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp1_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp2_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp2_crit: Kernel interface error
System: +37.5°C (low = +0.0°C)
(high = +255.5°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp2_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp3_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp3_crit: Kernel interface error
VRM MOS: +36.0°C (low = +0.0°C)
(high = +255.5°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp3_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp4_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp4_crit: Kernel interface error
PCH: +60.0°C (low = +0.0°C)
(high = +255.5°C, hyst = +0.0°C)
(crit = +0.0°C)
ERROR: Can't get value of subfeature temp5_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp5_crit: Kernel interface error
CPU Socket: +34.0°C (low = +0.0°C)
(high = +255.5°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp5_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp6_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp6_crit: Kernel interface error
PCIe x1: +18.0°C (low = +0.0°C)
(high = +255.5°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp6_type: Kernel interface error
(crit = +0.0°C) sensor = disabled
ERROR: Can't get value of subfeature temp7_max_hyst: Kernel interface error
ERROR: Can't get value of subfeature temp7_crit: Kernel interface error
M2_1: +31.5°C (low = +0.0°C)
(high = +255.5°C, hyst = +0.0°C)
ERROR: Can't get value of subfeature temp7_type: Kernel interface error
(crit = +0.0°C) sensor = disabled

 

[digdib]

@Scully Da bin ich jetzt leider etwas überfragt. Du könntest aber mal die lm_sensors Config löschen und sensors-detect nochmal neu aufrufen. Vorher aber überprüfen, ob das Modul auch geladen wurde. Die Config von lm_sensors sollte in /etc/conf.d/lm_sensors liegen, diese Datei einfach löschen.

 

[Scully]

Config Datei finde ich nicht, das Verzeichniss gibt es nicht...

 

[digdib]

Was kommen denn für Meldungen, wenn du einfach nochmal sensors-detect ausführst?

 

[Scully]

Spoiler: Sensors-detect

# sensors-detect version 3.6.0
# System: Micro-Star International Co., Ltd. MS-7D48 [2.0]
# Board: Micro-Star International Co., Ltd. PRO H610M-E DDR4 (MS-7D48)
# Kernel: 6.8.0-57-generic x86_64
# Processor: 12th Gen Intel(R) Core(TM) i5-12600K (6/151/2)

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
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 16h thermal sensors... No
AMD Family 17h thermal sensors... No
AMD Family 15h power sensors... No
AMD Family 16h power sensors... No
Hygon Family 18h thermal sensors... No
Intel digital thermal sensor... Success!
(driver `coretemp')
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 unknown chip with ID 0xd592

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
Found unknown SMBus adapter 8086:7aa3 at 0000:00:1f.4.
Sorry, no supported PCI bus adapters found.

Next adapter: SMBus I801 adapter at efa0 (i2c-0)
Do you want to scan it? (YES/no/selectively): y
Client found at address 0x50
Handled by driver `ee1004' (already loaded), chip type `ee1004'
(note: this is probably NOT a sensor 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)

Next adapter: i915 gmbus dpa (i2c-1)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpb (i2c-2)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus dpc (i2c-3)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc1 (i2c-4)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc2 (i2c-5)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc3 (i2c-6)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc4 (i2c-7)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc5 (i2c-8)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: i915 gmbus tc6 (i2c-9)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AUX A/DDI A/PHY A (i2c-10)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AUX USBC3/DDI TC3/PHY D (i2c-11)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AUX USBC4/DDI TC4/PHY E (i2c-12)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AMDGPU SMU 0 (i2c-13)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AMDGPU SMU 1 (i2c-14)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AMDGPU DM i2c hw bus 0 (i2c-15)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AMDGPU DM i2c hw bus 1 (i2c-16)
Do you want to scan it? (yes/NO/selectively): y

Next adapter: AMDGPU DM aux hw bus 0 (i2c-17)
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 `coretemp':
* Chip `Intel digital thermal sensor' (confidence: 9)

To load everything that is needed, add this to /etc/modules:
#----cut here----
# Chip drivers
coretemp
#----cut here----
If you have some drivers built into your kernel, the list above will
contain too many modules. Skip the appropriate ones!

Do you want to add these lines automatically to /etc/modules? (yes/NO)y
Successful!

Monitoring programs won't work until the needed modules are
loaded. You may want to run '/etc/init.d/kmod start'
to load them.

Unloading cpuid... OK