5 ms·

It looks like the author has hit some pretty serious snags along the way and is a lot more understanding than I might be under similar circumstances. My experi

It looks like the author has hit some pretty serious snags along the way and is a lot more understanding than I might be under similar circumstances. My experience, having just bought a framework 13 with AMD internals a couple of months ago (and letting them build it for me), has been a purely flawless one with ubuntu 24.04. Everything just works and I love being able to swap the ports and the ethernet adapter as needed. The fan rarely makes a sound at all and it's blazing fast compared to the similarly spec'd system 76 darter pro it replaced (though it was a few years old). Battery life is "fine" but not amazing but charging is pretty quick, so it's still a bit of an improvement over the darter.

2OEH8eoCRo0 2y ago
They chose to use an unsupported OS. https://frame.work/linux https://frame.work/linux
- anotherhue 2y ago
  I'm in the NixOS camp, and while there have been a few fiddly bits the community support has been excellent. It and Arch have a following among more skilled users so I imagine that factors in. s/skilled/willing if not happy to fart around in their os config rather than doing actual work/
  - 2OEH8eoCRo0 2y ago
    That's all fine but if I've learned anything in 20 years of using Linux it's to stick to the beaten path. It's rarely worth deviating (to me). There be dragons It's fun to mess around but we should manage expectations. It likely won't be trouble free.
- catdog 2y ago
  That's not the main problem. They chose Debian Stable which by design is not and never was the best choice for bleeding edge hardware.
mananaysiempre 2y ago
> Everything just works Keyboard wakeup doesn’t—it’s due to the same problem as TFA describes for the 16 except for the 13 the Framework folks have submitted (the moral equivalent of) TFA’s fix to the kernel. Apparently firmware 3.06, currently in beta, is expected to finally solve the problem on the AMD 13. S3 is unsupported (thanks AMD), and s0ix battery drain is higher than I’d like (IIRC like half a week in suspend with 64GB RAM). Out of the box, the Wi-Fi/Bluetooth connectivity is also subpar, but that’s an issue common to the MediaTek cards AMD pushes on laptop manufacturers nowadays, not specific to Framework. (And it’s fixed by a $25 component swap.)
- FrameworkFred 2y ago
  I'll admit that I'm not well versed in the different shades of suspend...I had to look up S3 and it definitely eats more battery than I'd like when it's suspended. With that said, I've only ever had two laptops that would actually wake up after a suspend and one of those only did that after it was resurrected after a 5 year hiatus. So my expectations were low enough that I was thrilled that it worked at all. I look forward to the fix in the firmware (which seems to update via standard apt upgrade efforts...also pretty cool). I haven't hit any problems with wifi and bluetooth...both work well for me.
- codedokode 2y ago
  I didn't understand why the laptop was waking up by itself. Was the lid too close to the buttons and it was pressing it? > S3 is unsupported (thanks AMD) My AMD laptop (not a Framework) seems to have no issues with sleeping though (although I don't know what power state it is in).
  - mananaysiempre 2y ago
    > I didn't understand why the laptop was waking up by itself. The official line at the moment is that some kind of firmware bug led to something other than the keyboard signalling the same interrupt line. So at the moment keyboard wakeup needed to be disabled to get reliable sleep. We’ll see if the latest firmware update[1] works out (and how long it takes to come out of beta). > I don't know what power state [an unspecified AMD laptop] is [sleeping] in That’s the crux of the issue[2], though. It’s either suspend-to-RAM (S3; dump hardware state to RAM and power off most of the hardware including the CPU) or suspend-to-idle (S0ix or “Modern Standby”; try to put most of the external hardware in low-power states, downclock the CPU, and hope nothing wakes up). Apple did get their S0ix equivalent (“Power Nap”) right enough that most don’t complain; in PC-land, reports of laptops cooking themselves in bags due to inadvertent[3] wakeups from S0ix are everywhere. I cannot find the exact CPU generation cutoffs at the moment, but the problem is that the CPU manufacturers are responsible for a good part of firmware development, and they no longer offer support for S3 at all—the corresponding procedure may be removed from the ACPI bytecode completely, or they may leave it there but declare it buggy and unreliable (usually truthfully). The only exception I know of is Linux-certified ThinkPads, because apparently Lenovo has enough weight to throw around that they can get special treatment. [1] https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-06-release-beta/60732 https://community.frame.work/t/framework-laptop-13-ryzen-704... [2] https://blog.jeujeus.de/blog/hardware/laptops-will-not-sleep-anymore/ https://blog.jeujeus.de/blog/hardware/laptops-will-not-sleep... [3] Not clear how much of this is Windows looking for updates regardless of the user’s desire.

