The commands listed at SDB:Radeon don't work for me

English Hardware
1

Absolutely none of the driver location or reversion commands listed at SDB:Radeon - openSUSE Wiki work for me:

lsmod | grep radeon

PS /home/rokejulianlockhart> lsmod | grep radeon
NativeCommandExitException: Program "grep" ended with non-zero exit code: 1.

modprobe radeon

PS /home/rokejulianlockhart> modprobe radeon               
modprobe: The term 'modprobe' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

cat /etc/modprobe.d/fglrx.conf

PS /home/rokejulianlockhart> cat /etc/modprobe.d/fglrx.conf
/usr/bin/cat: /etc/modprobe.d/fglrx.conf: No such file or directory
NativeCommandExitException: Program "cat" ended with non-zero exit code: 1.

which is weird as heck, since surely I must be running one of either of the drivers listed there, right?

At least

glxgears

image

works, although it doesn’t appear to specify which driver this demonstrates is in use.

I don’t know what to make of all of this.

2

Help us help you. We know nothing about your Radeon from anything you wrote here. Using the PRE icon above the input window here to reply, paste the whole input/output from inxi -GSaz run from a GUI terminal like Xterm or Konsole.

3

@mrmazda,

inxi -GSaz

image
image786×821 158 KB

PS /home/rokejulianlockhart> inxi -GSaz                                      
System:
  Kernel: 6.4.9-1-default arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.4.9-1-default
    root=UUID=01306e9f-2ee7-4144-8878-16b04ff549dc splash=silent
    resume=/dev/disk/by-uuid/7ffbb2f4-3e39-410c-9fea-48964cf2ccd1
    mitigations=auto quiet security=apparmor
  Desktop: KDE Plasma v: 5.27.7 tk: Qt v: 5.15.10 wm: kwin_x11 vt: 2
    dm: SDDM Distro: openSUSE Tumbleweed 20230813
Graphics:
  Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
    vendor: XFX Pine driver: amdgpu v: kernel arch: RDNA-1 code: Navi-1x
    process: TSMC n7 (7nm) built: 2019-20 pcie: gen: 4 speed: 16 GT/s
    lanes: 16 ports: active: DP-2 off: HDMI-A-1 empty: DP-1,DP-3
    bus-ID: 0a:00.0 chip-ID: 1002:731f class-ID: 0300
  Device-2: Logitech BRIO Ultra HD Webcam
    driver: hid-generic,snd-usb-audio,usbhid,uvcvideo type: USB rev: 3.1
    speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 2-4.4:4
    chip-ID: 046d:085e class-ID: 0300 serial: <filter>
  Display: x11 server: X.Org v: 21.1.8 with: Xwayland v: 23.1.2
    compositor: kwin_x11 driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: radeonsi gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 676x380mm (26.61x14.96")
    s-diag: 775mm (30.53")
  Monitor-1: DP-2 pos: primary model: AOC Q3279WG5B serial: <filter>
    built: 2019 res: 2560x1440 hz: 60 dpi: 90 gamma: 1.2
    size: 725x428mm (28.54x16.85") diag: 842mm (33.1") ratio: 15:9 modes:
    max: 2560x1440 min: 720x400
  Monitor-2: HDMI-A-1 mapped: HDMI-1 note: disabled model: Pi-X3
    serial: <filter> built: 2022 res: 2560x1440 dpi: 184 gamma: 1.2
    size: 609x355mm (23.98x13.98") diag: 604mm (23.8") ratio: 16:9 modes:
    max: 3840x2160 min: 640x480
  API: OpenGL v: 4.6 Mesa 23.1.5 renderer: AMD Radeon RX 5700 (navi10 LLVM
    16.0.6 DRM 3.52 6.4.9-1-default) direct-render: Yes
PS /home/rokejulianlockhart>

Thanks.

4

We’re also missing what drew you to that SDB page. What problem are you trying to correct?

Last modification time on that SDB page was about 4 years after your radeon was on the drawing boards. I’m not sure how much of it might still be applicable, but modprobe radeon is not an appropriate action for one as new as yours.

Inxi has reported your GPU is using the amdgpu kernel driver. This is optimal for the vast majority of modern Radeon users. Your GPU is using the modesetting DIX display device driver. This is the default, which may or may not be optimal for your use. The package xf86-video-amdgpu provides an amdgpu DDX display device driver, which you should give a try. This touches on the subjects of making such a change and what they do. If it’s not installed already, simply installing it should implement its use automatically with an X restart or reboot. If it is already installed, we need to find out why it is not in order to make the switch. Before we get into that, install it if it isn’t already, and report back.

1 Like
5

I want to install

Thanks, @mrmazda. I should have first confirmed I hadn’t fallen victim to X/Y.