Raspberry Pi 4 Ubuntu Server 18.04.3 Installation Guide

Ubuntu Server logo
Ubuntu Server logo

Ubuntu Server has been my favorite Linux distribution for years. On everything but the Raspberry Pi I run Ubuntu Server but felt stuck with Raspbian on the Pi. Until now! Ubuntu Server 18.04.2 has been released and major improvements have been made to the official Pi branch.

The Raspberry Pi 4 is not officially supported out of the box yet on the current Ubuntu Server Raspberry Pi images but you can get it working by manually updating the firmware. Solid state storage is also working but with the catch of having to use a micro SD card as a bootloader since the Pi 4 does not have official boot support yet. I describe how to do both in this article.

The Raspberry Pi’s peripherals such as WiFi / Bluetooth are now fully supported. Previous Ubuntu Server versions for Raspberry Pi (like many other distros) had broken or completely missing drivers for core components such as WiFi / Bluetooth. In the 18.04.2 update the firmware for the WiFi and other components is now included out of the box making it a fully functional distribution!

This is the first distribution besides Raspbian that feels like you can just image it and everything works. I’ll guide you through the process in this guide. It only takes a few minutes to set up.

Update 1/4/20 – New Prebuilt Image Available (v26)

These are the manual instructions to get things working. If you are looking for a precompiled Ubuntu image check out my post here: https://jamesachambers.com/raspberry-pi-4-ubuntu-server-desktop-18-04-3-image-unofficial/

I have compiled my own unofficial kernel and created a preinstalled release that overcomes all previous RAM limitations. That’s right, the image let’s you use all 4 GB of memory if you have the 4 GB model. WiFi tweak is also included and should be working properly.

Pre-Release v5 – 9/3/2019

  • Desktop support added
    • Expect lots of warnings in the logs. If you find solutions to them please leave a comment — many commits come from the comments!
    • Be advised — installing can take quite a while on a Pi — overnight or when you have something to do is a good time
  • Type one the following commands to install your preferred flavor of Ubuntu Desktop
    • sudo apt-get install xubuntu-desktop # or
    • sudo apt-get install kubuntu-desktop

Recommended Gear

I highly recommend upgrading to a solid state setup. The performance gains are gigantic. It’s now less than 30 bucks to take your Pi solid state. This is the best performance upgrade you can possibly get for a Pi.

With the new Raspberry Pi 4 it’s even more beneficial to use USB storage since a USB 3.0 bus was finally added in the Pi 4 letting it take full advantage of solid state drives. This is the setup I am currently using:

Raspberry Pi 4 Model B 2 GB

StarTech 2.5″ SATA to USB 3.0 Adapter -AND- Kingston A400 SSD 120GB SATA 3 2.5” Solid State Drive

Or for a compact setup: SanDisk Extreme Pro 128 GB USB Solid State Flash Drive

For a micro SD card setup: SanDisk Extreme A2 Application Class Micro SD Card

These storage choices are ones that all scored highly on the end-user submitted Raspberry Pi Storage Benchmarks and will give you outstanding I/O performance on the Raspberry Pi. I also personally own all of them and recommend them knowing they are compatible and perform well on the Pi.

Getting Ubuntu Server

64 bit (aarch64)

I have a custom compiled prebuilt 64 bit image available for testing. This version supports addressing all 4 GB of RAM if available. The WiFi fix for bootflags3 is also already implemented into the precompiled version. Get my custom built kernel from the Ubuntu-Server-raspi4-unofficial GitHub page.

32 bit (armhf)

To get the 32 bit version head to the official Ubuntu Raspberry Pi page at https://wiki.ubuntu.com/ARM/RaspberryPi and scroll to the “Official Images” section. Until the official Raspberry Pi 4 image is released choose the Raspberry Pi 3B+ armhf release and follow the directions in the next sections to update the firmware for a Pi 4 boot.

Writing the Base Image

This part is easy. Extract the image from xz format to img format (7zip is great and free and can extract these). Now write the img to your media (Micro SD card, solid state drive, USB storage, etc). the same way you would for any other distribution!

Updating Firmware for Raspberry Pi 4

