I feel like this is the perfect place for Right to Repair legislation: the product is broken? And it's outside your support window? Then give customers what they need to make the fix themselves. It's not good enough to say "meh, guess you gotta buy one of our newer chips then 🤷"
teawrecks
joined 1 year ago
Ahh, yeah if it's specifically when coming back from a VM, that sounds different. Maybe the vfio_pci driver isn't getting swapped back to the real one? I barely know how it works, I'm sure you've checked everything.
Propaganda has lead a depressing number of people to believe exactly the opposite. MTG literally said, "what, you think Putin just decided to invade Ukraine?"
For me, I have intel integrated + amd discrete. When I tried to set DRI_PRIME to 0 it complained that 0 was invalid, when I set it to 2 it said it had to be less than the number of GPUs detected (2). After digging in I noticed my cards in /dev/dri/by-path were card1 card2 rather than 0 and 1 like everyone online said they should be. Searching for that I found a few threads like this one that mentioned simpledrm was enabled by default in 6.4.8, which apparently broke some kind of enumeration with amd GPUs. I don't really understand why, but setting that param made my cards number correctly, and prime selection works again.
I actually may have seen the same issue recently. Have you tried adding initcall_blacklist=simpledrm_platform_driver_init to your kernel launch params?
Do you have two GPUs or do you fully switch to the VM while passed through?
Ok, I'm not crazy. I've been thinking I haven't seen updates on my desktop in a while too, but my laptop has been updating fine. I just updated mirrors using eos-welcome as others suggested and now I've got a couple gigs of updates ready 👍
I've tried lutris, I've tried bottles, I've tried Heroic. Heroic is the best experience I've had.
I forget the order 5 times in the middle of crimping each side, so you're doing better than me.
Not only is there btrfs support for Windows, but since windows and linux files don't conflict, someone got both arch and windows booting from the same partition. Is it a good idea? Hell no. But can it be done? Apparently yes.
Ahh, yeah proton overhead would add up. I wonder if there's a way to run a single proton instance that launches all of them. When I was running the wow launcher via bottles, I believe it was running both the launcher and the client it spawned using the same resources.
And yeah, I've almost never had the minimize on lost focus issue, but I've mostly used tiling WMs. The cursor getting locked to the window bounds is way more common.
I would still say dual booting is the superior option, but that might be complicated for some people, so this is probably a good recommendation.