justanotheruser has quit [Ping timeout: 260 seconds]
cole-h has joined #nixos-aarch64
hmpffff has joined #nixos-aarch64
alp has joined #nixos-aarch64
orivej has joined #nixos-aarch64
lovesegfault has quit [Ping timeout: 260 seconds]
lovesegfault has joined #nixos-aarch64
alpernebbi has joined #nixos-aarch64
zupo has joined #nixos-aarch64
cole-h has quit [Ping timeout: 240 seconds]
<sphalerite>
clever: is not-os still great for building 32-bit pi images? I have a pi 2 that I want to use, with a fairly minimal use case (play back sound coming in from the network)
zupo has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
edk_ is now known as deadk
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ib07 has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
<clever>
sphalerite: last i checked, it can still boot, but only because ive pinned it to an ancient nixpkgs rev
<sphalerite>
clever: hm ok, so no :D
<clever>
i forget why it had problems, was likely during build
orivej has quit [Ping timeout: 265 seconds]
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
monk has left #nixos-aarch64 ["Error from remote client"]
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
monk has joined #nixos-aarch64
hmpffff has quit [Ping timeout: 272 seconds]
hmpffff has joined #nixos-aarch64
njha has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
zarel_ has quit [Ping timeout: 265 seconds]
zarel has joined #nixos-aarch64
zupo has joined #nixos-aarch64
cptchaos83 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<patagonicus>
On that note, is there any good way of finding a revision of nixpkgs that builds for armv7? I was considering bisecting between currently-running-version and master before, but that also doesn't sound great (as there can be different problems in the range and you also wouldn't necessarily end up with the newest non-breaking version). The
<patagonicus>
alternative would be starting at master and going back one commit every time it fails, but that means at least rebuilding one package for each revision.
<patagonicus>
Currently for master it fails for coreutils and rebuilding that every time sounds a bit cumbersome.
<patagonicus>
I'm currently thinking of using nix-bisect to help a bit, but that also not quite what I want (it'll tell me when that specific package broke, but I don't really care about that).
Darkmatter66 has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 256 seconds]
justanotheruser has joined #nixos-aarch64
alp has joined #nixos-aarch64
<thefloweringash>
I’d suggest looking at my hydra, but I haven’t found time to tend to it recently and it seems like something broke
<patagonicus>
I have two tests failing in coreutils, but I haven't investigated why/what commit made them fail.
<patagonicus>
Ah. It breaks after 2020-10-07 and the latest build on your hydra seems to be 2020-09-28. :)
<patagonicus>
Maybe I should just finally set up my own hydra, was thinking about it. Doesn't look that complicated.
cole-h has joined #nixos-aarch64
<thefloweringash>
I do only build the channels. I figured it would mean the packages had passed some level of checking. The build on my hydra should be the latest from nixpkgs-unstable, which seems blocked at the moment.
<thefloweringash>
I’ll need to try and sort out whatever my hydra is doing wrong. Maybe I need to give up and just give it an s3 bucket to fill up.
<patagonicus>
I just went with master since the channels aren't really checked for armv7 as far as I understand, but maybe it makes more sense to go with unstable. Not sure.
<thefloweringash>
The channels aren’t checked for armv7, but I figure if the commit wasn’t good enough for the main architectures I don’t want to try building it for something more obscure.
<sphalerite>
danielrf[m]: I'm trying to build robotnix for my new pixel 4a (sunfish), but Webviewchromium is failing with /build/.attr-0: line 9: /nix/store/p4m87k5mbpjfxnay9v0m98gggba1lsgi-android-sdk-env/share/android-sdk/build-tools/30.0.2/aapt2: No such file or directory
<sphalerite>
any ideas?
<danielrf[m]>
maybe I broke something :( I was working on this recently
<danielrf[m]>
which derivation is failing?
<danielrf[m]>
Is the name of the derivation "prebuilt_Webviewchromium" ?
<clever>
samueldr: a recent rpi github issue, pointed me towards an initrd based "distro", that used the MSD gadget to expose the rootdisk, for reflashing
<clever>
samueldr: does that sound like something useful for mobile-nixos, as an alternative to adb?
<sphalerite>
danielrf[m]: argh, yes, I missed that part of the name
<danielrf[m]>
So, it seems to be working on my machine. Does /nix/store/p4m87k5mbpjfxnay9v0m98gggba1lsgi-android-sdk-env/share/android-sdk/build-tools/30.0.2/aapt2 somehow not actually exist on your machine?
<danielrf[m]>
For reference, this particular derivation can be built using:
<samueldr>
clever: it's already been done
<danielrf[m]>
nix-build --arg configuration '{device="sunfish"; flavor="vanilla";}' -A source.dirs."robotnix/prebuilt/Webviewchromium".src
<danielrf[m]>
And I think it's failing for you at line 175 of modules/apps/prebuilt.nix
<danielrf[m]>
but I don't believe there should be IFD anywhere in that chain
<clever>
libbb/time.c:260:14: error: '__NR_clock_gettime' undeclared (first use in this function); did you mean 'clock_gettime'? 260 | if (syscall(__NR_clock_gettime, CLOCK_MONOTONIC, ts))
<clever>
samueldr: pkgsCross.armv7l-hf-multiplatform.pkgsStatic.busybox fails to build, have you seen anything like that before?
<samueldr>
nope
<clever>
2 , enableStatic ? false
<samueldr>
been a while since I dropped static stuff
<sphalerite>
clever: that feels horribly familiar to me
<clever>
though .override looks better
<samueldr>
(in the end I saved space by not going with static binaries)
<clever>
yeah, once you have multiple binaries, dynamic starts to save space
<sphalerite>
clever: yep, I got it while trying to cross-build busybox for mips. Not sure if that's at all relevant for you.
<clever>
but ive just got only busybox at the moment
<clever>
sphalerite: i am cross-compiling to arm32 with static
<sphalerite>
clever: I never found a working solution, so if you work out what it takes I'd be very glad to hear it
<sphalerite>
I tried sed -i $'13a#define __NR_clock_gettime 113\n' include/libbb.h
<sphalerite>
but that then failed at runtime
<sphalerite>
danielrf[m]: hrm, I'm building from the repo now rather than using the exact example command (with s/crosshatch/sunfish/) and it seems to be Working™
<clever>
the real fun part though, is that i'm pushing this initrd over usb, via the usb-device boot channel
<sphalerite>
Where is this heading? I can't really tell but it does sound interesting
<clever>
so i dont have to flash the device to be able to flash the device
<clever>
sphalerite: the official msd/start4.elf firmware, only gets ~10mbyte/sec in MSD mode, while linux MSD can do 32mb/sec, and direct SD is 43mb/sec
<samueldr>
sphalerite: which part? webusb or gadget?
<sphalerite>
I think I'm missing some context
<sphalerite>
what's the big picture here?
<sphalerite>
Or even the medium picture
<clever>
sphalerite: my rpi4 is configured to boot in usb-device mode, then i use webusb, to push rpi firmware files over to it
<clever>
the star4.elf firmware then continues usb-device mode, and accepts a kernel.img + initrd file, and boots it
<clever>
all pushed from the browser, with no need to compile special apps
<clever>
then linux boots, goes into MSD mode, and the pi4 shows up as a normal usb drive
<clever>
samueldr: oh, that gives me a crazy idea, a webusb based adb/fastboot, to forcibly install mobile-nixos from a browser
<samueldr>
clever: we can probably already use what google made
<samueldr>
it's *already* possible to fastboot install stuff from your browser
<sphalerite>
first robotnix build is flashing now :D
<clever>
and for extra fun points, i confirmed that webusb works from chrome on android
<samueldr>
sphalerite: at what rate?
<samueldr>
60hz? 30hz?
<clever>
samueldr: so you could pull up a magic webpage on one phone, then use it to flash a second phone!
<samueldr>
yeah
<sphalerite>
do I hear mobile-nixos-as-a-virus?
<clever>
sphalerite: :D
<samueldr>
that would be kind of neat
<sphalerite>
danielrf[m]: it booooteeeeeed!! I'm so excited :D :D :D
<samueldr>
danielrf[m]++ sphalerite++
<{^_^}>
danielrf[m]'s karma got decreased to 3
<{^_^}>
Wait no, it got *increased* to 5
<{^_^}>
sphalerite's karma got increased to 113
justan0theruser has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 260 seconds]
<danielrf[m]>
sphalerite: Nice! It's it great that nix makes builds just work! :)
<sphalerite>
unfortunately it's the very sparse plain-vanilla build which isn't _really_ what I wanted. But hey, it built in 2 hours, it's survivable
<samueldr>
I remember how with sony-pioneer on LineageOS, on that sketchy branch I got instant success with robotnix, while I didn't with the official toolchain
<danielrf[m]>
:D
<sphalerite>
danielrf[m]: hm, if I try to use the example configuration, it complains about an auditor.x509.pem file not existing, even though I've disabled signing… is there something else I need to disable?
<danielrf[m]>
yeah, I'd disable the auditor/attestation thing entirely for now. It requires the hash of the signing key to be built into the auditor apk
<danielrf[m]>
It'd also be better to enable just the things you'd like instead of using example.nix directly.
<danielrf[m]>
Things like the `apps.fdroid.additionalRepos` in `example.nix` are really just for my setup
<sphalerite>
hm ok
v0|d has joined #nixos-aarch64
<clever>
samueldr: something that would help greatly, is if extraUtils = pkgs.runCommandCC "extra-utils" was refactored out of nixos, and was reusable