The workaround seems to be to use patched AMD drivers from a web site that doesn't exist anymore, where the application blocklist has been removed. I used to run earlier versions of those drivers back on Windows 7, so that's not completely untrusted in principle - but leshcatlabs is not on archive.org, and all the random download sites which claim to have a copy are iffy. Though someone seems to have collected the drivers on Sourceforge, that's probably the best option down that route...
...or I just keep things as they are, setting layers.acceleration.force-enabled = true in FF seems to have helped some too.
Wonder when W10 will drop support for old graphics drivers, and it's going to be end of the line for that hardware.
(Situation on Linux isn't much better - the two workable options are either to force-enable the AMD GPU in BIOS and have extremely short battery run tumes, or to disable the AMD GPU in Linux and run everything on the Intel IGP.)
@galaxis I had one of these, too, and iirc there was a Linux mechanism for switching between gpus on a per-window basis? I think it was called bumblebee, but then had a name change
@phooky Yeah, that's for the Nvidia Optimus solution though. Different beast. For Intel's first switchable graphics, the first was some DKMS module called vgaswitcheroo, and then I think kernel support was implemented differently later on. Always was a hassle though, sometimes userspace didn't know how to deal with the setup and such. Completely switching off either GPU works around those secondary problems.
@galaxis yikes, I didn't realize there was a whole parallel AMD version of this as well!
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!