nassauer

has this issue been resolved in any way? threw out my ARC because of this.

the 8125 plugin driver. sorry for the confusion. I´ve been on the C10 hunt for weeks. Too long ;)

Success! Well, at least a bit. I did manage to get the 8125 driver allowing C10 by adding only "options r8125 aspm=1" to modprobe. Thanks to a user on page 15 of this thread, who has the same mainboard (Gigabyte B760M DS3H). The only small downside is that although copying FROM a share can achieve full 2.5be speeds, copying TO a share is maxing out at 70-80mb/s after doing "ethtool -K eth0 tso off gso off gro off". I also can download with docker filezilla at 120mb/s (gigabit internet) to a share. but well ... I think it´s a good tradeoff.

Kingston SM2267XT. An older drive I guess. Can´t remember in which of my old computers I found it.

Ah sorry. Somehow I did not expect Proxmox in here ;) I can relate to the Kingston problem. Found out the one I had does not do any ASPM. Now running two Samsung 980pro.

gotta try this over the weeekend. I can get into C10 if using kernel driver, but I get 20-30mb/s only. using ich777 driver gets me the speed, but system won´t go lower than C3.

I know the feeling. I have been doing some more testing and I´ve abandoned using the ARC for the moment. My C10 comes at some more cost though: the 2.5gbe speed I get from my Realtek onboard NIC is abysmal. Because I run on the stock kernel drivers and not the recommended ich777 drivers. When I install the RTL drivers I get sweet 2.5gbe speeds, but the system won´t go below C3, no matter what I do with any of the usual power saving commands. It shows as ASPM Enabled, but just won´t enter below C3. So getting into C10, now with two nvme, one even on the CPU lanes, comes with 20-20mb/s on the network. Not ideal I´d say. Maybe you should try the kernel network driver and try enabling ASPM with ASPM Helper plugin. At least you can rule out another culpirt, if it does not work.

