{"id":3930,"date":"2023-05-04T07:01:14","date_gmt":"2023-05-04T14:01:14","guid":{"rendered":"https:\/\/jasonsblog.ddns.net\/?p=3930"},"modified":"2023-05-06T20:01:45","modified_gmt":"2023-05-07T03:01:45","slug":"fix-raspberry-pi-4b-stuck-on-5-15-kernel","status":"publish","type":"post","link":"https:\/\/jasonsblog.ddns.net\/index.php\/2023\/05\/04\/fix-raspberry-pi-4b-stuck-on-5-15-kernel\/","title":{"rendered":"Fix Raspberry Pi 4B Stuck on 5.15 Kernel"},"content":{"rendered":"\n<p>I had noticed that my Raspberry Pi 4B which is a dedicated Bitcoin and Lightning node was still on kernel 5.15 when all my other Raspberry Pi&#8217;s based on Debian 11 have been upgraded to <a href=\"https:\/\/www.omglinux.com\/raspberry-pi-os-update-may-2023\/\" target=\"_blank\" rel=\"noreferrer noopener\">kernel 6.1<\/a>. So I went to force it to kernel 6.1 through using <a href=\"https:\/\/github.com\/raspberrypi\/rpi-update\" target=\"_blank\" rel=\"noreferrer noopener\">rpi-update<\/a>, which completed with no errors and showing that it updated to kernel 6.1, but after rebooting it was still on kernel 5.15. Turned out I needed to update my <a href=\"https:\/\/github.com\/raspberrypi\/rpi-eeprom\" target=\"_blank\" rel=\"noreferrer noopener\">eeprom<\/a>, bootloader version. You can check with the following command.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo rpi-eeprom-update<\/code><\/pre>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"856\" height=\"415\" src=\"https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2023\/05\/rpieeprom.png\" alt=\"\" class=\"wp-image-3931\" srcset=\"https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2023\/05\/rpieeprom.png 856w, https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2023\/05\/rpieeprom-300x145.png 300w, https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2023\/05\/rpieeprom-768x372.png 768w\" sizes=\"auto, (max-width: 856px) 100vw, 856px\" \/><\/figure>\n\n\n\n<p>If it shows an update is available, you can update with the following command.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo rpi-eeprom-update -a<\/code><\/pre>\n\n\n\n<p>After updating the eeprom I rebooted and then ran rpi-update again. One thing to note is you usually don&#8217;t want to run rpi-update unless you&#8217;re having an issue and the next firmware and kernel would be to solve the issue as it&#8217;s still in testing. But in my case there was a problem and it wasn&#8217;t updating to the next kernel properly. <\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>sudo rpi-update<\/code><\/pre>\n\n\n\n<p>After the kernel and firmware are updated, time for another reboot and you should be on the latest kernel, 6.1 LTS. And this is a pretty new kernel as some of my Arch based distributions have just switched to the brand new 6.3 kernel, with most other distributions on kernel 6.2. And this is technically a much newer kernel than the Debian stock kernel 5.10. And I run Debian 12 Beta as one of my daily rotation GNU\/Linux distributions, and it&#8217;s on kernel 6.1, so our Raspberry Pis are pretty up to date for a Debian based distribution.<\/p>\n\n\n\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"856\" height=\"489\" src=\"https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2023\/05\/ArcoLinux.png\" alt=\"\" class=\"wp-image-3937\" srcset=\"https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2023\/05\/ArcoLinux.png 856w, https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2023\/05\/ArcoLinux-300x171.png 300w, https:\/\/jasonsblog.ddns.net\/wp-content\/uploads\/2023\/05\/ArcoLinux-768x439.png 768w\" sizes=\"auto, (max-width: 856px) 100vw, 856px\" \/><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>I had noticed that my Raspberry Pi 4B which is a dedicated Bitcoin and Lightning node was still on kernel 5.15 when all my other Raspberry Pi&#8217;s based on Debian 11 have been upgraded to kernel 6.1. So I went to force it to kernel 6.1 through using rpi-update, which completed with no errors and [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-3930","post","type-post","status-publish","format-standard","hentry","category-tech"],"blocksy_meta":[],"featured_image_src":null,"author_info":{"display_name":"Jason","author_link":"https:\/\/jasonsblog.ddns.net\/index.php\/author\/jturning\/"},"_links":{"self":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/3930","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/comments?post=3930"}],"version-history":[{"count":6,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/3930\/revisions"}],"predecessor-version":[{"id":3984,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/3930\/revisions\/3984"}],"wp:attachment":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/media?parent=3930"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/categories?post=3930"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/tags?post=3930"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}