5
Parzi
14d

my new rig is more and more causing me issues:

- Ryzens fucking kill 9x and MS-DOS applications and the OSes themselves when they run unemulated, so they can't be run in a KVM. This makes them slow as shit, and in qemu-TCG's case, buggy as shit too. VMs can't reboot successfully, they have to be totally forced down and brought back up on TCG or they hang during the reboot. It also performs poorly. VERY poorly. The "shit runs full-speed like 65% of the time and it feels slow as fuck as video output is a stuttery blurry mess" type. This makes 2 projects problematic to complete and I have to remake 17 VMs in virt-manager now as vbox doesn't work with any virtualization method for a 9x/DOS guest now!

- For some reason my new RX 5500xt has an issue when it hits about 80% usage, the fans spin to 100% on it at 80% and taper off to like 5% when idle. Pretty standard stuff... except it's erroneously tied to... current load, not temperature. Hmm.

- Debian got an update that renames my ethernet device mid-boot. Up until just before the login screen, it's named "eth0". After that, it's named "enp8s0". This was hell to work around and idk why it does this.

Comments
  • 3
    Regarding the interface naming (if you didn't already now):
    Previously, if you added a new interface, and rebooted, those interfaces might have switched name, depending on the kernel module load order.
    Debian maintained a file of inyerfaces to prevent it, but apparently this was quite fragile. The new naming depends on hardware type, bus order, and mac address.

    If you didn't read it yet: https://wiki.debian.org/NetworkInte...
  • 4
    Probably not the greatest idea to use Debian with a newer AMD gpu. You want the latest stable kernel you can get.
  • 1
    Besides the issue @RememberMe outlines (old as dirt kernel/bios and new hardware is often a bad combo). Did you enable hardware virtualization (AMD-V or SVM) in BIOS?
  • 0
    @RememberMe I'm using Debian Sid, so my kernel's like 5.8, 5.9?
    @hjk101 Yes, or VM software wouldn't run at all. Look up "Ryzen VME bug" and disregard where it says 2nd gen Ryzens are unaffected.
Add Comment