If you are using the CloudKernel 64 bit image you can skip to the “Boot Ubuntu Server” section as it already implements the updated firmware. If you are using the 32 bit image or the official Ubuntu Server preinstalled server image from Ubuntu’s web site you will need to update the firmware using these instructions.

Remove Existing Firmware

The firmware in the current release was not built with Raspberry Pi 4 support so we need to update the firmware on the /boot/ partition for the Pi 4 to be able to boot correctly.

Insert/mount the micro SD card in your computer and navigate to the “boot” partition. Delete everything in the existing folder so it is completely empty.

Download Latest Firmware

32 bit Firmware Instructions

If you are trying to run the 64 bit version of Ubuntu skip to the 64 bit instruction section next. For 32 bit versions of Ubuntu download the firmware from the official GitHib repository here: https://github.com/raspberrypi/firmware/archive/master.zip

The latest firmware is everything inside master.zip “boot” folder (including subfolders). We want to extract everything from “boot” (including subfolders) to our micro SD’s “boot” partition that we just emptied in the previous step. Don’t forget to get the “overlays” folder as that contains overlays necessary to boot correctly.

The end result will look something like this on the “boot” drive:

$ ls
  COPYING.linux                bcm2711-rpi-4-b.dtb   kernel.img
  LICENCE.broadcom             bootcode.bin          kernel7.img
 'System Volume Information'   cmdline.txt           kernel7l.img
  bcm2708-rpi-b-plus.dtb       config.txt            overlays
  bcm2708-rpi-b.dtb            fixup.dat             start.elf
  bcm2708-rpi-cm.dtb           fixup4.dat            start4.elf
  bcm2708-rpi-zero-w.dtb       fixup4cd.dat          start4cd.elf
  bcm2708-rpi-zero.dtb         fixup4db.dat          start4db.elf
  bcm2709-rpi-2-b.dtb          fixup4x.dat           start4x.elf
  bcm2710-rpi-3-b-plus.dtb     fixup_cd.dat          start_cd.elf
  bcm2710-rpi-3-b.dtb          fixup_db.dat          start_db.elf
  bcm2710-rpi-cm3.dtb          fixup_x.dat           start_x.elf

64 bit Firmware Instructions

To boot Ubuntu Server in 64 bit mode we need to download the 64 bit version of the firmware. The .dtb files are different between 32 bit and 64 bit operating systems. Raspbian does not come with a 64 bit bootloader and one isn’t provided in the official GitHub repo either.

I have these 64 bit versions available in my Ubuntu Server precompiled image.

Create/Update config.txt and cmdline.txt

Navigate to the micro SD /boot/ partition. Create a blank cmdline.txt file with the following line:

dwc_otg.fiq_fix_enable=2 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0

Next we are going to create config.txt with the following content:

# Enable audio (loads snd_bcm2835)



64 bit config.txt Configuration

To boot the Pi in 64 bit mode we need to add the following lines to the config.txt:


The final configuration for 64 bit will look like this:

# Enable audio (loads snd_bcm2835)




These enable all the different 64 bit related options you need to perform a 64 bit boot on the Pi.

Boot Ubuntu Server

We are now ready to boot the device. Insert the micro SD card and power on the device.

Note: The very first startup can be very slow. Be patient. It can take up to a couple minutes with no activity lights then all the sudden everything will start blinking and SSH will open up.

Fix apt-get update / Prevent Further Updates

If you try to apt-get update now it will try to update your firmware with older firmware from the Ubuntu repository. The workaround for now is to remove that package so it keeps your existing firmware. Make a note to remember you did this step as later on we will want to reenable updates from the repository once support has been added.

sudo apt-mark hold flash-kernel

You may now run sudo apt-get update && sudo apt-get upgrade. I would avoid using dist-upgrade yet because the kernels in the repository it will update you to don’t support the Pi 4 yet. But this should get you all up to date on the packages!

Once the firmware in the apt repositories has been updated for the Pi 4 it will be safe to reinstall initramfs-tools and let it update through the normal process again.

Solid State Drive (SSD) Configuration (Optional)

USB booting has not been added into the Raspberry Pi 4 firmware yet but is being worked on right now. In the mean time you can use your micro SD card as a bootloader and still boot the whole operating system (rootfs) from the solid state drive giving you the full USB 3.0 speed increases system wide. Once the Pi USB booting is officially released you should be able to boot directly from the device without any makeshift bootloader SD card necessary.

