The best three brands with natively-supported hardware:
Pretty much everything else requires a lot more tinkering than just launching SteamVR/OpenVR applications.
Some helpful links for diagnosing compatibility:
As I understand it, this driver isn’t ready for personal use unless you don’t care about the contents of your btrfs partitions mounted on Windows.
It was indeed carrier locked, which was why I used it as trade-in value for a phone rather just selling it and later buying a newer phone.
In my case, AT&T sent me a Galaxy Note 9 to replace my Google Pixel XL, which I ended up never using and just used a trade-in value to get a Pixel 5a.
The easiest ways to run custom executables for Proton titles is either going to be SteamTinkerLaunch or my shim script.
As I found out recently myself, you should almost always set the minimum amount of reserved memory for the iGPU on modern hardware. The reserved memory is just that— reserved. The kernel still dynamically allocates memory for GPU usage as needed on iGPUs.
Largely things look good. It might be a good idea looking for a motherboard that has Intel ethernet rather Realtek. I’m also a bit curious if the barebones VRM design on the board is adequate as well.
It doesn’t currently allow for concurrent execution of EXE files, but that’s a good idea. I’ll see about implementing it.
Tiny 11 comes in two variants:
Tiny11 Core is not suitable for use on physical hardware as it outright disables updates. It’s best used for short-term VM instances.
Tiny11 also has problems with updates. The advantages gained through Tiny11 will erode with applying Windows updates. The installer is more tolerable than Windows 11 by not forcing an online account (but still needing to touch telemetry settings). Components like Edge and One drive will inevitably rebuild themselves back in with cumulative updates. If this is something that coerces you to not update your system, don’t subject yourself to using Tiny11. Additionally Tiny11 fails to apply some cumulative updates out of the box, which could be a further security risk.
I recently tested the main Tiny11 in a VM based on a different user recommending it in a now deleted thread. I was skeptical knowing the history of Tiny10 onward that 11 would actually be able to update properly, and NY findings backed up my initial skepticism of functional updates.
The A485 is actually such a terrible laptop. I would never reccomend such garbage to anyone considering mine almost never worked properly. I had in three years have six main board replacements for various hardware faults. Not a single of the boards has been free from severe hardware faults.
I’m glad I am not the only one who calls my little ASUS netbook craptop. Kinda flimsy and definitely underpowered, but a perfect little device to run basic applications and terminal applications on a minimal window manager.
I believe it’s mostly drawing tablet support in Qt and in turn porting to Qt6 that’s holding native Wayland builds back.