Raspberry Pi 5 support

[agners]

The Raspberry Pi 5 looks like a really another really platform from the Raspberry Pi folks to run Home Assistant OS on 🤩 . Obviously we'd like to support it as fast as possible.

Currently the main blocker is U-Boot support for Raspberry Pi 5. We use U-Boot on all other Raspberry Pi platforms as well as other Arm based boards. U-Boot is a feature rich boot loader with scripting capabilities. We mainly use it to have a common boot flow across all boards, which lowers maintenance support.

I'll use this thread to report progress and discuss potential alternatives to run Home Assistant on Raspberry Pi 5.

[agners]

Just to clear some things up wrt U-Boot requirement: One of the key features we use is it's environment support, which can be accessed from the main operating system as well. This allows to support two operating system versions and switch between those (A/B slot). Home Assistant OS uses this so we can revert back to the previous installation in case the new version somehow doesn't boot successfully on a particular board.

Secondly, we also use it to load the main kernel binary from a compressed squashfs partition. This allows us to efficiently store larger kernels versions than our initial partitioning would have allowed (which was limited to 24MB).

We definitely prefer to use U-boot, but we also consider other options. However, using an alternative for Raspberry Pi 5 specifically would mean to either drop features (such as the A/B slot, something the Raspberry Pi firmware doesn't support) and/or implement it in a different/new way (compressed squashfs is not supported by the Raspberry Pi firmware).

[jens-maus]

As you know, the RaspberryMatic project I maintain also uses a similar environment (U-boot bootloader + buildroot OS) like HomeAssistantOS. And I am also highly interested in getting a future RaspberryPi5 support implemented. So have you already checked the current state of affairs regarding RaspberryPi5 support in U-boot? I know that Pi5 hardware is only about to ship in a few weeks/months, thus U-boot maintainers might simply not have the necessary hardware at hand yet, but I guess with some help it might still be possible to get preliminary Pi5 support in the sources of U-boot so that we can continue using U-boot without having to introduce workarounds.... So lets work together ;-)

[waveform80]

A quick note regarding A/B boot capabilities, just in case people aren't aware of it. The Pi's bootloader has supported a "tryboot" mode for a few years. There were some issues with it, but I think I'm right in saying those were resolved sometime late 2022. Anyway, this thread is well worth a read on the subject, along with the docs.

I realize this is a potentially complicated way forward given that it is Raspberry Pi specific. However, given you already need to ship the Pi's bootloader* in addition to u-boot anyway, it's not necessarily that complicated.

