I’m in a similar boat as you and my current plan is to switch to PopOS. They are Ubuntu/Debian based so you will be familiar with it, and they also are a distro that is more focused on gaming, so you will have an easier time with video card drivers.
The only issue that I have with pop OS is that it seems unnecessarily slow at times.
I'm running a Lenovo legion 5 with a 10750x, 32 gigs of ram, and a 2060 in it and sometimes it would feel a full second between when I click the button and when something happens.
Fedora was a little bit better about that, but I don't use that because of the weird politics surrounding Fedora right now.
Now I'm on a mint cinnamon and it's actually pretty good, although I have yet to try playing any games from steam on it.
The other issues I have is that Fedora would keep my Bluetooth speakers connected between reboots but both pop OS and Linux cinnamon require that I manually reconnect every time.
I was in a similar boat to you, but then I installed pop and just gave it a go. Stuck it on a separate hd for now but with everything setup and working I’m very happy with it.
Debian is great for gaming just takes a little work. I run Debian sid and that has its pros and cons but I do it to have super updated packages and to help report bugs. But running stable with a mix of flatpaks and backports works great as well.
Debian is great since it’s just super vanilla packages from upstream for you to make it the way you want it.
I use KDE but that is out of habit and preference I have used them all and they all have pros and cons. Debian doesn’t customize them at all so there is no Debian specific DE for stable or sid.
It’s all about how they make you feel using them. also the nice thing is you can use gnome apps on kde and kde apps on gnome so unless you super care about theme there is no down side.
Like my favorite scanner app is Document Scanner for gnome and when I’m on gnome my favorite text editor is Kate. Yeah you’re doubling your needed disk space for libraries but disks space is cheap and your going to use up more space with flatpaks anyway.
I’m currently looking into xfce vs KDE plasma, something I need to pay attention to is a DE with x11 because nvidia hasn’t fully supported wayland ?
Am I right to consider it that way? Or do both support nvidia drivers?
I’m sorry, I only use debian as bare bone on my server and currently considering to switch my main desktop from windaube to linux and alot of informations on the web seem contradictory or incomplete :/
I run AMD now but ran Nvidia for years (RIP Evga). I had no issues with ether DE, other than the occasional update breaking things (only an issue with Sid) but that’s what you use timeshift to rollback for when something breaks and apt-listbugs to be aware of issues before you update.
Note you can swap between X11 and Wayland on KDE by just changing the session on login.
Thanks :) good to know I can switch between those two in KDE ! I need to test Plasma and xfce to see wich fits better my needs and has better suppport for my system !
Nvidia nuked power managment mid-Maxwell. Gladly, at least one vulnreability has been discovered, that theoretically allows nouveau load their power manager.
Almost a decade ago there was a discussion how to draw into display buffers for Wayland. Everybody agreed on using Mesa GBM, nvidia wasn’t really interested, but said they’d do EGLstreams.
As nvidia wasn’t interested, and generally is a dick to everybody anyway Wayland development just progressed ignoring nvidia, and now they have to catch up to where all the other graphics driver were at already years ago. While ignoring most of the things those others learned, because they want to keep their own tiny proprietary island.
Just avoid supporting nvidias dickish behaviour by not giving them money, and eventually they might learn and change.
I appreciate it, I was more so wondering whether or not I could keep my existing build as is aside from the GUI. I’ve done it the headless/CLI via ssh route previously but thought I’d check out using the GUI during the setup stages and being able to enable/disable the GUI at will and how that would affect performance vs installing only CLI at the start of the build.
Depends on specific machine setup and how good the backup is.
Backup requirements for /usr there are sticky bits set on some binaries. That needs to be preserved. In all cases soft links likely need to be preserved for things to work correctly on future package installs. Hard links can be problematic, but if you have a large enough drive or not that many it wont matter. Running package verification can be help after restore to make sure everything looks right. If running a Linux system with SELinux in enforcing mode (RHEL on many derivatives), then the security context will also need to be preserved BUT running a relabel will probably work if the security context was not included in backups. Sometimes running the relabel process wont work if there are files that needs a specific security context but are not listed in the security context database. Can’t provide more details because most of my experience with that is on systems we just replace (LSPP custom labeling resulted in systems that if you booted into permissive would then be unbootable, so they were just reinstalled once any debugging was done).
For /boot things can get tricky depending on the distribution, what boot manager is used, and /boot was a separate partition or not. Basically the boot manager (probably grub) needs to know how to find the files in boot so it can load the kernel. In most cases if you restore /boot and rerun the tools to update the boot manger everything will be fine. BUT some distributions, hardware setups, or dual boot configurations are more complicated, so extra work might be needed.
You didn’t mention /dev, which is all special files. These don’t need to be restored, just make sure the right processes recreate them. There are tools to do this, hopefully the packages are installed. Or boot from a rescue disk and fix it. Look up instruction for your specific distro.
What a sensational, over blown article. ArsTechnica this is shitty journalism and you should know it.
The headline would be about as correct if it said “SystemD update will bring Amiga’s Guru Meditation screen to Linux.”
This update has nothing to do with Windows. Error displays with additional information about the crash is not exclusive to windows, nor new. In fact a Kernel Panic screen happened in Unix.
The majority of linux articles have me checking the comments first to see if someone talks about ridiculous click bait crap, honestly saved me a lot of time.
I suppose that’s the main problem, I didn’t check the article since the title reeks clickbaity enough. However I wouldn’t share an article if the the title obviously is a clickbait, I’m sure there are bunch of respectable sources about this development.
linux
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.