First create a fully imaged and booting micro SD card following the earlier steps in the tutorial. After you have created the micro SD installation you should now image your SSD / USB drive with the same Ubuntu image you used to create the SD card.

Now navigate to the “boot” partition on the newly created SSD / USB drive and remove everything in there just like we did with the SD card earlier. Now copy the “boot” folder from the micro SD card to the solid state drive. This is necessary because even though the files in “boot” are read off our micro SD card initially some firmware files in the later load stages are read off the mounted drive and if the necessary firmware files are missing the system won’t boot.

Now that you’ve created the SSD / USB drive partitions and copied the “boot” partition from the SD card to your new drive we need to update your SD card’s cmdline.txt to point to the SSD / USB drive’s partition.

dwc_otg.fiq_fix_enable=2 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0

The key part we need to change here is the “root=/dev/mmcblk0p2” section. mmcblk0p2 is a hardware identifier for micro SD storage. We need to change this to the device your storage is detected as.

If you are using a USB to solid state drive adapter it’s very likely your drive will be addressed as /dev/sda2. Therefore we will change the root=/dev/mmcblk0p2 to root=/dev/sda2


The final line will be:

dwc_otg.fiq_fix_enable=2 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/sda2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0

Plug both the micro SD and the solid state drive into the Pi and boot it up.

Remember: the first boot can take 2-3 minutes for first startup so give it some time before assuming it didn’t work.

Wireless Fix

The current non-free Raspberry Pi firmware had the wrong bootflags3 for quite a while for the Raspberry Pi 4 and these firmware files are definitely out there. Here is a one liner I wrote to replace the Raspberry Pi 3 boot flags in this driver with the Raspberry Pi 4 one:

sudo sed -i "s:0x48200100:0x44200100:g" /lib/firmware/brcm/brcmfmac43455-sdio.txt

Restart the system afterward.


Default User / Password

The username and password for your initial login to Ubuntu Server will be:

user: ubuntu
password: ubuntu

You will be required to change your password after logging in for the first time. Make sure on the prompt you enter the current “ubuntu” password before typing in your new password or the device will kick you out completely and you’ll have to log in again.

Set Time Zone

To configure the correct time zone for Ubuntu Server use the following command:

sudo dpkg-reconfigure tzdata

This will take you to a very easy to follow menu to select your correct time zone and applies it to the system.

Update System

For best stability, security and performance you should immediately update your system and packages to the latest version. This will also grab all of the latest fixes/improvements making your Raspberry Pi Ubuntu experience much better.

This part is easy. Type:

sudo apt-get update && sudo apt-get upgrade

Change Default GPU Memory Split

The default amount of memory allocated to the GPU on the Raspberry Pi is around 76 MB of our 1 GB. In 2 GB and 4 GB models the amount gained from this is negligible but is still worth it for the 1 GB model.

If you type the command “free” you will see that your Raspberry Pi is missing this memory under the “total” column. We can reclaim most of this memory back by setting the GPU memory split to 16 MB. If you are planning on installing a GUI in the future you should not make this change.

This option is set in the config.txt file. It’s exactly the same file as Raspbian uses but it is located at /boot/firmware/config.txt instead of /boot/config.txt. Open config.txt with the following command:

sudo nano /boot/firmware/config.txt

We will add the following line at the bottom of config.txt:


Press Ctrl + X and type yes to save the file. Now restart the Pi by typing

sudo reboot

After the reboot finishes type “free” again and you will see that your total available memory has increased and can now be used by the system and your applications!

Benchmark Storage (Optional)

It’s very important to have a well performing storage device on the Raspberry Pi. Storage has always been and continues to be one of the biggest performance bottlenecks for Raspberry Pis.

Until the Raspberry Pi 4 we didn’t even have 3.0 transfer speeds. Now that we have them with Raspberry Pi 4 we are discovering there is a very large difference between not only manufacturers and models, and in the case of SD cards the manufactured date / batch produced! This means that if you bought a FakeName Extreme 3.0 in 2015 you could buy the exact same line and brand of SD card one year later and you would get something with a totally different grade of flash memory and microcontroller that would perform much better/worse.