* Well, until the Pi 5 which incorporates start*.elf and all that into the boot EEPROM so all you actually need is the kernel and a config.txt (and even that's optional!)

[sblantipodi]

Does the pi5 supports booting from USB by default
without additional tricks?

[agners]

Since there is no HAOS port, we can't tell at the moment. If you talk about RPi 5 in general, than this is the wrong place to ask.

[pamatika]

You need to change the boot order in the eeprom. Same as in pi4 ?

[juhanjuku]

My HA runs on Pi4 and I newer changed anything in eeprom. Boots from sd and from ssd without problems

[schematt]

ssd on usb
boot without change

[gustad]

I have a Pi5 and it can boot from USB using the default ROM loader.

[kannan-balasubramanian]

Will there be a beta community created where we can test the beta version and provide feedback?

[frenck]

Once there is something to share, we will. Right now, it is blocked as per OP.

[kannan-balasubramanian]

Thank you for replying. Hoping the U-Boot blocker is overcome. Eagerly waiting to be part of the beta testing community.

[RTJKNR]

Received my Pi5 Today looking forward to the first developments

[agners]

One thing which is new with Raspberry Pi 5 is that the kernel is compiled with 16kB page sized by default. This should improve performance (see also the Raspberry Pi 5 blog post about this topic). It remains to be seen if Raspberry Pi sticks with that page size, but currently it seems that Home Assistant Core cannot deal with this increased page size. In a quick test running Home Assistant Core in a container on Raspberry Pi OS leads to this:

Fatal Python error: _PyRuntimeState_Init: memory allocation failed
Python runtime state: unknown

[agners]

I'll focus on 4kB page sizes for now. From a HAOS perspective we could switch to different page sizes with an update.

[jens-maus]

I also think that, especially looking at the performance comparisons of 4k vs. 16k page sizes in that references blog post, all this upcoming hassle with 16k page size incompatibilities does not justify this tiny little performance improvement that is shown there

[agners]

I would not read too much into their benchmark. Afaik, they did run Geekbench CPU benchmark, which really measures compute performance. I could imagine that real-world applications like Python, which is quite memory intensive since it runs a garbage collector etc. can be a quite different story.

This Twitter/X post claims 16% performance gain for kernel compilation workload. Apple iOS uses 16kB page sizes, I guess for reasons.

[satmandu]

Worth noting that it is easy to boot the RPI5 into the 4kb page size... Just have to use kernel=kernel8.img in the /boot/firmware/config.txt file... No other software changes are needed.

[agners]

FWIW, this particular problem will be resolved with 2024.2, see also home-assistant/core#105768 (comment).

[a24me]

Once there is something to share, we will. Right now, it is blocked as per OP.

Hi @frenck,
Excellent work up to now.
All the community is looking forward.
Hope that it will not take too long from alpha to release 🙏.
WKR, A24me

[hevili]

so rpi5 support will be our christmas present? 🥹

[frenck]

Alright going to hide/this part of the discussion.

This discussion is about making the Home Assistant OS suitable for the Raspberry Pi. If you want to run Home Assistant Core in Docker, you can do so, which is already documented in our official documentation. Again, that is not what this discussion is about.

I suggest on moving unrelated discussions into our community forums or Discord chat, so this discussion can stay on topic.

Thanks! 👍

../Frenck

[frenck]

The issue tracker of Core.
https://github.com/home-assistant/core/issues

In case of doubt, please check https://www.home-assistant.io/help on where to go.

[Zahidp786]

Just wanted to know if there is any further updates on this? @agners @frenck

[crasu]

The pr is here #2914

[agners]

We are getting closer, we have a working integration of the Raspberry Pi firmware "tryboot" boot mechanism with our RAUC update system. There will be a development build soon!

Keep in mind this is still early stage. We might decide to change the layout/boot flow if we find issues with the current approach. Depending on the changes it will mean that a new installation will be necessary.

[Th0tti]

Where can I find the image?

[jens-maus]

We are getting closer, we have a working integration of the Raspberry Pi firmware "tryboot" boot mechanism with our RAUC update system.

Still no progress in sight regarding U-Boot support for RaspberryPi 5?

[joekolassa]

I am brand new to Home Assistant and excitedly bought a RaspberryPi 5 a few days ago before researching and finding it isn't supported yet. Do your research kids... Originally support was expected around now to early next year. Do you think that is still the case or do you think it'll still be a few months before it's ready?

[agners]

Update: There are newer builds on the beta channel available currently. Please see #2844 (comment).

The latest dev builds now include an image for Raspberry Pi 5:
https://os-artifacts.home-assistant.io/index.html

Specifically, flash the image at https://os-artifacts.home-assistant.io/11.3.dev20231212/haos_rpi5-64-11.3.dev20231212.img.xz using your favorite flasher such as balenaEtcher onto an SD card and run Home Assistant OS on your Raspberry Pi 5 🎉

⚠️ This is a development build! Depending on testing, we might need to change the partition layout, which would mean a complete re-installation is required. Make sure to keep a backup and stay informed by reading this GitHub Discussion thread.

ℹ️ Since Supervisor architecture information for Raspberry Pi 5 just got added, a dev version of Supervisor is required. Make sure to change to the dev channel and update the Supervisor

ha supervisor options --channel=dev
ha supervisor reload
ha supervisor update

Restoring from Backup at on-boarding time is not recommended because of the unavailability of the add-on store. If you want to restore from a backup, go through on-boarding, install the SSH/Web Terminal add-on and run the commands above, then upload the backup and restore it from the temporary installation.

Currently I am mainly curious to see how the update system behaves in practice. Being on the dev channel will present development builds of OS and Core.

[McTristan]

@Zaleo80 no issues after restarting the pi?

[micha-clgn]

@kannan-balasubramanian
Had the same issue. Just to confirm.

[kannan-balasubramanian]

@micha-clgn Thank you for confirming. Let me format the SD card, reinstall the latest dev version and check it out.

[Zaleo80]

No issues restarting.

I have the 8gb model and everything is running on an USB thumb drive.

Maybe the SD card or memory limitations are involved?

[lor74]

Succesfully installed on my new PI5 flashing the SD with BalenaEtcher
Succesfully restored configuration from backup (migrating from VirtualBox VM running on my macmini)
All modules, components etc are working fine
Rebooted the system several times with no issues

Core 2024.1.0.dev20231218
Supervisor 2023.12.0.dev1401
Operating System 11.3.dev20231214
Frontend 20231218.0.dev

Finally I can leave my Macmini free :)

