That was half the reason I upgraded. I don’t know if my old box would’ve been compatible (probably was), but I wanted it off Microsoft territory so bad and heating about Copilot sent shivers all over my spine.

I’ve never heard of installing any new OS without having to back stuff up. That’s just wishful lazy thinking lol.

You probably won’t have to do anything manually about Wine. Steam has Proton built in and it works great. As others always mention, check ProtonDB.com for user reports on how a specific game will work out.

I haven’t run into any problems in my library, but I honestly haven’t installed a ton of games.

I’ve used Heroic Games Launcher and Lutris for some other launchers (like Battle.net or Epic Games), and those have been a little hit or miss, but I think the main problem is something I’m missing. Not a huge priority but I’m still working on it occasionally.

I haven’t heard anyone call or 3D card since the 90s. They’re video cards or GPUs these days man. AMD has open source drivers that work just fine with Linux and should work just the same as the Windows version I believe.

Nvidia has open source ones, but they seem to be pretty terrible compared to the closed source ones. I had one issue with them last week but I think that was more related to KDE than it was the drivers’ fault.

I don’t really have any fancy hardware to describe how easy that was to get to work. Just a mouse, kb, headset(with mic) all of which worked fine without doing anything. I have a physical dongle for the controller, so I had to get a driver for that so I didn’t have to use a Bluetooth connection (pretty shitty comparatively speaking) or gasp plug it in. Had a few issues with it for a while, there was an updated version under a new name and such but it all works now. Just turn the controller on and it’s working instantly (unless I forget to charge it lol).

1. Depends on how much crap you’re willing to put up with. It’ll all be worth it in the end! (Pro tip: disable secure boot in BIOS)

2. I wrote a whole guide on the two options, but then accidentally deleted my comment. You can either install Linux on another drive, or shrink your NTFS partition and install Linux alongside it. You can always access NTFS from Linux, but not the other way around (by default). If you don’t understand what I’m talking about, you should really look it all up. I would personally just backup and wipe, you can always reinstall Windows if you want to.

3. Have you heard of Valve’s Steam Deck? It’s a handheld gaming device that can play nearly every PC game, and it runs Linux! Valve made gaming on Linux an absolute breeze thanks to Proton. There are some popular games that don’t work, either because Tim Sweeney hates Linux (yes, really) or because the anti-cheat won’t accept Linux, but I only know about Destiny 2 and Rust that have that problem. Easy Anticheat works just fine, I play Apex Legends and Deep Rock Galactic with no issues!

4. If you have AMD, you don’t even have to think about it. Their drivers are part of the Linux kernel. Nvidia is not impossible to use, but you might have some issues. I experience random desktop environment crashes that I can only attribute to their drivers, but it only happens on startup sometimes, which is the least annoying it could be. If you choose a distro that doesn’t mind automatically installing non-free software, you probably won’t need to think about it either. The open source driver, Nouveau, works fine but performs awfully in games (or at least it did a year ago).

If you just want some clear instructions: backup your files, wipe your disk and install Linux Mint Cinnamon Edition. It’s easy peasy to use and getting the proprietary graphics drivers is only a few clicks away. Just configure your Steam games to run through Proton and you might not even tell the difference.

Everything people are saying here checks out, but you might struggle with VR. I haven’t tried VR on Linux yet, but I’ve heard some things about support being pretty janky. Maybe others with experience can weigh in.

There would be no hassle in wiping the drive, you can do it as part of the super easy installation process for any Linux distro. Ideally you would back up any important files and drop them into your fancy new file system once the install is finished. And you can pretty much launch almost any game directly out of steam and it will run. There are a few exceptions for some of those games with anti cheats that rootkit your system, but the majority just work out of the box. Drivers included, but Nvidia might be ever so slightly annoying

Games work fine, if you install linux as a dual boot, you can move the files over (windows files appear as if the windows install was a usb key). Also drivers are fine

To install at minimum you’ll need to likely shrink existing partitions and create new ones for linux if you don’t want to wipe the drive, that would be a dual-boot setup with Windows still installed along side. Or you can just wipe the drive entirely and have only Linux.

Regarding the files you should already have backups of anything important, if you don’t, set it up ASAP.

Messing with partitions can easily cause data loss if something goes wrong.

You also never know when hardware failure, malware, power surges, lightning strikes, or whatever other disaster will happen and cause data loss. 1 copy of files might as well be 0 copies.

You can try to see which mounts get exposed with

showmount -e IP

To see if the actual shares are working.

I think the disks could be Dynamic Disks on which it would not be a good idea to install a linux distro.

Unfortunately Microsoft’s own advice to change it to a basic disk (since it considers dynamic deprecated) WILL RESULT IN DATA LOSS.

Since you only want to access them it seem to be possible with ldmtool. While it is a cli tool there is a corresponding service that at least according to some askubuntu posts and arcwiki should make them behave like normal filesystems.

If you can boot back into windows, turn off quick startup/shutdown, run chkdsk or whatever on the drives, reboot back into windows then boot back into Linux and you’ll be okay.

Quick startup is a kind of weird sleep/hibernate mutant that leaves drives in an unclean state when it turns off, so the Linux drivers for ntfs say “I’m not gonna touch that possibly damaged drive”.

Can you elaborate on the issue you are having? Having a desktop environment is usually necessary to run games.

Just come ask here when you have trouble, and we’ll try to help.

When troubleshooting, the biggest thing is searching the web honestly. But some more things to help you out: look for logs. Linux has loads of logs and sometimes can tell you how to fix the problem.

Logs may not be immediately apparent. Some programs have their own log files that you can look into. Sometimes, if you run the program from the terminal, it’ll print out logs there. Otherwise, you read look through journalctl, although this has logs for everything so might be harder to search.

