Aside of PureOS as a distro itself, there are other things that we need to catch up with upstreams with as well. One of them is our Linux tree for the Librem 5, which has been stuck on 6.6 LTS for a while.
As the first step forward, linux-image-6.12.0-1-librem5 is now available to install from crimson-updates-proposed. It’s not being pulled in by default yet - you need to install the package manually - but if I don’t hear about any issues with it I’ll make it the default on crimson. I’ve been running it on my daily driver phone for the last two weeks and I’m not aware of any remaining regressions to solve, so it’s now your turn to either confirm that or prove me wrong
This kernel can be installed alongside the current version 6.6. In case of troubles, you can go back to the previous kernel temporarily by issuing sudo flash-kernel --force 6.6.0-1-librem5 (which will be overridden when flash-kernel runs the next time), or permanently by removing the package. In case of boot failure, librem5-devkit-tools repo has a uuu script that can boot a previous kernel without having to fiddle with Jumpdrive or other rescue methods - but this shouldn’t be necessary at this point.
Once 6.12 becomes the default, we’ll move towards 6.18 (which I already have booting here, but it still needs some more work).
You didn’t say anything new. This isn’t actionable at all.
What’s the state the phone’s in when it seemingly “shuts down”? Do you need to long press the power button to boot it again, or does it just act normally like after a regular shutdown? Is there a shutdown sequence logged in the journal or does it just crash? Does it happen in response to some action (pressing the power button, attempting to wake it up from suspend etc.) or just randomly and abruptly on its own?
Please try to be specific, only then these reports will be helpful, as I have obviously not seen such behavior on any of my phones, otherwise this kernel wouldn’t be uploaded into PureOS at all.
Once phone boots into phosh and kept idle for some time, by itself it shuts down. To boot it again, I have to press the power button again. I will install it again and see the logs.
I installed Linux 6.12 yesterday and i noticed similar behavior like autoshutdown, but i not sure if it was because i not unlock luks or after unlock luks, but whatever ATM is working OK.
Yes, it auto reboots and shutdown happens if I don’t enter the luks password. I have installed it again and it rebooted multiple times already. Let me see the logs.
That would mean we’re not talking about shutdowns at all, but rather reboots, which are likely caused by kernel panics. You’ll have to catch the logs somehow, the most reliable way is through the serial console.
Wild guess: does this happen with WiFi turned off as well? Or suspend?
I think it happened only when I did not login after the system booted. Once I logged in and ran these commands to check logs, it has not rebooted till now.
last reboot commands shows 3 reboots with 6.12 kernel with 4 minutes gap.
It is crimson only, installed it from crimson-updates-proposed. But last time I think I saw similar shutdown behavior with mobian (don’t remember the exact details), so I switched to pureos crimson.
Now it seems to be holding fine. So it seems it happens only if we don’t login immediately after the kernel installation.
ok I could reproduce it again. So not just immediately after installation. It rebooted just now. I entered the luks password, but did not unlock the phosh screen. It rebooted and showed me the luks screen roughly after 4 minutes.
