azvasKvklenko

joined 2 years ago
[–] azvasKvklenko 1 points 9 hours ago

I'm pretty sure it is or at least will be at some point

[–] azvasKvklenko 6 points 1 day ago

Thanks for nothing Microsoft

[–] azvasKvklenko 103 points 1 week ago (1 children)

I wish you a beautiful downfall Abode

[–] azvasKvklenko 2 points 2 weeks ago

Not bad huh?

[–] azvasKvklenko 1 points 3 weeks ago

That depends on which GPU you're using as nvidia-open is for Turing and newer, but that makes no practical difference as it is and will always be out-of-tree.

[–] azvasKvklenko 3 points 3 weeks ago (2 children)

It really depends on how the distro you're using is integrating them and while installing them is usually the easy part, working around certain quirks they come with can be a bit tedious in my experience.

The proprietary driver comes in binary form and is shipped with a small kernel module that handles loading the binary driver. The Linux kernel modules that aren't part of Linux itself (which most drivers are) must be compiled for specific kernel and its binary can work only for that specific kernel and nothing else. This means that even if then driver is the same but kernel changes, the nvidia module must still be recompiled. There are two ways distros handle that: 1) by running the compilation process in the background while installing or updating the driver package 2) by shipping binary form of the nvidia module, in case where it's distro that always recommends synchronization of all packages so that kernel and modules always match. Historically this caused way more problems than it sounds, compilation might have failed for certain kernels occasionally leaving users with broken video after simple system update. Overall though it mostly works fine, especially nowadays.

Another quirk is that the user-space part of the driver that exposes OpenGL and Vulkan interfaces for applications are also proprietary and closed source, and they must also match exactly with the kernel part of the driver. This creates another problem for sandboxed applications using for instance Flatpak. Applications in container won't use the system-wide libraries, but rather ship their own - and that's by design for good reasons. Flatpak will automatically detect NVIDIA and install matching driver just fine, but then after installing system upades, you must always update your flatpaks as well or the ones that use GPU in any way will simply fail to launch or fall back to software rendering making it extremely slow. This doesn't happen for open source drivers, because Mesa can work with basically any kernel, so Mesa in Flatpak can be in completely different version than the one installed as system package. Moreover, I experienced problems with storage space because Flatpak wouldn't automatically remove old NVIDIA drivers and after a year or so it was a chunky pile of NVIDIA drivers.

And even when it works, there can still be missing functionality or integration with the OS might not be perfect. Last time I used them I was limited to X11 with many quirks regarding multi monitor setup and vertical synchronization. Wayland is technically usable now on NVIDIA, but not perfected yet.

[–] azvasKvklenko 1 points 1 month ago

Robocock in my ass

[–] azvasKvklenko 38 points 1 month ago (1 children)

“Elon, deep down you will always be cringe no matter how much money or power you have.”

Deep down? To me he's cringe on the very outside.

[–] azvasKvklenko 14 points 1 month ago

Is that juice brand actually something available in Toronto area? That could tell us more if she's telling the truth or not

[–] azvasKvklenko 7 points 1 month ago

I think that speaking out loud about malicious activities towards women is important and yes, harassment is real, but it really feels like society became almost too sensitive when it comes to approaching women. Some years ago there were video campaigns where they would literally show how one men stops another from talking to stranger female, before he was given a change to be either creepy or nice and respectful with like assumption that this is bad anyway. And also who's to judge where's the boundary between being creep or not anyway, this can be very subjective.

And it's not my POV, I just speak about what I see in internet/media. Being gay introvert I couldn't care less about talking to strangers...

[–] azvasKvklenko 4 points 1 month ago (14 children)

Didn't they explicitly ask via #metoo movement and what not for men to NOT approach them directly ever or else they screem that this is harassment?

[–] azvasKvklenko 15 points 1 month ago (5 children)
 

Pretty exciting times ahead as Valve might finally release SteamOS to more hardware. This amount of Linux desktop coverage would be unimaginable few years ago.

 

Hi, I'm using Arch with gamescope-session-steam and I switch between this and Plasma, usually booting right to Gamescope session. It was all fine and games, but with recent Steam update it is no longer able to connect to any network with its built-in NetworkManager integration.

It shows all the wifi networks as well as my wired connection, but WiFi simply doesn't connect (asks for password and fails immediately) not leaving any log anywhere as if nothing happened.

At first I thought that this might be problem with kwallet not being open, but there's pam log that it opens kwallet fine + it worked before not requiring any extra configuration. The problem also reproduces in gamescope nested mode from within Plasma, though it fills the remembered password from kwallet, fails exactly the same way immediately (not waiting for anything) without producing any log in either NetworkManager service or output from gamescope/steam.

Looks like a Steam bug, or now Steam needs something that I don't have installed, but I don't know what that could be. Any ideas where to troubleshoot?

 
117
That was totally not me (sh.itjust.works)
submitted 10 months ago by azvasKvklenko to c/cats
 

What a vandalism, who would do that

151
I'm made of gum (sh.itjust.works)
submitted 1 year ago by azvasKvklenko to c/cats
 
view more: next ›