Because no one person could possibly buy all this hardware and benchmark it on their own I created a script to benchmark your storage and anonymously submit it via a basic web form here.

The best thing would be for you to run the script but if you don’t want to run it yourself check out the existing recommendations for high performance storage ideas to get the most out of Ubuntu Server on the Pi.


I’m very excited to see my favorite Linux distributions continue to evolve to the point where they are comparable in performance and stability to Raspbian. I’ve been testing extensively on Ubuntu Server 32 bit and 64 bit for my Raspberry Pi Minecraft Server project and not only is it on par with Raspbian but starting to do things so well it sometimes makes Raspbian feel a little dated.

If you have any questions or suggestions don’t hesitate to leave me a comment on the post or use my contact form to message me privately! I’m good about responding quickly and my articles are constantly revised to address questions or do something a better way that a reader pointed out.

Have fun!

202 thoughts on “Raspberry Pi 4 Ubuntu Server 18.04.3 Installation Guide”

  1. Avatar for Jim Starkey

    With due recognition that it is not within your intended scope of work, do you have any suggestions or guidance on how a variant that boots on both 3Bs and 4Bs might be put together?

    V6 solved my video problem. Nice work. Thanks

    1. Avatar for jamesachambers

      Ahh yes I think I have heard of this issue. What is the resolution of the TV? Is it 4k?

      My test bench uses a normal HD 1920 x 1080 monitor (connected via HDMI) where I did all my testing but I have heard of higher resolutions causing problems.

      When you comment out that line do you have 3D acceleration? Like if you drag windows around does it look smooth, etc.

        1. Avatar for jamesachambers

          Can you try editing the following config file: ~/.config/kwinrc

          Change the line that starts with Backend to:


          This would be with the 3d driver uncommented.

  2. Avatar for Joan

    Hi James can’t wait to see new v3! Will you write down a resume of the changes/fixes/improvements when released?

    If you plan to add GUI I agree with others to make it optional, I think it works better in terminal mode.

    I achieved to install Ubuntu-desktop an ubuntu-mate and I recommend a lightweight desktop like mate.

    Good work and thanks!

  3. Avatar for firejoust

    Hi James,

    When I run
    “sudo apt-get upgrade”

    It displays the error
    “E: Could not get lock /var/lib/dpkg/lock-frontend – open (11: Resource temporarily unavailable)” and
    “E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?”,

    How would I solve this?

    1. Avatar for jamesachambers

      Hey firejoust,

      This means the Ubuntu background updating process was running at the same time. If you use the command “top” you should see a bunch of processes called things like unattended upgrades, apt processes going, etc.

      If you installed the GUI version this can take quite a while to complete. The way to prevent it is to do sudo apt-get update && sudo apt-get dist-upgrade BEFORE installing kubuntu-desktop.

  4. Avatar for Zubin

    I followed instructions for the 32bit version (used 18.04.3 base image) . The image boots fine but I couldn’t get the wifi working. I applied the wireless fix but still can’t get the wlan0 interface to show up. Did anyone else get wifi working on 32 bit?

    1. Avatar for jamesachambers

      Hey Zubin,

      I haven’t built the 32 bit image yet (I have the 64 bit version uploaded) but my guess is that your image is missing the bootflags3 fix.

      Try this on the Pi:
      sudo sed -i “s:0x48200100:0x44200100:g” /lib/firmware/brcm/brcmfmac43455-sdio.txt

      This will replace the wrong bootflags3 value in the Broadcom firmware with the updated correct value for the Pi 4. Do a full reboot after making the change.

      If you did this already and are still having issues there is another step that isn’t currently in the instructions. You can update the firmware on the Ubuntu side in /lib/firmware. There’s two ways to do this. You can simply copy the relevant folder over from a Raspbian install (this is on the rootfs not the bootfs, it is /lib/firmware). So you will remove everything inside of Ubuntu’s /lib/firmware and replace it with the contents from your Raspbian image.

      The second way to do this is by using the repository. In this version I have the Ubuntu .img file mounted and will update the firmware on the mount with the newest firmware from the repository. Here’s an excerpt from my build script:


      cd ~
      sudo rm -rf firmware-nonfree
      git clone https://github.com/RPi-Distro/firmware-nonfree firmware-nonfree
      cd firmware-nonfree
      git pull
      sudo rm -rf firmware-nonfree/.git
      sudo cp -ravf firmware-nonfree/* /mnt/lib/firmware

      1. Avatar for julio garcia

        I am facing same issue. I tried wireless fix with sudo sed -i “s:0x48200100:0x44200100:g” /lib/firmware/brcm/brcmfmac43455-sdio.txt. Additionally, I copied firmware-nonfree content to /mnt/lib/firmware, but it didn’t work. Although I am not sure if I did it properly. My /mnt folder was empty, so I created lib and firmware folders (mkdir -p /mnt/lib/firmware) and later copies them sudo cp -ravf firmware-nonfree/* /mnt/lib/firmware.

  5. Avatar for Simon Dubrulle

    Hi James,

    Thanks so much for your investment in this project. I tried your V2 and it is working like a charm for the moment. I am using it mostly to run Docker/Docker-compose and this is just perfect now with 4GB. I guess you will be remembered by all MongoDB users right here ! If I see any issue, I’ll open a ticket on the github, but this is running fine for now. Keep up with your good job.

  6. Avatar for EmilFR

    Hi James,

    Great work on releasing V2 image.
    I have first release of your image, and I almost finished setting up my personal mail server on RPI4 4GB (replacing the 1GB-ram-limited-RPI2) and I’m wondering is there anyway to bring the quality like updates or fixes you have done on V2 image to the previous image?
    Perhaps you can list what can be done for people like me.


    1. Avatar for jamesachambers

      Hey EmilFR,

      The pre-releases have been changing so fast (and so much) that it would be more work to try to do that than to reimage it unfortunately. I will definitely keep in mind for the final release though that this is a requested feature!

      1. Avatar for EmilFR

        Hi James,

        Understood. Looking forward for your final release then.
        But please make desktop as optional, as some people like me like the idea to run ubuntu as headless server.

        1. Avatar for jamesachambers

          Hey EmilFR,

          Thanks for the feedback. I also largely use it as just Ubuntu Server and don’t use the GUI stuff too much. Getting the desktop working was more of a challenge of is the kernel good enough/stable enough to run it that way.

          I may do some precompiled desktop additional downloads during the stable releases though to help people out if they don’t want to download thousands of packages one at a time on a slow connection!

  7. Avatar for martafoo

    Hi, I prefer using debian instead of ubuntu. Is it possible with your script from github to create a debian based image for rpi4?

  8. Avatar for EmilFR


    Can you check if the console access work?
    I connected my console cable to the GPIO but i cannot see anything on screen.
    As my understanding, the cmdline.txt already has console designation:

    # cat /boot/firmware/cmdline.txt
    dwc_otg.fiq_fix_enable=2 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 rootwait rootflags=noload net.ifnames=0

  9. Avatar for ntux

    Hello, and thanks for your hard work on this!

    I have just a few questions:
    – Is there an upgrade path between your versions? I installed your previous one (from 28.08 I think) and it’s working flawlessly, however I was wondering if I could upgrade to your 31.08 version without a full reinstall? Or maybe it’s not worth the trouble and I should wait for official support and unlock the flash-kernel package then?
    – I’m trying to get wiregard installed but I can’t seem to find the kernel headers for the 4.19 kernel you build (it only has 4.15 included) and I’m not sure where to get them. Do you have an idea?

    1. Avatar for jamesachambers

      Hey ntux,

      There isn’t a way to upgrade easily in the prereleases but I’m going to try to make the final public releases upgradable without a reinstall!

  10. Avatar for Tom Lake

    I have a Pi 4 and can use the precompiled image to boot to the CLI with no problem. Thank you!

    Is any work being done to get the GUI desktop to work?

    sudo apt install ubuntu-desktop

    of course doesn’t work.

    1. Avatar for Joan

      Yes I managed and it’s working. But ubuntu desktop is very slow. Ubuntu-mate desktop is a better alternative. Unfortunately mate stops working on xrdp after the last kernel uodate ☹️

  11. Avatar for Mark Hawkins

    Was able to get James’ pre-release v2 of Ubuntu 18.04.3 up and running on RPi4 using microsd but with fast thumbdrive for storage for a mongodb instance. Seems stable so far.

    Definitely get lots of warnings similar to this but I believe that is to be expected. Will be nice when we can unlock the “kernel-flash”. I assume this warning will then go away. So far though it hasn’t have affected anything I’d installed. Even got wifi up fine with the wifi fix recommended:
    W: APT had planned for dpkg to do more than it reported back (5 vs 9).
    Affected packages: flash-kernel:arm64

  12. Avatar for Hpi

    Thanks a lot for pre-compiled image. I was quite sure I had bad hardware as nothing worked well with raspian. Example I tried many torrent clients and never get proper download speed. Now with ubuntu, it works very nicely.

    Only thing I found so far is 5 GHz wifi seems not connecting.

    Again, thanks!

  13. Avatar for AHritz

    Okay, after experiencing same UAS support problem with my JMicron driver, and then reading a couple hours on how support works in Linux… I think this Ubuntu Kernel config needs to specify CONFIG_USB_UAS=y in the make config, or be compiled as a module, in order for UAS support to be enabled. I think that’s the reason here for the slower SSD speeds in this build vs. Raspbian.

    I attempted to force unbind the drive from usb-storage and re-bind as uas, only to find no uas driver shown in /sys/bus/usb/drivers. What do you think?


    1. Avatar for jamesachambers

      Hey AHritz,

      I can definitely compile this module into v3 since the JMicron adapter is very common. I’ll add the support in there!

  14. Avatar for Aaron

    For what it’s worth, similar to Beau, I ran your benchmark under 64-Bit Ubuntu w/ a Samsung Pro 960 NVME and scored a 5200. Under Raspbian Buster, scored an 8800 with same drive. I’m using a USB to M.2 adapter with the JMS583 chipset.

    Have confirmed that my device supports it:
    bInterfaceProtocol 98

    Any ideas on how to enable? I understand all parts of the firmware chain need to support it in the OS. I wonder if this would be an issue with this drive is raspberry hardware wasn’t in the mix.

  15. Avatar for Beau

    Thanks for doing this. I ran into a couple problems.
    (1) Your setting in config.txt to force sound over HDMI is incompatible with DVI monitors. I don’t know how many people this will affect, so just pointing it out.
    (2) My JMS567 disk enclosures aren’t recognized as UAS capable with your Ubuntu image. Raspbian does recognize UAS. Simple benchmarks show quite a difference with a Samsung 750 EVO 250GB SSD. I did a quick look for a blacklist that I could remove but didn’t see anything.

  16. Avatar for Niels

    ubuntu@ubuntu:~$ sudo apt-get upgrade -y
    Reading package lists… Done
    Building dependency tree
    Reading state information… Done
    Calculating upgrade… Done
    The following packages have been kept back:
    linux-headers-raspi2 linux-image-raspi2 linux-raspi2
    0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
    1 not fully installed or removed.
    After this operation, 0 B of additional disk space will be used.
    Setting up initramfs-tools (0.130ubuntu3.8) …
    update-initramfs: deferring update (trigger activated)
    Processing triggers for initramfs-tools (0.130ubuntu3.8) …
    update-initramfs: Generating /boot/initrd.img-4.15.0-1041-raspi2
    W: mkconf: MD subsystem is not loaded, thus I cannot scan for arrays.
    W: mdadm: failed to auto-generate temporary mdadm.conf file.
    Unsupported platform.
    run-parts: /etc/initramfs/post-update.d//flash-kernel exited with return code 1
    dpkg: error processing package initramfs-tools (–configure):
    installed initramfs-tools package post-installation script subprocess returned error exit status 1
    Errors were encountered while processing:
    E: Sub-process /usr/bin/dpkg returned an error code (1)

  17. Avatar for Tjockesmocke

    I’m stuck at “Once the firmware in the apt repositories has been updated for the Pi 4 it will be safe to reinstall initramfs-tools and let it update through the normal process again.”
    How do I do this?

Leave a Comment

Your email address will not be published. Required fields are marked *

Type here..