data1701d

I've never run an installfest, but I've been to my university's Linux Users Group installfests, and here's what they did:

• Brought USBs with Fedora and OpenSUSE, which are their standard noob recommendations. Personally, I've used Debian for a long time, but I can get why Debian might not be something they want to recommend for noobs.
• Be there to help them
• If they're a bit squeemish about it, have them install in a VM software like VirtualBox on Windows or something like UTM on macOS.

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.

Here’s my go at it:

My rationale is this is an Intrepid-based Miranda replacement attempt. The boom below the nacelles can be configured for extra weapons, sensors, or even as nacelles to allow an improved warp geometry for towing vessels below the ship (although good for towing, the ship has overall slower max speeds this way). They can also just be straight-up removed, the fastest configuration for the ship, as it get rid of the structural integrity field requirements for the boom.

All Starfleet warp cores built 2378 and later secretly use a constantly tortured transporter clone of Chief O’Brien in order to improve dilithium usage efficiency by 76%.

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.

I think that's true, but permissions might come into play and really cause pain; it's probably best to just reinstall.