Ericson2314 has joined #nixos-aarch64
orivej has quit [Ping timeout: 252 seconds]
tathougies has joined #nixos-aarch64
efraim has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
efraim has joined #nixos-aarch64
efraim has quit [Changing host]
efraim has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
tathougies has quit [Quit: Leaving.]
Ericson2314 has quit [Ping timeout: 252 seconds]
sphalerite has quit [Quit: WeeChat 2.0]
sphalerite has joined #nixos-aarch64
sphalerite has quit [Quit: WeeChat 2.0]
sphalerite has joined #nixos-aarch64
sphalerite has quit [Quit: WeeChat 2.0]
sphalerite has joined #nixos-aarch64
orivej has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
Ericson2314 has joined #nixos-aarch64
Piece_Maker has joined #nixos-aarch64
Acou_Bass has quit [Ping timeout: 252 seconds]
Piece_Maker is now known as Acou_Bass
orivej has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-aarch64
lopsided98 has quit [Quit: Disconnected]
lopsided98 has joined #nixos-aarch64
lopsided98 has quit [Client Quit]
lopsided98 has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
dotlambda has joined #nixos-aarch64
<dotlambda> I'm trying to boot NixOS on my rpi 3B+ but am stuck on "Starting kernel ...". Also no further output on UART. Any idea?
<samueldr> dotlambda: wait a long time
<samueldr> I haven't yet confirmed
<samueldr> but I think the console arguments may be wrong and it's currently in stage-1 resizing partitions :/
<samueldr> and I can't confirm for a 3B+ as I only have a 3B
<dotlambda> samueldr: How long? I've already waited ~20min
<samueldr> oh, definitely less than that
<samueldr> I am uncertain as to what's the actual current status of the 3B+, but I think it should be working :/
* samueldr checks to buy a 3b+
<samueldr> hmm, not sure I want to at the cost, considering what I'd do with it
<samueldr> (mostly check whether nixos works :/)
<dotlambda> I'll now try the (no longer necessary) workaround image and hope it'll magically work
Ericson2314 has quit [Ping timeout: 260 seconds]
<samueldr> this makes me want to build some kind of affordable testing infra for SBCs so a complete image can be tested remotely
<gchristensen> I've got some work towards that here
<samueldr> but uh, kinda difficult to do is you want to test booting on real SD without burning the fuses to usb or network boot the pi
<samueldr> if you want*
<gchristensen> annoying to test but I have some work towards it. using a serial monitor and netboot
<samueldr> usb could be doable using a usb gadget and another device
<samueldr> (so you are not forced to rely on the results of netboot)
<samueldr> (usb gadget as in linux usb gadget)
<gchristensen> that seems cool
<dotlambda> Sounds like a neat idea. I have a spare BananaPi that could be used for that.
<samueldr> though usb gadgets mostly means two SBCs per target, the target one, and another for usb gadget, unless there's known hardware with multiple usb devices that can be used as gadget *thing*
<gchristensen> how would the gadget work?
<samueldr> (only limited thoughts)
<samueldr> network -eth> gadget-sbc -serial+usb> target-sbc
<samueldr> target-sbc could also be connected to the network
<gchristensen> hmm cool
<samueldr> the gadget-sbc would be for all intents and purposes a usb drive
<dotlambda> Maybe the people from e.g. armbian have some testing infrastructure we could copy
<samueldr> maybe!
<gchristensen> +1
<makefu> i am getting a compile error when trying to build uhub for aarch64, instead of just excluding aarch64 i would like to fix the build : https://github.com/NixOS/nixpkgs/pull/48021 . anyone had similar issues before with a different package?
<{^_^}> #48021 (by makefu, 1 hour ago, open): uhub: re-enable sqlite plugin
<samueldr> dunno if the repo is up to date
<samueldr> but it looks like it doesn't know about aarch64
<samueldr> at that point, I would generally look to other aarch64 distros, and buildroot, for patches
<samueldr> (I could have misdiagnosed)
<makefu> it seems to be related to -Wall weirdly only on aarch64
<dotlambda> samueldr: Yay, I got it working! I used sd-image-aarch64-with-kernel-4.18-rc1.img and added console=ttyS1,115200n8 to the boot params :)
<makefu> in a tokenizer test ... geez https://logs.nix.ci/?key=nixos/nixpkgs.48021&attempt_id=a8c098f4-700d-49d1-be2b-d615390604e1
<makefu> samueldr: thanks
<samueldr> though I don't see the patch on the debian patch tracker for uhub
<samueldr> dotlambda: ooooh, right, maybe the default aarch64 image still builds with 4.14 since it's the nixos default
<samueldr> I hadn't thought about that
<makefu> samueldr: i think it is related to CPUINFO being missing. thanks :)
<samueldr> makefu: most of the time searching for the error or trying to guess where the error gets me 90% of the way there, every time
<samueldr> often other distros HAD to fix it
<makefu> so true
<makefu> first try is archlinux because the PKGBUILDs are easy to read and the patches are not in some weird version control, but git
<samueldr> yeah, same
Ericson2314 has joined #nixos-aarch64
<makefu> okay that worked out quite well, i've pushed the extra commits to the PR
<samueldr> :D -1 aarch64 failure <3 makefu
<makefu> thanks for the super clean 18.09 btw, i am sure this was the smoothest update i've ever had with nixos