I did live like this with all my intel/nvidia systems just fine, though. If AMD tends to have bugs like this, they still seem to suffer from the same shitty software development attitude as they did back in the fglrx days.... with the added advantage that people from the community can now firefight some of the problems. For a product I paid a few hundred euros for I expect some quality assurance for its driver development - that seems to work with nvidia.
If other people apparently have no probiems, it can't be AMD in general. Never trying AMD because of a bad experience 10 years ago would also be extremely unwise. "We've always done it like this around here" is how you fall behind the times.
It's a completely new card, so I will not fiddle around with it. Also it runs almost flawless on Windows (aside from a similar crash on the very first boot during driver install).
I need to give the LTS kernel a shot tomorrow, but I could swear I tried that and had the same issue. Which now makes me fear that I might have a different problem. Argh.
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.
I probably shouldn't have read tests and forums, but simply searched for crashes and open bugs to get a feeling for what I am getting into. Then again I also read from people with very ugly problems with nvidia, so it's not a really good measure.
I really want AMD to be good; they offer more VRAM where nvidia always seems to cheap out in pretty suspicious ways. Then again nvidia seems to be more power efficient.
Prime Video was nice, but I don't like the move with including ads. Since they fucked me over as a linux user by using dumb DRM, I don't really miss it.
Shipping: same as the author. I will likely get used to increased wait time. Shipping was never my main use case.
I will miss my free monthly twitch subscription. So I will likely not support my favorite streamer anymore (via twitch sub at least).
I'll see how it goes. But fuck the industry for their ad-ridden shit tour. I will rip any service out of my life that tries that bullshit.
I don't believe in this distinction. I am proud of my work. If I wasn't, I would have almost no drive to deliver good or even any results. I like what I do.
So of course it becomes a difference if you tell me that there is a better way to do what I did (aka giving me something to improve) or if you tell me that my work is utter crap (aka taking away any positivity I had).
So yes, my code can be wrong or bad. But it's still something I produced. So I prefer to not have it treated like a piece of shit.
That's pretty clever for that age and shows, that your brain already had the right wiring for (software) engineering. You set out to solve a problem by leveraging the tools you had and bending their functions to your needs. There's a lot of abstract thinking involved.
I did live like this with all my intel/nvidia systems just fine, though. If AMD tends to have bugs like this, they still seem to suffer from the same shitty software development attitude as they did back in the fglrx days.... with the added advantage that people from the community can now firefight some of the problems. For a product I paid a few hundred euros for I expect some quality assurance for its driver development - that seems to work with nvidia.