Solution

Uninstall AMDVLK, you should probably use vulkan-radeon anyway.

I think there was a wine / proton update earlier today, I've just tried to launch the game from Steam and gotten the aforementioned message. I've found out that the message is common on Nvidia and Intel Arc GPUs but not AMD. I was wondering if anyone is now experiencing the same thing and if anyone knows a fix, I was quite looking forward to sinking another day into Starfield tomorrow...

AMD announced FSR 3 will allow for fluid motion frame generation in-game on almost any GPU in any DirectX12 game, doubling or even tripling your FPS.

Would this work on Linux? Considering DirectX to Vulkan translation and our lack of Radeon software. Obviously I expect when FSR 3 releases it'll be a little while until people get it working on Linux if it is possible to get it to work.

I'm quite excited for FSR 3, not that I don't have a good GPU (I have a 6800XT) but I'm just excited to try real-time frame generation without spending a small fortune on a sub-par GPU from a sub-par company. Should I, and probably many other Linux gamers, look forward to FSR 3?

TL;DR: Do. Not. Share. Boot. Partitions. Across. Linux. Installs.

------------~~~++~~~------------<

So a couple days ago I posted a screenshot of my first Gentoo install in a VM. I mentioned that I planned on putting it on my hardware in a triple boot setup (Arch - Main, BillyG-O$ - VR games, Gentoo - Pain). This is a follow-up on my adventures doing that.

Everything went well initially, I followed almost the exact same steps as the VM and things went by much faster (as it had access to all my resources). However I made 1 respectfully sized blunder, for some stupid reason, I tried to share boot partitions between my Arch and this Gentoo. DO NOT DO THAT, I can speak from ~this~ experience.

Because of sharing boot partitions, GRUB got absolutely buggered 6 ways from Sunday resulting in GRUB unable to find my Arch initramfs. Not good at all. So for about 2 days my system was unbootable (I took a break from the computer, I'd just about had it).

Thanfully though it turns out my previous Arch-only GRUB install still existed so with a quick boot override I was finally able to get back into Arch. I then proceeded to totally destroy every last trace of Gentoo from my boot drive and reinstall the kernel, thereby remaking my initramfs. My system is restored 🥹.

So, in conclusion, I feel that Gentoo is definitely good fun and worth doing, however if you're installing it on the same drive as a pre-existing OS be. Hyper. Vigilant. I'm not sure how or why my old Arch-GRUB still existed but by golly am I thankful it did.

This did not scare me off Gentoo at all because it was my error. So I'm probably going to reattempt it soon. I also jusy wanted to say thanks for the engagement and tips on my previous post, I love the Linux community and our little corner of the internet. I await the day where our pride and joy is mainstream, along with so many others I'm sure. I hope you have a great day/night :).

Screenshot of QEMU VM showing an ASCII Gentoo Logo + system info

I followed Mental Outlaw's 2019 guide and followed the official handbook to get up-to-date instructions and tailored instructions for my system, the process took about 4 hours however I did go out for a nice walk while my kernel was compiling. Overall I enjoyed the process and learnt a lot about the Linux kernel while doing it.

I'm planning on installing it to my hardware soon, this was to get a feel for the process in a non-destructive way.