dlove67

I don’t play, but perhaps it has something to do with either Proton or Linux? (I’m assuming you’re mostly a windows player outside of the deck).

You could try running it with DXVK, which does work on Windows, though it’s not officially supported or anything.

Got mine about 3 hours ago~

It’s the Limited Edition, and while most of what the reviews said was spot on, it seems either QAM and Steam buttons on the LE are a bit different or something, because they’re ever so slightly raised above the body of the deck.

Mine just updated about an hour ago, so yours should be soon, if not by now.

Mine shows as shipped on UPS, supposed to get to me on Wednesday

Limited Edition here.

Weird. I just checked and it says 1-2 weeks still, like it always has for me :/

I don’t know where 2-4 weeks comes from, maybe Canada(Your comment isn’t the first time I’ve seen it)?

The delivery date (at least what I’m seeing) is 1-2 weeks, not the shipping date.

For instance, mine already has a label ready, just waiting on UPS to update for the estimated day.

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.

If you were missing firmware, that’s not actually a driver issue. You do need the firmware and (unless you also installed the professional drivers as well) you should be all good now and using the full open source stack.

Anyway, glad to hear it’s working for you!

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.

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.