RPi4
nixpkgs
RPi4 | nixpkgs | |
---|---|---|
54 | 975 | |
1,146 | 15,753 | |
1.7% | 2.8% | |
5.6 | 10.0 | |
23 days ago | 1 day ago | |
Shell | Nix | |
GNU General Public License v3.0 or later | MIT License |
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.
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.
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...
What are some alternatives?
NanoPi-R4S-OpenWRT - OpenWrt Frimwares for FriendlyARM NanoPi R4S
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
openbsd-rpi4
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
zram-swap - A simple zram swap service for modern systemd Linux
git-lfs - Git extension for versioning large files
BorgBackup - Deduplicating archiver with compression and authenticated encryption.
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
k3s - Lightweight Kubernetes
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
uhubctl - uhubctl - USB hub per-port power control
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.