Great!

[Zaleo80]

Currently I am mainly curious to see how the update system behaves in practice. Ideally, tester should enroll the dev channel using:

ha supervisor options --channel=dev
ha supervisor reload

I have a spare Pi 4 and a Pi 5.
Would lover to help.

But don't understand your question about the update process behaviour.

We can't run the old version on the Pi5, so how to update to dev?

[agners]

You can install the image above, and just use Home Assistant normally. Since today was the first development build, there is no update yet, so nothing to test wrt updates right now. But more development builds will come out during this week. Running those update will show us if things work as expected.

[Th0tti]

I noticed that the Raspberry Pi OS has Imager 1.83. The information that an OS for Homekit is supported may be helpful for your great work.

[Greo83]

Hey all, that's very great news! In fact yesterday I tried running Home Assistant in Raspberry Pi OS - and failed.
I start downloading the dev image now and will perform a fresh install on Pi 5, then try to restore a backup. I used a Pi 3 before and meanwhile had a lot of performance issues.

I'll let you know when I'm done and also a very big thank you from my side for this pre-christmas present :-)

[Greo83]

Okay, my first tests for this evening.

After 1 1/2 hours of restoring I didn't want to wait longer. So I tried opening HA in a new browser tab. It opened immediately. Exactly the same look as before on Pi 3. But damn is that fast, wohoo! Warp 9.9, engage :-) Mobile app working as well.
I never tried restoring a backup before, I'm not sure if this "deadloop" is normal behaviour? I googled around and found others claiming a long restoring time. It was a full backup with around 100MB. I think a rather small installation.

Next step: Connect Sonoff Zigbee USB stick and restart. Result: Works like a charm. Not even a need to reconnect Zigbee devices. Amazing!

Regarding addons: HACS works as before, but the official AddOn Store does not regocnize my installed and actually running and working addons (like Zigbee). All Add-Ons in the store are greyed/disabled. I'll try the suggestions of the other comments tomorrow. But for now, I'm gonna mount coolers and case. From my point of view I'm already running in production system now. Great great great!

Let me know if you need certain things to be tested. I'll try to help.

[LukeRabauke]

Hi,
Updating from Pi3 -> Pi4 two weeks ago I faced the same deadloop...did that like 3 times and after a restart the system was running

[dbrb2]

Hmmm - I was running the HA on the pi5 fine, but the system failed to come back up after a power cycle.
Reflashing and restoring a backup all is fine again, and all HACS addons are running - but as @Greo83 found above, the system seems to think they are not in fact running

A hard power cycle fixed everything

However, I haven't dared try a soft host reboot, as twice now that has killed the system

[Zaleo80]

I've installed following your instructions and it works, but I can't install any add ons in Add-ons store, is there a way to fix this?

From what I understand (Quite a newbee on HA), this makes absolute sense, after the "ha supervisor reload" command core has lost connection with the supervisor and cannot manage any dockers running on the supervisor. (Add-Ons are additional docker instances). Also the network settings page remans blank for the same reasoning I guess.

Solution, power cycle the Pi5.

[agners]

The Core should try to reconnect though 🤔

[Zaleo80]

Not sure how/where/when/if to report this?

