You are not logged in.
I am trying to auto disable my NVIDIA 1650 (Turing) when no needed to win some battery time since I have also integrated AMD video.
Following this manual https://wiki.archlinux.org/title/PRIME#NVIDIA in the end I receive that runtime_suspended_time is always 0 (which means something goes wrong).
Despite I did it carefully nothing worked. I tried nvidia-prime-rtd3pm just be sure. Also no effect.
OS: Arch Linux x86_64
Kernel: 6.7.9-arch1-1
Packages: 982 (pacman)
Shell: zsh 5.9
Resolution: 1920x1080
DE: Plasma 6.0.2
WM: kwin
Theme: Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [GTK2/3]
Terminal: konsole
CPU: AMD Ryzen 5 5500U with Radeon Graphics (12) @ 4.056GHz
GPU: NVIDIA GeForce GTX 1650 Mobile / Max-Q
GPU: AMD ATI 05:00.0 Lucienne
Memory: 4543MiB / 15324MiBecho "$XDG_SESSION_TYPE"
waylandnvidia-smi
Fri Mar 22 20:18:28 2024
+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 550.54.14 Driver Version: 550.54.14 CUDA Version: 12.4 |
|-----------------------------------------+------------------------+----------------------+
| GPU Name Persistence-M | Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap | Memory-Usage | GPU-Util Compute M. |
| | | MIG M. |
|=========================================+========================+======================|
| 0 NVIDIA GeForce GTX 1650 Off | 00000000:01:00.0 Off | N/A |
| N/A 38C P8 2W / 30W | 4MiB / 4096MiB | 0% Default |
| | | N/A |
+-----------------------------------------+------------------------+----------------------+
+-----------------------------------------------------------------------------------------+
| Processes: |
| GPU GI CI PID Type Process name GPU Memory |
| ID ID Usage |
|=========================================================================================|
| 0 N/A N/A 1302 G /usr/lib/Xorg 4MiB |
+-----------------------------------------------------------------------------------------+What am I missing?
The strange is a process name with Xorg.
Would appreciate any help.
Last edited by poznianski (2024-04-02 18:03:27)
Offline
Please use [code][/code] tags. Edit your post in this regard.
The strange is a process name with Xorg.
That's likley xwayland and "normal" - the display server is assigned to the GPU even if you're running on the IGP, speaking of which: do you have better results w/ plasma on X11?
Also nvidia-smi will wake the device for sure, only check the runtime_status
Have you confirmed that NVreg_DynamicPowerManagement is used by the module?
Also nb.
For Turing generation cards with Intel Coffee Lake or above CPUs as well as some Ryzen CPUs like the 5800H, it is possible to fully power down the GPU when not in useand https://us.download.nvidia.com/XFree86/ … sAndW6426e
systool -vm nvidiaOffline
do you have better results w/ plasma on X11
Wayland feels smoother and better overall.
Have you confirmed that NVreg_DynamicPowerManagement is used by the module?
systool -vm nvidia
Module = "nvidia"
Attributes:
coresize = "10022912"
initsize = "0"
initstate = "live"
refcnt = "33"
srcversion = "BABF5253924D36C48E7D170"
taint = "OE"
uevent = <store method only>
version = "550.54.14"
Sections:modinfo nvidia | grep NVreg_DynamicPowerManagement
parm: NVreg_DynamicPowerManagement:int
parm: NVreg_DynamicPowerManagementVideoMemoryThreshold:intWhich means the option was not applied.
Offline
cat /proc/driver/nvidia/gpus/0000:01:00.0/power
Runtime D3 status: Not supported
Video Memory: Active
GPU Hardware Support:
Video Memory Self Refresh: Not Supported
Video Memory Off: SupportedWhy? ![]()
Offline
Wayland feels smoother and better overall.
I meant for RTD3.
Why?
For Turing generation cards with Intel Coffee Lake or above CPUs as well as some Ryzen CPUs like the 5800H, it is possible to fully power down the GPU when not in use
Which means the option was not applied.
Modinfo can't tell you that but apparently nvidia still doesn't export the parameters to sysfs, check your journal - if you enable the serivces but forgot/failed to enable the parameters, the driver will complain about that.
If that's the case, chances are you've nvidia in the initramfs and forgot to regenerate that?
Offline
I meant for RTD3.
didn't try
For Turing generation cards with Intel Coffee Lake or above CPUs as well as some Ryzen CPUs like the 5800H, it is possible to fully power down the GPU when not in use
Yea, that's good news, I read it. Since you point it twice, you know the direct way how to do that?
chances are you've nvidia in the initramfs and forgot to regenerate that?
I did that after
mkinitcpio -PAs far as I understood it's a common problem https://forums.developer.nvidia.com/t/n … /250023/28
Offline
Journal:
Mar 24 16:19:41 arch kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw loglevel=3 cryptdevice=/dev/nvme0n1p3:volgroup0 quiet nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_DynamicPowerManagement=0x02
Mar 24 16:19:41 arch kernel: Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/volgroup0-lv_root rw loglevel=3 cryptdevice=/dev/nvme0n1p3:volgroup0 quiet nvidia_drm.modeset=1 nvidia_drm.fbdev=1 nvidia.NVreg_DynamicPowerManagement=0x02
Mar 24 16:19:41 arch kernel: nvidia: loading out-of-tree module taints kernel.
Mar 24 16:19:41 arch kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
Mar 24 16:19:41 arch kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 242
Mar 24 16:19:41 arch kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0003)
Mar 24 16:19:41 arch systemd-modules-load[651]: Inserted module 'nvidia_uvm'
Mar 24 16:19:41 arch kernel: nvidia-uvm: Loaded the UVM driver, major device number 234.
Mar 24 16:19:42 arch kernel: nvidia-modeset: Loading NVIDIA UNIX Open Kernel Mode Setting Driver for x86_64 550.54.14 Release Build (archlinux-builder@)
Mar 24 16:19:42 arch kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Mar 24 16:19:43 arch nvidia-persistenced[1012]: Started (1012)
Mar 24 16:19:44 arch kernel: nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
Mar 24 16:19:44 arch kernel: [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 1
Mar 24 16:19:44 arch kernel: nvidia 0000:01:00.0: [drm] No compatible format found
Mar 24 16:19:44 arch kernel: nvidia 0000:01:00.0: [drm] Cannot find any crtc or sizes
Mar 24 16:19:44 arch kernel: nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
Mar 24 16:19:44 arch kernel: nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
Mar 24 16:19:44 arch kernel: nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
Mar 24 16:19:45 arch kernel: nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
Mar 24 16:20:07 arch kernel: nvidia-modeset: WARNING: GPU:0: Correcting number of heads for current head configuration (0x00)
Mar 24 16:26:05 arch nvidia-powerd[3719]: nvidia-powerd version:1.0(build 1)
Mar 24 16:26:05 arch nvidia-powerd[3719]: Error open pid file 13
Mar 24 16:26:09 arch nvidia-powerd[3731]: nvidia-powerd version:1.0(build 1)
Mar 24 16:26:09 arch nvidia-powerd[3731]: Error open pid file 13Offline
Yea, that's good news, I read it. Since you point it twice, you know the direct way how to do that?
That point is that this is supported for SOME, but NOT necessarily for EVERY ryzen chip (incl. possibly yours)
W/ "nvidia.NVreg_DynamicPowerManagement=0x02" in the kernel commandline, the parameter is however set.
Make sure the udev rule actually applied.
cat /sys/bus/pci/devices/0000:01:00.0/power/control
cat /sys/bus/pci/devices/0000:01:00.0/power/runtime_statusAnd disable nvidia-powerd, it only works w/ ampere chips - https://download.nvidia.com/XFree86/Lin … boost.html
Edit: forgot to ask over the ryzen situation, do you remove the usb devices?
https://bbs.archlinux.org/viewtopic.php … 4#p2159544
Last edited by seth (2024-03-24 20:46:41)
Offline
cat /sys/bus/pci/devices/0000:01:00.0/power/control
on
~ cat /sys/bus/pci/devices/0000:01:00.0/power/runtime_status
active
~ cat /sys/bus/pci/devices/0000:01:00.0/power/runtime_suspended_time
0systemctl is-enabled nvidia-powerd
disabledIt was disabled.
But anyway I did
systemctl stop nvidia-powerd.service
systemctl disable nvidia-powerd.serviceEdit: forgot to ask over the ryzen situation, do you remove the usb devices?
Since the docs says its not requider for kernel >= 5.5 I skipped initially.
But I did that now
# Remove NVIDIA USB xHCI Host Controller devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c0330", ATTR{remove}="1"
# Remove NVIDIA USB Type-C UCSI devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c8000", ATTR{remove}="1"
# Remove NVIDIA Audio devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x040300", ATTR{remove}="1"nothing changed
Last edited by poznianski (2024-03-25 15:01:05)
Offline
but now however don't see anything regarding nvidia-powerd in the journal
journalctl -g nvidia
Mar 12 15:36:53 MiWiFi-R3-srv kernel: nvidia-modeset: WARNING: GPU:0: Corr
ecting number of heads for current head configuration (0x00)
Mar 12 15:36:54 MiWiFi-R3-srv kernel: nvidia-modeset: WARNING: GPU:0: Corr
ecting number of heads for current head configuration (0x00)
Mar 12 15:37:05 MiWiFi-R3-srv kernel: nvidia-modeset: WARNING: GPU:0: Corr
ecting number of heads for current head configuration (0x00)
Mar 12 16:06:14 MiWiFi-R3-srv kernel: nvidia-modeset: WARNING: GPU:0: Corr
ecting number of heads for current head configuration (0x00)
Mar 12 16:08:14 MiWiFi-R3-srv kernel: nvidia-modeset: WARNING: GPU:0: Corr
ecting number of heads for current head configuration (0x00)
Mar 12 16:18:55 MiWiFi-R3-srv kernel: nvidia-modeset: WARNING: GPU:0: Corr
ecting number of heads for current head configuration (0x00)
Mar 12 16:42:29 MiWiFi-R3-srv kernel: nvidia-modeset: WARNING: GPU:0: Corr
ecting number of heads for current head configuration (0x00)
-- Boot b0cba270de1d4b81a2d2872e21b193db --
Mar 12 16:59:44 archlinux kernel: nvidia: loading out-of-tree module taint
s kernel.
Mar 12 16:59:44 archlinux kernel: nvidia: module license 'NVIDIA' taints k
ernel.
Mar 12 16:59:44 archlinux kernel: nvidia: module verification failed: signature and/or
required key missing - tainting kernel
Mar 12 16:59:44 archlinux kernel: nvidia: module license taints kernel.
Mar 12 16:59:45 archlinux kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 508
Mar 12 16:59:45 archlinux kernel: nvidia 0000:01:00.0: enabling device (0000 -> 0003)
Mar 12 16:59:45 archlinux kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel
Module 550.54.14 Thu Feb 22 01:44:30 UTC 2024
Mar 12 16:59:45 archlinux kernel: nvidia_uvm: module uses symbols nvUvmIntOffline
It was disabled.
And still was running…
cat /sys/bus/pci/devices/0000:01:00.0/power/control
onYou want that to say "auto", please post your entire udev rule.
https://wiki.archlinux.org/title/Udev#T … re_loading
Offline
Somehow there was not a conf file in /etc/udev. I created it again.
Now I managed to get 'auto'.
sudo udevadm test /sys/class/drm/card1
This program is for debugging only, it does not run any program
specified by a RUN key. It may show incorrect results, because
some values may be different, or not available at a simulation run.
Trying to open "/etc/systemd/hwdb/hwdb.bin"...
Trying to open "/etc/udev/hwdb.bin"...
Trying to open "/usr/lib/systemd/hwdb/hwdb.bin"...
Trying to open "/usr/lib/udev/hwdb.bin"...
=== trie on-disk ===
tool version: 255
file size: 12553028 bytes
header size 80 bytes
strings 2586460 bytes
nodes 9966488 bytes
Loading kernel module index.
Found cgroup2 on /sys/fs/cgroup/, full unified hierarchy
Found container virtualization none.
Using default interface naming scheme 'v255'.
Parsed configuration file "/usr/lib/systemd/network/99-default.link"
Created link configuration context.
Reading rules file: /usr/lib/udev/rules.d/01-md-raid-creating.rules
Reading rules file: /usr/lib/udev/rules.d/10-dm.rules
Reading rules file: /usr/lib/udev/rules.d/11-dm-lvm.rules
Reading rules file: /usr/lib/udev/rules.d/13-dm-disk.rules
Reading rules file: /usr/lib/udev/rules.d/39-usbmuxd.rules
Reading rules file: /usr/lib/udev/rules.d/40-usb-media-players.rules
Reading rules file: /usr/lib/udev/rules.d/45-i2c-tools.rules
Reading rules file: /usr/lib/udev/rules.d/50-udev-default.rules
Reading rules file: /usr/lib/udev/rules.d/60-autosuspend.rules
Reading rules file: /usr/lib/udev/rules.d/60-block.rules
Reading rules file: /usr/lib/udev/rules.d/60-cdrom_id.rules
Reading rules file: /usr/lib/udev/rules.d/60-ddcutil-i2c.rules
Reading rules file: /usr/lib/udev/rules.d/60-ddcutil-usb.rules
Reading rules file: /usr/lib/udev/rules.d/60-dmi-id.rules
Reading rules file: /usr/lib/udev/rules.d/60-drm.rules
Reading rules file: /usr/lib/udev/rules.d/60-evdev.rules
Reading rules file: /usr/lib/udev/rules.d/60-fido-id.rules
Reading rules file: /usr/lib/udev/rules.d/60-infiniband.rules
Reading rules file: /usr/lib/udev/rules.d/60-input-id.rules
Reading rules file: /usr/lib/udev/rules.d/60-nvidia.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-input.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-mtd.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage-tape.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-storage.rules
Reading rules file: /usr/lib/udev/rules.d/60-persistent-v4l.rules
Reading rules file: /usr/lib/udev/rules.d/60-rfkill.rules
Reading rules file: /usr/lib/udev/rules.d/60-sensor.rules
Reading rules file: /usr/lib/udev/rules.d/60-serial.rules
Reading rules file: /usr/lib/udev/rules.d/60-tpm-udev.rules
Reading rules file: /usr/lib/udev/rules.d/63-md-raid-arrays.rules
Reading rules file: /usr/lib/udev/rules.d/64-btrfs.rules
Reading rules file: /usr/lib/udev/rules.d/64-md-raid-assembly.rules
Reading rules file: /usr/lib/udev/rules.d/65-libwacom.rules
Reading rules file: /usr/lib/udev/rules.d/69-dm-lvm.rules
Reading rules file: /usr/lib/udev/rules.d/69-libftdi.rules
Reading rules file: /usr/lib/udev/rules.d/69-libmtp.rules
Reading rules file: /usr/lib/udev/rules.d/69-md-clustered-confirm-device.rules
Reading rules file: /usr/lib/udev/rules.d/70-camera.rules
Reading rules file: /usr/lib/udev/rules.d/70-infrared.rules
Reading rules file: /usr/lib/udev/rules.d/70-joystick.rules
Reading rules file: /usr/lib/udev/rules.d/70-memory.rules
Reading rules file: /usr/lib/udev/rules.d/70-mouse.rules
Reading rules file: /usr/lib/udev/rules.d/70-power-switch.rules
Reading rules file: /usr/lib/udev/rules.d/70-steam-input.rules
Reading rules file: /usr/lib/udev/rules.d/70-steam-vr.rules
Reading rules file: /usr/lib/udev/rules.d/70-touchpad.rules
Reading rules file: /usr/lib/udev/rules.d/70-uaccess.rules
Reading rules file: /usr/lib/udev/rules.d/71-seat.rules
Reading rules file: /usr/lib/udev/rules.d/73-seat-late.rules
Reading rules file: /usr/lib/udev/rules.d/75-net-description.rules
Reading rules file: /usr/lib/udev/rules.d/75-probe_mtd.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-broadmobi-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-cinterion-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-dell-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-dlink-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-ericsson-mbm.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-fibocom-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-foxconn-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-gosuncn-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-haier-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-huawei-net-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-linktop-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-longcheer-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-mtk-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-nokia-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-qcom-soc.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-quectel-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-sierra.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-simtech-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-telit-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-tplink-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-ublox-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-x22x-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/77-mm-zte-port-types.rules
Reading rules file: /usr/lib/udev/rules.d/78-sound-card.rules
Reading rules file: /usr/lib/udev/rules.d/80-drivers.rules
Reading rules file: /usr/lib/udev/rules.d/80-libinput-device-groups.rules
Reading rules file: /usr/lib/udev/rules.d/80-mm-candidate.rules
Reading rules file: /usr/lib/udev/rules.d/80-net-setup-link.rules
Reading rules file: /etc/udev/rules.d/80-nvidia-pm.rules
Reading rules file: /usr/lib/udev/rules.d/80-udisks2.rules
Reading rules file: /usr/lib/udev/rules.d/81-net-dhcp.rules
Reading rules file: /usr/lib/udev/rules.d/84-nm-drivers.rules
Reading rules file: /usr/lib/udev/rules.d/85-nm-unmanaged.rules
Reading rules file: /usr/lib/udev/rules.d/85-tlp.rules
Reading rules file: /usr/lib/udev/rules.d/90-bolt.rules
Reading rules file: /usr/lib/udev/rules.d/90-iocost.rules
Reading rules file: /usr/lib/udev/rules.d/90-libinput-fuzz-override.rules
Reading rules file: /usr/lib/udev/rules.d/90-nm-thunderbolt.rules
Reading rules file: /usr/lib/udev/rules.d/90-pipewire-alsa.rules
Reading rules file: /usr/lib/udev/rules.d/90-vconsole.rules
Reading rules file: /usr/lib/udev/rules.d/95-dm-notify.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-hid.rules
Reading rules file: /usr/lib/udev/rules.d/95-upower-wup.rules
Reading rules file: /usr/lib/udev/rules.d/96-e2scrub.rules
Reading rules file: /usr/lib/udev/rules.d/99-fuse.rules
Reading rules file: /usr/lib/udev/rules.d/99-fuse3.rules
Reading rules file: /etc/udev/rules.d/99-nvidia-remove-devices.rules
Reading rules file: /usr/lib/udev/rules.d/99-systemd.rules
Reading rules file: /usr/lib/udev/rules.d/wacom.rules
card1: /usr/lib/udev/rules.d/50-udev-default.rules:51 GROUP 985
card1: /usr/lib/udev/rules.d/60-drm.rules:3 Importing properties from results of builtin command 'path_id'
card1: /usr/lib/udev/rules.d/60-drm.rules:6 Added SYMLINK 'dri/by-path/pci-0000:01:00.0-card'
card1: /usr/lib/udev/rules.d/73-seat-late.rules:16 RUN 'uaccess'
card1: Preserve permissions of /dev/dri/card1, uid=0, gid=985, mode=0660
card1: Successfully created symlink '/dev/char/226:1' to '/dev/dri/card1'
card1: sd-device: Created db file '/run/udev/data/c226:1' for '/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card1'
DEVPATH=/devices/pci0000:00/0000:00:01.1/0000:01:00.0/drm/card1
DEVNAME=/dev/dri/card1
DEVTYPE=drm_minor
MAJOR=226
MINOR=1
ACTION=add
SUBSYSTEM=drm
TAGS=:seat:uaccess:master-of-seat:
ID_PATH=pci-0000:01:00.0
ID_PATH_TAG=pci-0000_01_00_0
DEVLINKS=/dev/dri/by-path/pci-0000:01:00.0-card
CURRENT_TAGS=:seat:uaccess:master-of-seat:
ID_FOR_SEAT=drm-pci-0000_01_00_0
USEC_INITIALIZED=22075597
run: 'uaccess'
Unload kernel module index.
Unloaded link configuration context.Offline
It wasn't there because nobody put it there ![]()
Any discernible impact on the concerned situation?
Offline
It wasn't there because nobody put it there
Well, I did it. I guess it was deleted when I removed nvidia-prime-rtd3pm package.
Any discernible impact on the concerned situation?
No. It didn't effect anything.
Can you please confirm this is correct for my case?
/etc/mkinitcpio.conf
MODULES=(nvidia nvidia_modeset nvidia_drm)Offline
You don't need the modules in the initramfs for this to work.
"cat /proc/driver/nvidia/gpus/0000:01:00.0/power" still says "not supported"?
Offline
You don't need the modules in the initramfs for this to work.
I should set MODULES=() ?
"cat /proc/driver/nvidia/gpus/0000:01:00.0/power" still says "not supported"?
Yes.
cat /proc/driver/nvidia/gpus/0000:01:00.0/power
Runtime D3 status: Not supported
Video Memory: Active
GPU Hardware Support:
Video Memory Self Refresh: Not Supported
Video Memory Off: SupportedLast edited by poznianski (2024-03-25 21:32:32)
Offline
Based on this https://forums.developer.nvidia.com/t/n … poznianski my CPU should support RD3. I have Ryzen 5500U.
Last edited by poznianski (2024-03-25 21:36:29)
Offline
It's fine to add the modules to the initramfs and will prevent the GUI from starting "too early", but it's not relevant to this topc.
there’s no official docs from nvidia regarding D3 on ryzen, it seems it only works on ryzen 5xxx models
Which is speculative and inconclusive (as is the arch wiki) because "there’s no official docs from nvidia regarding D3 on ryzen" - you can also flat-out ask there, "hey, nvidia - is my CPU supported and why is there no official list"
All indication so far is that it's not - you could test against a driver regression (older nvidia drivers - 535xx, 545xx a 550xx all had their hiccups. nb. that older dkms packages will not compile against linux 6.8, you'd have to patch them or test the LTS kernel) or wait for future releases.
Edit: "inconclusive" as is does not state "on all 5xxxx models"
Last edited by seth (2024-03-25 21:42:13)
Offline
Got it. Thanks for you help. I will add an info here if I get something.
Offline
To pile onto this, the wiki mentions "some Ryzen CPUs like the 5800H" which is a https://en.wikipedia.org/wiki/Zen_3 while you've a 5500U https://en.wikipedia.org/wiki/Zen_2 what might be a significant difference here (and the way hardware is labeled by amd, intel and nvidia these days should be punishable by public slapping or something like that)
Offline
Today I did
cat /sys/bus/pci/devices/0000:01:00.0/power/controland it shows 'on' again, instead of 'auto'. I dunno why. Despite the conf files are in place this time. How to debug?
Last edited by poznianski (2024-03-26 12:03:47)
Offline
Reading rules file: /etc/udev/rules.d/99-nvidia-remove-devices.rulesWhat is this?
Offline
You asked me about USB. I created such file
# Remove NVIDIA USB xHCI Host Controller devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c0330", ATTR{remove}="1"
# Remove NVIDIA USB Type-C UCSI devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x0c8000", ATTR{remove}="1"
# Remove NVIDIA Audio devices, if present
ACTION=="add", SUBSYSTEM=="pci", ATTR{vendor}=="0x10de", ATTR{class}=="0x040300", ATTR{remove}="1"Offline
/etc/udev/rules.d/80-nvidia-pm.rules looks like https://wiki.archlinux.org/title/PRIME#NVIDIA ?
What if you remove the unbinding parts?
Do you use anything like optimus-manager, bbswitch etc et pp.?
Offline
/etc/udev/rules.d/80-nvidia-pm.rules looks like https://wiki.archlinux.org/title/PRIME#NVIDIA ?
Yes, exactly.
What if you remove the unbinding parts?
Removed that file. Nothing changed.
Do you use anything like optimus-manager, bbswitch etc et pp.?
No
Offline