I was forced to use heroic launcher because I couldn’t get genshin impact to run on steam from my games drive. It kept pushing it to my home drive and I didn’t want that. I’m now in love with heroic launcher(this is my first time ever using it). So beautiful and very practical. I also use it to install regular .exe files. Very solid. I’m going to donate to the project, that’s how much I actually like it 😄
I’ve been trying harder to diversify my youtube content. Please share links to visible minority (from a western pov) creators who post similar content. Why are there so few?
Gnome 3 has an option to keep one display fixed when changing workspaces… Also most window managers allow you to keep certain windows on all workspaces, maybe that will help?
Provided that the approriate drivers and binary firmware blobs for the new card are already on your system (and with a user-friendly distro like Mint, they should be), I’d expect you to be able just to plug in and go. The only extra hoops I had to jump through while sidegrading from a 1050 to an AMD card of the same era were due to my having a hand-configured kernel and X setup with no AMD drivers.
Linux noob here. Why do people refuse to use the proprietary driver? I did not had any seriousl issue with my 2080ti on Nobara. I can game and edit videos with better performances than in windows with same pc
using external kerner driver (“out of tree”) come with caveats you need to take care of
typically most linux distros will do this completely transparent but certain usecases will be more complicated
espcially if you install packages outside of your linux distro repository like a newer kernel version or an older Virtual Box version
I’ve been using Linux for over 20 years and I don’t get it either. I don’t know why a vocal minority get so fixated on it. It’s not like it’s the only manufacturer with proprietary drivers. As long as the drivers work and are easy to install I don’t see a problem.
I’ve used ATI/AMD cards equally over the years and I’ve always ended up having more problems overall with them than with Nvidia cards & drivers. If I were inclined to generalize I could say that open source drivers are apparently lower quality, right? 🙂
But that would be just as silly as the other way around. I don’t think that open or closed drivers, in itself, automatically says anything about quality.
If closed source drivers really were a problem then Nvidia wouldn’t be used by 80% of Linux gamers.
You are lucky if you can play without a crash for even one minute with that card. I am not exaggerating. Something is seriously messed up with the 20XX series.
Also Wayland is still a mess for Nvidia cards overall which is becoming more and more important.
Weird. I’ve tried about 12 games, they all work perfectly. Only in one case, I had to switch to an x session. Wayland is super responsive, only some small visual glitch from time to time. Da vinci studio edits and render videos super fast.
According to a ProtonDB user the specific crashes I am referring to have been finally fixed with 545.29.02. So two weeks ago for a 5 years old card. Good job Nvidia!
I would have loved having that earlier, because I threw mine out after all the frustration with Nvidia and I still doubt that it is fully working now.
Don’t get me wrong it’s great for others stuck with Nvidia hardware though. I would never ever recommend buying any Nvidia hardware for Linux though. The experience is miserable compared to AMD.
I have had so many issues with Nvidia drivers, especially on laptops with Optimus. Black screens after booting, random breakage when updating, having to fuck around with OpenGL libraries all the time when you have integrated Intel graphics and Nvidia graphics on the same system. It’s just a pain for me on laptops.
Wouldn’t be such a big issue on a desktop, but I’ve had a work-provided workstation with an Nvidia and 99% of the time if something broke on that machine, it was because Nvidia wasn’t compatible with some updated kernel or libraries.
Intel and AMD have both provided us with a painless driver experience that just works out of the box all the time and is integrated in all the open source things (mainly the Linux kernel and the Mesa libraries for OpenGL & Vulkan). With Nvidia, you need to throw all that out and use their proprietary blobs for OpenGL and Vulkan.
Also, I just think Nvidia is a scumbag company, trying to force single-vendor proprietary solutions on the market by abusing their dominant position (pushing CUDA while refusing to implement any new OpenCL version for over a decade, so software vendors couldn’t just pick a competitive open alternative is one example, the original G-Sync is another). I prefer not to give them any money if I can help it.
Nvidia Optimus has come a long way on Linux. Manjaro and Mint have utilities to enable it out of the box.
THAT SAID
We still have to prepend all programs we want to use the Nvidia GPU with prime-run. I’m not sure if mobile AMD users have to do the same, but this is legitimately annoying as hell this many years later and would actually be a good reason to pick AMD over Nvidia.
I’m not sure if mobile AMD users have to do the same
No we don’t. Mesa and the kernel automatically decide to use the dGPU for intensive tasks. It is only on rare ocassions that I have to use the DRI_PRIME=1 to force the use of the dGPU. It has been months since I last did it
There is a strong desire to see if there is secret sauce in the driver that makes their cards so darn performant. Could it be applied to other video drivers?
To audit for vulnerabilities and fix them.
To allow the driver to use some kernel internals that the kernel developers keep trying to wall proprietary drivers off from.
Ideology
Community might be able to hack it to work better with Wayland, since the Wayland team has no interest in extending any kind of support to proprietary driver driving GPU’s… despite x11 working just fine forever. … see Ideology.
Its a proprietary driver, which could be an insane security and privacy risk. Its a modification to your kernel, normal on Windows, but not on Linux. It basically makes Linuxes security model weak.
I pretty new to Linux gaming but I love it. Currently playing games directly from Steam and Blizzard games via Bottles. Please help me out with a few questions. What is the use case for gamescope? What is the use case for Heroic? Is it instead of Bottles/Lutris?
Game scope is a micro-compositor, it’s how the Steamdeck handles games and probably steam. Basically the settings there, you can have the game in 1080p but upscaled by FSR/DLSS to 4k. The difference is that only the game is upscaled, not the whole system
Heroic is a launcher for Epic, Amazon, and GOG
Yes, it can be seen as an alternative to Bottles/Lutris but the stores and libraries are baked in
The application needs to speak a protocol to be able to use it. If you use a X wm your apps need to be able to talk X’s protocol to work, if you use a Wayland compositor your apps need to be able to talk Wayland’s protocol (or run on Xwayland, which is basically an X server that runs inside Wayland).
The wm/compositor abstractions only work if your apps know how to use them via the correct protocol
They are themselves abstraction layers for the apps that are made for them. Software has many levels of abstraction from what you see on the screen all the way down to hardware.
Typically the abstraction to draw elemnts inside a app window is in the application framework, like GTK, Qt, Electron (chromium), etc.
This is also why apps built with the same framework typically have the same problem on wayland (looking at you, electron).
The abstractions you are thinking of is not in the window manager, which only controls things outside of the main app window, like tiling, border, window top bar, etc.
Yes, part of my confusion was simply mixing up the job of the app frameworks/gui toolkits for the wm. It was weird to me that some apps like firefox had to provide wayland support by themselves and couldn’t simply rely on abstraction layers from whathever they’re coded in. However, I looked for some info, and found out that firefox renders some widgets on its own, and now it makes sense that they need to provide wayland support.
If you’ve ever had your WM crash, then you may lose the decorations on your windows, the ability to minimize/maximize them or move them around, but the windows themselves still stick around. Restarting the WM brings that all back as well
For X there was only one protocol, so they all wrote for x.
This also allowed some hacky things to be done that are questionable from a security standpoint afaik.
X11 and Wayland are just protocols. These protocols are used to abstract the window drawing from the actual hardware and runtime environment as much as reasonably possible - because nobody wants to maintain 3215 versions of their app for different runtime environments. So in order to be shown on the screen an app needs to implement either the X11 or the Wayland protocol (or both!).
The piece of software that is on the other side depends on whether the app is using X11 or Wayland. For the sake of simplicity let's assume that the app does only support one of those. If the app supports Wayland then it will try to connect to a Wayland compositor. The compositor implements every part of the protocol and makes sure that the window is rendered on the screen and that user input is forwarded to the app. If the app supports X11 then it will try to connect to a X server and take the role of an X client. This is (on Linux, essentially) always X.org*. X.org also implements every part of the protocol and makes sure that the window is rendered on the screen and that user input is forwarded to the app.
Unless you're running a Wayland compositor, then it will connect to XWayland which passes through the window to your compositor.
Wayland compositors have full control over the apps while the abilities of apps are purposefully restricted.
A window manager is just another regular, boring, old X client connecting to the X server. It doesn't actually abstract anything. It can move windows because the X11 protocol allows it to, but any other X client could just as well move all other windows around, read all user input to all other windows and even move the mouse around as it pleases.
So, to be specific, there is no mouse pointer bug in Virtualbox while using Wayland. There is a mouse pointer bug affecting specific Wayland compositors, likely because they enforce GPU hardware acceleration that is lacking in either your VM or the Linux kernel because of missing drivers. Try using a different compositor, (re)installing Virtualbox Guest Additions with the correct version on the guest system and/or check whether hardware acceleration is enabled for the VM and has enough video memory.
I picked up a Black Friday Lenovo ChromeBook (Flex 3) for US $160 and use it essentially the same way you describe. You can load up a Debian-based Linux environment within ChromeOS. It’s basically my web-capable thin client.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.