Skip Navigation

Posts
1
Comments
68
Joined
3 yr. ago

  • Ryzen 5 2600X w/ an RX580.

    I detailed the issue here. Very persistent and tricky issue to track since there's no reproducible steps and it generates no errors. Happens under zero load, full load, after 5 minutes, 2 hours... it's about as random and as you can get. And yes, RAM is fine.

  • Need to give this a shot. I'm still stuck on 6.6 since 6.7 introduced some obscure bug that's freezing AMD systems.

  • How's Kagi?

  • An unfortunate part of the fediverse is that it attracts people who were too obnoxious for even the more annoying parts of Reddit/Twitter/etc. I've made plenty of attempts to "get into" Mastodon and can confidently say that's a miserable experience across the board if you aren't willing to do the work to curate your feed. Even if you do get a feed that is free of bad actors, conversations rarely veer off-course from Linux, programming, computers, tech, etc., at which point that's fine, I guess, but it's hardly diverse. Also, for all the complaining about "techbros" ruining the fediverse, it sure is full of them.

    I have more faith in Bluesky currently. If they're able to achieve their own kind of federation then I'll gladly jump ship since their userbase is a lot friendlier and more diverse that Mastodon IMO.

  • I was just listening to a podcast recently where one of the (tech illiterate) hosts somehow stumbled upon ffmpeg and went direct to ChatGPT to get instructions on how to use it. They said after a bunch of time plugging different commands into the terminal they realized ChatGPT's output was just close enough to look right but was ultimately "complete gibberish" compared to the actual commands they found via some other resource.

    I've already stumbled upon a few different help posts on various Linux-related forums where people have messed something up after following ChatGPT. I don't doubt that it can sometimes come up with useful output, but it's a real roll of the dice.

  • I had a rock solid AMD RX 580 up until the release of kernel version 6.7. Now I'm lucky to get a system that can remain up for longer than thirty minutes. Sticking to 6.6 has worked for me and definitely something you should try as well, but it's worth noting that any amount of time spent on the issue tracker for AMD GPU stuff will reveal tons of issues from 6.6 as well.

  • I did my first BTRFS setup over the weekend. I followed the Arch wiki to set up what I thought was RAID 1 only to find out nearly a TB of copying later that it was splitting the data between the drives, not mirroring them (only the metadata was in R1.) One command later and I'd converted the filesystem to true RAID 1. I feel like any other system would require a total redo of the entire FS, but BTRFS did it flawlessly.

    I'm still confused, however, as it seems RAID 1 only works with two drives from what I've read. Is that true? Why?

  • I'm fresh off ruling out the RAM via memtest. I'll let it do a longer soak overnight to see if anything fails then, but I'm now on to bisecting the kernel from what I believe is the last release of 6.6 (6.6.13) to hopefully whatever the offending commit is. Been a while since I've had to mess around with manually building the kernel without the aid of linux-tkg, but I'm off to learn it anyway. Thanks for the help!

  • This is what I'll try next. I do think memory is the problem now that I've had a few more hours of research. Kernel 6.7 has issues with elevated RAM usage, so it's absolutely doing something funky with memory that might be exposing underlying hardware issues. I also realized my stable kernel was a version or two away from 6.6.13 (6.6.10), so I'm running it now to see if the issue was introduced late in the 6.6 release cycle, which would be easier to bisect than 6.7.

  • Yeah, the qemu idea was brought up earlier in the thread and it's very interesting. Glad you confirmed you could repro real issues there in the test environment, so it's at least a little likely I'll be able to do the same. Makes sense that it would work and is way better than letting the real system crash and burn. My kernel compile time is pretty short so it shouldn't be too bad to bisect, I'm just not sure how many commits separate my stable kernel from the bugged 6.7. TBH I'm not that familiar with kernel dev., so maybe it's way simpler than that.

  • I was afraid of that. Since I'm not the only one, maybe someone else is doing it already. But if it's still an issue in a few weeks, maybe I'll take it on as a weekend project. As for the motherboard, I believe the latest version is currently on it (2022 or 2023.)

  • Fixed the link. Thanks!

    I've also tried linux-tkg, which I believe rolls in the Zen patches. If it doesn't, I'll definitely try it.

  • That's an interesting idea. I'll have to look into whether it's a viable option first, though.

  • This will be my last resort mostly because I'm fairly certain it's a kernel issue, but yes, I've never ran an extended memtest on this build and should probably let it run overnight at some point just to make sure.

  • If you want to do a bit of engineering: CalDAV supports todo lists. I forget what server software I've got running, but I sync the list to my android phone via DAVx5 and tick off/add items via tasks. For other platforms you can just look for CalDAV-supported programs (most email apps.)

  • This was a solved problem on other sites via wikis and weekly threads. There's no value in another "what distro should I use?" post. It's great that people want to contribute, but there should be a more centralized resource we can refer people to where people can focus this energy.

    As for the Windows threads, they've been a staple of every Linux-focused community for as long as I've been browsing them. I guess if it makes people feel better then I suppose that's enough of a reason to keep them around.

  • Can't you just put the key in? Do they even have physical keys?