[mariusor]

Basically the same things happened to my tuxedo also. With the addition of having to change batteries once a year, because it would drop to half it's factory charge, which wasn't really sufficient. I also gave up on them when they wanted so much money for a screen change (which died after about 3-4 years).

I've replaced it with the new framework 13 inch, which so far works well, but I've only had it for 4-5 months. ( well, but not perfect, because the new AMD AI CPU has issues with suspend on linux)

[blacksmith_tb]

That's a shame, I got a 13 w/ the previous non-AI AMD 7 7840U in April, and it's been rock-solid running Pop_OS. I wondered at the time if I should have waited for the newer CPUs...

[ekianjo]

at least with framework you know exactly how much the replacement parts will cost ahead of time.

[wyldfire]

> issues with suspend on linux

Oh? I'd seriously considered buying the 13 w/this AMD CPU and I guess I naively thought it would be ideal. What sort of problems with suspend are you seeing?

[oDot]

I have a Zephyrus G16 with a 370 and can confirm it would fail to sleep on Linux 6.12.

Upgraded to 6.15 and sleep seems to work well now.

I use NixOS

[microtonal]

I have a T14 Gen 5 AMD. No issues with suspend/resume at all. NixOS, kernel 6.12. The Ryzen AI APUs are fairly new, so it may take a few months for things to settle.

[mariusor]

I haven't spent time investigating if my specific setup is the problem, or an actual bug in the drivers, but after I resume from suspend, the btrfs root fs is in a read-only state.

The only solution is to reboot/shutdown, but it takes a long time and there are some scary fs checks running. Luckily no lost data so far. Currently I'm just shutting down the machine every time because it the boot times are quite fast.

[javier2]

If you use Ubuntu or something similar, it literally takes years for kernel fixes to trickle down. Its quite unfortunate