• 0 Posts
  • 106 Comments
Joined 1 year ago
cake
Cake day: June 21st, 2023

help-circle
  • Pointing a desk fan into a computer works fine and is a useful troubleshooting step if you suspect something is overheating, but if you need to do it that probably means heatsinks are clogged with dust, aren’t sized appropriately or aren’t making good contact. So you really should fix that problem.



  • Network namespaces and policy based routing are black magic, IMO.

    I’ve got a VPN set up on my router and separate VLANs set up for ordinary traffic and VPN traffic. A device doesn’t need to support VPNs at all, I just connect it to the VPN VLAN and all its traffic goes over the VPN whether it likes it or not. I’ve got separate wifi SSIDs for each VLAN.

    My desktop is connected to both VLANs with a network namespace set up for the VPN VLAN, so sudo vpn rtorrent runs rtorrent in the namespace that’s connected to the VPN VLAN.

    My setup is nice, but I wouldn’t recommend it to anyone who doesn’t want to learn quite a bit about networking.













  • ERROR: […/src/amd/vulkan/radv_physical_device.c:1877] Code 0 : Device ‘/dev/dri/renderD128’ is not using the AMDGPU kernel driver

    This is the smoking gun, btw.

    I see you’ve got it working, so I’ll just add a bit of explanation.

    AMD GPUs used to use a driver called radeon. It was replaced with the current amdgpu driver. For a while, you had devices that were supported by both drivers and you could choose between the stable radeon driver that was missing features like Vulkan and HDMI audio or the brand new amdgpu driver that had the newest features but was unstable and not well tested.

    The kernel has a policy of not unnecessarily breaking things with kernel changes so even though amdgpu has been well tested in the years since, devices from that era still default to the radeon driver and need to be forced onto the amdgpu driver.