• 0 Posts
  • 134 Comments
Joined 2 years ago
cake
Cake day: July 13th, 2023

help-circle

  • Super simple, like 30 minutes to setup mergerfs and then the bind mounts are a few lines added to the LXC config files at most. This isn’t necessarily needed, but I have users setup on the proxmox host with access to specific directories that are kind of a pain in the ass to remap the LXC users to, but were needed to give my *arr stack access to everything needed without giving access to the entire storage pool. Hard links won’t work across multiple bind mounts because the container will see them as separate file systems, so if your setup is /mnt/storage/TV, /mnt/storage/downloads, etc. then you’d have to pass just /mnt/storage as the bind mount.










  • I did this same controller search earlier this year, and I can’t really compare it to any similar controllers because it’s the only one I’ve used, but I ended up going with the Abxylute S9 and I’ve been happy with it. I really wanted usb-c power passthrough and a 3.5mm headphone jack.

    It’s probably too big for what you’re considering, but I think they sacrifice too much of what makes it usable and comfortable to go much smaller.






  • It ranges from significant performance differences between the drivers with specific games to games having rendering issues with specific drivers. A lot of games don’t work at all with the proprietary driver.

    My most recent issue was with the Indiana Jones game having horrible traversal stuttering making some areas basically unplayable on RADV, but AMDVLK had no stuttering and better framerate overall.



  • AMD is just simpler because you don’t have to manage the drivers, but it’s really not a big deal. It’s very easily handled.

    Honestly this isn’t as true as I was led to believe it was before I switched to AMD. Just like Nvidia has issues between the proprietary driver and nouveau; AMD has its own mix of issues with Vulkan between RADV (mesa), AMDVLK, and AMD’s proprietary driver on a per-game basis at times.