docs
RPi4
docs | RPi4 | |
---|---|---|
2 | 54 | |
884 | 1,152 | |
- | 2.3% | |
10.0 | 5.6 | |
almost 4 years ago | about 1 month ago | |
Shell | Shell | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docs
-
Flatcar Container Linux
ublue is based off of fedora and rpm-ostree, which is what "CoreOS" is today.
What happened was old school CoreOS was A/B partition based: https://github.com/coreos/docs/blob/master/os/sdk-disk-parti...
My memory is hazy but here's how I remember it: After Red Hat acquired CoreOS they rebased the entire thing around rpm-ostree, which is the CoreOS people know today: https://coreos.github.io/rpm-ostree/
At the time there was some anxiety in the community as to what would happen, as there was no direct upgrade path from old CoreOS to new CoreOS. Theoretically if we all believed the kool-aid we were drinking it's just a redeploy, no pets!
Kinvolk came along, forked it, and made Flatcar Linux, which kept the A/B partitioning system, and more crucially, let you just change a config file and all your old CoreOS nodes would just move to Flatcar and then you were good to go. So now if you wanted to stay on the system you were comfortable with you could just use Flatcar. If the composability of rpm-ostree attracted you then new CoreOS have you covered. Red Hat deserves a hat tip here because in their documentation/blog they explicitly mentioned Flatcar as an option for people who wanted to stick with what they know, which I thought was cool and how I discovered it!
Later on Microsoft acquired Kinvolk and and then people raised eyebrows. I have not checked in a while but the folks involved continued to do their thing and run it like a good OSS project, hold public meetings, all that stuff.
I use both and they're both high quality.
- How to change SSH port in new ubuntu version? (Tried Many times not working)
RPi4
-
CentOS Stream and Raspberry Pi
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
-
What is the most trusted hardware most OpenBSD people would suggest?
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
-
Kernel Updates Installed but not Loading
Looks like you can use Grub on UEFI ARM systems, but Raspberry Pi isn't natively running UEFI. https://github.com/pftf/RPi4
-
Flatcar Container Linux
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
-
Does NetBSD 9.3 work on the RaspberryPi 4?
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.
-
Ethernet on my Pi4 is giving me headaches
Maybe similar discussion on github:
-
How can I dual boot Fedora on Pi4?
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.
-
Orange Pi 5: 8-core CPU 2.4GHz, up to 32GB DDR4, $60 preorders ship Dec. 1
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
-
[Aarch64] Help creating a generic image that boots on the 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.
-
I have come to bury the BIOS, not to open it: The need for holistic systems
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.
What are some alternatives?
Flatcar - Flatcar project repository for issue tracking, project documentation, etc.
NanoPi-R4S-OpenWRT - OpenWrt Frimwares for FriendlyARM NanoPi R4S
coreroller - CoreRoller is a set of tools to control and monitor the rollout of your updates.
openbsd-rpi4
ostree - Operating system and container binary deployment and upgrades
zram-swap - A simple zram swap service for modern systemd Linux
fedora-coreos-tracker - Issue tracker for Fedora CoreOS
BorgBackup - Deduplicating archiver with compression and authenticated encryption.
Flatcar - Flatcar project repository for issue tracking, project documentation, etc. [Moved to: https://github.com/flatcar/Flatcar]
k3s - Lightweight Kubernetes
uhubctl - uhubctl - USB hub per-port power control
edk2-sdm845 - (Maybe) Generic edk2 port for sdm845