The hardware button on the Pi5 does not trigger a graceful shutdown.
Is this a 'bug' or missing feature?

Related but working as expected:

• When shutting down the Pi5 by software it does go in its off state (Red LED) and pressing the power button in the off state does boot HAOS perfectly.
• Holding the hardware power it for 4 seconds in the on state does power off the unit hard.

[agners]

Uh, we do configure systemd to use long-press of the power button for a graceful shutdown (to avoid acidential shutdowns). A long press in systemd is longer than 4s, so that could be a problem for this board 😢

[Zaleo80]

Is there only one systemd config for all supported boards?

[amrutprabhu]

I found a bug in the HA OS 11.3 for Raspberry Pi 5.

I did a fresh install, I installed terminal and file editor add-ons.
Then a full shutdown from the settings menu and then tried starting again.
it goes into boot loop.

this is what I could capture from the screen.

[dbrb2]

The simplest method I have found is to connectthe drive (SD card or SSD) into a linux laptop, then mount the partition you need and edit it manually. The appropriate partition won't automount (or it didn't for me) . So the process was:

Connect drive to laptop
dmesg to find what path has been allocated to the drive (/dev/sdX)
mkdir /tmp/hdd
sudo mount -o rw /dev/sdX1 /tmp/hdd

cd /tmp/hdd
nano config.txt

[smarthomecircle]

I think the problem lies when you are on the RC version > then update to the release version.

After downloading the release version and freshly burning the image on the SD card dint cause the issue anymore.

[toffyjan]

Thank you dbrb2. Should I add both parameters

dtparam=nvme
and
dtparam=pciex1_gen=3

Update:

I add both parameters and did a test with dd and it reaches disk reads of 442.6MB/s BEFORE it was around 206.2MB/s

dd if=/dev/zero of=/root/testfile bs=1G count=1 oflag=direct
1+0 records in
1+0 records out
1073741824 bytes (1.0GB) copied, 2.313625 seconds, 442.6MB/s

I am using

• Home Assistant OS 11.4.dev20231226
• Home Assistant Core: 2024.1.2
• PINEBERRY PI (HatDrive! Bottom)
• Samsung 970 Pro NVME

[ckoeber83]

Have now with activated pciex1_gen=3 in /boot/config.txt on HA OS with a throughput of 438.4MB/s!
2147479552 bytes (2.0GB) copied, 4.671406 seconds, 438.4MB/s

This looks better than the 286.6MB/s before.
But does not reach the throughput of Raspi lite OS with 821.73 MB/sec.

Any suggestions why it is slower on HA OS?

[ckoeber83]

Okay, if I test a larger file and more in parallel, I get higher values and even over 800MB/sec at the peak 😍

dd if=/dev/zero of=/root/testfile bs=10G count=10 oflag=direct
0+10 records in
0+10 records out
21474795520 bytes (20.0GB) copied, 29.965555 seconds, 683.4MB/s

[gabimal]

Same happened to me couple of minutes ago. Any idea how to make it work again or an sd card wipe and a full restore is needed?

[RenierM26]

Looks like a partition or file system problem. If you have access to a linux machine, you could try running fdisk and see what pops up?

[RenierM26]

Can boot using a USB with PI OS lite or something then insert the SD after booting from usb to troubleshoot.

[fonsuak]

Can confirm that HA OS 11.3 update was running fine up until I manually rebooted the system from within the HA interface. It goes into a weird boot loop. RPi 5 on 128gb Samsung EVOSelect MicroSD.

[dbrb2]

My pi5 with HA seemed to be running fine, and had been for a number of days. Yesterday I updated from rc2 to the release version. Unfortunately as of just now, when I tried a full reboot (not the first since the update of hardware), boot hangs at:

deferred probe pending

I've reflashed and restored from backup, and for now all seems good again....

[dbrb2]

Damn. Ran solidly for days, but then a device reboot took me directly back to "deferred probe pending"
Time for another restore....

[yahwehPT]

same problem after update to 11.4 and reboot. Time to restore

[yahwehPT]

I'm using USB SSD on a 3.0 port and you?

[omega180984]

