0x0

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 started doing this after my phone number got into some kind of crazy scam call database. At the height of it I was getting somewhere in the neighborhood of 30 calls a day, basically rendering the phone unusable.

So I started actually picking up and running these jokesters through the ringer. I'm talking 15+ minutes of pointless conversation, false info, tons of backtracking, and general bullshit. I refined my craft over a few months and would time how quickly I could make them scream at me for fucking with them. At the end of it my phone got taken off at least one of the bigger lists because the calls went to down only 10 or so a day. Now it's one or two a day at the most, probably from me not answering like I used to.

Favorite call was one guy who figured out I was messing with him and it turned into this general question and answer thing about life in the US. Dude wanted to know how easy it was to pick up chicks and whether or not I'd dated a lot/was married. Great guy, really into Counter-Strike.

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.

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.

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?

Does a scheduler impact power draw? Maybe you're confusing this for a CPU governor perhaps?

And yes, the underlying tech here is user-configurable schedulers. Very neat.

For those getting excited, It doesn't "boost" gaming performance. It prioritizes the game over the background process (in this case, a kernel being compiled.)

Schedulers aren't magic. As pointed out in the comments of the linked article, there are other ways of doing this. The more interesting tech here is being able to choose between schedulers under specific workloads, which is very nice IMO.