UCyborg wrote on Yesterday, 18:27:
Do you Linux people change swappiness setting or leave at default? Or do you even run without swap partition / file?
I leave swappiness at the default setting and still use a swap partition, probably out of habit (yes, even on SSD), though these days it's compressed with zswap (add zswap.enabled=1 zswap.zpool=zsmalloc to the kernel command line). Some distributions, like Fedora, have switched to swap-on-zram instead (since Fedora 33).
UCyborg wrote on Yesterday, 21:25:
Playing H.264 videos in Firefox doesn't cause laptop to hang anymore now that amdgpu is used instead of radeon driver. But these things aren't obvious unless you're a (kernel) programmer. And the only thing that pushed me in the right direction was inspecting output of vulkaninfo. Which I didn't have much reason to do in the first place, but it pointed out the unsupported driver. I guess Vulkan now works too, theoretically, through GPU, even though I wasn't looking to get Vulkan working.
Given that your Radeon R2 is supported by both radeon and amdgpu, that means it's a Mullins/Beema (GCN2, UVD4.2) since GCN3+ is only supported by amdgpu (see the Arch wiki, though just ignore the distro-specific bits). I suspect you've found a corner case since hardware video decoding command submission is done in userspace (the radeonsi driver in Mesa). AIUI think the memory management is different between the two kernel drivers, which is why amdgpu is a requirement for Vulkan support (by the RADV driver in Mesa).
If your laptop has a VGA output, you may find that that now no longer works. The amdgpu driver adds support for analog output (VGA) for GCN1/2 generation of dGPUs and switches them to amdgpu by default in Linux 6.19 (to be released around February 2026). That still leaves the iGPUs on radeon though until they add analog output support for iGPUs.
lti wrote on Yesterday, 23:19:
I thought i915 was an outdated driver. Even on my old Sandy Bridge laptop, when I loaded that driver for the TearFree option, Firefox blacklisted a bunch of hardware acceleration features. Later, I switched to the newer driver (relying on modesetting) and found a different way to fix screen tearing that I preferred (it felt like a more legitimate fix), and those features were available.
The i915 kernel driver (for iGPUs from when it was part of the north bridge through to modern CPUs and the Arc A-series dGPUs) is still maintained and handles modesetting, memory allocation, and command submission. As you mention modesetting, I think that refers to Xorg modesetting DDX (device-dependent X) and that was indeed the replacement for the Xorg intel DDX "driver". The former depends on a kernel modesetting driver, like i915 (or amdgpu, radeon, nouveau, etc.), while the latter initially did modesetting in userspace but eventually relied on the i915 kernel driver anyway so AIUI Intel decided to stop maintaining their separate DDX.