Yes, exactly that.
Regarding this. Is it possible you might have set up the udev rules listed here and forgot about it? When I tried them I had the same issues you mention, they cause the issue; the keyboard backlight not working after resume from suspend. Without those rules, the backlight never fails for me.
Hey Matt, Itâs been almost 5 months since this was posted. Can you please update us on the status of the ever expanding list of bugs that need fixing on the 16? 5 months on top of the year since this device was released is an eternity in tech time. Is Framework seriously struggling on the software side still? Software/firmware issues are killing this product and I do not want to see that happen.
1 Like
Totally feel the same. My company is considering more 16âs, but as âfirst userâ Iâm seriously hesitating because of this. The backlight issue is still not fixed, and the last firmware update is ages ago. And on top of that the biggest issue that makes me hesitant for bying more 16âs: lack of communcation.
I seem to remember that FW used to be much more open with future plans up until the FW16 release. The batch 1 FW16 was months late. The abuse they received from customers was extreme. Some customers were even stalking their support staff! So, they changed policy. If customers donât know about a pending release being late, they cannot complain.
So, effectively, it is their customers / users that have caused FW to clam up.
I think it is a case of a few bad customers making the rest of their customer base suffer.
1 Like
Was some bad customers complain/abuse predate the batch 1 FL16 late, or the other way round? Either way the correlation is insufficient to conclude causation. I think it could be unpredictably, supply chain issues, tariffs etc. Correct me if Iâm wrong
Thatâs unfortunate if true. Closing up like this will hurt the company far more than having to deal with the minority insane âcustomersâ. With the Framework 16 already being out, holding back info about fixes is the last thing they should be doing because that tells everyone they are giving up on an existing product line. I see people all over the forums complaining more and more and itâs a terrible look. Also, whether they are quiet or not, their actions speak the loudest. Not having any bios update for this long is quite telling.
I finally tried your sleep solution as I was going to drive into work this Friday and didnât want to have to shut the laptop down while traveling. It worked great for this purpose but I do have the same issue as others, in that it completely disables the keyboard backlight. After waking the laptop up again, the keyboard backlight remains off and there is no way to enable it again.
To fix it without rebooting, this worked:
for device in /sys/bus/usb/devices/*/power/wakeup; do echo enabled > "$device"; done
And then sleep and wake it again and keyboard will be back to normal.
Honestly, how the hell is this still a problem? @Kieran_Levin care to explain why this isnât fixed? We are all aware that we bought a device which might have teething problems in the first half year or so, but not having a BIOS update to remedy this issue after more than a year is not acceptable.
2 Likes
Iâm still sort of dealing with this. I cannot tell whatâs doing this-- from what I can tell, I donât even need to have the laptop closed and it can just be sitting in place and itâll just sometimes do this behavior. Iâve gotten into the habit of, whenever I shut down the system, Iâll power it back up and immediately go into the BIOS, then shut it off from the BIOS, which seems to prevent this from happening. Of note is that I never use sleep mode, or any sort of âsuspendâ or âhibernateâ mode, only using the actual âshut downâ option within Fedora. Iâm guessing even thatâs not a true âshut downâ but itâd be nice if I could make it just do what I expect to begin with.
Mostly just posting here to say itâs still happening. Not sure what happened to the BIOS update or if Iâve just not installed that or something.
Are there any workarounds for the poor Windows users?
Running powercfg /devicequery wake_armed doesnât give me anything useful and the Keyboard entries in Device Manager donât have any Power Management options.
Just want to note that this is also still a problem. Any updates on the BIOS update?
Yes, Nirav mentioned it in Yesterdays product release video. There is a software update coming for the keyboard.
2 Likes
Is the fix for this actually out yet? Mentioning it is one thing (he only mentions that the screen is able to touch the keyboard when closed, but absolutely nothing on a fix for THIS problem), the fix has been coming âsoonâ for the past year. It is very annoying finding my laptop being burning hot due to the flimsiness of the screen allowing key/touchpad presses. Iâm certain this would be affecting my devices lifespan, which is also supremely annoying. Expecting me to rely on a temp fix this long after an issue this bad has been identified is just utterly ridiculous. @Matt_Hartley Any news or timeframes available that arenât just âsoonâ?
In the mean time, if you donât want to use the temporary fix that is available, you could hibernate or shut down the machine to avoid it being awakened in the bag. Putting a stiff sheet on the screen side could help as well. I sandwich my laptops between carbon fiber sheet, primarily to protect it from my tendency to overstuff the bag.
1 Like
yeah I was thinking of this too, just the laptop is already so thicc it barely fits in the laptop sleeve for my massive bag
yep, my battery is already down to 83% health from this, and this laptop isnât my main machine
Maybe I just need to learn to internet better, but after finding this thread, it took me another hour to find this post in the thread. I started reading from the top and didnât find any quick fixes there. Then jumped to the end and read the last 20 or so posts, no fixes there. Finally, when back to the top and read through everything until I found this one. Thanks for this fix. It was easy, and in the testing Iâve done so far, it works exactly as described.
On my fw16 running Pop!_OS 22.04 LTS with BIOS (3.07), the wakeup.sh script from linux-docs/disable-accidental-wakeup/readme.md at main ¡ FrameworkComputer/linux-docs ¡ GitHub keeps failing on systemctl start disable-wakeup.service.
The log shows:
ne 1: /sys/devices/platform/AMDI0010:03/i2c-1/i2c-PIXA3854:00/power/wakeup: Permission denied
I ended up using this guide to disable my keyboard until the fix is out:
I would rather use the official script if possible, is there something I need to change for Pop_OS?
The fix IS out and has been for a few weeks. Update your bios.