I think you have to do this, because 6.18 is not the default kernel yet:
sudo apt update
sudo apt install linux-image-6.18.0-1-librem5
I think you have to do this, because 6.18 is not the default kernel yet:
sudo apt update
sudo apt install linux-image-6.18.0-1-librem5
Try this agrresive to reset.
sudo apt autoremove --purge && sudo apt autoclean && sudo apt clean && sudo apt update
Thanks to all. Seems you still have to do it manually.
Yes. However if you wait a handful of days, it will turn up automatically.
Not really, there was a bug on apt, which preventing to upgrade gnu gnulinux automatically, but superhero @dos fixed the bug time ago, so this bug could still be on your L5 if you hadnt updated and rebooted for long time now.
Yes:
…which was fixed in crimson before crimson was released, so not relevant here as byzantium has neither 6.12 nor 6.18 kernels.
![]()
and the previous 6.18.44 build has meanwhile migrated to crimson-updates.
So if Linux it is on crimson-update why not autoupdate? any reason?
The package linux-image-6.18.0-1-librem5 is now available in crimson-updates (since it migrated automatically after a week), but nothing depends on it so far and linux-image-6.12.0-1-librem5 is being installed by default as I haven’t changed the dependency yet. As I said earlier, I plan to have linux-image-librem5 (which is what pulls the actual kernel into the image) point to 6.18 with the next upload if no issues show up meanwhile. This is completely orthogonal to crimson-updates-proposed migrations.
So expect 6.18 to be installed by default in around 2-3 weeks.
I’m curious how the progress is going on mainlining all the L5 kernel changes. Are we significantly closer to the mainline kernel in LOC than, say, a year or two back?
mainlining all the L5 kernel changes
Some information is given here: Sebastian Krzyszkowiak: "Linux 7.0 has now been tagged, coming with 19 com…" - Librem Social
Kernel 6.18.49 has now been made the default Librem 5 kernel in landing and crimson-updates-proposed.
Should there be no issues, it’s going to migrate to crimson-updates next week.
@dos, I have on one of my L5:
purism@old-pureos:~$ uname -a
Linux pureos 6.12.0-1-librem5 #2 SMP PREEMPT 6.12.105pureos1~cri1 2026-08-26 01:00:32 UTC aarch64 GNU/Linux
root@pureos:/home/purism# bluetoothctl --version
bluetoothctl: 5.66
and a BT keyboard works fine on a Debian live system with a 6.12.94 kernel, see:
I booted a Debian live system on a laptop: user@debian:~$ uname -a Linux debian 6.12.94+deb13-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.12.94-1 (2026-06-20) x86_64 GNU/Linux user@debian:~$ bluetoothctl info Device C3:4C:11:0A:AB:00 (random) Name: Inateck KB01105 Alias: Inateck KB01105 Appearance: 0x03c1 (961) Icon: input-keyboard Paired: yes Bonded: yes Trusted: yes Blocked: no Connected: yes WakeAllowed: yes …
but does not show up or pairs on the Crimson (on an Byzantium it pairs, but keystrokes are not passed and errors are in /var/log/syslog).
Is there any hope that it will work in Crimson with the 6.18 kernel? I have it to return to the seller on September 19 latest.
Thanks
Is there any hope that it will work in Crimson with the 6.18 kernel?
You tell me - try it. I can’t tell you much more about some hardware I don’t own.
You tell me - try it.
Ok. When and how can I update to 6.18?
See the thread above.
I wanted to report that so far kernel 6.18 is working well for me. Also, and more importantly, thank you very much for your work on this. I am finally getting excited again about the Librem 5 and the future of Linux mobile.
linux-image-librem5 still depends on 6.12. Are we still waiting?
Here’s the answer:
Kernel 6.18.49 has now been made the default Librem 5 kernel in landing and crimson-updates-proposed.
Should there be no issues, it’s going to migrate to crimson-updates next week.
Are we still waiting?
Yes. The clock is ticking though.
Kernel 6.18.49 is now the default one (for Librem 5) in both crimson and dawn.