I’ve already made a post about this, I made the switch from an Nvidia GPU to an AMD one and I was wondering if I needed to install anything extra. I’ve heard the drivers are included inside the kernel but how do I ensure that it’s installed?
I’ve already made a post about this, I made the switch from an Nvidia GPU to an AMD one and I was wondering if I needed to install anything extra. I’ve heard the drivers are included inside the kernel but how do I ensure that it’s installed?
That’s very strange. There are plenty of reasons for a GPU to be glitching like that, but I wouldn’t expect it to happen on an empty screen.
I’d start by checking the cables, the display, and verifying that the GPU is seated right and has all the right power connectors hooked up. Then, I’d look into the system logs (usually an application called “logs”, or
sudo dmesgif you prefer the command line) to check if the driver prints any warnings or errors on boot. If that doesn’t provide a clue, I’d check another OS (either a Linux install USB or a Windows install) to confirm whether or not it’s got something to do with your particular setup.I don’t know what kernel version Pop_OS! Is on, but it’s worth trying a kernel update. Kernel 6.1 and up received a whole bunch of AMD GPU improvements, so updating the kernel may help.
Lastly, some GPU manufacturers also publish BIOS updates for the GPU itself. If there’s an update available for yours, it’s worth reading the change log and seeing if it mentions glitches like these.
It seems my comment didn’t send but I plugged the HDMI cable to another port on the monitor and it got rid of the big glitches, however a small portion of them still remains. My GPU seems to be connected correctly as well and these glitches are not present in Windows. I’m updating the OS as we speak I’ll see if anything changes
If switching to a different monitor helps, I have to wonder if it could be the cable. I can imagine something weird like the Linux driver trying its hardest to send a full quality signal to the monitor, while Windows detects that the signal isn’t great and switches to lower-quality compressed video (modern display standards have compression built in which can mask this issue for a while…)
If the updates don’t help and you don’t have another cable lying around to test with, I’d start checking out the logs.
the thing you said makes sense because the rips can’t be seen in an obs recording