<apache8080>
`nix-build '<nixpkgs/nixos>' -A config.system.build.sdImage -I nixos-config=./sd-image-aarch64.nix` When I run this command now with the latest nixpkgs repo I don't get a .bz2 file and also for some reason it builds a 19.09 sd image. Then when I try to boot the image on an RPi moel 3B+ I get the following uboot error: card did not respond to
<apache8080>
voltage select.
<samueldr>
apache8080: "when I run this command with the latest nixpkgs repo"
<samueldr>
nix-build '<nixpkgs/nixos>' is akin ton expanding the path to what is in your NIX_PATH (or -I arguments)
<apache8080>
yeah, I have latest nixpkgs repo as my NIX_PATH
<samueldr>
so even if you `cd checkout/of/nixpkgs` beforehand it won't matter, since it's using whatever comes from your environment
<samueldr>
ah
<samueldr>
if you have a git checkout, just use `nix-build nixos`
<samueldr>
since you're *anyway* using a path in a way as an argument to nix-build, why go through a layer of indirection?
<apache8080>
ok, even still why would it be building a 19.09 image
<apache8080>
it used to build a 20.03 image
<samueldr>
the most likely explanation here is that the NIX_PATH was setup wrong and it's using a nixpkgs for 19.09
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<apache8080>
samueldr pulled the latest nixpkgs and now it built a 20.09 image but when I boot on the raspberry pi I still get the Card did not respond to voltage select.
<apache8080>
Also getting `lan78xx_eth Waithing for PHY auto negotiation to complete`, `missing environment variable: pxeuuid`
<samueldr>
that one shouldn't matter
<samueldr>
that's about network booting
<apache8080>
ok
<apache8080>
the other one is a uboot error right? it can't find the sd card?
<samueldr>
though, the 3B+ I can't test personally, other users have not had any issues producing working u-boot for them
<samueldr>
yep
<samueldr>
exactly
<samueldr>
though the pi itself seems to be fine with the card
<samueldr>
you're booting from the card and not USB, right?
<apache8080>
I tried an older 20.03 image from hydra and it worked fine
<apache8080>
yeah
<samueldr>
can you try with the previous u-boot? revert the commit that updated to 2020.07
<apache8080>
you know what commit that is?
<samueldr>
it would be the last one that touched the u-boot directory
<samueldr>
so bd7216506334a4233b08506001e76aaa58b36be5
<samueldr>
no patches for raspberry pi 3B on the u-boot mailing list, so it must not be widespread if it is an issue
<apache8080>
rebuilding right now
cole-h has joined #nixos-aarch64
<apache8080>
reverted that commit and it made no difference
<apache8080>
any chance this could be a hardware issue?
<samueldr>
I'm not sure, but it's a possibility
<apache8080>
did printenv on the uboot prompt and I don't see sdboot anywhere
<samueldr>
but the fact that a 20.03 image works makes me think it's less likely
<apache8080>
but I see usb_boot
<samueldr>
it should be running bootcmd
<samueldr>
and that in turn through some contortion does boot from sd
<apache8080>
so there is:
<apache8080>
``` bootcmd = run distro_bootcmd
<samueldr>
`run` runs what's in that environment variable
<samueldr>
so distro_bootcmd has a snipper, which... well you see the contortion now :)
<apache8080>
oh ok so it boots from the boot_targets and the boottargets are set to the following:`boot_targets= mmc0 mmc1 usb0 pxe dhcp`
<samueldr>
mmc* represent both emmc and sd cards in u-boot parlance
<apache8080>
so compared the printenv from the working 20.03 image and the broken 20.09 image and the only thing that I am seeing that is different is the broken one doesn't have `bootfile=/boot/extlinux/extlinux.conf` and `bootfstype=ext4`
<samueldr>
I don't know that it should be a problem
<samueldr>
since running the distro bootcmd is independent from detecting sd cards
<apache8080>
ok
<samueldr>
poking at the boot variables is probably not going to help
<apache8080>
is there a uboot command I can run to see if the sd card is detected
<samueldr>
`mmc` has subcommands
<apache8080>
did `mmc list`
<apache8080>
and it says there is an sd card in slot 0
<samueldr>
try `run bootcmd`
<samueldr>
do you have serial?
<apache8080>
same error, Card did not respond to voltage select
<samueldr>
if so, copying the whole output would help
<apache8080>
yeah I do
* samueldr
thinks
<apache8080>
it also says Device 0: unknown device
<apache8080>
oh damn I actually don't have a serial cable on me