2OEH8eoCRo0 2y ago

They chose to use an unsupported OS. https://frame.work/linux https://frame.work/linux

anotherhue 2y ago
I'm in the NixOS camp, and while there have been a few fiddly bits the community support has been excellent. It and Arch have a following among more skilled users so I imagine that factors in. s/skilled/willing if not happy to fart around in their os config rather than doing actual work/
- 2OEH8eoCRo0 2y ago
  That's all fine but if I've learned anything in 20 years of using Linux it's to stick to the beaten path. It's rarely worth deviating (to me). There be dragons It's fun to mess around but we should manage expectations. It likely won't be trouble free.
catdog 2y ago
That's not the main problem. They chose Debian Stable which by design is not and never was the best choice for bleeding edge hardware.

mananaysiempre 2y ago

> Everything just works Keyboard wakeup doesn’t—it’s due to the same problem as TFA describes for the 16 except for the 13 the Framework folks have submitted (the moral equivalent of) TFA’s fix to the kernel. Apparently firmware 3.06, currently in beta, is expected to finally solve the problem on the AMD 13. S3 is unsupported (thanks AMD), and s0ix battery drain is higher than I’d like (IIRC like half a week in suspend with 64GB RAM). Out of the box, the Wi-Fi/Bluetooth connectivity is also subpar, but that’s an issue common to the MediaTek cards AMD pushes on laptop manufacturers nowadays, not specific to Framework. (And it’s fixed by a $25 component swap.)

FrameworkFred 2y ago
I'll admit that I'm not well versed in the different shades of suspend...I had to look up S3 and it definitely eats more battery than I'd like when it's suspended. With that said, I've only ever had two laptops that would actually wake up after a suspend and one of those only did that after it was resurrected after a 5 year hiatus. So my expectations were low enough that I was thrilled that it worked at all. I look forward to the fix in the firmware (which seems to update via standard apt upgrade efforts...also pretty cool). I haven't hit any problems with wifi and bluetooth...both work well for me.
codedokode 2y ago
I didn't understand why the laptop was waking up by itself. Was the lid too close to the buttons and it was pressing it? > S3 is unsupported (thanks AMD) My AMD laptop (not a Framework) seems to have no issues with sleeping though (although I don't know what power state it is in).
- mananaysiempre 2y ago
  > I didn't understand why the laptop was waking up by itself. The official line at the moment is that some kind of firmware bug led to something other than the keyboard signalling the same interrupt line. So at the moment keyboard wakeup needed to be disabled to get reliable sleep. We’ll see if the latest firmware update[1] works out (and how long it takes to come out of beta). > I don't know what power state [an unspecified AMD laptop] is [sleeping] in That’s the crux of the issue[2], though. It’s either suspend-to-RAM (S3; dump hardware state to RAM and power off most of the hardware including the CPU) or suspend-to-idle (S0ix or “Modern Standby”; try to put most of the external hardware in low-power states, downclock the CPU, and hope nothing wakes up). Apple did get their S0ix equivalent (“Power Nap”) right enough that most don’t complain; in PC-land, reports of laptops cooking themselves in bags due to inadvertent[3] wakeups from S0ix are everywhere. I cannot find the exact CPU generation cutoffs at the moment, but the problem is that the CPU manufacturers are responsible for a good part of firmware development, and they no longer offer support for S3 at all—the corresponding procedure may be removed from the ACPI bytecode completely, or they may leave it there but declare it buggy and unreliable (usually truthfully). The only exception I know of is Linux-certified ThinkPads, because apparently Lenovo has enough weight to throw around that they can get special treatment. [1] https://community.frame.work/t/framework-laptop-13-ryzen-7040-bios-3-06-release-beta/60732 https://community.frame.work/t/framework-laptop-13-ryzen-704... [2] https://blog.jeujeus.de/blog/hardware/laptops-will-not-sleep-anymore/ https://blog.jeujeus.de/blog/hardware/laptops-will-not-sleep... [3] Not clear how much of this is Windows looking for updates regardless of the user’s desire.