Laptop: Acer Aspire A515-45 V1.52 | Fedora: 41 Workstation Edition (x64, default spin)
As it says on the tin, when using the kernels 6.10 and 6.11, regardless of which variant, I can’t (properly) resume a session after suspending by closing the laptop lid
In 6.10, the screen never turns on
In 6.11, the system resumes working for 15 seconds or so…and then locks up, and stops responding to all input besides the mouse cursor (Not even the keyboard works, I tried to switch to other TTYs and it didn’t work)
Haven’t remembered to confirm whether audio keeps playing
I would downgrade to 6.9, but running an older kernel for an extended period of time sounds like it’d be terrible for security, and more importantly, kernel 6.9 is no longer available to me
I did see a different, but similar thread about this, but I didn’t want to hijack it, partly because I’m not even sure this is the same problem
You could use the LTS Kernel: kwizart/kernel-longterm-6.6 Copr As long as you not have an alternative. This kernel you can use beside of of the 6.11 kernel.
I do believe that the hardware firmware needs some adjustments to support the new energy functions of the 6.11 kernel series. Did you have a look on Acers Website if you can find a never bios etc?
Thank you for the suggestion! No, really!
I’ve searched the manufacturer’s websites for BIOS updates, but:
The last one was from late 2023
I bought this computer at most two months ago (right now is late 2024), it shoud be preinstalled
Even then, the updates are only distributed for Windows 10 and 11
And I’m too scared to run them with WINE
I kind of want to avoid switching to an earlier kernel out of, well, paranoia that something will break irreversibly, especially when I do not have the means to produce backups.
But also, because there may also be a better solution.
Well, trying to boot into the older kernel gives me this error (bad shim signature - you need to load the kernel first), for which I could only find the workaround of disabling Secure Boot, which sounds like more trouble than it’s worth…
In September 2019, Acer joined the project, with initial support for their Aspire A315 model.[11] Starting from December 2019, Google requires that firmware updates can be applied with fwupd for certified Chromebooks.[12]
To list updates available using fwupd, run sudo fwupdtool get-updates in a terminal.
I have Dell systems – some updates via fwupd are released earlier than the kernel that requires them, so I have had firmware updates downloaded by fwuptool sit in a staging location until a kernel update arrived.
Right! Shame on me for forgetting this was a comamnd, because I ran this the other day after seeing GNOME Software didn’t update Secure Boot dbx(?) properly. (Just restarted without actually updating)
…When I type the command you provided, it outputs command not found…
Looking at my .bash_history, the correct command appears to be sudo fwupdmgr update.
…Running this shows me there no additional updates have been made avaialble since the last time I ran it.
Update to previous update: Wait. Wait no. The script in the Arch forum doesn’t work either. I forgot to actually properly test it. Darn!
I will go ask in that other thread!
Update: I found someone else with the same laptop who is having the same issue, and, it does appear theirs, and mine, and the author of the first thread I linked’s, problems, are all as a consequence of the Bluetooth module
That’s on me. I should have checked first before even making the post.
