Pillendreher

Members
  • Posts

    106
  • Joined

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Pillendreher's Achievements

Apprentice

Apprentice (3/14)

3

Reputation

  1. Ich hab jetzt direkt an der Quelle nachgefragt: Blau bedeutet also unterstützt, Grün unterstützt+aktiviert. Keine Ahnung wieso das bei mir dann nicht aktiviert ist; muss mir meine BIOS Einstellungen noch einmal genauer anschauen...
  2. Thanks for clearing that up. Curious since I enabled it in my mainboard's BIOS (or at least I think I did) a week ago...I'll go and recheck.
  3. Quick question: What do the colours concerning the CPU's features at the bottom of the screen signify? E.g. @kdwg's screen shows "CPPC" as "green", yet mine shows it as "blue". What gives? Is "blue" better than "green"?
  4. Er dreht z.T. schon voll auf: Ich habe eher den Eindruck, dass z.T. die Last nicht wirklich "ankommt", muss aber zugeben, dass ich das bisher nie beobachtet habe.
  5. Also so ganz rund scheint das Ganze noch nicht zu laufen. Ich lasse gerade im Hintergrund den MKVToolnix-Docker eine fast 40 GB große MKV-Datei aufteilen und der Prozessor dümpelt so vor sich hin (selbst "ondemand" ändert nix): Auf "performance" ein wenig besser, aber selbst da schießt er nicht Richtung Turbo hoch... Das ist wahrscheinlich so nicht richtig, oder? EDIT: Vielleicht lastet auch der Docker selber nicht stark genug aus? MKVToolnix + Bilderimport per Lightroom in einer W10 VM: Aber so richtig voll über alle Kerne wird da immer noch nichts ausgelastet: Mal Prime95 ausprobieren 😄
  6. Oh, my bad. The forum jumped to the latest posts automatically and I stopped scrolling backwards after a the first couple. Sorry!
  7. 2.30, also das aktuelle. Ich schaue gleich mal, wo der Stick steckt. Ich hab jedenfalls noch nen Empfänger für die Funktastatur dran, um im BIOS rumspielen zu können, aber der muss in der Tat nicht dranhängen, den entferne ich gleich mal. EDIT: Stick steckt in einem USB 2.0 Anschluss (zumindest gehe ich davon aus, denn der verwendete Steckplatz ist nicht "blau"); hab den Funkempfänger entfernt, jedoch hat sich am ASPM Status nichts geändert. Auch der Leerlaufverbrauch liegt bei abgezogenem HDMI Kabel und entferntem Funkempfänger weiterhin bei ca. 20 W.
  8. Hab auf Powersave umgestellt. Hier corefreq und powertop zur selben Zeit: Als Mainboard kommt ein ASRock B550M Pro4 zum Einsatz.
  9. Anybody else stuck on this on 6.11.0 rc2? Already tried reinstalling, even deleted anything Nerdpack related on the flashdrive...
  10. Ja, hab das alles in nem UserScript drinnen, welches bei jedem Start ausgeführt wird. Auch deine 2.14 Version zeigt mir bei den "tunables" keine offenen Punkte mehr an. Komme im Moment so auf 20 W im Leerlauf mit schlafenden Festplatten. Laute corefreq-cli aber immer noch nur C1. Interessanterweise habe ich den modprobe Befehl jetzt auch in Userscripts und habe wohl jetzt nen anderen CPU governor?! root@Tower:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 1.60 GHz.
  11. Bei 6 von 11 Geräten wird "ASPM L1 Enabled" angezeigt. ASPM mit dem von Dir verlinkten Befehl zu forcieren ändert daran nichts. Ach, um CPPC gings! Ja, das habe ich im UEFI schon aktiviert!
  12. So, jetzt scheint zumindest der Treiber zu laufen: root@Tower:~# modprobe amd-pstate root@Tower:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: driver: amd-pstate CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.27 GHz. analyzing CPU 1: driver: amd-pstate CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.84 GHz. analyzing CPU 2: driver: amd-pstate CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.27 GHz. analyzing CPU 3: driver: amd-pstate CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.28 GHz. analyzing CPU 4: driver: amd-pstate CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.28 GHz. analyzing CPU 5: driver: amd-pstate CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.34 GHz. analyzing CPU 6: driver: amd-pstate CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.34 GHz. analyzing CPU 7: driver: amd-pstate CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.30 GHz. analyzing CPU 8: driver: amd-pstate CPUs which run at the same hardware frequency: 8 CPUs which need to have their frequency coordinated by software: 8 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.43 GHz. analyzing CPU 9: driver: amd-pstate CPUs which run at the same hardware frequency: 9 CPUs which need to have their frequency coordinated by software: 9 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 3.05 GHz. analyzing CPU 10: driver: amd-pstate CPUs which run at the same hardware frequency: 10 CPUs which need to have their frequency coordinated by software: 10 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.43 GHz. analyzing CPU 11: driver: amd-pstate CPUs which run at the same hardware frequency: 11 CPUs which need to have their frequency coordinated by software: 11 maximum transition latency: 131 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 400 MHz and 4.46 GHz. The governor "schedutil" may decide which speed to use within this range. current CPU frequency is 2.28 GHz. root@Tower:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver amd-pstate Und so sieht corefreq-cli aus:
  13. Dann hab ich das richtig gemacht, aber gedacht ich wäre im go-file unterwegs. Keine Ahnung wie ich darauf kam, wahrscheinlich Schlafmangel
  14. root@Tower:~# lscpu | grep "cppc" Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf rapl pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 x2apic movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate ssbd mba ibrs ibpb stibp vmmcall fsgsbase bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd cppc arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif v_spec_ctrl umip pku ospke vaes vpclmulqdq rdpid overflow_recov succor smca fsrm Ich sehe jetzt hier nichts, was auf amd_pstate hindeuten würde? EDIT: Hab mal testweise mein go-file angepasst (hoffe, dort gehört der Befehl hin): Unraid OS kernel /bzimage append initrd=/bzroot amd_pstate.replace=1 Aber der pstate-Treiber ist wohl trotzdem nicht aktiviert: root@Tower:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver acpi-cpufreq EDIT2: Das Blockieren des ACPI-Treibers nach dieser Anleitung funktioniert zwar, aber es wird dann nicht der neue, sondern gar kein Treiber mehr geladen: root@Tower:~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver cat: /sys/devices/system/cpu/cpu0/cpufreq/scaling_driver: No such file or directory root@Tower:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to cpufreq@vger.kernel.org, please. analyzing CPU 0: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 1: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 2: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 3: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 4: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 5: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 6: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 7: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 8: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 9: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 10: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms. analyzing CPU 11: no or unknown cpufreq driver is active on this CPU maximum transition latency: 4294.55 ms.