<DigitalKiwi>
nix-build . -A standardnotes // is also broke on not aarch64 (since it doesn't work on aarch64 to begin with) i think also related to llvm
<DigitalKiwi>
thefloweringash: how did you find that
zupo has quit [Ping timeout: 260 seconds]
<thefloweringash>
i actually found it two ways: I guessed that someone did `<literal>foo<literal>` (two opening tags), so I grepped for that and it showed up.
<thefloweringash>
and I also ran your nix-build, but with `--keep-output`, and went and read what was on line in the error, which showed it again
<thefloweringash>
uh, `--keep-failed`
<DigitalKiwi>
oh, --keep-output, duh >.>
<DigitalKiwi>
oh, --keep-failed, duh >.>
<DigitalKiwi>
thefloweringash++
<DigitalKiwi>
so do you want to do the PR or should I
zupo has joined #nixos-aarch64
<DigitalKiwi>
where's the bot
<thefloweringash>
do you mind doing this one?
<DigitalKiwi>
sure i'll do it
<thefloweringash>
thanks :-)
<DigitalKiwi>
the postgresql doc one right
<DigitalKiwi>
idk what the other one needs :(
exarkun_ is now known as exarkun
<thefloweringash>
too many issues scrolling by, yeah the doc one, was the other one standardnotes or did I miss one?
<DigitalKiwi>
the other doc issue lol on aarch64 due to llvm and haskell
<thefloweringash>
oh right, where it all started
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<samueldr>
until mainline has better support for the pi 4, this is the temporary image that can be used
<cidkid>
alrighty
<samueldr>
comes with no documentation, no manual, users beware :)
<cidkid>
I'll find my way around it
<cidkid>
I'm sure
<cidkid>
brb
cidkid has quit [Quit: Leaving.]
cidkid has joined #nixos-aarch64
<samueldr>
replikvlt47: good news is: I can reproduce the issue
<samueldr>
bad news is: uh
<cidkid>
Oh yeah meant to ask, where does nixos-mobile mount vendor when looking for firmware
<samueldr>
in /vendor
<cidkid>
hmm
<samueldr>
though that's a nixos configuration
<samueldr>
I think it'll end up being "wherever that particular device needs it"
<cidkid>
wonder if I can just point the vendor partition to a different partition thats not vendor and have bootlogd dump to their
<cidkid>
*there
<samueldr>
you could try
<samueldr>
replikvlt47: the moment I plug it into a screen it continues correctly
<samueldr>
so, there's that that's verified
<replikvlt>
okay, i'm glad i could help
<samueldr>
I'll try on unstable see if that u-boot is better behaved
<replikvlt>
it really should default to no screen because well. I'm sure that not am the only one that wants to have a raspberry dedicated server xd
<replikvlt>
okay
<samueldr>
"default to no screen"?
<samueldr>
that's not a default, it's more of a bug in u-boot than a configuration thing
<samueldr>
it worked at one point, pretty sure
<samueldr>
now, did it ever work on *that* u-boot version that's on 19.09? dunno
<replikvlt>
oh, well sorry. i'm quite incompetent in arm computing. :D
<samueldr>
don't worry, we all once were
<DigitalKiwi>
hey now what's with that past tense
<samueldr>
that's true, we all once were, that doesn't imply that we are all competent now
<DigitalKiwi>
it me
<samueldr>
replikvlt47: unstable verified to go past u-boot
<samueldr>
replikvlt47: this means that 20.03 should be good too, once it hits stable
cidkid has quit [Quit: Leaving.]
Thra11 has joined #nixos-aarch64
<samueldr>
if I was a bit less busy, and 19.09 not that close to EOL, I would look into fixing this, but... it apparently wasn't reported that it failed that way, so I'm not sure what to make of this
<samueldr>
it's weird
cidkid has joined #nixos-aarch64
<replikvlt>
it is, can't deny that
<replikvlt>
well it seems like i be flashing debian tomorrow onto this thing. At least for now. Thanks for help.
<srk>
or you can fix uboot on the sdcard manually :)
<replikvlt>
i wish i knew how...
<srk>
something like cp ${pkgs.ubootRaspberryPi3_32bit}/u-boot.bin firmware/u-boot-rpi3.bin