My experience:

Rpi 5 with 8gb and official powerplug works fine. I performe multiple reboots and also a complete shutdown. After i start every works fine. No hanging boot.

I use a ssd samsung evo 860 500gb over usb 3 without any issues like descriebed.

Currently i working to implement something like a ramfs with Backup and restore beetween shutdowns or reboots, but this is not finished yet in my setup

[PennyAfNorberg]

The bootloop seems only to affect sd-cards.

[loudemer]

No I got it with USB device.

[CommanderROR9]

I also had it with an USB SSD.
My current 11.3 setup seems to be holding up and survived one reboot (to restore Addons) but I don't trust it yet...

[cj-github-dev]

[PennyAfNorberg]

@cj-github-dev I tested this and made a reboot early and it did boot fins, now lets see efter restre and some usb-dongels.

[Daniel167]

@PennyAfNorberg hello, can you test a shutdown and new start please? You have a Pi 5 with the new 11.4 System from this day? No problem at restart? Thanks a lot

[PennyAfNorberg]

@Daniel167 Works for me tested a couple of times, reboot soft, hard and shutdown/start up, all works at the moment.

[ckoeber83]

No bootloop or startup issues on RPi5 with Pineberry Pi HatDrive! Top and NVMe M.2 SSD Corsair model: MP600 MINI size: 931.51 GiB on Non-Volatile memory controller: Phison Electronics Corporation PS5021-E21 PCIe4 NVMe Controller (DRAM-less) 👍

Works also with NVMe SSDs at Gen 3.0 speed (getting up to 900 MB/sec) LnkSta: Speed 8GT/s (downgraded), Width x1 (downgraded)
See above

[Marcofant]

Installed 11.4rc1 on RPi5/8G/SD-Card, restored Fullbackup, connected USB devices for ZWave/RFlink and tested several cold/warm restarts without any problems.

[tormm78]

Hi,
for me everything crashed as soon i started to connect zigbee usb dongle, both sonoff plus and a ezsp unit with mosquito and zigbee2mqtt and i restarted.
The pi 5, 8gb wont start up and just runs full speed.
maybe you guys have experienced same?

[PennyAfNorberg]

Can you look at the terminal, does it look like a bunch of us ?

[tmonxx]

Currently restored from a backup on a Raspberry Pi5 with Pineberry HatDrive! Bottom on a Crucial P5 Plus NVME.
Runs perfectly with OS 11.4.
Congrats and thanks for the great work.

[lor74]

Just for update the OS.
usualky I never reboot the OS if is not needed… last uptime was 18 days. :)
Maybe tomorrow I will try… tonight I don’t have time to re-flash the SD in case something goes wrong ;)

[groenmarsmannetje]

I just did a reboot and luckily it came back 😄 but took some time. That was the reason that I asked because I got concerned,

[lor74]

Great to hear that the reboot works! :)

[CommanderROR9]

I decided to risk it an Update to 11.4
Update ran fine and the system survived the reboot..so far,.so good...🤞

[toffyjan]

I just updated to latest stable release 11.4 from 2023.12.2.dev2902...after reboots it doesn't boot any more.

[kantokant]

Has anybody tested already Raspi 5 with any GPIO module attached? I'm currently using a RaZberry2 ZWave GPIO module in my old Raspi 3B and would like to jump onto Raspi5 now. I know I should do this test by myself, but I'm a bit worried about losing the configuration stored in the RaZberry2 if something goes wrong during testing.

[dbrb2]

I found the same, booting from SSD A hard power cycle was fine, but a "reboot host System" from within the UI caused the system to hang during boot

…

On Tue, 9 Jan 2024, 23:34 AJO (Ajmal-Safi), ***@***.***> wrote: I just updated to latest stable release 11.4 from 2023.12.2.dev2902...after reboots it doesn't boot any more. — Reply to this email directly, view it on GitHub <#2844 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFQ44KD7QWN72PJPFKKGDYNXHWXAVCNFSM6AAAAAA6HE52FOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANZSHEYDQ> . You are receiving this because you commented.Message ID: <home-assistant/operating-system/repo-discussions/2844/comments/8072908@ github.com>

