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.