I’m not sure. Didn’t they just move the code that was previously executed in the proprietary kernel module to the new also proprietary userspace driver that’s just connected to the hardware by this new and open source wrapper module? And the other half into firmware? It’s still arbitrary and closed code that gets forwarded to the hardware. And running there it has access to all the memory, screen content etc… I’m not sure if this is a win concerning security. I think it’s pretty much unchanged.
But there are several big advantages. Now the kernel probably won’t get tainted any longer and we can have signed kernels and activate secure boot easily. And that’s maybe a big plus for security. And I hope we’ll get the convenience, too. In the past I had the NVidia driver crap out on me while debugging stuff with recent kernel versions or release candidates. And NVidia was lagging behind, leaving me with a console instead of the desktop environment…
Didn’t they just move the code that was previously executed in the proprietary kernel module to the new also proprietary userspace driver
Probably. And that is exactly what was expected from them since the beginning of their Linux drivers. Kernel is not a place for such big and proprietary piece of code. So this is the important change.
Yes, the driver is still proprietary, but it does not break the kernel any more the way it did.
It’s the part that can legally be distributed with Linux distributions (including in-car OS) due the kernel’s license. The actual functionality is in the proprietary user space driver
I think it’s more like small bugs in the kernel portion will be fixed faster. There are a lot of small patches needed to build the dkms module against the kernel as mainline and stable evolve - they’re often carried in various distro packages until upstream (Nvidia) picks them up for a future release. The open driver should speed that cycle along.
It’s not likely that the driver will be mainlined anytime soon, so no. It’s the same as with the proprietary kernel driver, except maybe some being able to patch problems with newer kernel versions by themselves.
I don’t play D4 anymore so I can’t say if this still works, but back when I did, I used to launch it (ie the Battle.net launcher) from Steam, as a non-Steam game.
I also used the latest Proton-GE as the compatibility tool, so that’s something you could try as well.
That never even occurred to me and I used to do this for non steam stuff all the time. I mean without the added learning curve of Linux but still.
I’m gonna try that as soon as it finishes patching. If that works it would be so amazing. Almost too simple to actually work.
Edit- It’s already working better than Lutris. It would have chunks of the UI just turn black sometimes. All the interactable bits would come back if I pointed the mouse at them, but there would be black squares and rectangles all over the place with Lutris and I just chalked it up to a weird quirk that forcing cross compatibility just brought up inherently. Never even questioned it.
Only advice: Don’t install on the same hard drive.
I dont care how many people say “oh it works for me” it works for everyone until it doesnt, and then you spend days fucking about with utilities that you shouldnt be fucking with, and at best it works until it stops working again.
There’s likely little risk that any attack goes after a potential linux partition, but there’s much more risk that either your linux or Windows partition bricks the other.
Game is still having problems even when launched from Steam.
I cannot get Battle.net to launch with any regular Proton version or Experimental. I also can only get it running with GE after version 8-26. (only 3 versions, 8-26, 9-1, and 9-5)
But every version up to 9-5 has the gray screen for a couple seconds, then the game closes with no error message.
I was having issues with Jedi Survivor and Steam Input apparently due to the latest EA launcher. Turning the controller on after the game loaded fixed the issue for me.
linux_gaming
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.