@marcan @G33KatWork @tnt @kkarhan @sima @lina

Still slandering Nvidia for Wayland shortcomings Hector, really? Wayland devs have needed to work with hardware vendors since day one, which was 2008. Y'all have had FOURTEEN years to get the product at least as capable and stable as X... and yet basic stuff routinely fails and yet you still blame the hardware company despite obvious support: https://9to5linux.com/nvidia-525-60-11-linux-graphics-driver-adds-dynamic-boost-support-on-amd-laptops

NVIDIA 525.60.11 Linux Graphics Driver Adds Dynamic Boost Support on AMD Laptops - 9to5Linux

NVIDIA 525.60.11 Linux graphics driver is now available for download with Dynamic Boost support on AMD laptops, many improvements.

9to5Linux

@winterschon @marcan @G33KatWork @tnt @sima @lina well, it's #nvidia's choice to purposefully hinder and prevent #FLOSS drivers with feature parity whilst not supporting #Wayland themselves.

It is just infuriating and the reason why I've had to migrate to #Intel & #AMD because nvidia are full-throttle greedy assholes.

@winterschon @marcan @G33KatWork @tnt @sima @lina #Thorvalds et. al. would not be pissed if #nvidia didn't barf out blackboxes that half the time cause issues...
https://www.youtube.com/watch?v=i2lhwb_OckQ
Nvidia Fuck You! (Linus Torvalds) My thoughts exactly

YouTube
@winterschon @marcan @G33KatWork @tnt @sima @lina
And yes I can confirm these issues, as well as #nvidia (due to not supporting #Wayland) not being able (or rather willing) to handle mixed DPI display configs gracefully, resulting in a useless experience...
https://infosec.exchange/@G33KatWork/110373997950858541
Andy (@[email protected])

@[email protected] @[email protected] @[email protected] @[email protected] After marcan's tweet yesterday, I decided to try and give Wayland on an RTX 2080 Ti a go again. I switched back to Xorg now, because Nvidia's wayland support is absolutely horrible: The most annoying part: Electron apps and proton with DXVK show the weird behavior that old frames are displayed between newer frames. While typing in Slack for example, the letters you just typed vanish for a split second and then show up again. The same happens in Far Cry 6 when running in gamescope + proton. Results in horrible stuttering. Some synchronization primitive is broken. I am not the only one and I am running the closed source driver, so this one seems to be affected as well: https://github.com/NVIDIA/open-gpu-kernel-modules/issues/187 Also I tried to 3D print something and Cura just crashed with an int3 on its way through `gdk_display_manager_open_display`. I didn't debug it further and just switched back to Xorg. See you in a year (or when I decide to buy new, non-Nvidia hardware)!

Infosec Exchange

@winterschon @marcan @G33KatWork @tnt @sima @lina the only issues I had with #Wayland & #Xwayland on #AMD GPUs are weird texture glitches in #Metro2033Redux & #MetroLastLightRedux which get "magically unf**ked" if one goes in the options menu, switches graphics quality around, confirms, and then switches back and confirms.

https://social.treehouse.systems/@marcan/110374117035854402

Hector Martin (@[email protected])

@[email protected] @[email protected] @[email protected] @[email protected] Yes, it's completely broken on Nvidia, and it's entirely Nvidia's fault, and this is one major reason Wayland undeservedly gets a bad rap. For the record, the missing synchronization feature in the Nvidia proprietary drivers is implicit sync. It's been years and they still don't have it. Wayland is completely broken without it (so is X on modesetting for that matter, but presumably they do something else in their proprietary DDX). @[email protected] implemented it for the Asahi GPU driver in two weeks, plus maybe a couple more of debugging, give or take. It's already been shipping to users for a while, with a few rare glitches that are identified and fixed for the next version already.

Treehouse Mastodon
@winterschon @marcan @G33KatWork @tnt @sima @lina in the case of the #MetroRedux games I am convinced that's a minor bug due to it being ported to #Linux and originally designed and optimized for #nvidia #GPUs, propably doing some weird texture loading routine on the #A4Engine by #A4Games.
@winterschon @marcan @G33KatWork @tnt @sima @lina
And whilst annoying at the start, it's easily mitigated and not gamebreaking. On max settings a Vega64 & 6700K deliver a bitter-smooth experience in 1080p whilst having a literal shitton of applications open and running in the background.

@winterschon @G33KatWork @tnt @sima a lot of people give #Apple a bad rep for being #AntiRepair and #AntiComsumer but at least they don't actively go out of their way to make things worse or harder for @marcan & @lina by locking out @AsahiLinux ...

https://mstdn.social/@kkarhan/110375946328549019

Kevin Karhan :verified: (@[email protected])

Attached: 1 image @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] @[email protected] well, it's #nvidia's choice to purposefully hinder and prevent #FLOSS drivers with feature parity whilst not supporting #Wayland themselves. It is just infuriating and the reason why I've had to migrate to #Intel & #AMD because nvidia are full-throttle greedy assholes.

Mastodon 🐘

@winterschon @marcan @G33KatWork @tnt @kkarhan @lina this is flat out wrong

nvidia cryptographically locks down their firmware, which is required to use the hw at anything but boot-up clocks. there _are_ nvidia drivers that fully support wayland, if you're ok with running at boot-up clocks

and this is something nvidia did, and only nvidia can fix (you can't break crypto, that's not a thing), and nvidia choose to not fix. everyone else with crypto-locked down fw figured this out (even apple!)