<samueldr>
if you are using an unstable (nixos-unstable/19.09+) rather than a stable (19.03) disk image, there will be some differences that are yet undocumented
<omnipotententity>
thanks, I'll give those a shot again. I'm using 19.03 currently.
<samueldr>
good, then the notes in the wiki should be accurate
<omnipotententity>
There's some option somewhere that's causing it not to boot after a nixos-rebuild.
<omnipotententity>
And I guess I'll need to hunt it down
<samueldr>
"causing it not to boot" means what?
<omnipotententity>
Hangs at "Starting Kernel..."
<samueldr>
right
<omnipotententity>
No diagnostic message.
<samueldr>
that's a non-obvious flaw in how u-boot/the kernel works
<omnipotententity>
text on the RPi sayeth: "Raspberry Pi 3 Model B V1.2"
<samueldr>
good, if it was a "+". it would be writtn "B+"
<samueldr>
though, basically, the linux kernel has no way to write to the framebuffer until the modesetting driver is loaded, vc4, and by default it is not told to add the driver to the modules available during early boot
<samueldr>
we're using the upstream linux kernel, so there are a bunch of differences compared to the raspberry pi fork
<omnipotententity>
ok, so if I just load those drivers it should be aok?
<samueldr>
adding those may help, depending on the reasons it stays stuck there
<samueldr>
with a serial console you would be able to have the full log AFAIK
<omnipotententity>
ok, I can definitely make that work at least.
<omnipotententity>
thanks.
<omnipotententity>
As a question, what would need to change, if I found a 3B+ nix config
<omnipotententity>
between the two?
<samueldr>
if you are using someone's 3B+ config, likely nothing
<samueldr>
the main issue is that the u-boot on stable has no idea that the 3B+ (and 3A+) exists
<omnipotententity>
roger. thanks
<samueldr>
with a more recent kernel (e.g. linux*_latest) there is a disagreement and HDMI doesn't work
<samueldr>
though I don't have a the 3*+ hardware to check things out better