From what the various people who have explained to him how it works says, it seems that he does know.
He just doesn't understand why the Norwegian government won't be corrupt and influence it, because to him that's an obvious thing you'd do when you have power and influence.
So I never personally raised a bug report, but this issue was the one I saw when I first got the gpu: https://gitlab.freedesktop.org/drm/amd/-/issues/2460
Exact same issue I've always had, MCLK gets stuck at 96MHz and refuses to budge, but since it was relatively easily solved with a quick script that just changes one of my monitors between 60hz and 59.97hz I just accepted that 3 second operation as part of what I had to do to play games lol.
I can replicate the issue, though right now I've got the opposite issue since getting a 4K144Hz monitor that ends with the MCLK being stuck at maximum at all times, which tbh I'm fine with as I don't care about the efficiency, I need the heating in this -30c weather anyway.
Literally anything I've had that was "uncommon" has had this issue.
These setups have worked fine:
Single, dual, and triple 1080p and 1440p, regardless of Hz.
Single 4k, also regardless of Hz.
All these setup my MCLK gets stuck in 96MHz or 456MHz and needs a reconnect or resolution/refresh rate change to "unstick" so I can get higher MCLK and actually play games.
Dual and Triple 4k, regardless of Hz.
Dual/triple 4K with vertical 1080, regardless of Hz.
Dual/triple 4k with dual vertical 1080, regardless of Hz.
It's strange that you say that they've worked specifically to get LOWER MCLK rates for single/dual displays, when my issue is specifically that my MCLK is stuck at low MCLK with "uncommon" display setups? Almost sounds like you're saying they've specifically worked to make my issue even worse lmao.
I'm a 7900 launch day customer who's been on Linux the whole time.
AMD still has not fixed the vram getting stuck at 96 or 456mhz (low power states) since day one.
It's an issue that only happens on uncommon screen setups, but every time I want to play a game I have to start the game and then replug my monitor, or change it's resolution to something else and back again. Every time.
This has been a reported bug ok the 6000 series cards, on launch. And they've still not fixed it.
This is quite cool, but I see nothing on how the choice of cities to include was done?
In my case my city isn't included, and the nearest city that is, is over 100km away on the other side of a mountain. The next one is about 500km away.
I also see plenty of smaller cities here in Norway than mine that are included, so this makes me think the selection of cities was probably made based on largest city within x radius.
Would be neat to know how these selections were made.
Maybe you avoided shock videos? It has been a quite common shock video on the Internet for the longest time, though I guess in more recent times it's relatively tame compared to the rest.
It was very common to stumble over it in the mid and late 2000s at least, and into the 2010s.
Personally I only know of this whole thing because of someone sending me that video way back when, and my curiosity made me look it up.
Battleshits?