Community ... help needed with ARC A380 GPU, which is preventing C10 System: Gigabyte B760M DS3H DDR4 Intel i3-12100 32GB Ram 4 x Toshiba N300 8TB (onboard sata ports) 1 x ASM1166 with flashed Bios 1 x Nvme (in chipset slot) 3 x Sata SSD 2 x BD Disc drives 3 x Fans controlled by Bios (can´t get them controlled reliably in unraid) PSU: Coolermaster NWE 400 Idle Wattage measured with a Tapo P110 plug: 27 Watt / C10 / spindown / Docker running I´d say not too shabby. A Watt or two remain to be shaved off by disableling the BD drives when not needed with a switch. And when I can I´ll swap the drives for bigger ones and reduce the amount of drives needed. It was a fight going for a week or two in between work and sleep. I´ve been trying to get my system past C3. Tried numerous clean unraid sticks and ubuntu and even went into SCEWIN, searched through all settings related to ASPM, PEG, DMI and whatnot. Willing to destroy my Bios and board flashed the editied bios file and was about to give up. Then took my USB unraid stick, removed all that was in go file and syslinux (only went with the usual "force" and suddenly my system went into C10. For no apparent reason, or at least for no reason I could point to. Lets say I´m quite happy with the outcome of 27 Watts. For the final battle I´ll need your help. I would like to install a Sparkle A380, but it won´t let the HW Package go past C3 again. It adds 15 Watts of idle. From what I´ve read it might be that 15 Watts is the lowest it will go anyway (no idea how Wolfgang did it). But if it prevents C10 I´ll be ditching the card and move it into my main computer for encoding tasks. Up until now I´ve tried: # ASPM Global Policy setzen echo powersave > /sys/module/pcie_aspm/parameters/policy echo performance > /sys/module/pcie_aspm/parameters/policy echo default > /sys/module/pcie_aspm/parameters/policy # Bridge 01:00.0: L1.2 Substates erzwingen (Register 1e4) setpci -s 01:00.0 1e4.l=425a000f # ARC 03:00.0: L1 Substates manuell aktivieren (Register 158 / 1a8) setpci -s 03:00.0 158.l=f setpci -s 03:00.0 1a8.l=f setpci -s 03:00.0 158.l # Common Clock (CommClk+) für Bridge und ARC erzwingen setpci -s 01:00.0 CAP_EXP+0x10.w=0040:0040 setpci -s 03:00.0 CAP_EXP+0x10.w=0040:0040 # PCIe Link Retrain setpci -s 01:00.0 CAP_EXP+0x10.w=0020:0020 # Link Speed auf Gen 3 (8GT/s) forcieren setpci -s 01:00.0 CAP_EXP+0x30.w=0003:000f # LTR (Latency Tolerance Reporting) deaktivieren setpci -s 01:00.0 0x400.l=0 setpci -s 03:00.0 0x400.l=0 # Root Port 00:01.0 ASPM L1 aktivieren setpci -s 00:01.0 CAP_EXP+0x10.w=0002:0003 setpci -s 00:01.0 1e4.l=425a000f Our AI friends tell me because the card is falsely reporting 1x speeds it can´t be done. What more information you need? taruga-diagnostics-20260126-0846.zip

Entschuldigt Leute. Ich war einfach Mega-gefrustet und habe das ganze Ding einfach bis gestern abgeschaltet und mich anderen Dingen gewidmet.

https://www.intel.com/content/www/us/en/support/articles/000094587/graphics.html its´s a bug

Moin Gemeinde. Sorry, wenn ich etwas hier vergesse, aber ich versuche seit Tagen meine A380 in unraid irgendwie zu nutzen. Eigentlich wollte ich sie als AV1 Encoder in ARM, aber da ging garnix. Testweise mit Handbrake rumgefummelt, nix zu machen. Tdarr ... hat sie zwar erkannt, aber lieber die iGPU genommen. Zum Schluss wollte ich es mit Immich probieren und habe auch noch die iGPU deaktiviert, sodass die ARC als card0 im System vorhanden ist. Aber immich openvinio .. nimmt nur die CPU. Auch ein extra installierter Container für machne-learning ... CPU. mittlerweile weiß nicht mehr weiter, Gemnini und Chat raten auch nur dummes Zeug. Ich füchte, meine halbe Config ist mittlerweile genauso Lost, wie ich. Unraid 7.2.3taruga-diagnostics-20260110-1240.zip ich habe es mit /dev/dri ... dev/dri/renderD128 ... sämtlichen Mappings von 128 auf 129 oder andersrum. Nichts klappt. Die Karte steckt im System, wird erkannt, aber kein Docker will mir ihr was anfangen.

Ja den Quadro hab ich auf dem Schirm. Es wurmt mich nur tierisch, dass das nicht funktioniert. Die HDD Temperaturen werden von Unraid korrekt gelesen und könnten zur Steuerung genutzt werden. Aber warum sich das Board da komplett quer stellt ... Wie gesagt: es hat mal funktioniert und seit einem Reboot nicht mehr. Sowas macht mich wahnsinnig.

Wie auch immer...ich habe mal einen anderen USB Stick mit frischem Unraid getestet und nur System Temp, Fan Control und it87 Treiber installiert. Aber auch da lassen sich die Lüfter nicht steuern. Schon wild, dass es irgendwann einmal funktioniert hat. Egal. Ich überlasse es jetzt dem Bios.

Ich glaube, dass ist irgendwie hoffnungslos. Ich hab Fan Control und CA System Temp deinstalliert, gigabyte wmi Blacklist, neu gestartet. sensors it8689-isa-0a40 Adapter: ISA adapter in0: 888.00 mV (min = +0.00 V, max = +3.06 V) in1: 2.03 V (min = +0.00 V, max = +3.06 V) in2: 2.04 V (min = +0.00 V, max = +3.06 V) in3: 2.05 V (min = +0.00 V, max = +3.06 V) in4: 36.00 mV (min = +0.00 V, max = +3.06 V) in5: 1.81 V (min = +0.00 V, max = +3.06 V) in6: 1.20 V (min = +0.00 V, max = +3.06 V) 3VSB: 3.34 V (min = +0.00 V, max = +6.12 V) Vbat: 3.10 V fan1: 1085 RPM (min = 0 RPM) fan2: 890 RPM (min = 0 RPM) fan3: 1418 RPM (min = 0 RPM) fan4: 597 RPM (min = 0 RPM) temp1: +32.0°C (low = +0.0°C, high = +127.0°C) sensor = thermistor temp2: +32.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +28.0°C (low = +127.0°C, high = +127.0°C) sensor = Intel PECI temp4: +29.0°C (low = +0.0°C, high = +127.0°C) sensor = thermistor temp5: +31.0°C (low = +0.0°C, high = +100.0°C) sensor = thermistor temp6: +30.0°C (low = +0.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM acpitz-acpi-0 Adapter: ACPI interface temp1: +16.8°C (crit = +20.8°C) temp2: +27.8°C (crit = +105.0°C) coretemp-isa-0000 Adapter: ISA adapter Package id 0: +29.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +26.0°C (high = +80.0°C, crit = +100.0°C) Core 1: +24.0°C (high = +80.0°C, crit = +100.0°C) Core 2: +22.0°C (high = +80.0°C, crit = +100.0°C) Core 3: +29.0°C (high = +80.0°C, crit = +100.0°C) root@Taruga:~# pwmconfig # pwmconfig version 3.6.0 This program will search your sensors for pulse width modulation (pwm) controls, and test each one to see if it controls a fan on your motherboard. Note that many motherboards do not have pwm circuitry installed, even if your sensor chip supports pwm. We will attempt to briefly stop each fan using the pwm controls. The program will attempt to restore each fan to full speed after testing. However, it is ** very important ** that you physically verify that the fans have been to full speed after the program has completed. Found the following devices: hwmon0 is acpitz hwmon1 is coretemp hwmon2 is it8689 Found the following PWM controls: hwmon2/pwm1 current value: 66 hwmon2/pwm1 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) n hwmon2/pwm2 current value: 0 hwmon2/pwm2 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon2/pwm3 current value: 200 hwmon2/pwm4 current value: 63 hwmon2/pwm4 is currently setup for automatic speed control. In general, automatic mode is preferred over manual mode, as it is more efficient and it reacts faster. Are you sure that you want to setup this output for manual control? (n) y hwmon2/pwm5 current value: 255 Giving the fans some time to reach full speed... Found the following fan sensors: hwmon2/fan1_input current speed: 1106 RPM hwmon2/fan2_input current speed: 627 RPM hwmon2/fan3_input current speed: 1415 RPM hwmon2/fan4_input current speed: 573 RPM Warning!!! This program will stop your fans, one at a time, for approximately 5 seconds each!!! This may cause your processor temperature to rise!!! If you do not want to do this hit control-C now!!! Hit return to continue: Testing pwm control hwmon2/pwm2 ... hwmon2/fan1_input ... speed was 1106 now 1106 no correlation hwmon2/fan2_input ... speed was 627 now 614 no correlation hwmon2/fan3_input ... speed was 1415 now 1415 no correlation hwmon2/fan4_input ... speed was 573 now 571 no correlation No correlations were detected. There is either no fan connected to the output of hwmon2/pwm2, or the connected fan has no rpm-signal connected to one of the tested fan sensors. (Note: not all motherboards have the pwm outputs connected to the fan connectors, check out the hardware database on http://www.almico.com/forumindex.php) taruga-diagnostics-20240620-1050.zip

Das gleiche Verhalten zeigt sich auch ohne Plugin. Ich werfe nochmal alles raus, versuche Blacklist vom wmi und probiere nclochmal.

WMI Treiber sind aktiv. Ich habe mal getestet, aber nichts zu machen: root@Taruga:~# cat /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm*_enable 1 2 2 2 0 root@Taruga:~# echo 1 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm*_enable bash: /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm*_enable: ambiguous redirect root@Taruga:~# echo 1 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm2_enable root@Taruga:~# echo 1 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm3_enable root@Taruga:~# cat /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm*_enable 1 1 1 2 0 root@Taruga:~# echo 1 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm4_enable root@Taruga:~# cat /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm4_enable 1 root@Taruga:~# ls -1 /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1* /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1 /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_auto_channels_temp /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_auto_point1_temp /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_auto_point1_temp_hyst /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_auto_point2_temp /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_auto_point3_temp /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_auto_slope /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_auto_start /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_enable /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm1_freq root@Taruga:~# sensors it8689-isa-0a40 Adapter: ISA adapter in0: 252.00 mV (min = +0.00 V, max = +3.06 V) in1: 2.03 V (min = +0.00 V, max = +3.06 V) in2: 2.04 V (min = +0.00 V, max = +3.06 V) in3: 2.05 V (min = +0.00 V, max = +3.06 V) in4: 36.00 mV (min = +0.00 V, max = +3.06 V) in5: 1.81 V (min = +0.00 V, max = +3.06 V) in6: 1.20 V (min = +0.00 V, max = +3.06 V) 3VSB: 3.34 V (min = +0.00 V, max = +6.12 V) Vbat: 3.10 V fan1: 1080 RPM (min = 0 RPM) Array Fan: 743 RPM (min = 0 RPM) Array Fan: 1418 RPM (min = 0 RPM) Array Fan: 571 RPM (min = 0 RPM) temp1: +32.0°C (low = +0.0°C, high = +127.0°C) sensor = thermistor temp2: +32.0°C (low = +127.0°C, high = +127.0°C) sensor = thermistor temp3: +29.0°C (low = +127.0°C, high = +127.0°C) sensor = Intel PECI temp4: +29.0°C (low = +0.0°C, high = +127.0°C) sensor = thermistor temp5: +31.0°C (low = +0.0°C, high = +100.0°C) sensor = thermistor temp6: +30.0°C (low = +0.0°C, high = +127.0°C) sensor = thermistor intrusion0: ALARM acpitz-acpi-0 Adapter: ACPI interface temp1: +16.8°C (crit = +20.8°C) MB Temp: +27.8°C (crit = +105.0°C) coretemp-isa-0000 Adapter: ISA adapter CPU Temp: +30.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +24.0°C (high = +80.0°C, crit = +100.0°C) Core 1: +25.0°C (high = +80.0°C, crit = +100.0°C) Core 2: +24.0°C (high = +80.0°C, crit = +100.0°C) Core 3: +30.0°C (high = +80.0°C, crit = +100.0°C) root@Taruga:~# cat /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm*_enable 1 1 1 1 0 root@Taruga:~# lsmod | grep wmi gigabyte_wmi 24576 0 wmi_bmof 16384 0 wmi 28672 3 video,gigabyte_wmi,wmi_bmof root@Taruga:~# modprobe -r gigabyte_wmi root@Taruga:~# lsmod | grep wmi wmi_bmof 16384 0 wmi 28672 2 video,wmi_bmof root@Taruga:~# cat /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm*_enable 1 1 1 1 0 root@Taruga:~# echo 128 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm3 root@Taruga:~# echo 128 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm4 root@Taruga:~# echo 255 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm4 root@Taruga:~# echo 255 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm2 root@Taruga:~# modeprobe it87 bash: modeprobe: command not found root@Taruga:~# modprobe it87 root@Taruga:~# echo 255 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm2 root@Taruga:~# echo 255 > /sys/devices/platform/it87.2624/hwmon/hwmon3/pwm2 bash: /sys/devices/platform/it87.2624/hwmon/hwmon3/pwm2: No such file or directory root@Taruga:~# echo 255 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm3 root@Taruga:~# echo 255 > /sys/devices/platform/it87.2624/hwmon/hwmon2/pwm2

Ich habe Auto Fan nochmal installiert, aber selbes Ergebnis. Es geht ums Verrecken nicht. Gestern habe ich noch die aktuellste Bios-Version geflasht. Insofern ist da alles auf "Anfang". Bei mir ist der Pfad /sys/devices/platform/it87.2624/hwmon/hwmon2/ ... aber es interessiert die Lüfter nicht ob echo 128 > oder 255 oder 0 ... oder ob pwmXY_enable. Ich hab auch #Chip Drivers in mein Go File hinzugefügt. Irgend etwas beisst sich da. Ich könnte mir vorstellen, dass es die Gigabyte WMI driver sind, aber ist auch nur so eine Idee.

# sensors-detect version 3.6.0 # System: Gigabyte Technology Co., Ltd. B760M DS3H DDR4 [Default string] # Kernel: 6.1.79-Unraid x86_64 # Processor: 12th Gen Intel(R) Core(TM) i3-12100 (6/151/5) 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... 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): 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'... Yes Found unknown chip with ID 0x8689 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): 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): Found unknown SMBus adapter 8086:7a23 at 0000:00:1f.4. Sorry, no supported PCI bus adapters found. Module i2c-dev loaded successfully. Next adapter: SMBus I801 adapter at efa0 (i2c-0) Do you want to scan it? (YES/no/selectively): 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) Next adapter: i915 gmbus dpa (i2c-1) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpb (i2c-2) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus dpc (i2c-3) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus tc1 (i2c-4) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus tc2 (i2c-5) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus tc3 (i2c-6) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus tc4 (i2c-7) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus tc5 (i2c-8) Do you want to scan it? (yes/NO/selectively): Next adapter: i915 gmbus tc6 (i2c-9) Do you want to scan it? (yes/NO/selectively): Next adapter: AUX USBC1/DDI TC1/PHY B (i2c-10) Do you want to scan it? (yes/NO/selectively): Next adapter: AUX USBC2/DDI TC2/PHY C (i2c-11) Do you want to scan it? (yes/NO/selectively): Next adapter: AUX USBC4/DDI TC4/PHY E (i2c-12) 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 `coretemp': * Chip `Intel digital thermal sensor' (confidence: 9) Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO): To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe coretemp /usr/bin/sensors -s #----cut here---- You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. Unloading i2c-dev... OK

Ich habe Autofan inzwischen x mal runtergeworfen und wieder installiert. Das Skript hatte ich zwischenzeitlich einfach ausprobiert. Immerhin reagieren die Lüfter insofern, als dass sie abschalten taruga-diagnostics-20240619-2106.zip

Ich hab wieder den halben Tag rumgedoktort, aber ohne Erfolg. Die Lüfter bleiben völlig unbeeindruckt von sämtlichen Kommandos. Ich würde gerne noch das hier testen: https://gist.github.com/bakman2/e801f342aaa7cade62d7bd54fd3eabd8 Aber ich such mir seit Stunden den Wolf nach 'make'.

Das Skript hatte ich im anderen Post hochgeladen. Das prüft auf jeden Fall, ob Mode 1 ist und wenn nicht, ändert es auf Mode 1. Anyway...man kann die Befehle zum Testen ja manuell eingeben und da tut sich rein garnichts. Ich checke mit sensors-detect und sensors, welche Lüfter überhaupt gefunden werden und versuch die dann anzusteuern. Oder eben mit 'pwmconfig' als Befehl.

Ja hab ich. Aber so richtig klappt es nicht. pwmconfig findet keine Correlationen und ist z.b. der Meinung, dass input_1 von pwm_2 gesteuert wird (so ähnlich). Ich teste heute Abend weiter.

Ja ich bleibe jetzt hier. Sorry. Ich war mir nicht sicher, wo das Thema gut aufgehoben ist. Vielleicht im it87 Support thread, vielleicht im Fan Control support thread ... und ich hab mir darüber einfach zu lang den Kopf zerbrochen und gesucht und gesucht. Ich bin nur ein Fahrlehrer und kein IT Mensch.

Ich hab nach mehreren Tagen, an denen ich mal Zeit hatte, mich damit zu beschäftigen, einfach ausprobiert, was mir das Internet so als mögiche Hinweise gegeben habt. Ich habe acpi_enforce wieder entfernt. Was mein Go-File angeht ... anders komme ich bislang nicht auf C8. Tut mir leid, wenn Dich das irgendwie stört. Was ich gemacht habe: ich habe tatsächlich nur das Gehäuse getauscht und die Lüfter-Konfiguration von 1x4Pin & 1x3Pin (auf 4Pin Kontakt) auf 2x4Pin Lüfter geändert. Vorher hat das mit Fan Control super funktioniert.

What could be the issue here: the driver does work, as it reports accurate RPM and temps, but the PWM percentage is 0. Can´t control the fans at all. The only time they react is when set to 100% in Bios and then running the script (attached). But with the script they just turn off and never back on. taruga-diagnostics-20240617-1329.zip Fan Script.txt