vika_nezrimaya has quit [Ping timeout: 244 seconds]
omnipotententity has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
t184256 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
ris has joined #nixos-aarch64
zupo has joined #nixos-aarch64
koral has joined #nixos-aarch64
koral is now known as k0ral
orivej has quit [Ping timeout: 246 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-aarch64
<k0ral>
Hello
<k0ral>
I am surprised the /boot/config.txt file is not created at all when I set the boot.loader.raspberryPi.firmwareConfig option -- did I do something wrong ?
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
orivej has quit [Ping timeout: 246 seconds]
FRidh has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
<lopsided98>
k0ral: can you share your config? You need to set "boot.loader.raspberryPi.uboot.enable = true" and you probably want to set "boot.loader.raspberryPi.uboot.enable = true" as well, unless you have a reason for using the plain Raspberry Pi bootloader without U-Boot
<lopsided98>
There are lot of changes there, but I linked the most relevant one. I'm planning on making a PR soon
<samueldr>
ooh, is there anything I can to to help get this to master in time for 19.09. lopsided98?
<samueldr>
lopsided98++
<{^_^}>
lopsided98's karma got increased to 7
<samueldr>
hm, there's a different u-boot for the pi zero? weird
<samueldr>
ah, 0_w_defconfig, I wonder if these have been reconciled into a more common config shared between the zeroes and the 1
<samueldr>
(though out of scope of those changes obv.)
<lopsided98>
I could use some help making sure this doesn't break existing installations. All of mine are either recently installed from custom SD images or were manually modified to move the FAT partition off of /boot a long time ago
<lopsided98>
I'll ping you when I create the PR
<samueldr>
we could figure out a few test cases and I'd take the few devices I have on hand and try them
<samueldr>
oh, I was thinking of raspi 0/1/2 but forgot it'd mean to rebuild the world :)
<samueldr>
still, use the 3B to test a few cases
chiefgoat has quit [Read error: Connection reset by peer]
chiefgoat has joined #nixos-aarch64
chiefgoat has quit [Read error: Connection reset by peer]
chiefgoat has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
vika_nezrimaya has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
k0ral has quit [Ping timeout: 264 seconds]
k0ral has joined #nixos-aarch64
elvishjerricco has quit [Ping timeout: 252 seconds]
c00w has quit [Ping timeout: 252 seconds]
elvishjerricco has joined #nixos-aarch64
c00w has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
simpson has joined #nixos-aarch64
<k0ral>
lopsided98: I already have "boot.loader.raspberryPi.uboot.enable = true"; and yes, I have a recent SD image (1 week old)
<samueldr>
k0ral: from 19.03 or from unstable?
<k0ral>
from unstable
<k0ral>
should I avoid unstable at the moment ?
<samueldr>
no, it's more that there were changes about the handling of "firmwares" for the sd images
<samueldr>
knowing it's from unstable, though, allows us to know what's going on :)
<k0ral>
the real issue I am trying to fix is that right now, my raspberry does not boot until I plug the HDMI cable in; I read that a couple of options in /boot/config.txt could fix that, but since I could not get nixos to generate that file...
<samueldr>
you can test them by manually mounting and editing the file /config.txt in the firmware partition
<samueldr>
the firmware partition has the label FIRMWARE
<k0ral>
I know the one :) we discussed it last week