Chr1sch Posted December 1, 2023 Share Posted December 1, 2023 25-30W weniger heißt du bist mit Spindown "immer noch" bei ~30-35W idle? Wie sieht denn dein System aus, also Hardware? (Mobo, NT, Speicher, HDDs, NVMes etc) Quote Link to comment
alturismo Posted December 2, 2023 Share Posted December 2, 2023 9 hours ago, RandiGetSomeCandy said: Das Geraffel kam heute schon: Ausm Stand raus 25 - 30 Watt weniger. yep ... ist halt (leider) so ... AMD Systeme wollen halt einfach nicht ... 9 hours ago, RandiGetSomeCandy said: gut, dass ich noch in den 14 Tagen innerhalb des Kaufes der CPU und des Boards bin - auch wenn ich ein echt schlechtes Gewissen habe 😅 kannst du auch haben ... und die 14 Tage sind mit "Verbau" eh nur Kulanz des Händlers ... persönlich hoffe ich sogar dass der Quatsch mal aufhört, aber das ist jetzt ein ganz anderes Thema Quote Link to comment
mgutt Posted December 9, 2023 Author Share Posted December 9, 2023 On 8/17/2023 at 11:08 AM, Pillendreher said: Is this the way it should be though? As of right now, the CPU is not run by pstate but rather by corefreq itself. I thought the whole point of this was to run pstate? Den Teil verstehe ich nach wie vor nicht. Wenn der pstate Treiber von corefreq sparsamer sein sollte, warum wird das, was auch immer der Treiber besser macht, nicht in den Original amd_pstate Treiber übernommen. Für mich ergibt es keinen Sinn, wenn die Hardware das von sich aus können sollte, noch eine extra Software laufen lassen zu müssen. 🤨 Ich spiele übrigens auch gerade damit herum (B550i + 4750GE) und nach zig Einstellungen aus diesem Thread, stellt sich bei unRAID 6.12.4 heraus, dass ich nur diese eine Kernel Option benötige, um amd_pstate zu aktivieren: amd_pstate=passive Danach sieht man in cpufreq-info, dass er aktiv ist. Allerdings hat das genau gar keinen Effekt auf den Stromverbrauch, auch wenn man sieht, dass die Frequenzen runtergehen. Ich probiere jetzt mal verschiedene BIOS Optionen aus, denn wenn ich das richtig verstanden habe, muss ja von da aus, also hardware-seitig die pkg C-States gesteuert werden. Quote Link to comment
Hiko0 Posted December 18, 2023 Share Posted December 18, 2023 @mgutt Ich habe mich jetzt auch endlich mal an das Thema Stromsparen gesetzt. Ich habe in die Syslinux Config "amd_pstate=passive" eingefügt und neu gestartet. cpufreq-info zeigt mir Quote cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to [email protected], please. analyzing CPU 0: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 0 CPUs which need to have their frequency coordinated by software: 0 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.36%, 1.70 GHz:1.05%, 1.40 GHz:97.59% (2368) analyzing CPU 1: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 1 CPUs which need to have their frequency coordinated by software: 1 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.67%, 1.70 GHz:1.14%, 1.40 GHz:97.18% (2344) analyzing CPU 2: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 2 CPUs which need to have their frequency coordinated by software: 2 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.24%, 1.70 GHz:1.03%, 1.40 GHz:97.73% (2206) analyzing CPU 3: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 3 CPUs which need to have their frequency coordinated by software: 3 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.76%, 1.70 GHz:1.21%, 1.40 GHz:97.03% (1992) analyzing CPU 4: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 4 CPUs which need to have their frequency coordinated by software: 4 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.22%, 1.70 GHz:0.87%, 1.40 GHz:97.91% (2133) analyzing CPU 5: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 5 CPUs which need to have their frequency coordinated by software: 5 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.28%, 1.70 GHz:1.42%, 1.40 GHz:97.31% (1927) analyzing CPU 6: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 6 CPUs which need to have their frequency coordinated by software: 6 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.27%, 1.70 GHz:1.62%, 1.40 GHz:97.11% (2078) analyzing CPU 7: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 7 CPUs which need to have their frequency coordinated by software: 7 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.26%, 1.70 GHz:0.97%, 1.40 GHz:97.77% (1976) analyzing CPU 8: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 8 CPUs which need to have their frequency coordinated by software: 8 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:0.90%, 1.70 GHz:1.05%, 1.40 GHz:98.05% (1602) analyzing CPU 9: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 9 CPUs which need to have their frequency coordinated by software: 9 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:0.70%, 1.70 GHz:1.12%, 1.40 GHz:98.18% (1306) analyzing CPU 10: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 10 CPUs which need to have their frequency coordinated by software: 10 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:0.81%, 1.70 GHz:0.65%, 1.40 GHz:98.55% (1221) analyzing CPU 11: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 11 CPUs which need to have their frequency coordinated by software: 11 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:0.90%, 1.70 GHz:0.73%, 1.40 GHz:98.37% (1161) analyzing CPU 12: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 12 CPUs which need to have their frequency coordinated by software: 12 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:0.82%, 1.70 GHz:0.75%, 1.40 GHz:98.42% (1566) analyzing CPU 13: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 13 CPUs which need to have their frequency coordinated by software: 13 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:0.93%, 1.70 GHz:0.95%, 1.40 GHz:98.12% (1697) analyzing CPU 14: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 14 CPUs which need to have their frequency coordinated by software: 14 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:0.81%, 1.70 GHz:0.92%, 1.40 GHz:98.27% (1527) analyzing CPU 15: driver: acpi-cpufreq CPUs which run at the same hardware frequency: 15 CPUs which need to have their frequency coordinated by software: 15 maximum transition latency: 4294.55 ms. hardware limits: 1.40 GHz - 4.45 GHz available frequency steps: 3.60 GHz, 1.70 GHz, 1.40 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 1.40 GHz and 3.60 GHz. The governor "powersave" may decide which speed to use within this range. current CPU frequency is 1.40 GHz (asserted by call to hardware). cpufreq stats: 3.60 GHz:1.03%, 1.70 GHz:0.62%, 1.40 GHz:98.35% (1542) Ich gehe nicht davon aus, dass ich das Ganze richtig konfiguriert habe, wundere mich vor allem über die 1,40 GHz. Die CPU ist eine 4750G auf nem ASRock B550 Taichi. Quote Link to comment
Pillendreher Posted December 19, 2023 Share Posted December 19, 2023 On 12/9/2023 at 11:18 PM, mgutt said: Den Teil verstehe ich nach wie vor nicht. Wenn der pstate Treiber von corefreq sparsamer sein sollte, warum wird das, was auch immer der Treiber besser macht, nicht in den Original amd_pstate Treiber übernommen. Für mich ergibt es keinen Sinn, wenn die Hardware das von sich aus können sollte, noch eine extra Software laufen lassen zu müssen. 🤨 Ich spiele übrigens auch gerade damit herum (B550i + 4750GE) und nach zig Einstellungen aus diesem Thread, stellt sich bei unRAID 6.12.4 heraus, dass ich nur diese eine Kernel Option benötige, um amd_pstate zu aktivieren: amd_pstate=passive Danach sieht man in cpufreq-info, dass er aktiv ist. Allerdings hat das genau gar keinen Effekt auf den Stromverbrauch, auch wenn man sieht, dass die Frequenzen runtergehen. Ich probiere jetzt mal verschiedene BIOS Optionen aus, denn wenn ich das richtig verstanden habe, muss ja von da aus, also hardware-seitig die pkg C-States gesteuert werden. Kann bestätigen, dass "amd_pstate=passive" über cpufreq-info als angewandter Treiber angezeigt wird: root@Tower:~# cpufreq-info cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009 Report errors and bugs to [email protected], 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 2.88 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 563 MHz. 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 2.14 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 2.02 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 4.44 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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.45 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 3.21 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 3.55 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 3.55 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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.75 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 4.44 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: 20.0 us. hardware limits: 400 MHz - 4.46 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, per formance, 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 3.55 GHz. root@Tower:~# Mit allen Festplatten runtergefahren, zwei BD-Brennern (keiner aktiv) und zwei SSDs, einem 5600G, zwei RAM-Riegeln, einer Dell PERC H310 und 3x 140mm Lüftern komme ich so im Leerlauf auf ca. 35 W. Nicht so schlecht, aber auch nichts besonderes m.E. Quote Link to comment
Hiko0 Posted January 1 Share Posted January 1 (edited) @mgutt Wie laufen die Tests mit deinem Testsystem? Ich bekommen den amd-pstate nicht geladen. Folgende Einstellungen habe ich im BIOS des ASRock B550 Taichi vorgenommen: PM L1 SS = L1.1 Global C-state Control = Enabled CPPC CTRL = AUTO (bei Enabled kommen EPP Min/Max Range und Perf Limit Min/Max Range Werte, mit denen ich mich nicht auskenne) In der Syslinux CFG stehen Quote initcall_blacklist=acpi_cpufreq_init amd_pstate=passive ich hatte es auch nur mit amd_pstate=passive probiert, bzw. ein anderes command zum blacklisten des acpi-Treibers probiert. In der go-file steht direkt unterhalb von # Start the Management Utility /usr/local/sbin/emhttp & Quote modprobe amd_pstate Immerhin funktionier "powertop --auto-tune &>/dev/null" so, dass auch die HDD, die am verbauten ASM SATA-Chip hängt, wieder problemlos aus dem Ruhezustand aufwacht. Powertop zeigt mir leider nur bis C3 an. Ich komme so im idle aller Platten mit zwei verbauten 980 Pro 1 TB SSDs und vier 14 cm Noctua Lüftern auf ± 30W. Hat jemand eine Idee, woran es scheitert? Edited January 1 by Hiko0 Quote Link to comment
Pillendreher Posted January 7 Share Posted January 7 On 1/1/2024 at 11:49 AM, Hiko0 said: @mgutt Wie laufen die Tests mit deinem Testsystem? Ich bekommen den amd-pstate nicht geladen. Worin äußert sich das denn bei dir? Was zeigt er bei "cpufreq-info" an? 1 Quote Link to comment
Hiko0 Posted January 10 Share Posted January 10 (edited) On 1/7/2024 at 6:00 PM, Pillendreher said: Worin äußert sich das denn bei dir? Was zeigt er bei "cpufreq-info" an? Egal, was ich eingebe, er lädt trotz des Blacklistings den "acpi-cpufreq" und demnach zeigt er den auch mit "cpufreq-info" an. Den AMD pstate Treiber lädt er entsprechend auch nicht. Könntest Du mir mal Screenshots deiner Syslinux cfg und des go-file einstellen? Ich vermute, ich habe die Kommandos trotz mehrmaligem Gegenchecken falsch (Formatierung?) eingegeben. Edited January 10 by Hiko0 Quote Link to comment
BasWeg Posted January 10 Share Posted January 10 Also bei mir funktioniert es erst seit 6.12.6 (hatte vorher 6.11.5). Meine einzigste Änderung ist in sylinux cfg das amd_pstate=passive Im go file war kein modprobe nötig label Unraid OS menu default kernel /bzimage append rcu_nocbs=0-15 isolcpus=6-7,14-15 pcie_acs_override=downstream,multifunction initrd=/bzroot amd_pstate=passive vfio_iommu_type1.allow_unsafe_interrupts=1 video=efifb:off idle=halt Quote Link to comment
Pillendreher Posted January 11 Share Posted January 11 17 hours ago, Hiko0 said: Egal, was ich eingebe, er lädt trotz des Blacklistings den "acpi-cpufreq" und demnach zeigt er den auch mit "cpufreq-info" an. Den AMD pstate Treiber lädt er entsprechend auch nicht. Könntest Du mir mal Screenshots deiner Syslinux cfg und des go-file einstellen? Ich vermute, ich habe die Kommandos trotz mehrmaligem Gegenchecken falsch (Formatierung?) eingegeben. Steht nichts besonderes drinnen. Quote Link to comment
Hiko0 Posted January 13 Share Posted January 13 (edited) On 1/11/2024 at 12:26 PM, Pillendreher said: Steht nichts besonderes drinnen. Alter Falter. Es muss ein Formatierungsproblem gewesen sein. Ich hatte nach dem Kommentar von @mgutt direkt nur mit amd_pstate=passive gebootet und es funktionierte nicht. Und dann fing ich an, herum zu probieren. Jetzt, mit allen Bootargumenten in Syslinux config und go-file raus, wie bei Dir, funktioniert es. Kann es daran gelegen haben, dass ich in eine neue Zeile in der Syslinux config begonnen hatte? Naja, egal. Es funktioniert nun und Dein Post ist der erfolgreiche Abschluss einer wochenlangen Odyssee inkl. Bemühen des ASRock-Supports (der übrigens super schnell und gut ist). Danke! Zeigt Euch Powertop denn mehr als C3 an? Die höheren C-states fehlen bei mir noch, wenngleich nun unter "Frequency stats" sehr viel ausdifferenziertere clock speeds stehen, als zuvor (da waren es nur vier inkl. Idle). Edited January 13 by Hiko0 Quote Link to comment
mgutt Posted January 13 Author Share Posted January 13 6 hours ago, Hiko0 said: dass ich in eine neue Zeile in der Syslinux config begonnen hatte? Jo, das darfst du nicht machen. Aber wie gesagt, auch wenn ich die reduzierten Frequenzen sehen kann, haben sie keinerlei Einfluss auf den Stromverbrauch. Noch fehlt etwas, was dann auch die C-States runterbringt. Quote Link to comment
Pillendreher Posted January 15 Share Posted January 15 On 1/13/2024 at 8:34 AM, Hiko0 said: Zeigt Euch Powertop denn mehr als C3 an? Die höheren C-states fehlen bei mir noch, wenngleich nun unter "Frequency stats" sehr viel ausdifferenziertere clock speeds stehen, als zuvor (da waren es nur vier inkl. Idle). Ich hab diese bisher nur in Corefreq gesehen Da hast du dann aber die seltsame Situation, dass eigentlich Corefreq alles übernimmt und nicht der P-State-Treiber. Quote Link to comment
Pillendreher Posted February 1 Share Posted February 1 Die C-States in Corefreq sind wohl übrigens softwarebasiert, sofern ich diesen Beitrag richtig verstehe: https://github.com/cyring/CoreFreq/discussions/320#discussioncomment-8117677 Quote Link to comment
CyrIng Posted February 4 Share Posted February 4 On 2/1/2024 at 11:32 AM, Pillendreher said: Incidentally, the C-States in Corefreq are software-based, provided I understand this article correctly: https://github.com/cyring/CoreFreq/discussions/320#discussioncomment-8117677 Yes, software only with AMD With Intel, C-States come from directly hardware Why AMD does not specify its C-State counters ? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.