Hello. Thank you for this great topic.
So I decided to try build my own image for rpi zero w.
I basically used provided flake and try to compile on aws aarch64 machine.
However, without luck.
System is 23.11 and this issue (unable to unpack archive) seems to be weird.
What I missed? NixOS on aws is just some random selected comunity ami so maybe should I start to dig here?
error: builder for '/nix/store/vy12b7lmf3y548whsjfv3m81vlm8g2zz-libpng-apng-armv6l-unknown-linux-gnueabihf-1.6.40.drv' failed with exit code 1;
last 3 log lines:
> unpacking sources
> unpacking source archive /nix/store/jpqz1p52xw3jlhc8w143v92k0iaar2i4-libpng-1.6.40.tar.xz
> do not know how to unpack source archive /nix/store/jpqz1p52xw3jlhc8w143v92k0iaar2i4-libpng-1.6.40.tar.xz
For full logs, run 'nix log /nix/store/vy12b7lmf3y548whsjfv3m81vlm8g2zz-libpng-apng-armv6l-unknown-linux-gnueabihf-1.6.40.drv'.
error: 1 dependencies of derivation '/nix/store/2q5j823rwvrr8431y8dyg9i2w3cdrbsr-freetype-armv6l-unknown-linux-gnueabihf-2.13.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/9v3h4811dqsqc65yrvwq4y7mbyz7s8k0-fontconfig-armv6l-unknown-linux-gnueabihf-2.14.2.drv' failed to build
error: 1 dependencies of derivation '/nix/store/kdw5vbdbnp6djlqggmcw02lniqkay0zd-fontconfig-conf.drv' failed to build
error: 1 dependencies of derivation '/nix/store/li54ky7kl6yhjq204rkba2aig66x2hqk-system-path.drv' failed to build
error (ignored): error: cannot unlink '/run/user/0/nix-build-binutils-armv6l-unknown-linux-gnueabihf-2.40.drv-0/binutils-2.40/ld/.deps': Directory not empty
error (ignored): error: cannot unlink '/run/user/0/nix-build-libtasn1-armv6l-unknown-linux-gnueabihf-4.19.0.drv-0': Directory not empty
error: 1 dependencies of derivation '/nix/store/ban8rmijp7l85kvhgy5jg3qsrynahgm1-nixos-system-nixos-23.11.20240115.b8dd8be.drv' failed to build
error: 1 dependencies of derivation '/nix/store/sg2x74hlkf721z4355s8sy3zs9sqwm1y-ext4-fs.img.zst-armv6l-unknown-linux-gnueabihf.drv' failed to build
error: 1 dependencies of derivation '/nix/store/34ywqprscl80bmpwcpc2ihggnrk021wa-nixos-sd-image-23.11.20240115.b8dd8be-armv6l-linux.img-armv6l-unknown-linux-gnueabihf.drv' failed to build
[root@ip-172-31-16-53:~/flake]# nix --extra-experimental-features nix-command log /nix/store/vy12b7lmf3y548whsjfv3m81vlm8g2zz-libpng-apng-armv6l-unknown-linux-gnueabihf-1.6.40.drv
warning: The interpretation of store paths arguments ending in `.drv` recently changed. If this command is now failing try again with '/nix/store/vy12b7lmf3y548whsjfv3m81vlm8g2zz-libpng-apng-armv6l-unknown-linux-gnueabihf-1.6.40.drv^*'
@nix { "action": "setPhase", "phase": "unpackPhase" }
unpacking sources
unpacking source archive /nix/store/jpqz1p52xw3jlhc8w143v92k0iaar2i4-libpng-1.6.40.tar.xz
do not know how to unpack source archive /nix/store/jpqz1p52xw3jlhc8w143v92k0iaar2i4-libpng-1.6.40.tar.xz
Not sure about that error, I think I also saw this onetime, but don’t know anymore how I got it and also what I did to solve it. Could you maybe provide more logs (nix log /nix/store/vy12b7lmf3y548whsjfv3m81vlm8g2zz-libpng-apng-armv6l-unknown-linux-gnueabihf-1.6.40.drv) and the exact flake (of course redact secrets) you’re using?
Thank you very much for that tip. That did the trick in combination with my initial device tree overlay. I2C now works.
I then tried to analyze if I can get the &i2c1 version to work. Reading about your two links I now understand that these &[node] things are semantic sugar to extend other nodes. I then tried to use that in combination with the hardware.i2c.enable = true but I still had no success as I already predicted since this doesn’t change the dtb file (I already analyzed this in my last post). I then tried to remove the -i2c suffix and still had the hardware.i2c.enable = true set which works now. So
Output of nix log is provided in previous comment.
Just:
do not know how to unpack source archive /nix/store/jpqz1p52xw3jlhc8w143v92k0iaar2i4-libpng-1.6.40.tar.xz
Hi @xiil, that build is for an old version of NixOS. There are multiple things in there which don’t apply to NixOS 25.05.
Relevant to this thread, it uses boot.loader.raspberryPi.enable, which has been removed. Nowadays, NixOS uses u-boot (boot.loader.generic-extlinux-compatible.enable). See sd-image-raspberry.pi.nix for how u-boot is installed on the SD card.
With the old raspberryPi boot loader, it was possible to enable i2c with:
# outdated - no longer works
{ boot.loader.raspberryPi.firmwareConfig = "dtparam=i2c=on"; }
That’s nice @matthewcroughan. It’s good to use mainline and systemd-boot.
Although, after reading your nix code, it’s not “just” a case of replacing the hacks with systemd-boot and mainline linux. There are still kernel config changes, a patch applied to systemd, and assembling the the repart image.
This is my current basic config for rpi1 (for rpi zero w it would need config for wireless networking and i2c):
One definition of “simple” is less code on top of nixos. Using mainline kernel and system-boot is the future and it will be good. But for me, at the moment, using linux_rpi1 plus a few hacks seems easier.
Which channel/branch do you use to build this? I’ve tried building with unstable on my Mac and I get intermittent failures. The latest one I saw was something about libapparmor being unable to link to Python.
Update: I managed to build it properly on an x86_64-linux machine (like every example uses as the buildHost). So I guess somethings are a little broken building from aarch64-linux (the mac build was via the linux-builder).
(snippet of log output)
> -lpython3.12 -ldl -L/nix/store/rzc5hin8k6ffk2058hmkspsn2p90rbr9-libxcrypt-4.4.38/lib -lm
> checking python extra linking flags... /nix/store/gbml27jdc722w5srjw6mw28v08wi0xbf-python3-3.12.10/bin/python3-config is /nix/store/gbml27jdc722w5srjw6mw28v08wi0xbf-python3-3.12.10/bin/python3-config
> -L/nix/store/gbml27jdc722w5srjw6mw28v08wi0xbf-python3-3.12.10/lib -lpython3.12 -ldl -L/nix/store/rzc5hin8k6ffk2058hmkspsn2p90rbr9-libxcrypt-4.4.38/lib -lm
> checking consistency of all components of python development environment... no
> configure: error:
> Could not link test program to Python. Maybe the main Python library has been
> installed in some non-standard library path. If so, pass it to configure,
> via the LDFLAGS environment variable.
> Example: ./configure LDFLAGS="-L/usr/non-standard-path/python/lib"
> ============================================================================
> ERROR!
> You probably have to install the development version of the Python package
> for your distribution. The exact name of this package varies among them.
> ============================================================================
>
For full logs, run 'nix log /nix/store/iimhan62asn3mpmg4385slwrjwkf1ya0-libapparmor-armv6l-unknown-linux-gnueabihf-4.1.0.drv'.
error: builder for '/nix/store/iimhan62asn3mpmg4385slwrjwkf1ya0-libapparmor-armv6l-unknown-linux-gnueabihf-4.1.0.drv' failed with exit code 1
error: 1 dependencies of derivation '/nix/store/q8f9ir8jr45nk42c8wgb4qsdklm44l8n-dbus-armv6l-unknown-linux-gnueabihf-1.14.10.drv' failed to build
error: 1 dependencies of derivation '/nix/store/fl951p16jpyfwlwn6gwcj70y1wf5faq8-systemd-armv6l-unknown-linux-gnueabihf-257.5.drv' failed to build
error: 1 dependencies of derivation '/nix/store/4jngd95qrnllhzyzcrsl1fqwlnvx1fy7-nixos-system-nixos-sd-card-25.05pre-git.drv' failed to build