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.
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.
Half of these exist because I was bored once.
The Windows 10 and MacOS ones are GPU passthrough enabled and what I occasionally use if I have to use a Windows or Mac application. Windows 7 is also GPU enabled, but is more a nostalgia thing than anything.
I think my PopOS VM was originally installed for fun, but I used it along with my Arch Linux, Debian 12 and Testing (I run Testing on host, but I wanted a fresh environment and was too lazy to spin up a Docker or chroot), Ubuntu 23.10 and Fedora to test various software builds and bugs, as I don't like touching normal Ubuntu unless I must.
The Windows Server 2022 one is one I recently spun up to mess with Windows Docker Containers (I have to port an app to Windows, and was looking at that for CI). That all become moot when I found out Github's CI doesn't support Windows Docker containers despite supporting Windows runners (The organization I'm doing it for uses Github, so I have to use it).
Another update: https://startrek.website/post/13283869 I found a fix for my issue. I'm annoyed that I had it in the first place, but I overall still like my laptop.
Important update in this post: https://startrek.website/post/14075369 I still consider this a good laptop, but this is an important fix if you're using this on Debian 12. When 13 comes out next year, the out-of-box support of this laptop should be basically perfect.
Anyhow, back to the original post: I recently got a brand new laptop, a Thinkpad 21JT001PUS, to consolidate/replace my array of various on-the-go-Linux devices, and I have to say, I'm impressed. I know Thinkpad and Linux aren't news, but for such a recent device, I am surprised how well it works. The price wasn't bad (which makes up for the fact that it's a Zen 3 chip with DDR4, in my opinion), it has good upgradability (I'll touch a bit on my experience later), and hardware support was really good.
I initially tested hardware support with Debian Testing Trixie XFCE (as that was the Live USB I happened to have on hand, since I often test devices and also keep it around as a backup for my desktop, which runs Testing). At first I couldn't get it to boot, but then I found the BIOS setting to enable non-Microsoft certificates. After that, I booted in and found everything worked out of the box (except the fingerprint sensor, of course, but that's extremely rare for any laptop anyway). However, after experience with my previous portable devices, I learned I prefer stable distributions on those, as during some parts of the year, I can go months without opening the laptop.
Thus, I retested with Bookworm. Almost everything worked still, except for the Wi-Fi (which seems to have been introduced in later kernel versions). Luckily, this thing has an ethernet port (From which it is HECK to remove cables - I've found I had to twist the end up a bit to get it out), so I was able to do an install and then add the Backports kernel to get Wi-Fi working.
One minor issue I had (a software fault rather than a hardware/kernel one) was Bluetooth headphones, but as it turned out, it was just that PulseAudio was installed instead of Pipewire, so after switching, it worked flawlessly with Blueman).
As for battery life, so far it seems okay (as I write this, it says 3:29 left at 51%), but I haven't rigorously tested it yet (though I threw on the usual tlp and stuff like that for good measure).
For performance, I once again haven't tested it too rigorously, but I did play some Civ VI, which it was keeping up with just fine.
The upgrabability of this laptop does have one caveat, though. The bottom is a bother to remove, and most Youtube crap conveniently glosses over them. For one, some of the screws would get loose but not come out all the way. I eventually found the trick was to throw some pry tool under the screw head to hold it up so I could get it the rest of the way out. After they were all out, the bottom cover STILL wouldn't budge. This too ended up being a matter of jamming a pick in one corner of the case and running another one to slowly pry up the bottom case on all sides. I lost a plastic tab or two in the process, but that doesn't show up on the outside, and I think 24 GB of RAM (and 2 TB of NVME 2280 storage + 256 GB, the Windows drive that I left in the 2242 bay) will be plenty for a long time.
Overall, I would say this is a great laptop for those who don't want to go the route of purchasing a used laptop for Linux. I'll say an 8.5 out of 10 due to the hard-to-remove bottom cover and weird ethernet port (Update: 8 out of 10 now due to the nasty Wi-Fi bug I had to fix with a few module options, see posts linked in top of page).
Here's the Linux Hardware probe: https://linux-hardware.org/?probe=1e50fb1862
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.