[PennyAfNorberg]

Is it the same: no filesystem mounten?

[dbrb2]

Unsure I could see that all partitions had been detected, but then boot hung showing: deferred probe pending

…

On Wed, 10 Jan 2024, 00:02 PennyAfNorberg, ***@***.***> wrote: Is it the same: no filesystem mounten? — Reply to this email directly, view it on GitHub <#2844 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFQ4ZLXT5GW46LPMMMXDDYNXK7ZAVCNFSM6AAAAAA6HE52FOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANZTGE2DG> . You are receiving this because you commented.Message ID: <home-assistant/operating-system/repo-discussions/2844/comments/8073143@ github.com>

[Fabry82]

same problem for me too, once the latest version was installed and the reboot was done, the system went into a continuous loop. in previous versions I rebooted easily but didn't shut down. Now I'll have to rewrite the SD. Il Mar 9 Gen 2024, 23:43 yahwehPT ***@***.***> ha scritto:

…

I'm using USB SSD on a 3.0 port and you? — Reply to this email directly, view it on GitHub <#2844 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A4GVODHYG5LQ2S5SKXHXTSTYNXBY7AVCNFSM6AAAAAA6HE52FOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANZSGQYDQ> . You are receiving this because you commented.Message ID: <home-assistant/operating-system/repo-discussions/2844/comments/8072408@ github.com>

[tmonxx]

I do not have any problems. It was a clean install, not an update.

[dbrb2]

As an aside, it would be very useful if the images, as burnt, had: usb_max_current_enable=1 Set in config.txt - since it would speed up restoring from backups for anyone without an official supply. Mine is not an official supply, but is capable of supplying over 4A, which is isn't even coming close to

…

On Wed, Jan 10, 2024 at 7:59 AM tmonxx ***@***.***> wrote: I do not have any problems. It was a clean install, not an update. — Reply to this email directly, view it on GitHub <#2844 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABFQ42PVV5H5Y4BYR23YSLYNZC5TAVCNFSM6AAAAAA6HE52FOVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DANZWGQ4TK> . You are receiving this because you commented.Message ID: <home-assistant/operating-system/repo-discussions/2844/comments/8076495@ github.com>

[iacavd]

Only thing i can fine is this
https://forums.raspberrypi.com/viewtopic.php?t=356501

[yahwehPT]

yes, when rebooting from HA I allways get that error, but sometimes I get that in other reboots.

[yahwehPT]

Updated the bootloader and same error. If I insert a blank SD card theres a boot loop.

[nsteffan-ct]

@iacavd @yahwehPT thats the same issue as I reported above. There appears to be some sort of issue with the bootloader and the file system.

[timh0r]

Got the same issue as everybody
Downloaded the latest version and compared.
Boot file add different uuid than in the install image and different kernel too.
I replaced the boot and kernel images from my SD card with the new ones and it fixed.
After reboot it was still saying I was on 11.3RC2 and not 11.4
At least i was able to make a backup of my system to redeploy a fresh 11.4

[Caboz]

I installed 11.3 on Raspberry Pi 5 8G and updated it to 11.4. Every time I shutdown the Pi it goes into a restarting loop.

I flashed the SD card a couple of times and the problem remains.

[sairon]

Don't use Discussions as an issue tracker, please

This thread already contains over 400 messages in almost 100 threads and it is very hard to keep track of all of them. The original purpose of this forum topic was to discuss the progress of porting the OS to Raspberry Pi 5, which is now mostly done and now we need to focus on resolving the outstanding issues. We can't do it without you, the community, however, we can't do it efficiently if the reports are scattered across many threads, or even platforms.

Please, from now on, report all the issues you encounter only using the Issues tracker in this repository. So far it seems bunch of you ran into an issue with corrupted cmdline file or boot partition, which we'd like to analyze in #3065. For any other problems, please try to gather as much information as possible, as you can see, even a simple photo can help a lot.

For any other topics, feel free to start another discussion here or on our Community forums. Thank you for your help and the enthusiasm you share with us 🤗