Shall we manage the known issues by the community so that people can easily see the issues and optionally solutions? At least it’s still useful to list important issues only. I didn’t find any similar thread listing the “current” known issues.
Started with 3.06 on 28th Feb this year updated to 3.07 so not real idea, then 3.08, then 3.09 and now 3.10. There has never been an issue with the main battery discharging when powered off.
The ongoing issue is the drain in sleep mode which relates to the other issue.
The expansion cards USB A | µSD card reader | The 256GB SSD all require acknowledgement from the main board when plugged in whether powered on or not, but do not actually drain the battery. The main board draws power form the mains supply if it connected.
Plugging in power brings the main board ‘alive’ which then connects to the expansion cards via some dubious protocol which use more power than makes sense.
The USB C cards are the only ones that seem not to cause a power drain. But as I said this is from the supply not the battery.
I intended the former, “known issues” including issues without solution / workarounds / fixes. Thanks for sharing the list of the known issues. It’s better to add the list to the first comment later.
Although people have issues they are not endemic to the 11th for example so a list is long, complex and not very representative from my experience. I’ve yet to find a problem.
I see. I think the list is still helpful even when the list is long or complex and hard to maintain. We don’t need to aim for the complete up-to-date list. Just the prioritized list is still helpful. That’s how ArchWiki Framework Laptop’s troubleshooting session works.
What I want to solve by this thread is accessibility to the known issues by everyone. You are an active member of this forum, and maybe you know most of the issues reported on this forum. But not everyone does. Essentially this is to fill a gap between a user or potential customer’s expectation and reality.
I considered using the “issue” tag feature on this forum. But I have seen a change in the forum’s functionality is slow or none. And the tag doesn’t have priority on the list.
Adding this issue, what seems to be a combination of TB display with / without power (lack of TB certification on Framework?), and x / wayland display detection (software):
Happy for Framework that they’re launching another product (Chromebook)…
But I’m still waiting for a few things to be fixed / addressed / improved / optimized on the 11th gen laptop.
…and lately, I got official word that tau is not end-user adjustable.
@junaruga if you’re still tracking/maintaining this, I wonder if it’s worth splitting into 11th and 12th gen (and maybe soon Chromebook)? I think the RTC issues are different between 11th and 12th gen since the former is worse (can require a motherboard reset, while 12th gen shouldn’t get stuck in a bad boot state).
The top listed items are hardware/firmware issues (battery drain in suspend, RTC drain, power off drain even when off in non-updated 11th gen systems) that are common to all Framework laptops. Whether you find it a “problem” I suppose is a personal opinion, but I think it’s still very useful to collect the laptops quirks/common problems for new users in a single place.
I suppose two other useful links would be useful in that regard are links to the top threads in the quarter and all time - sadly support threads are split across all sorts of categories and not really tagged in any systematic way AFAICT.
OK. It looks good idea for creating 11th, 12th Intel category and coming Chromebook. But I don’t think creating OS sub-categories is good idea, because there are many OSes. Maybe we can note such as “Fedora 36 specific” for now.
For now, I modify the first comment. But I was asking moderators to change it to the wiki, to avoid I work hard, and am a bottleneck for this task. But moderators didn’t act to change it to the wiki. I am not sure why they didn’t.
Despite the name of the thread, it looks like there are users on other distros reporting the same problem. This seems to be most common w/ those using Gnome (I haven’t encountered this problem over the past couple months running Sway), and possibly related to installing legacy Xorg drivers, various i915 kernel configurations, or the use of an external display.
Bummer, well, hopefully people use the thread to post any updates, and maybe there’ll be an actual community wiki at some point.
