Open pachof opened 10 months ago
my system is holo iso
What card exactly?
I got confused, it's not a Radeon R9, it's a Radeon r2, exactly the amd Radeon r2 with e1-6010
El jue, 11 ene 2024, 5:10 a. m., Joshie @.***> escribió:
What card exactly?
— Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/gamescope/issues/1094#issuecomment-1886777183, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUJ55E6CKH2DHD3XYQOKER3YN6275AVCNFSM6AAAAABBVZ4AC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBWG43TOMJYGM . You are receiving this because you authored the thread.Message ID: @.***>
If anything is Sea Islands, it is the architecture. And when running in KDE, gamescope runs without problems but when run from sddm it does not start
I also have this issue, with the Radeon R7770 (Southern Islands). I put amdgpu.si_support=1 in the kernel args but still not working.
I ran into the same error with my Radeon RX560. Here's what I found in the /run/user/1000/gamescope-session.log:
vulkan: selecting physical device 'AMD Radeon RX 560 Series (RADV POLARIS11)': queue family 1 (general queue family 0)
vulkan: physical device does not support DRM format modifiers
wlserver: [backend/headless/backend.c:67] Creating headless backend
wlserver: [libseat] [libseat/backend/seatd.c:64] Could not connect to socket /run/seatd.sock: No such file or directory
wlserver: [libseat] [libseat/libseat.c:76] Backend 'seatd' failed to open seat, skipping
wlserver: [libseat] [libseat/libseat.c:73] Seat opened with backend 'logind'
wlserver: [backend/session/session.c:109] Successfully loaded libseat session
drm: opening DRM node '/dev/dri/card1'
drm: drmSetClientCap(ATOMIC) failed
Failed to create backend.
My computer is running HoloISO. Here’s the output from uname -a
:
Linux holoiso 6.7.4-holoiso-beta_lljy-kernel-lljy-g76a2d2abfbba #2 SMP PREEMPT_DYNAMIC Sat, 09 Mar 2024 14:41:45 +0000 x86_64 GNU/Linux
[root@holoiso /]# neofetch
.,,,,. root@holoiso
.,'onNMMMMMNNnn',. ------------
.'oNMANKMMMMMMMMMMMNNn'. OS: SteamOS Holo x86_64
.'ANMMMMMMMXKNNWWWPFFWNNMNn. Host: H110N
;NNMMMMMMMMMMNWW'' ,.., 'WMMM, Kernel: 6.7.4-holoiso-beta_lljy-kernel-lljy-g76a2d2abfbba
;NMMMMV+##+VNWWW' .+;'':+, 'WMW, Uptime: 35 mins
,VNNWP+######+WW, +: :+, +MMM, Packages: 868 (pacman)
'+#############, +. ,+' +NMMM Shell: bash 5.1.16
'*#########*' '*,,*' .+NMMMM. Resolution: 1920x1080
`'*###*' ,.,;###+WNM, CPU: Intel Pentium G4560 (4) @ 3.5GHz
.,;;, .;##########+W GPU: AMD ATI Radeon RX 550 640SP / RX 560/560X
,',. '; ,+##############' Memory: 0.29GiB / 7.72GiB (3%)
'###+. :,. .,; ,###############'
'####.. `'' .,###############'
'#####+++################'
'*##################*'
''*##########*''
''''''
If you need more information, just let me know.
UPD: Forgot to mention that I need to use amdgpu.dc=0
to make GPU work on any system (incl. Ubuntu 20.04, 22.04, Arch Linux 2020+, etc.). Maybe this is the root of the issue.
I made a simple C program and shared it in a gist to show the issue I'm facing. To get it to run on my system, I had to switch from /dev/dri/card0 to /dev/dri/card1.
Here’s the gist: https://gist.github.com/3ap/db40f820e42454347361159d27509cd3
When I run the program, this is what I get:
drmSetClientCap(3, DRM_CLIENT_CAP_ATOMIC, 1) = -1
errno = 95
The error code 95 stands for EOPNOTSUPP.
According to the documentation at https://dri.freedesktop.org/docs/drm/gpu/drm-uapi.html#c.DRM_CLIENT_CAP_ATOMIC:
If the driver doesn’t support atomic mode-setting, enabling this capability will fail with -EOPNOTSUPP.
Does this mean GameScope will never work for me?
Polaris should be AMDGPU kernel driver, and should support ATOMIC just fine. You must have done something weird with your setup.
Oh, amdgpu.dc=0
, yes you need AMDGPU DC for atomic to work. You are correct that that is the root cause of the issue.
sorry for not responding in time, I was in my studies, I'm going to try that script and that commandline
El lun., 29 de abr. de 2024, 8:45 p. m., Joshie @.***> escribió:
Oh, amdgpu.dc=0, yes you need AMDGPU DC for atomic to work. You are correct that that is the root cause of the issue.
— Reply to this email directly, view it on GitHub https://github.com/ValveSoftware/gamescope/issues/1094#issuecomment-2084118450, or unsubscribe https://github.com/notifications/unsubscribe-auth/AUJ55E2AF6H7BKG63GOQLVDY73ZSBAVCNFSM6AAAAABBVZ4AC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBUGEYTQNBVGA . You are receiving this because you authored the thread.Message ID: @.***>
It doesn't want to run the gamescope session in sddm but in kde it runs without any problem