Raspberry Pi 5 support #260754
Comments
FliegendeWurst
added
0.kind: question
|
"NixOS" proper won't see support for the Raspberry Pi 5. Just like all other ARM platforms, NixOS support depends on the platform's support in upstream mainline projects. We will not repeat the mistake we did with the Raspberry Pi 4 and adding bespoke support for a proprietary ecosystem. It is too much work to support for the resources available to NixOS. Note that this reply applies to any So the roadmap to "NixOS booting trivially on Raspberry Pi 5" is:
Then we can add its U-Boot build to the token pre-baked firmware partition (assuming we still ship it by then) and it should work [just as well as mainline supports it]. An additional side-note: With the super-powers conferred to the end-users of NixOS, nothing stops someone from providing useful configurations, overlays, etc to make it work in the meantime as a workaround. Though as implied, it would be user-supported. |
samueldr
added
the
2.status: wait-for-upstream
|
I think we're all on the same page that it'd be great to have official support but as @samueldr says a lot of work has gone into supporting the Pi (and the oddities of other SOCs). https://github.com/NixOS/nixos-hardware/commits/master/raspberry-pi/4 A nix-community project might be more appropriate this time around so there's a centralized spot to collaborate but it's still distinctly marked unofficial. vision5/riscv support has been going alright without a more central project due to a couple of vocal and active community members + a bit of sponsorship support |
|
I wasn't able to get the Pi 5 to boot with NixOS. The boot loader shows me the following: Wasn't able to get it to boot - no matter what I've tried. |
|
My pi5 needs Nixos :-) |
You need to use patched kernel sources from Raspberry. You also need to use device tree files from Raspberry and merge them using opensource but non-standard I wholeheartedly support the decision not to deal with these oddities officially and support only boards with all drivers & patches & DTSs in the upstream kernel & having standard EFI! But it is NOT that hard to get a new embedded system running in Nix. Not at all. I actually found Nix through embedded systems when I was fed up after many years with I do plan to get Pi5 running along with a simplified disk image generation (lots of unneeded magic stuff surrounding the current |
|
There are actually patches for u-boot for the rpi5, though they're far from complete. I was able to use that to get a very haphazard build of nixos's sd image booting, but it's pretty rough. |
|
I got things sort of working without U-Boot: |
|
NixOS seems to "just work" with https://github.com/worproject/rpi5-uefi, though device support is currently very limited (Ethernet and fan control are the most painful omissions for headless/server use). For some applications, it might already be enough, though. Compared to U-Boot, this has the major benefit of being able to just use the standard aarch64 installer with a mainline kernel. If device tree support gets added to EDK2, it'd hopefully be possible to switch to the vendor kernel post-installation for more complete hardware support, without needing a special Pi-specific installer image. Using the vendor kernel with ACPI might be superior in some senses, but this seems fragile, and I really doubt it'd be considered a supported usecase by the driver developers. |
|
There are a number of reasons this is a bad idea, but installing NixOS using EDK2 and then adding this to the configuration seems to mostly work: {
boot.kernelPackages = (import <nixpkgs-rpi5> {}).linuxPackages_rpi5;
boot.kernelParams = [ "dtb=\\bcm2712-rpi-5-b.dtb" ];
} |
|
rpi5-uefi 0.2 adds device tree support, which seems to work perfectly when using the vendor kernel with UEFI! I'll try to make a flake with the Pi 5 kernel and start writing a wiki page. |
|
I've created a preliminary wiki page with basic installation instructions: https://nixos.wiki/wiki/NixOS_on_ARM/Raspberry_Pi_5 |
|
The above wiki entry is very helpful for getting the PI to boot, but I've had no success booting to X11 or Wayland. While the wiki does list "Graphics drivers are not yet available in NixOS.", this surprises me, given that mesa 23.3.0 has since made it into nixpkgs, which I believe has the drivers for the pi's GPU. If anyone gets graphics working, I'd be curious how :) |
|
@leo60228 I tested rpi5-uefi and you flake, and it seems to be working perfectly! Thanks a lot! I think the only addition in your flake compared to the upstream linux-rpi vendor kernel is the added defconfig line? If so, would you mind submitting a PR so we can just use linuxKernel.kernels.linux_rpi5 (and hopefully be able to use the binary cache)? |
I made that flake before the recent PR updating linux-rpi in Nixpkgs, but this is more or less correct. I was waiting on that PR to be merged before submitting one adding linux_rpi5, I'll try to do that once I'm home tonight if I remember. |
|
Realistically, we should be able to build one rpi kernel for rpi 3, 4, and 5. That's how raspbian works. We can even do the same with u-boot, using u-boot's |
|
Apparently according to https://www.raspberrypi.com/documentation/computers/linux_kernel.html, rpi5 uses a different config so it uses 16K page instead of 4K. |
|
@nbdd0121 hm, seems like it's a tradeoff of performance vs compatibility. For performance, use the rpi5 specific kernel, for compatibility, use the rpi4 one. |
|
I've hacked around and got the installation medium booting from the EFI. Does anyone know if it's possible to install NixOS to the same medium (SD card) as the EFI? The EDK2 docs are elusive. |
|
I used the wiki page @leo60228 created as somewhat of a guide (thanks - you're a star), got my Pi 5 to boot the UEFI from SD, imaged the aarch64 minimal installer to a USB drive and booted that. From there I was indeed able to install to the SD, with NixOS's boot images sharing the same partition as the UEFI loader. Whether that's a good or bad idea I don't know. Not sure what would happen if you somehow booted the installer from the same SD however. I suspect having the partition(s) mounted might hinder those efforts. 🤷 A few notes from my experience which may be useful:
That aforementioned partition table issue I do plan to rectify in due course, but currently that kernel build from @leo60228 is unfortunately an overnight job for my Pi, so I don't have the free time to keep retrying at the moment. If I do get around to trying that then I'll report my findings, good or bad, unless someone beats me to it. |
Try: Then |
|
I'm another who has got it working with rpi5-uefi and @leo60228's flake! The debian UEFI docs where useful in understanding you can extract the bootloader to the same partition as the EFI implementation. For posterity, here are some step-by-step instructions. Format your SD-card, create filesystems, and extract the Raspberry Pi UEFI EDK2 implementation to the boot entry: Flash NixOS arm64 minimial installer to USB drive: On the Pi now, boot into the installer and network it over WiFi (as Ethernet doesn't work). Mount the SD-card: Generate and edit your config with You'll want to set: To install the bootloader to And to add the vendor kernel with e.g.: Then you can install NixOS with Then to boot the vendor kernel, in the UEFI settings switch from ACPI to Device Tree in I also removed NB I couldn't get NixOS to boot automatically even adding the So I need to manually boot from file: Perhaps this is related to using a GPT partition table. I also tried to a cross-compiled installation straight to the SD card from an x86_64 machine which failed due to grub's perl dependency not building.Perhaps cross-compiling with QEMU would work. |
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/install-nixos-on-raspberry-pi-5/38833/2 |
I don't think EFI runtime variables are supported (yet?), so you should set
You need to add |
|
Thanks for all the useful conversation had here and resources put together! I was able to get NixOS installed with relative ease on my Pi 5 yesterday, which has now replaced my previous NixOS Pi 4 as a DHCP, DNS, WireGuard, and nginx server for my network and has been working great, much more performant ✨ I figured I'd share a little bit of my experience here in case it helps others. Then proceeded with the mounting. Generate the config. Edit the config to what should roughly be a minimal working system: configuration.nix{ config, lib, pkgs, ... }:
{
imports = [ ./hardware-configuration.nix ];
boot.loader.systemd-boot.enable = true;
boot.loader.efi.canTouchEfiVariables = false;
networking.hostName = "rpi5"; # Define your hostname.
networking.wireless.iwd = {
enable = true;
settings.General.EnableNetworkConfiguration = true;
};
time.timeZone = "Europe/London";
environment.systemPackages = with pkgs; [
vim
curl
git
];
# just for access after install to continue provisioning
services.openssh.enable = true;
services.openssh.settings.PermitRootLogin = "yes";
networking.firewall.enable = false;
system.stateVersion = "23.11";
}hardware-configuration.nix{ config, lib, pkgs, modulesPath, ... }:
{
imports =
[
(modulesPath + "/installer/scan/not-detected.nix")
];
boot.initrd.availableKernelModules = [ "usbhid" "usb_storage" ];
boot.initrd.kernelModules = [ ];
boot.kernelModules = [ ];
boot.kernelPackages = (import (builtins.fetchTarball https://gitlab.com/vriska/nix-rpi5/-/archive/main.tar.gz)).legacyPackages.aarch64-linux.linuxPackages_rpi5;
boot.extraModulePackages = [ ];
fileSystems."/" =
{
device = "/dev/disk/by-uuid/ecb26648-686e-403c-a415-406ac554653d";
fsType = "ext4";
};
fileSystems."/boot" =
{
device = "/dev/disk/by-uuid/0CAE-25FE";
fsType = "vfat";
};
swapDevices = [ ];
networking.useDHCP = lib.mkDefault true;
nixpkgs.hostPlatform = lib.mkDefault "aarch64-linux";
}Made sure to set Before continuing with the install, here's what others may find particularly useful: the Pi is going to take a loooooong time to compile the kernel. If, like me, you happen to be using NixOS on another, more ample aarch64 system (I'm running NixOS with Asahi on an M2 MacBook Air), you can just build your Pi's system closure on that and then copy it to the installer's Nix store:
(if you have problems with impurity because of flakes, either pass
I appreciate that's a bit of a 🧠 dump, so please feel free to ask for any clarification on the above steps. One other curiosity I had before I did the install was if ethernet worked once booted to NixOS with the vendor kernel and Device Tree/System Table mode. It wasn't clear to me based on comments/info available if it would. For anyone wondering: it does :) |
|
Big thanks for the kernel packages and guides.
For anyone else who's curious, I ran the experiment to put a number on it. Haven't gone through with the installation yet, but building from a Pi 5 4GB running debian on an nvme drive, the result was: $ nix build -L .#nixosConfigurations.....config.system.build.toplevel
# ...
took 2h9m50sIt's long, but it's not waiting for hydra long. ;) |
|
I was refering to this pr NixOS/nixos-hardware#927 but do you mean this is rpi4 + some tweaks and not rpi5 itself? |
|
nixos-hardware isn't part of Nixpkgs. |
|
Oh stupid me… thanks! |
|
Has anyone gotten this to work recently? I've tried multiple times to get the uefi bootloader to install but it just leads to black screens. The pi works I've installed Debian on it and it works like a charm, but I do want to have nixos on it |
|
@Daholli I'm running my RPi5 for a while on NixOS now, booting from UEFI [1] with the vendor 6.6 LTS kernel [2] from @leo60228's nix-rpi5 flake [3]. [1] https://github.com/worproject/rpi5-uefi |
I am just so confused by setting up the uefi-bootloader, supposedly there should be a menu/loading bar, but neither of them show up for me, I was just wondering if anyone else ran into that issue |
|
The only issue i remember was somewhere between the switch from 6.1 LTS to 6.6 LTS, the kernel panicked in stage 1 with the DTB bundled with the 0.3 release of rpi-uefi. I copied over the one built from the nix flake and the system booted again. But that was obviously after UEFI initialized the HW, etc. For initial setup, i followed this comment from @RyanGibb, more or less (gptfdisk), but basically, it's just GPT with a FAT32 partition and extracting the files from the latest rpi5-uefi release zip-file onto it. The last thing i could think of is a different bootloader? rpi-eeprom-update I don't know if the rpi-eeprom-update output is indeed correct, though, considering i'm not running RaspberryPi OS. Admittedly, i haven't seen (via HDMI) my Pi booting for quite a while now, so i can't tell if it's still working, but i'm about to switch to the 24.11 Beta and i'll wire up HDMI for the next reboot and have a peak. |
Thanks for all the advice, I've done all these already, maybe I will just give it another shot tomorrow... So far I managed to have the nixos-installer show up, but once I select any option in the initial menu, the screen turns black but active. I was just so surprised nobody else seemed to have this problem. |
|
The iso image i initially booted from is from this commit, if it's any help at all.. |
I've used nix-community/raspberry-pi-nix for my Pi 5s. Works perfectly for my use-case (hosts a small k3s cluster) and it was farely easy to setup. |
|
@DerRockWolf I am currently trying to set this up, since I was still not able to get UEFI boot to work. @sydneymeyer have you ever seen this screen? But I am just so confused the instructions and what is supposed to happen are so straight forward but for some reason I am stuck at step 1 with very little options to debug, as I don't think there is any logging happening at that level |
|
@Daholli Yes, that is the aforementioned UEFI Menu. The odd thing here is, that i had to boot the NixOS Image in ACPI Mode (because of NixOS's upstream kernel). In the live-environment you only have network access via wifi. After nixos-install with the vendor kernel from the flake, one is supposed to switch from "ACPI" to "Device Tree" for the next boot. |
I haven't seen this screen even once, across multiple sd-cards, so I cannot even run the live image in ACPI mode, |
|
@Daholli I also have the 8GB version, and i just checked, the UEFI Menu show the correct 8192MB of memory. This is confusing indeed, now i'm truly intrigued.. |
I am currently trying to compile a newer version of the firmware using the build.sh script in the uefi-rp5 repo, but setting this up to build on nix is a nightmare in itself |
|
IMO, the whole platform is a nightmare, truly can understand the decision this time not to maintain for the RPI5. This comment also mentions the apparently necessary step to make sure the esp flag were to be set on the FAT32 partition, but i guess, that's depends on the different partitioning tools used. Furthermore, trying to disable the "force_turbo" option from the config.txt (perhaps an issue with your specific chip?). But that last one kind of illustrates the kind of perplexity of facing atm. Also, i believe there is a newer stepping of the SoC getting produced, but i think it's only the 2GB version as of now. |
Yeah between being sick and this nightmare I finally got it to work today, unfortunately I was also plagued by webkitgtk cache-misses. Finally got it to work with this, sadly not uefi, but at least I got the raspberry-pi-nix flake properly integrated into my existing config. @sydneymeyer thanks a lot for all your effort in trying to help me figure this out <3 |
|
@Daholli Thanks for sharing, and speedy recovery! Perhaps of interest to people considering going down the UEFI/NixOS/downstream kernel route: Raspberry's kernel has the whole ACPI subsystem disabled (or rather not enabled) in comparison to a generic NixOS aarch64 kernel, and therefore all the modules that depend on it, like e.g. tpm-*, which is a dependency of systemd in initrd. I noticed that their kernel disables support for the memory cgroup controller by default. Furthermore, i failed at booting a VM with cloud-hypervisor, because the RPi5's SoC generic interrupt controller does not support (or perhaps is not licensed to?) message signaled interrupts, a requirement for virtio-pci. I also have the RPi5 Active Cooler attached, which goes nuts if not properly initialized, and most of the accesories (like ethernet) are hanging now off the new RP1 chip, but otherwise i might perhaps wait until more support for the RPi5 has been upstreamed, considering i'm not interested/comfortable in maintaining a fork until then. |
|
I've been following this bug for a bit and finally found some time to try to get it installed for myself. My OS knowledge is pretty superficial and I'm relatively new to NixOS so I went with what looked to be the most turnkey version with nix-community/raspberry-pi-nix. The trick to getting the whole thing bootstrapped for me was to start with the rpi5 running Rasperry PI OS and Nix. I used that to build the SD image and avoid any of the cross-compilation issues. Then I wrote the image to a new SD card and used it to boot NixOS. Here are the steps that feel like they're pretty repeatable:
This is my flake with the modifications:
I haven't done much to test it out beyond that, but I was pretty happy getting it that state. Next on the TODO list is to figure out if I can get it booting off of the NVMe instead of the SD card. |
|
@gk5885 you're almost there. This is the steps I followed to boot from the NVMe:
Turn it on. It should now boot the image you just wrote on the NVMe. |
|
I actually got distracted along the way... I saw the "Pi 5 u-boot devices other than sd-cards (i.e. usb, nvme)." note at the end of the raspberry-pi-nix README, so I figured that I'd see if I could get U-Boot to work before I switched over to the NVMe drive. Short version: I couldn't. Adding I used So, to summarize my tests with |
|
Hi, I am trying to also boot from nvme but there are some parts that are unclear for me. I tried installing it manually ( Also did anyone managed to run zfs on rpi5? I would love to get my impermanence setup there. |
Yes, you can write that to an NVMe drive and it'll boot as is.
The SD image setup is made to |
Yes, that's exactly what I did as well. I just used that image with the rpi imager and chose the NVMe device as the storage device.
FWIW, unless I'm mistaken, The one thing to note here is that this sets |
Oops, you're correct. That version is still doing the thing. |
|
I've had some time to fiddle around with @leo60228's work and am now able to bring y'all 3 new kernels! The current VC6 drivers create a minor artifact 6.6.70+
boot.nix config, lib, pkgs, ... }:
{
config = {
boot = {
loader = {
systemd-boot.enable = true;
efi.canTouchEfiVariables = false;
grub.device = "nodev";
grub.efiSupport = true;
};
supportedFilesystems = [ "ext4" "ntfs" "nfs" ];
kernelPackages = let
linux_rpi5_pkg = { stdenv, lib, buildPackages, fetchFromGitHub, perl, buildLinux, rpiVersion, ... } @ args:
let
# Stable (6.6.70)
overlays = fetchFromGitHub {
owner = "raspberrypi";
repo = "firmware";
rev = "9e65e647c2d8cb1453875c509bf6a730288b7491";
hash = "sha256-d0P7qAZRPJvCMhw5BwJcT9IEreb7RInRD9HOoSQjOng=";
};
# Next (6.12.9+)
#overlays = fetchFromGitHub {
# owner = "raspberrypi";
# repo = "firmware";
# rev = "0b1c37755f820948fed2f2223a07abd083093c4e";
# hash = "sha256-fmE7N6sjyCSbYyP2EGpxHn3dS8aa/ws4IpulKKHE8Jw=";
#};
# NOTE: raspberrypifw & raspberryPiWirelessFirmware should be updated with this
modDirVersion = "6.6.70";
tag = "rpi-6.6.y";
#modDirVersion = "6.12.9";
#tag = "rpi-6.12.y";
in
lib.overrideDerivation (buildLinux (args // {
version = "${modDirVersion}-${tag}";
inherit modDirVersion;
# Kernel 6.6.70
src = fetchFromGitHub {
owner = "raspberrypi";
repo = "linux";
rev = "dfff38316c1284c30c68d02cc424bad0562cf253";
hash = "sha256-Vz4o8GIObbF4fyKl5aKi4zJxjINMQjd5PsQPZ8Hprbw=";
};
# Kernel 6.12.9
# src = fetchFromGitHub {
# owner = "raspberrypi";
# repo = "linux";
# rev = "a20d400dff3d1d3eb40a192fecff22a70d064b3e";
# hash = "sha256-RCwMLkPbf755NQf0fVVgQovHmSAwU+q99P430eDYr8M=";
# };
# Kernel 6.13.0-rc7
# src = fetchFromGitHub {
# owner = "raspberrypi";
# repo = "linux";
# rev = "c807724f29160ce9b043f6c870ba234c1691e373";
# hash = "sha256-GFAeJoGgS0wEp+cI5RIrNX+bWm52akkESynuK2S7JuQ=";
# };
defconfig = {
"1" = "bcmrpi_defconfig";
"2" = "bcm2709_defconfig";
"3" = if stdenv.hostPlatform.isAarch64 then "bcmrpi3_defconfig" else "bcm2709_defconfig";
"4" = "bcm2711_defconfig";
"5" = "bcm2712_defconfig";
}.${toString rpiVersion};
features = {
efiBootStub = false;
} // (args.features or {});
extraMeta = if (rpiVersion < 3) then {
platforms = with lib.platforms; arm;
hydraPlatforms = [];
} else {
platforms = with lib.platforms; arm ++ aarch64;
hydraPlatforms = [ "aarch64-linux" ];
};
} // (args.argsOverride or {}))) (oldAttrs: {
postConfigure = ''
# The v7 defconfig has this set to '-v7' which screws up our modDirVersion.
sed -i $buildRoot/.config -e 's/^CONFIG_LOCALVERSION=.*/CONFIG_LOCALVERSION=""/'
sed -i $buildRoot/include/config/auto.conf -e 's/^CONFIG_LOCALVERSION=.*/CONFIG_LOCALVERSION=""/'
'';
postBuild = ''
mkdir -p $out/arch/arm64/boot/dts/overlays
mkdir -p $out/dtbs/overlays
cp -r ${overlays}/boot/overlays/* $out/arch/arm64/boot/dts/overlays/
cp -r ${overlays}/boot/overlays dtbs/
cp -r ${overlays}/boot/overlays $out/dtbs
'';
# Make copies of the DTBs named after the upstream names so that U-Boot finds them.
# This is ugly as heck, but I don't know a better solution so far.
postFixup = ''
dtbDir=${if stdenv.isAarch64 then "$out/dtbs/broadcom" else "$out/dtbs"}
rm $dtbDir/bcm283*.dtb
copyDTB() {
cp -v "$dtbDir/$1" "$dtbDir/$2"
}
'' + lib.optionalString (lib.elem stdenv.hostPlatform.system ["armv6l-linux"]) ''
copyDTB bcm2708-rpi-zero-w.dtb bcm2835-rpi-zero.dtb
copyDTB bcm2708-rpi-zero-w.dtb bcm2835-rpi-zero-w.dtb
copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-a.dtb
copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-b.dtb
copyDTB bcm2708-rpi-b.dtb bcm2835-rpi-b-rev2.dtb
copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-a-plus.dtb
copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-b-plus.dtb
copyDTB bcm2708-rpi-b-plus.dtb bcm2835-rpi-zero.dtb
copyDTB bcm2708-rpi-cm.dtb bcm2835-rpi-cm.dtb
'' + lib.optionalString (lib.elem stdenv.hostPlatform.system ["armv7l-linux"]) ''
copyDTB bcm2709-rpi-2-b.dtb bcm2836-rpi-2-b.dtb
'' + lib.optionalString (lib.elem stdenv.hostPlatform.system ["armv7l-linux" "aarch64-linux"]) ''
copyDTB bcm2710-rpi-zero-2.dtb bcm2837-rpi-zero-2.dtb
copyDTB bcm2710-rpi-3-b.dtb bcm2837-rpi-3-b.dtb
copyDTB bcm2710-rpi-3-b-plus.dtb bcm2837-rpi-3-a-plus.dtb
copyDTB bcm2710-rpi-3-b-plus.dtb bcm2837-rpi-3-b-plus.dtb
copyDTB bcm2710-rpi-cm3.dtb bcm2837-rpi-cm3.dtb
copyDTB bcm2711-rpi-4-b.dtb bcm2838-rpi-4-b.dtb
'';
} // (args.argsOverride or {}));
linux_rpi5 = pkgs.callPackage linux_rpi5_pkg{
kernelPatches = with pkgs.kernelPatches; [
bridge_stp_helper
request_key_helper
];
rpiVersion = 5;
};
in
pkgs.recurseIntoAttrs (pkgs.linuxPackagesFor linux_rpi5);
# Currently do not build for 6.12.
# initrd.kernelModules = [ "8821au" ];
# extraModulePackages = with config.boot.kernelPackages; [ rtl8821au ];
kernelParams = [ "8250.nr_uarts=11" "console=ttyAMA10,9660" "console=tty0" "usbhid.mousepoll=0" ];
kernelModules = [ "uinput" ];
};
zramSwap.enable = true;
};
}configuration.nix deviceTree = {
enable = true;
filter = "*rpi-5-*.dtb";
};
}; |
|
@celesrenata What do you mean by this comment?
I remember having trouble building vendor kernels newer than 6.6.. |
In 6.11+ the 8821AU module will not build, however, it is included in 6.13 natively. It is just a note for that kernel module, it is not used by the rpi5 by any builtin hardware, it is just a usb driver for a wireless dongle. From my experience, vendor kernels are hit or miss, the ones I provided will work. I have had better luck by cherry picking revisions at random than using any official release/tag. |
|
Woot woot! Thanks to the comment above: #260754 (comment) Thanks @gk5885 I originally tried to compile this flake on my amd64 machine, but after >12 hours I gave up. It took ~4 hours to build on a pi5 with nvme running Raspberry Pi OS with nix on it. - This makes no sense to me. Why does the compiler care what architecture it is running on? It shouldn't need emulation. Does anyone understand this please? It works! This is running from the SD Updated the wiki with a link to this ticket |
and others
Has anyone been able to run NixOS on the newly released Raspberry Pi 5? It's not included yet in the wiki's compatibility matrix.
The text was updated successfully, but these errors were encountered: