<thefloweringash> FWIW I’ve been using latest mainline (+ patches from arch) on my rock64 since 19.03.
<lopsided98> I'm just switched to mainline U-Boot, but I was previously using the one in nixpkgs. I will submit a PR that replaces the downstream U-Boot with mainline in nixpkgs once I finish testing my RockPro64
orivej has quit [Ping timeout: 276 seconds]
h0m1 has quit [Ping timeout: 250 seconds]
h0m1 has joined #nixos-aarch64
<lopsided98> I have blob free mainline U-Boot working on my RockPro64
<samueldr> I have some exciting and annoying news
<samueldr> got a new phone to replace my old one, like personal bought for me phone
<samueldr> (so I can actually make the addison the hybrid target)
<samueldr> (but that's not the news)
<samueldr> the new phone supports eDP out on type-c
<samueldr> and it looks like that, in android, it's done through the kernel DRM
<samueldr> so it's likely not something spooktastic made-for-android
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-aarch64
<{^_^}> #74580 (by lopsided98, 57 seconds ago, open): ubootRock64, ubootRockPro64: use upstream U-Boot
tilpner has quit [Quit: tilpner]
zupo has joined #nixos-aarch64
tilpner has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
lordcirth has joined #nixos-aarch64
lordcirth__ has quit [Ping timeout: 250 seconds]
marek has quit [Ping timeout: 240 seconds]
<flokli> lopsided98: I could give the new ubootRockPro64 a test run on my hardware, too
<flokli> WDYT about documenting where to dd what on the SSD in nixpkgs, near the expression?
<flokli> Ideally, we'd have this information in some passthru's, so some "make sdimage" function would be able to put it in the right location
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 268 seconds]
orivej has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 268 seconds]
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Read error: Connection reset by peer]
zupo has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
<lopsided98> flokli: It would be helpful if you tested it. I forgot you had a RockPro64 , or I would have CC'd you.
<lopsided98> Regarding documentation, I was planning to put it in the wiki page, but I suppose we could put it in nixpkgs as well
<flokli> lopsided98: I think it'll still change quite a bit. So nixpkgs might be better actually
orivej has joined #nixos-aarch64
<samueldr> I wonder what's the best pattern to compose derivations with "quirks"
<samueldr> here it would be OEM kernel trees
<samueldr> quirks like "this kernel has this unusual build-time bug", like not generating a file it should before a Makefile target
<samueldr> (alternatively, figuring out the Makefile fix would be better here)
<DigitalKiwi> rewrite it in redo
<samueldr> ...
<samueldr> ...
<samueldr> oops, didn't mean to repeat myself
<samueldr> make[2]: 'vmlinux' is up to date.
<samueldr> make[3]: *** No rule to make target 'vmlinux', needed by 'arch/arm64/boot/Image'. Stop.
orivej has quit [Ping timeout: 240 seconds]
<flokli> lopsided98: I try to find some hours this weekend to give it a whirl
<flokli> for now, it has mostly collected dust :-D
<flokli> But yeah, a declarative kitchen radio would indeed be very nice
<gchristensen> omg
<flokli> gchristensen: I assume you have a lot of expertise in making reproducible pies?
<gchristensen> unfortunately not :( they don't come out so reliably
<flokli> :-)
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 246 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 252 seconds]
zupo has joined #nixos-aarch64
<betaboon> I'm just trying to setup my local system to use the community aarch64 builder, but for some odd reason it is not being used. i followed https://github.com/nix-community/aarch64-build-box#configuring-your-computer-for-remote-builds.
<betaboon> gchristensen: ^ any suggestions ?
<gchristensen> what happens?
<clever> betaboon: what does nix-build print out when failing? what are the contents of /etc/nix/machines ?
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<gchristensen> oh no my new fancy rust code doesn't compileon aarch64
<gchristensen> spooky it is building the second try
zupo has joined #nixos-aarch64
<betaboon> I'm trying to build `android-device` of the mobile-nixos demo. it just runs into `Building with crossSystem?... -> we are` and then fails with the regular aarch64-cross-build failures. as if it doesnt even try
<clever> betaboon: what are the contents of /etc/nix/machines ?
<betaboon> clever: `betaboon@aarch64.nixos.community aarch64-linux /root/.ssh/aarch64-build-box.id_ed25519.pub 64 1 big-parallel`
<clever> betaboon: and the exact error from nix-build is?
<clever> error: attribute 'targetPlatform' missing, at /home/betaboon/src/nix/nixpkgs/pkgs/development/tools/build-managers/meson/default.nix:98:17
<clever> betaboon: the error has nothing to do with build machines
<betaboon> clever: but that is the error it fails on due to trying to crossbuild
<betaboon> clever: exactly
<clever> 98 system = '${targetPackages.stdenv.targetPlatform.parsed.kernel.name}'
<clever> betaboon: i think your nixpkgs rev isnt compatible
t184256 has left #nixos-aarch64 ["Error from remote client"]
<betaboon> clever: that's just due toe crosscompiling
<clever> betaboon: it hasnt even reached the phase where it tries to connect to the community box
t184256 has joined #nixos-aarch64
<betaboon> clever: thats current master
<betaboon> on nixpkgs-unstable it fails in the same way
<clever> betaboon: are you on a branch of mobile-nixos?
<betaboon> same for nixos-unstable. and as far as i understood the documentation of mobile-nixos it is supposed to be build against nixos-unstable for now
<betaboon> clever: I'm on mobile-nixos master
<clever> - The option definition `services.xserver.displayManager.slim' in `<unknown-file>' no longer has any effect; please remove it.
<clever> for me, it fails even harder
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<betaboon> clever: yeah. slim is depricated on master since two weeks. I'm using this change to lightdm that is on samueldr wip-branch: https://github.com/samueldr-wip/mobile-nixos-wip/commit/96cbc5cd8d50a19d2f2935fb019cbd3a8612bb5f
<clever> 2019-11-29 18:35:56 < betaboon> clever: I'm on mobile-nixos master
<betaboon> clever: ehm. yeah sorry that was unclear. master + that commit . sorry
<clever> betaboon: looks like youll need samueldr to help, it seems to fail in 3 different ways, on every nixpkgs rev i test
<betaboon> yeah. seems like it. i was under the impression that the meson error was due to the evaluation being run without the remote-builder. guess that was wrong
<clever> it would clearly say i am x86, but need aarch64
<betaboon> gonna ask samueldr tomorrow. :)
<betaboon> thanks for trying tho ;)
ryantrinkle has quit [Ping timeout: 240 seconds]