Linux

48310 readers

645 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

AgreeableLandscape@lemmy.ml

nooter692@lemmy.ml

MarcellusDrum@lemmy.ml

cypherpunks@lemmy.ml

cyclohexane@lemmy.ml

d3Xt3r@lemmy.nz

101

AMD GPUs are cursed for me (lemmy.world)

submitted 9 months ago by aksdb@lemmy.world to c/linux@lemmy.ml

114 comments fedilink hide all child comments

Each time I try AMD graphics, something is fucked for me. Back with fglrx, fglrx just sucked, so I used Nvidia. Then I had an AMD right around when they finally had opensource drivers, but it was still buggy as hell. So I went with Nvidia again (first a GTX 790, then a GTX 1060). In the meantime I had a new work notebook where I also went with an AMD APU, and had driver crashes for a long time when I was in video calls and it had to decode multiple streams. That thankfully stabilized with Linux 6.4.

Since sooo many people in the community swear by AMD, I thought "dammit, let's try it again for my new desktop" and got an 7800rx ... and I have to reboot ~5 times until I finally make it to a running xserver or wayland session. Apparently I am hit by this problem (at least I hope so). But that doesn't even read nice ... the fix seems to be to revert another fix for powermanagement. So I either have a mostly non-booting card or suboptimal power management.

I start to regret having chosen AMD .... again :-/ I seem to be cursed.

you are viewing a single comment's thread
view the rest of the comments

[–] acockworkorange@mander.xyz 8 points 9 months ago* (last edited 9 months ago) (1 children)

Sorry to hear that. For what it's worth, I've had no problems with integrated AMD graphics, so maybe it's a PCIe issue?

[–] aksdb@lemmy.world 4 points 9 months ago (2 children)

Hmm, interesting idea. I need to investigate that. The dmesg output is full of amdgpu irq errors, but of course that could also happen with an issue on the board.

I would rule out a generic hardware issue, since 1) I get graphics during boot up until it needs to do a modeswitch (I guess) and b) it works fine so far on Windows.

I did have a similar issue after the first boot on Windows as well and assumed so far that the modeswitch after the initial driver install caused the problem. But Windows likely also installed chipset drivers at that time, so PCIe could be a possibility. Then again... I know that Windows reloads graphics drivers on-the-fly... but chipset drivers? Probably not. Which would speak against that theory.

[–] acockworkorange@mander.xyz 1 points 9 months ago

I have no clue how Linux initiates the communication with a PCIe board, and whether the amdgpu driver would take care of that. But hardware excluded, some misconfiguration on the driver's part could be present. Good luck!