• 0 Posts
  • 29 Comments
Joined 2 years ago
cake
Cake day: July 11th, 2023

help-circle









  • Do you mean it constantly does it when a monitor is turned off or that when you initially turn off a monitor, it rearranges all windows to fit on the remaining monitor.

    If the first, I’m not sure what the problem might be, but the second is pretty normal, I think. The card sees that the display was detached and moves your windows to the attached display so you can see them.



  • dlove67@feddit.nltoLinux Gaming@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 years ago

    So…what can I do? Neon is mostly Ubuntu 22.04 to most effects. Kernel is 6.2.0-36-generic.

    The kernel in use should support RDNA3, I believe.

    Edit: judging from the comment made a bit ago, it wasn’t the kernel or mesa, they were just missing the firmware. And yeah, that’ll do it. I remember being frustrated with my 7900xtx not working on Pop! before I pulled in the firmware back on release.


  • dlove67@feddit.nltoLinux Gaming@lemmy.world*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    2 years ago

    As others have said “Ya doin it wrong!”

    AMD has the AMDGPU kernel driver already in place in the linux kernel, and excluding the newest generations of cards for about a month or two after they come out, that part should work fine. Additionally, you need Mesa installed for the userspace drivers. It is typically preinstalled and covers the OpenGL and Vulkan drivers for your card.

    Pretty much the only time you want to run the driver from AMD’s site is if you’re using some particular professional applications, otherwise Mesa tends to outperform it. There are relatively few games that AMDVLK (the AMD official open source Vulkan driver) is ahead, and it’s got an edge in most (all?) raytracing cases currently.

    Lastly, the reason it doesn’t work is because the driver install script is checking your os-release version to see if it matches the Ubuntu version it was packaged for. If you’re confident that you can fix any problems that arise from doing this, you could presumably just change the string in /etc/os-release to match what it’s looking for. I don’t recommend doing this, though, unless you don’t care if the drivers break things because they weren’t packaged for the release you’re using.




  • “Linux + SteamOS” compatibility is a bit legacy. It mostly refers to games that have a native linux client (I believe some of the early Proton Validated games are included as well.

    The Steamdeck (and generally speaking, any linux system) uses Proton as a compatibility layer with windows, and the “Steamdeck Verified” system is more relevant today. That said, even the Steamdeck verified system isn’t perfect. There are a number of titles that, while verified, have some problems with the deck, typically later in the game or after running for some number of hours. There’s also a vast number of games that while not “Steamdeck Verified” work perfectly on the deck and linux via proton (though you do have to enable it in the settings).


  • At one point their AMD driver managed to uninstall itself somehow.

    Yup, that’s windows. AMD tends to release most of their drivers without WHQL certification (think, final drivers, just without Microsoft signing off on them, so they get out faster and (presumably) slightly cheaper).

    Windows sees this and thinks “Hey! This driver doesn’t have our stamp of approval! Let’s help this dumb user out and ‘update’ it to the latest one that does!”

    Unfortunately, this not only puts you on an old version, but now the adrenalin software sees that the driver doesnt match its install and doesn’t let you use those features.

    God I hate windows >.>