“Life forms. You precious little lifeforms. You tiny little lifeforms. Where are you?”
- Lt. Cmdr Data, Star Trek: Generations
I used to use this, but I always found it really janky - window boundaries not updating, weird graphical glitches, etcetera.
It was especially annoying to use with Photoshop and GPU acceleration (I do GPU passthrough to my VM).
In the end, I just abandoned it and just used the monitor the VM’s GPU is plugged into.
As a completely new user who’s self-described as “not very tech savvy”, Arch is probably a terrible idea, and you should switch distros.
I really like Debian, but something like Linux Mint or Fedora might be wiser for you; all three hold your hand more, which would be very important in your case. Fedora and Debian specifically are designed to work well with KDE, although Fedora will have newer versions.
You certainly seem willing to learn (you got through the Arch install process), and I think you still have a great opportunity to enjoy Linux, but considering you’re calling the terminal emulator “Konsole”, your self-description is probably apt. FYI Konsole is just one application to access the terminal, kind of like how Firefox and Chrome are both web browsers, but you don’t use “Chrome” to refer to web browsers.
I use this image, which mostly just works (other than the need to throw model info and a made-up serial into a config.plist.
https://github.com/thenickdude/KVM-Opencore
I can’t say for 15.6, but mine is currently running 15.2 just fine; I usually fall a bit behind on updates since these days, I only really use it to upload They Might Ne Giants rarities to my cloud library via Apple Music.
The only annoyance with the VM is iPhones can’t connect over USB easily.
I don’t use Proxmox, but since it’s all libvirt anyway, I’ve frequently found someone doing something on it that helps me with my VMs.
For instance, my GPU passthrough Hackintosh VM is part based on some dude who made a tutorial for Proxmox that applies elsewhere.
No.
I usually just use Bash; there’s a certain level of complexity where it begins to be more reasonable to just use Python.
Yes and no. I think connotation is important here; “stable” means different things in different contexts even within computing, and they both denote different but important things - kind of like free of cost verses freedom.
In the distro case, people need/want a distribution where they know a new version won’t come and break their config when they update at 2 AM and miss it in the changelog, and “stable” has been agreed upon as the term in that context. Of course, that can change, as all language does, but that’s just the current convention.
Also, Debian tends to make sure software is not unusable before stable is shipped (the Nvidia thing is an anomaly I’ll explain below); while they sometimes fail, as you’ve hinted, I find it quite rare that it actually happens. Also, the “static” of Debian isn’t absolute; if something really has a breaking bug or a security vulnerability that affects overall system usability (basically something that can’t be fixed by installing a Flatpak), they will put out a fix, like with the Linux kernel or a web browser (via the security repo, included by default in all installs).
Additionally, looking at this changelog, while the Nvidia situation is objectively a bit embarrassing, it looks like they were working on getting them updated, but just didn’t have much luck - I’m guessing a breaking change in the software that made it harder to package. Also, it’s in the non-free repo, which is on the back burner compared to the rest of the distro - something in the main repo will usually only be at most a few months behind at time of distro release.
I mean, I think static is stable.
I feel like stability in some contexts means more than just the software not crashing often (although that is the big part); it means being able to expect the behavior to stay the same until you’re ready to upgrade to the next release and confront the new behavior all at once, sort of like upgrading Windows XP to Windows 7.
There’s certainly a place for rolling release - I use Debian Testing on my desktop - but I certainly appreciate being able to go a month without opening my laptop without getting a daunting notification like “There are 1578 updates available “ (on my Debian 12 Thinkpad, it’s usually only double digit, very minor updates).
Unrelated thing - just found out something funny.
Apparently, Torvalds himself uses a 580.
Someone else brought up Virt Manager here, which is my preferred; if you’ve ever used VirtualBox, you’ll probably be fine on Virt Manager. I like Virt Manager for using GTK3, as I’m in XFCE. I wouldn’t be surprised if both applications have similar settings, as they’re both LibVirt front ends, it seems.
Also, DistroBox, while a different sort of thing, is great for the sort of thing OP mentioned in that last paragraph. I usually just use command line, but there seems to be an unofficial GUI out there.
I always just booted the old kernel when I ran into the issue, but it was less than ideal, which is why I would prefer to run a stable distro in this case.
Also, isn’t ElementaryOS a stable distro anyway due to being Ubuntu-based?
I’ve never run an installfest, but I’ve been to my university’s Linux Users Group installfests, and here’s what they did:
Also, I’d recommend you bring extra USB peripherals in case the internal devices need a little bit of work; bring some extra mice, keyboards, and ethernet adapters. You hopefully won’t need any of them, but they’ll certainly make life easier if you do.
As for time, I’d imagine doing the basic install and ironing out some (not all) of the kinks probably takes less than it takes for a group to stat D & D characters, if that’s a helpful comparison for you.
It’s pre-T2, so it should be very easy to install a Linux distro on it. The only bit of misery you’re going to encounter, as others have said, is the Broadcom drivers. Except for a select few distros, you’ll probably need a USB Ethernet adapter for installing the operating system and adding the drivers.
Also, I’d rather put my hand in the circle saw than try running a rolling release on this laptop because the driver uses DKMS, meaning that kernel updates sometimes break it.
I only know this because the desktop I’m typing this on has a Broadcom Wi-Fi card from when I used to bare metal Hackintosh this machine. I’ve since moved to a nice house with an Ethernet port in every room; also, I just use macOS in a VM these days anyways.
As others have said, OCLP is a thing and a well-oiled machine from what I hear, but also, the oath I have made to the Church of Linuxology demands that I at least recommend Linux.
As said by @iii@mander.xyz, bog standard Debian Stable.
You really don’t want a rolling release distro for something like this - major software updates might change the behavior of your software, break your configs, etcetera. Stable distros do as much as they can to make sure that software behaves the same, only porting security fixes.
This way, you don’t really have to touch it except for updates with a nearly nonexistent chance of going wrong (and there’s stuff like unattended-upgrades so updates are automatic) and major upgrades.
You can go several years without a major upgrade just fine - Debian versions are supported for 5 years, and we’re only a few days from getting Trixie, which will last into 2030. New versions come out every two years, and it’s not that hard to upgrade between consecutive ones; I don’t think sitting down on a weekend every two years is that bad.
I kind of hate Ubuntu, but it’s pretty based in this case due to really long support. This might be a really great case for Rocky Linux though, as it also gets 10 years support.
Luckily, I can probably live with using mine a few more years. Mine’s an early AM4 system with a Ryzen 5 2600 in it. My CPU performance isn’t a huge bottleneck (although I’d like a couple more cores for faster compilation).
Really, it’s my graphics card. The 580’s fine for some basic gaming, but it sort of got left in the dust with ROCm support - it’s kind-of-sort-of supported, but not well enough for Blender to work with it.
I think the situation’s improved with ROCm on consumer GPUs enough now that so long as I buy a newer card, I should be fine. Debian support’s improved a lot as well - for many GPUs, it should just be a matter of sudo apt install hipcc now. However, Debian is still a few versions behind in experimental and doesn’t support the latest AMD cards, but I suspect that getting it packaged was the hard part, and that once Trixie releases, Forky/Testing will catch up in a few months.
I didn’t even know there were still cases bundled with power supplies! But yes, in general, throughout the history of PC building, I’m pretty sure included power supplies in any brand tend to be very low wattage. The power supply probably isn’t even broken - I’m just guessing the PC’s was upgraded to an RX 580, and the RX 580 was more power hungry than the original graphics card and the power supply just wasn’t designed for it.
Just a tip - next time you build or upgrade a PC, use this tool to estimate what power supply you need; https://www.newegg.com/tools/power-supply-calculator
You can get a 700 watt PSU that should work in the $50-70 range, although honestly, it might be worth it to go a bit bigger so you can cannibalize it for a future build when the time comes - even the RX 580, which is newer than your CPU, is getting a bit old and I hope to replace it if I build a new PC in 2028.
Just to clarify, this almost certainly won’t be better on Mint for several reasons. One, PopOS! and Mint are both based on Ubuntu, so they would likely run into a lot of the same issues. I also have an RX 580, and while I haven’t used either of these distros on that machine, I have run Debian Testing for several years, and since both these distros descend from Debian, I have run similar package versions and would likely have known years ago if a major bug occurred for my GPU.
As said by @Mordikan@kbin.earth below, I would be inclined to check the power supply, and maybe even make sure the PCIe card is properly seated.
I’ve been running with an RX 580 on my desktop with Debian Testing for three years, and I’ve had no problems like this.
I’m running with a 750W power supply, so I’m inclined to agree that the the OP should pop open their PC case and check their wattage. Assuming this is an ATX box, it’s probably just a matter of removing two screws and sliding off the side of the case and reading the wattage. If it’s a reasonable wattage and it’s still giving issues, then try the aforementioned undervolting.
True! I guess I don’t mean that many implementations are inherently bad.
I guess the web browser analogy brings up the point that even though there’s many major behavioral differences between Wayland implementations right now that can make life a bit miserable, there’s hope that standardization could improve and make it easier to make sure applications work anywhere. I’m just a little sad a lot of important thinks weren’t standardized from the beginning/
I mean, at least systemd is one(-ish) program with one API that everyone can target like xorg. There’s so many different Wayland implementations that it gets rather mind-boggling.
Of course, I don’t hate Wayland - I just currently use XFCE. If XFCE ever switches, I’ll go along with it. If applications end xorg support before XFCe switches(or if XFCE becomes unmaintained), I’ll consider jumping ship to something that uses Wayland.
Maybe it’s because I only use stable on my laptop with Flatpaks, but honestly, Bookworm never got that crusty to me until recently - it feels like new software versions didn’t introduce a lot of must have features in the past two years. Only hiccup was I had to install the backports kernel to get Wi-Fi working.