If I remember right, no. If I clean boot, load sddm, immediately type my password and log in, then I have to wait a while for the mouse to start working.
But if I clean boot, load sddm, wait the same 5-10 seconds, then the mouse starts working on the login screen and then just continues to work once logged in.
You don’t get it.
They are destroying the planet on top of all the other things.
Yeah, like, come on! Being born in the Middle East? Rookie mistake!
So do 100% concentrated evil, but they also wipe their arses with the constitution, set up concentration camps, and literally ruin the political and economic position of the US.
So it’s performing worse than 3060 or 4060?
Then don’t buy the current-gen low-end card for video editing, mate. Get previous-gen with more vRAM, or go AMD.
Because it’s the low-end xx60? Also, apparently Nvidia did some high-tech magic that allows higher-res textures to be handled with less vRAM.
But, yeah, it’s a 5060. You’re not buying this to play in 4k Ultra.
Hmm… There’s a connector from the card to 3-pin connector on the motherboard, but the description in the manual suggests that it only allows me to control RGB through it. As in: if I don’t connect it, they’ll just be on in whatever default state they’re in and that’s that.
I’ll look into this, thanks!
Oh, nice! Thanks for the info!
In general, I’d suggest being a bit more curious and playing around with stuff
Man, I’m 40, my 9-5 job is being curious, testing and retesting stuff. When I’m home, I just want to play some games…
Like you said you didn’t understand the options for OpenRGB and it sounds like you didn’t try installing it at all to eliminate it as an option before posting
Yeah. I’ve learned (through curiosity and testing, btw) that it’s super easy to break stuff in Linux, so I was a bit weary of installing third party software that does “something” to control the LEDs on a graphics card.
I did test it out yesterday, though. Sadly, does not recognise the GPU. It did recognise my mouse, though, which is neat.
It’s not like an app like OpenRGB is going to break your GPU or anything.
That’s the thing - I’m in a state where stuff works and is fine. That came after five reinstalls and three distros. Linux is not Windows - it’s fairly easy to do some unrecoverable* damage if you don’t know what you’re doing.
* yes, I know, technically everything is recoverable, but that requires knowledge and time, neither of which I have for this kind of stuff.
I would rather disable it on the OS level because I’m slightly paranoid that the dGPU dies at some point and then I can’t even access UEFI, because the iGPU is disabled.
Ooh, nice one! I’ll need to have a look for some detailed manuals/design diagrams of the Sapphire Pure, see if it’s mentioned.
Huh, a Windows VM might be a brilliant solution to this.
And now I’m wondering - could I maybe use something like Bottles or Wine to install the Windows software that handles Sapphire LEDs? Or would these apps not see the dGPU when virtualised like that?
someone suggested disconnecting the LEDs themselves, which is not something I’m willing to do with my 2-day old card
Sapphire Pure RX 9070 XT.
Sapphire Pure RX 9070 XT.
Ah, good to hear there’s hope! Thanks for that!
You can’t really disable rgb but you can set brightness with openrgb to 0.
I guess that’s good enough.
Do you speak from experience with 9070, or just in general as a “thing that OpenRGB does”?
Well, to be fair, there was A LOT of weird stuff happening. Steam wouldn’t open at all (unless called from the terminal), or would open with just a black screen (GPU acceleration issue). At some point, I’m pretty sure, I had three instances of Steam installed. It was chaos.
Hey, thanks for your comment! Someone on Reddit was able to help out, I posted the solution in the OP.