Another useful tip, particularly for system tools and terminal tools, is manual pages. Just run man ls and replace ls with any command, you’ll get the documentation on how to use that tool.

Ubuntu Wiki Ask Ubuntu Ubuntu Forums

The wiki has some information and should correspond to how Ubuntu specifically is configured. You can ask for ubuntu specific help in those communities. You can also ask here and on several Linux communities on Lemmy.

The Arch Wiki I find to be more in depth than the ubuntu wiki. Of course some things may differ from Ubuntu’s defaults but I found it a useful resource when using Ubuntu.

Finally I suggest you learn a bit about how Linux works in general, what is in what directory, what is wayland and xorg, understand how drives are named etc and some understanding of the terminal (moving around in directories, how to use sudo etc, no need to learn to make bash scripts).

The first thing I’ll say is the reason you’re more comfortable with Windows is because you’ve been using it for however long and learning to deal with the issues it has. The same needs to be done on Linux. You’ll have to learn how it works just like you forgot you did for Windows.

Second, along with logs like other users said, you have to know how to use a search engine well. Most issues will be easy to solve, but some may take some searching. The Arch wiki is a good resource even if you aren’t using Arch.

First suggestion: commit to using Ubuntu for a set period of time. Could be a week, could be 2 hours. When you encounter issues, force yourself to stay on Ubuntu.

What you’ll find is that at first, errors will seem like gibberish, then you’ll do some snooping online, and find out how to access some log files or poke around your loaded modules. You’ll slowly learn commands and what they do.

Eventually, something will click, ie; “wait a minute, I just checked to see which kernel modules are loaded, and I’m missing one that was mentioned in my error, that must mean I need to load that module at boot.” You load that module, reboot, try your command again, and bam, everything works. You’ve learned how to troubleshoot an issue.

The best way to learn Linux is to immerse yourself in it. You can’t efficiently learn German if, every time you hear a phrase you don’t understand, you switch back to English, right?

The language you want is “nonfree” in Debian derivatives.

Depends on the distro. Some have a configuration setting to allow unfree software or not, others have separate repos.

Depends on the distribution, many package managers can filter by license. So you can find anything that doesn’t have an open source license.

This would depend on the distro you use. Most distros will require you to enable a non-free repository before you can install anything that isn’t Foss or open source from the official repos. You could also use an FSF approved distro. Keep in mind, the FSF will only approve distros that don’t include any non-free anything in the official repos. Besides that, you just have to know the licensing before you install it.

Year of mobile linux

[ astronauts meme ]

Always has been

After 26 years of using Linux, I did my first baremetal “immutable” distro install last week.

My youngest son is starting school and instead of the Chromebooks that they recommend, I took a chance and installed Fedora Silverblue on a $200 Lenovo “student-rugged” class laptop. Everything works and he hasn’t had any issues so far. He gets access to the same student platform as the other students through Chrome, but then I can install Minetest and Tux Paint and GCompris as well.

The older kids run Debian stable for years now, but if this works out, I might transition them over next semester.

The other day I learned that you can just grep an unmounted filesystem device. It will read the entire disk sequentially like it’s one huuuuge file. And it will reveal everything on that disk… whether a file inode points to it or not.

Used it to recover data from a file I accidentally clobbered with an errant mv command. It’s not reliable, but when you delete a file, it’s usually not truly gone yet… With a little luck, as long as you know a unique snippet that was in it, you can find it again before the space gets something else written there. Don’t even need special recovery tools to do it, just use dd in a for loop to read the disc in chunks that fit in RAM, and grep -a for your data.

I learned how a kernel actually loads a program and switches between them by using timer interrupts and interrupt vectors that point to specific locations in memory to resume execution from. Not specifically Linux related, but I’m trying to learn more computer science, and it just clicked for me two weeks ago. I’ve been programming microcontrollers for ten years, but those are monolithic programs, and while I knew what interrupts were and have used them, I never understood how an OS actually runs multiple things while staying in control. Now I do. About time I understood a core concept of these machines that have been here all 42 years of my life.

It’s one of those “aha!” moments like when I realized classes and structs are just data types like any other in C++ when I was starting off programming and can be used like them. OOP became fun after that.

I have read that it is faster, though I have not tested it myself. Personally, my initial reason to use it was just to try something new and explore the unix world. My reason for staying is that it is a very simple init system that is pleasant to work with. It made me understand what an init system is and use it a lot more.

Systemd is good if you just want something invisible and you do not want to mess too much with an init system unless you have to. Everything integrates with it

OpenRC is nicer if you want to write your own init scripts. It is very well documented also.

i’d suggest starting by finding out what package in your distro actually decides where audio goes - mostly it is pulseaudio (older) or pipewire (newer).

depending on the details of how your distro and the dongle work, it could either be a simple “pactl set-default-sink <headset-name>”, or a more complicated set of udev rules or pipewire/wireplumber scripts.

note that distros using pipewire still often support a lot of pactl commands, so it may be worth looking at the simple option even when not using pulseaudio.

Is the dongle visible by the system only when the headset is powered on? Does the computer have any way of knowing you’ve turned your headset on? What make and model is that headset?

I don’t use Mint, but I would guess that you could change your repos in /etc/apt/sources.list, run sudo apt update, and then sudo apt full-upgrade. Just make sure the full upgrade isn’t doing really dumb stuff like deleting a bunch of programs.

I could be completely wrong and this could be terrible advice, but this has become the wisdom for me when I use Debian Testing. Of course, I just did straight sudo apt update after Bookworm was released and the upgrade to Trixie went mostly fine. I have never upgraded between stable versions, so I may not be one to say.