Nowadays, I mostly don’t even care about compatibility issues anymore and just expect a game to work in Linux, which is just freaking cool. Obviously, some competitive MP games are off the table due to anti-cheat, but that isn’t my main gaming category nowadays so it works out.
I’ve heard something about Apple Silicon GPUs being tile-based and not immediate mode, which means the Vulkan API is different compared to regular PCs. How has this been addressed in the Vulkan driver?
Huge fucking deal, especially for Nvidia users, but it is great for the entire ecosystem. Other OSes have had explicit sync for ages, so it is great for Linux to finally catch up in this regard.
You’re correct. While the stable version of KDE Wayland is usable right now with the new driver with no flickering issues, etc., it technically does not have the necessary patches needed for explicit sync. Nvidia has put some workarounds in the 555 driver code to prevent flickering without explicit sync, but they’re slower code paths.
The AUR has a package called kwin-explicit-sync, which is just the latest stable kwin with the explicit sync patches applied. This combined with the 555 drivers makes explicit sync work, finally solving the flickering issues in a fast performant way.
I’ve tested with both kwin and kwin-explicit-sync and the latter has dramatically improved input latency. I am basically daily driving Wayland now and it is awesome.
LOL, same. I did a docker-compose pull and restarted, came here to look at the release notes, and almost started panicking whether I omitted some important upgrade steps. Turns out everything upgraded smoothly automatically though.
I truly believe the answer to this question is going to be yes around the May - June timeframe when Nvidia releases their explicit sync enabled drivers. All aboard the Wayland hype train babyyyy!
They’re at different layers of the audio stack though so not really replacing.
Well…have you filed bugs for your issues?
Most people have had a very smooth transition over to Pipewire. I have 4 Arch machines and Pipewire has been flawless. I am even using one machine for pro-audio usecases (REAPER, Ardour).
Oh come on, that camera bar sticks out so much. I am so tired of this design gimmick. Every Pixel phone with a case already looks ridiculously thick just so that the stupid bar is protected. With how thick it looks on the Pixel 9, the whole phone is just going to be a chonker by the time someone slaps a case on it.
All this coming at a time when my perfectly fine Pixel 5 just got EOLed is demoralizing.
I’ve been using it for years and now I basically can’t live without it. I consider OpenWrt compatibility in all of my router purchases. Currently using a Netgear R7800 and a Belkin RT3200, both are going strong.
It isn’t as widely used because it can be finicky to flash sometimes, and that’s if it’s even compatible in the first place. Even if it works, you may experience a drop in performance unless OpenWrt supports using the routers hardware acceleration features. If there’s no support, OpenWrt basically uses the onboard CPU to do routing and they’re usually not all that powerful.
My main issue with it is that it is way too thick. Most lopsided camera bumps somehow are more compact and thinner. You’d think with the amount of real estate that visor takes up they’d be able to make it flush with the rest of the back somehow, or at least match the thickness of phone cameras
I really wish they’d ditch that stupid camera bar. Every phone case attempts to hide it and it just makes the whole thing needlessly thick.
It’s a native app on Windows and Mac?
You should do it. Easy to setup using either their official AIO image or the community-driven micro service one. I am using the latter and it’s been amazing. It’s completely replaced Google Drive, Calendar, and Contacts for me and with the DAVx5 Android App it feels like a drop-in replacement. I am also using the auto upload feature to back up my photos to it.
Yeah, I pay for Netflix, Hulu, and Amazon Prime and yet, I am still downloading shows that are on those services because their shitty DRM schemes limit me to 720p. It’s insanity.
Yeah I am getting this offset bug as well. It works if you enable the native window frame in the Customize settings though, but I do miss having my tabs at the very top of the window.
Does it have any features missing in the open driver?
You can see the differences in the official README here: https://us.download.nvidia.com/XFree86/Linux-x86_64/550.54.14/README/kernel_open.html
The main difference for me is the inability to preserve video memory during suspend and hibernate. Without it, sleep and hibernate will cause all sorts of weird graphical glitches upon resume.
I am so happy power-profiles-daemon now sets the CPU driver instead of only setting the platform_driver when it is present. It was a big pain point of mine.
Definitely not necessary. If that was the case, it wouldn’t live up to it’s claims of being a transparent Docker replacement at all. I think you do need to use systemd if you want to go full rootless, but I haven’t tried it enough to make a solid call on that.
But yeah, with the above steps, I’ve moved seamlessly over to Podman for my self hosting stack and I’ve never looked back. It’s also great because I can take literally any Docker Compose I find on the Internet and it will most likely just work.
Yeah, in a Reddit comment, Hector Martin himself said that the memory bandwidth on the Apple SIlicon GPU is so big that any potential performance problems due to TBDR vs IMR are basically insignificant.
…which is a funny fact because I had another Reddit user swear up and down that TBDR was a big problem and that’s why Apple decided not to support Vulkan and instead is forcing everyone to go Metal.