RPi4 VS raspberry-pi-dramble

Correct. It does not as shipped. However, the use of this project will bring the firmware into system ready spec, so it can boot with a standard aarch64 UEFI image: https://github.com/pftf/RPi4

are you using the uefi firmware from https://github.com/pftf/RPi4 or are you trying to boot through the gpio serial header?I don't think the pi can boot on its own through uboot unless your using a serial/usb connection

Looks like you can use Grub on UEFI ARM systems, but Raspberry Pi isn't natively running UEFI. https://github.com/pftf/RPi4

The rpi4 has uefi firmware available, this allows you to boot any generic uefi aarch64 image, you no longer need rpi specific images.

https://github.com/pftf/RPi4

Straight out of the box, the image wouldn't boot, said that start.elf was invalid, so I went to https://github.com/pftf/RPi4/releases as suggested in the Readme.md file in the EFI partition. I installed that (version 1.34) over the existing EFI partition and tried again. That booted up the kernel, but it apparently died when it enabled the interrupt controller. The last messages are about armgic0.

Maybe similar discussion on github:

You can use these firmware images for UEFI as well as install with the arm ISO. I didn't have graphics acceleration that way, but it might be an easy fix.

I'm guessing these are not SystemReady certified with UEFI firmware and require "bespoke" preinstalled arm images?

https://www.arm.com/architecture/system-architectures/system...

https://developer.arm.com/documentation/102677/0100/UEFI-req...

I have three SystemReady arm devices and it's pretty awesome to be able to just boot an aarch64 live ISO and install. The experience is the same for running vms via ESXi arm edition.

Nvidia Jetson AGX Xavier - https://developer.nvidia.com/embedded/downloads#?search=uefi

Honeycomb LX2 - https://github.com/SolidRun/lx2160a_uefi

RPI4 - https://github.com/pftf/RPi4

It can be tedious building/provisioning the firmware but once complete they are ready for any aarch64 uefi iso.

What is annoying however is when distros don't ship an aarch64 uefi iso - but instead choose to build a zillion device specific "preinstalled" arm images. (looking at you manjaro)

The list of supported devices for ESXi arm edition is a great place to start for identifying options and is constantly updated.

https://flings.vmware.com/esxi-arm-edition

  Raspberry-Pi-4

The only reason why I am was trying to build the image was because I wanted to move stuff as mainline as possible and was worried that any installation made with the help of RPi4 UEFI firmware would stop booting after a while.

Most ARM hardware is cellphones, raspberry pi and the Mac M1, which certainly aren't that type.

But a lot of ARM hardware is that type. The keywords are SBSA / SBBR / SystemReady. If your hardware is SBBR compatible then Fedora and Ubuntu's ARM64 iso, and Windows ARM64, downloaded from their website, will at least boot fine (drivers are a different question as always).

There's a good list of supported hardware in the lower half of https://community.arm.com/arm-community-blogs/b/architecture... . Many systems from Avantek, Gigabyte, NXP, Marvell, Solidrun etc are standardizing on this way of booting.

DeviceTree is low-level enough that you can implement UEFI on top of it. There's a UEFI port for the Raspberry Pi 4 at https://rpi4-uefi.dev/ that produces an SBBR layer, allowing it to boot any off-the-shelf ARM64 SBBR distro.

https://www.pidramble.com - but you do need to power the router. 5th port is an uplink

Don't bother. Just put them on an open stack and blow a quiet Noctua fan sideways through the stack. I used to have a four-pi4 cluster ala https://www.pidramble.com and one fan blowing back to front was easily good enough. I also removed the fans from the official PoE HATs since they sounded like rocket engines no matter what I did.

There's no rack, it's simply on the corner of my desk. I haven't made photos of it but it looks pretty much like Jeff Geerling's Dramble: https://www.pidramble.com/

Had a pi 'dramble' just like this one and it worked fine. I ran k3s at the time on it. Since it was a lab experimentation thing, I didn't throw more hardware at it, but I could have likely gotten similar results with a bunch of Vagrant/VirtualBox VMs on one NUC.

Automate the Pi Dramble website I run in my basement with Drupal Pi.

How is latency and stuff? Any slowness that you wouldn't expect from the software that may come from running it on a rpi4? I've been thinking of setting up a few services, but I kinda want to do something like the Pi Dramble, wasn't even aware that a single pi would have the power to run all of these services. Though I'm not actually surprised it does.

A couple years ago when I thought I'd have to get into kubernetes for a living, I built a 4x4GB pi4 cluster with the exact parts list from Jeff Geerling's "dramble" setup (link) and did a bunch of experimentation with k3s as a lightweight cluster solution. Worked pretty amazingly for things like "spin me up 10 more of those things" and for moving things around to upgrade the SD card on the 3rd pi while keeping the services running on the other pi. But I don't need to do kubernetes for a living so the cluster is just sitting here collecting dust powered-down basically.

I see this kind of question asked a lot when people are posting their Kubernetes Pi clusters. The rpi 4 quad core with 4-8GB RAM gives a lot of potential for the price in a kuberenetes setup I feel. I found the pi dramble project interesting, and even more the turing pi using rpi compute modules. Are NUCs really a cheaper alternative for a kubernetes cluster, every time I start try to come up with something I end up with a far more expensive setup and fewer cores. Any hints on viable setups, e.g. replacing 4x POE powered RPI 4's.?

My setup is exactly the same as the top photo on https://www.pidramble.com just with the stack'o'pi zip-tied to the switch so I can move it around without the things sliding around.