<Robbiedobbie>
So to come back on my remark yesterday that I could not seem to run the armv6 image on the raspi 0w; It seems that the uboot in the image does not support the 0w. When I manually build a suitable uboot and put that on, I do get the bootloader to show up on screen. (Unfortunately, it then fails on a missing dtb for the zero-w, which I'm going to solve next, however building a new sd image takes ages on the raspi :')
<Robbiedobbie>
@dezgeg, may I ask how you build those armv6 packages? Do you have some raspi1 server farm? Or is there some trick that I don't know of...
orivej has joined #nixos-aarch64
Robbiedobbie has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 256 seconds]
vcunat has joined #nixos-aarch64
orivej has joined #nixos-aarch64
rob has joined #nixos-aarch64
rob is now known as Robbiedobbie
<Robbiedobbie>
Another step in my search of running nixos on the raspi0w, I managed to fix the dtb by manually copying the bcm2708-rpi-0-w.dtb to bcm2835-rpi-zero-w.dtb so that the bootloader can find it. However, I now get a kernel panic during boot. Since I'm not sure about the dtb files and what they do exactly, am I missing something here? Any clues?
<Robbiedobbie>
The kernel panic is the following:
<Robbiedobbie>
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
<Robbiedobbie>
CPU: 0 PID: 1 Comm: swapper Tainted: G W 4.9.59 #1-NixOS
<Robbiedobbie>
Hardware name: BCM2835
<Robbiedobbie>
And then a stacktrace showing that the panic happened in mount_block_root
Robbiedobbie has quit [Ping timeout: 248 seconds]
kier has quit [Read error: Connection reset by peer]