I got a RX 7600 XT installed and running. I'm having problems with Steam or any vulkan program, specifically. (Stardew valley, minecraft are fine.)

inxi -b output: https://pastebin.com/eH3WhAvK

lspci -k: 09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 33 [Radeon RX 7700S/7600/7600S/7600M XT/PRO W7600] (rev c0)
Subsystem: Tul Corporation / PowerColor Device 2430
Kernel driver in use: amdgpu
Kernel modules: amdgpu

vkcube and /usr/bin/32/vkcube work fine (Selected GPU 0: AMD Radeon Graphics (RADV NAVI33), type: DiscreteGpu)

X11 log: https://pastebin.com/d8ycx10m

Steam is Alien Bob's package.

Here's a log from a game using proton: https://pastebin.com/s4ufEdZx

I note:
But it shouldn't be using the radeonsi driver? (I've done steam --reset, too.)

I also created a completely new user, installed Brotato to it, and had the exact same issue. (So reasonably certain it's not just cruft.) I did a reinstall of mesa (slackpkg reinstall mesa) just to be safe.

Interesting. After I updated my current install on 5/1/2024 Steam started defaulting to using my igpu instead of my dgpu which is a Radeon RX 6600.

Which it never did before the updates.

Since using the ipgu is slow and crashes the system with some games I disabled it in the UEFI/BIOS. Now half my games refuse to run I just get black screen and nothing. For example I cannot get Counter Strike 2 running because it complains of failure to initialize vulkan, it was running fine last week. But vxcube runs well and vulkan-info give out correct output. And I can run DOTA Underloads which is a pure Vulkan game.

I tried downgrading mesa to the previous release both x64 and multilib that didn't work, I tried removing all off Steam and installing and restarting from scratch but to no avail. I tried three different kernels and same thing.

I booted into windows and stressed test my system and gpu and there no issues on the dark side. All my games under windows are running fine.

A weird one

https://github.com/ValveSoftware/ste...ime/issues/668 Could this be it? (And the new video card a red herring?)

1 members found this post helpful.

This is caused by the recent (April 29) update of ncurses.
I spent a couple of hours today fighting this until I found this post: https://www.linuxquestions.org/quest...ml#post6499672

1 members found this post helpful.

Whew. So the new video card's a big red herring, then. Native Vampire Survivors works.

1 members found this post helpful.

Thanks for the help guys! On my end pulling the slackbuild for libedit from the current tree and rebuilding fixed my Steam issues.

Lots of hair-pulling and vape smoking trying to figure out that problem out on my end.

1 members found this post helpful.

Yeah, I spent a good 2-3 hours chasing down every last piece of nvidia cruft, thinking things were just crufty. Then I was looking over environment variables, things loaded, things not loaded, and so on. hell of an introduction to the AMD ecosystem, that's for sure.

Yeah, rebuilding libedit did the trick, but there's also the 32-bit one for mutilib. (Which I forgot.) But, hey, 64-bit proton things work. Marking solved for now...

If you trust me, you can download the multilib package here: https://homepages.tuni.fi/petri.kauk...-1compat32.txz. The version number is the same as the previous one, so 'upgradepkg --reinstall' is needed.

1 members found this post helpful.

Still one more package appears to need be rebuilted.
https://github.com/ValveSoftware/ste...ent-2094248470

Thanks!

Hrmm...yeah. Guild Wars 2 crashes, still, and I get a message about my GPU not being supported on Diablo IV (but Diablo IV still loads, but that's using vkd3d.) reports RADV NAVI33, though.

Marking unsolved...

ETA: not just GW2, which can be notoriously fussy, but also Palworld, which worked on my former card.

garpu are you using https://www.protondb.com/ to help with tinker steps for your games?

Alot of games that run under Proton need different command switches or workarounds to work right under different gpu chip brands and architectures

I am, yes, but I haven't updated the 32-bit side of multilib yet. (The post above was made before the 47 updates, which fixed a lot.)

In my case, rebuilding the libedit seems to have fixed the steam issue. I have the 32bit packages from "convertpkg-compat32" script. I have not installed the May 4 updates yet or their 32bit counterparts.

Hrm. Something's still not right on my computer. With No Man's Sky (something that should work out of the box) I'm still crashing. I've reset the steam prefix. I've got export AMD_VULKAN_ICD=RADV (with "source .zshrc) in my .zshrc. I've tried launching with AMD_VULKAN_ICD=RADV %command%. I've launched steam with "VKDRIVER_FILES=/usr/share/vulkan/icd.d/radeon_icd.i686.json:/usr/share/vulkan/icd.d/radeon_icd.x86_64.json steam" I deleted and recreated the prefix.

proton log: https://gist.github.com/garpu/20aff3...5b51d0537e874c

I'm not sure if this is still the ncurses problem, or something else. (GW2 works, which is using dxvk. So does Diablo IV (vkd3d) and Sims 4 (dxvk).) I noticed that Sims 4 and Diablo IV didn't recognize my video card, which is why I was trying the vulkan environment variables with No Man's sky. (Palworld also still crashes. Diablo IV and Sims 4 both run, although Sims 4 said it set my graphics to a safe level...that was Ultra, but it loaded and ran fine.)

(I'm up to date on my updates since this morning. Yes, I realize this is a real first world problem.)