Wasn’t necessarily suggesting 11 LTSC; just my personal choice.

Not really.

Ampere’s for servers; if you have the cash to blow, you can get a fancy workstation, but not a laptop. It’s really a shame; I think Ampere might be able to do well in the consumer CPU market if they wanted to face Qualcomm (and assuming they can get their single core performance up). A lot of their hardware seems to follow standards pretty well.

Graviton is only used internally inside Amazon and not sold to customers.

The only semi-decent ARM laptops you can get right now are Snapdragon ones, some of which kind of support Linux but with a lot of caveats and obnoxious quarks.

I have to have Windows for my university’s test-taking spyware, so I just have a barebones 11 LTSC installed on a secondary drive.

I just looked it up, and it seems a lot of the pre-Apple Silicon MacBook had swappable airport cards that used a completely standard mini PCIE slot. From a cursory google search, it looks completely possible to swap in something like an Intel Wi-Fi card that is supported natively by the kernel.

A mini-PCIE Wi-Fi modem can be had for not too expensive, around the $30 range; in fact, if you have a good stack of old Wintel laptops, one of those might have a card that works well. In fact, I did that with my sister‘s laptop (although she was using Windowd) – her Realtek Wi-Fi card was causing endless misery, so I ripped the Intel modem out of an ultra book from circa 2016 and put it in her laptop. No more issues.

Exactly. Luckily, back in high school, my IB History class spent a good couple months just learning about authoritarian rulers and their tactics.

I especially like pulling out Pinochet because he’s a clear and relatively recent example of right wing authoritarianism, manipulation of existing religious structures, and US government support of authoritarian regimes that help contextualize its trend towards authoritarianism.

I mean, I had an uncle showing me HTML at 7 (not a programming language, but still). I learned basic JS on Khan Academy at 11, and if I’d known it had existed earlier, I would have started earlier.

That’s pretty normal for most UEFI x86_64 things up to 2020 or so.

UEFI first became common on new computers in 2011-2012, so I don’t a lot of 2014 computers were BIOS.

I have a cheapo laptop from 2012 (one of last Gateways) and it’s a UEFI machine.

At this point, I think 15 years ago is a more realistic estimate for the last legacy BIOS machines - my Win7 box with a 1st gen i5 is legacy BIOS.

My grandfather asked me about Linux, but unfortunately, he’s still using Photoshop for now.

Not great. I even got GPU passthrough working once, but you get weird graphics glitches because it’s all being sent over RDP.

I think Cassowary might be better than WinApps, but honestly, at this point, I just gave up on those and just use the VM directly.

When it freeze, after you’ve rebooted it, try running sudo journalctl -p 5 -b -1; you might see something in those logs.

Maybe also open a task manager before you do anything graphics intensive, just to see if there’s a process that rapidly increases its memory usage; while it might not be the cause, I’ve experienced similar freezes when I use all my memory (on a machine with 32GB of RAM).

FYI Don’t use this command. I think it was intended as a joke, but I just want to clarify.

Fun fact: you didn’t have to reinstall; you can actually boot up a live usb and chroot into your install to fix things.

That is kind of awesome.

I wish Debian’s default Grub theme was less ugly; I know I could change it (and I have on other installs, but I’m quite lazy about theming these days. Part of it is I have a laptop that I rely on for college and don’t want to risk any theme glitches, so I keep its Debian install as vanilla as possible.

May I ask what your config was, such as distro, packaging format, and extensions were used? Also, what hardware?

Additionally, what issues specifically were you experiencing specifically? Were sites just loading slowly?

I ask because I’ve used recent versions Firefox on decently old hardware with 4 GB of RAM and 2 cores and had almost no problems. Everything rendered correctly and in a reasonable amount of time. I’d be curious to know why that isn’t happening for you.

Huh. I guess 3 years of Debian usage has just gotten me used to stuff like that.

I can see where one might go wrong; there’s a lot of sections in that guide with contingencies only meant for specific situations, like upgrading from a USB or optical disc.

May I ask: when did you last try Firefox? There was a period during the 2010s when it has truly horrible performance, but they rolled out some major updates several years ago that greatly improved performance (though wouldn’t call some of the UI changes improvements).

Honestly, every major rendering engine is terrible in some way.

• Blink is resource intensive and has so many non-standard APIs for the sake of Google’s version of “Embrace, Extend, Extinguish”.
• WebKit takes 50 years to support the newest standards.
• Gecko (Firefox) is non-modular and is limited to being used in Firefox, Thunderbird, and forks and Firefox as a result. Its performance is also somewhat worse than Chrome’s, but not noticeable for daily use.

Ultimately, I choose Firefox because its issues are the least annoying to me. I do wish its structure was more community-based and less corporation-eating-its-own-hand, but whatever. So long as Debian sees it fit to keep in its repos, I’ll use it.

Honestly, even those don’t run that horrid for me when I have to use them.

Did you restart the computer after the upgrade and before reinstalling third party repo packages?

The “half the programs not working” kind of sounds like you had packages compiled for a newer libc and the like but the newer libc wasn’t in memory yet because you hadn’t restarted.

May I ask how your Debian upgrades go wrong?

I mostly say so because I recently upgraded from 12 to 13 with almost no issues; the only issue was something with Apache that ended up being a quick fix. I followed the official Debian guide and temporarily remove third party repos and packages.