Acou_Bass has quit [Read error: Connection reset by peer]
Acou_Bass has joined #nixos-aarch64
Acou_Bass has quit [Client Quit]
Acou_Bass has joined #nixos-aarch64
orivej has joined #nixos-aarch64
Acou_Bass has quit [Quit: byeeeeeeeeeeeeeee]
Acou_Bass has joined #nixos-aarch64
jtojnar has quit [Ping timeout: 240 seconds]
mog has joined #nixos-aarch64
<mog>
hi
<sphalerite>
o/
<mog>
what is the right way for me to setup my other nixos box as a cross compile remote build-host for my aarch64 pi?
<sphalerite>
mog: cross-compilation is still fairly unreliable, and you need to use the right expressions — essentially, import nixpkgs for x86_64-linux with the cross config wherever you'd normally just import nixpkgs and pass the empty set
<sphalerite>
unreliable in the sense of many packages don't build with it
<mog>
*nods*
<mog>
okay. im building linux_rpi and its taking forever and a day, so in future wanted to avoid that
<sphalerite>
that should be in the cache I think..?
<mog>
so for aarch64 and rpi3 its marked as not allowed, someone had a pr to fix that and im building that on my box now to play with it
<sphalerite>
aaah ok
<sphalerite>
not sure if the kernel cross-compiles with nixpkgs, but an easy way to test it would be (directly on your x86 machine) `nix build nixpkgs.pkgsCross.aarch64-multiplatform.linux_rpi`
<sphalerite>
(with NIX_PATH set to point to the right nixpkgs)
<Dezgeg>
or build it with the community box
* mog
nods
<sphalerite>
you might also be judged as a known/trusted community member by gchristensen to get access to the community box
<mog>
thanks for advice
<sphalerite>
damn Dezgeg too fast
<mog>
i think gchristensen trusts me
<Dezgeg>
it probably already is there since I tested that PR
<Dezgeg>
well, test-built
<mog>
but im not ready to devote a box as a builder
<gchristensen>
yeah send a pr, mog
<gchristensen>
I can't get to it until this evening at the soonest
<mog>
gchristensen, ill put up resources for it soon. thank you though
<gchristensen>
I mean
<sphalerite>
mog: what do you mean devote a box as a builder?
<gchristensen>
its free, so
<mog>
oh i misread readme. i thought that was about adding builders to the cluster not using its services
<mog>
yes ill send a pr to add me then
<sphalerite>
yeah it's just the one box which can be accessed by everyone who's configured to have access :)
<gchristensen>
can anyone SSH to the builder and issue a reboot?
<mog>
can anyone tell me what i would need to do to get hat to populate in my device-tree like it did on raspbian? i thought just running their kernel would be enough
<sphalerite>
gchristensen: I would but I don't have permission it seems
<gchristensen>
ack
<sphalerite>
I just had a random idea. OTP-based auth so that gchristensen can give anyone with ssh access to the builder temporary sudo :p
orivej has joined #nixos-aarch64
<mog>
gchristensen, just needs a bot here to do his bidding
<mog>
of borg will expand to conqueror irc as well
<gchristensen>
a cute idea sphalerite
<sphalerite>
only problem is… it needs a secret, and I don't think there's a way to make that secret persistent and not accessible to whoever gets sudo
<sphalerite>
unless you have another server storing the secret and the community box asks that one to confirm the code. Which seems like a big fuss and probably isn't included in the pam otp module :p
<samueldr>
though, maybe something less... all-encompassing with sudo reboot being granted to a subset of trusted users?
Thra11 has joined #nixos-aarch64
samrose_ has joined #nixos-aarch64
<samrose_>
is there any known issues with running qemu-kvm *on* nixos-aarch64?
* sphalerite
tries it
<sphalerite>
well for a start you need to specify a machine type unlike on x86
<sphalerite>
well I'm not getting any immediate crashes :D
<mog>
i tried adding the i2c and spi settings to config.txt but no luck there
<samrose_>
sphalerite: awesome! a good sign, thanks for trying as I don't yet have a physical aarch64 to try this out on.
<samueldr>
AFAIK, samrose_, it's dependent on the CPU too, but I don't know a good way to check if it's available or not
<sphalerite>
samrose_: I didn't try actually running an OS either :p
<sphalerite>
samueldr: I think ls -l /dev/kvm
<samueldr>
I meant without access to the hardware :)
<sphalerite>
aarch64 community box has it, my chromebook doesn't
<samueldr>
sometimes useful to know beforehand
<sphalerite>
oh right
<sphalerite>
yeah
<samueldr>
and I'd wager that /dev/kvm could be missing in situations where the hardware permits it, but the right kernel drivers aren't used (though unverified statement here(
<samrose_>
so, aarch64 community box runs nixos, and is able to run qemu and kvm yes?
<sphalerite>
yes should be
<sphalerite>
samueldr: good point!
<samrose_>
on, my quest to get nixos working on the bananapi m64 I am stuck on "Starting Kernel ...." I was able to build the sunxi.bin with ARM trusted firmware. I wondered if anyone else ran across this kind of issue here?
<samueldr>
samrose_: it's *possible* that it works, but hdmi out doesn't
<samueldr>
do you have the hardware required to test with serial?
<samueldr>
(you'd also need the proper "console=" option on the kernel command line)
<samrose_>
samueldr: I had a suspicion that this is the case, because the machine appears to have network traffic on ethernet, and it appears to restart on Ctrl-Alt-Del key combo
<sphalerite>
oh, that sounds good!
<samueldr>
(on previous iterations of the mainline kernel, the ethernet port on my pine64 woud light up, but not actually work)
<samueldr>
(same CPU and similar board config AFAIK)
<samueldr>
samrose_: you could try to blindly (via a usb keyboard) type reboot[enter]
<samueldr>
you should in theory be connected as root automatically on boot
<samrose_>
I don't have hardware to test with serial, I guess by that you mean old monitor samueldr ?
<samueldr>
(it works pretty much like the installer image)
<samueldr>
no, something like the usb TTL raspberry pi thing *searching for a link*
<samueldr>
e.g. I think you linked this to us already
<samrose_>
samueldr: ah so there is some supported method from the manufacturer for using serial console to diagnose board issues
<samueldr>
on most SBCs, and it looks like on yours too
<samrose_>
cool I will look into that thank yuou
<samueldr>
it would be highly irregular NOT to have serial somewhere :)
<samueldr>
(but not unthinkable though)
<samrose_>
samueldr: I suppose this is related to this item in the nixos.wiki that reads 'If you try to use UART to log on NixOS, you might hang on the line "Starting kernel ...". To enable UART, you will need to add at the end of the line that contains loglevel4 in the file /extlinux/extlinux.conf the text"
<samrose_>
once again thank you samueldr and sphalerite
<samrose_>
I have code in a branch and will be sure to PR this
<samrose_>
(once it works! :-D)
<samrose_>
samueldr: where this link talks about editing /extlinux/extlinux.conf I would need to run my own build of sd-image-aarch64-linux.img to achieve this I take it?
<samueldr>
it's in the FAT32 partition
<samueldr>
so no need to
<samueldr>
you could even do that from most non-linux distros!
<samrose_>
ah ok
<samueldr>
non-linux OS*
<samrose_>
so I can basically mount the partition and then edit the file
<samueldr>
yes
<samrose_>
cool
<samueldr>
that extlinux.conf is like a grub.conf or the systemd-boot config files in the ESP for UEFI
<samrose_>
aha
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 252 seconds]
jtojnar has quit [Remote host closed the connection]