<Ashy>
yeah that didn't seem to work for me, maybe the lists were being merged and zfs was being re-included
<lopsided98>
Ashy: I keep the rock64-4.19.y LTS branch up-to-date (because I use it on the Rock64 w/ ZFS), but I don't know how well it works on the RockPro64
<lopsided98>
I normally build SD images without including base.nix and installation-device.nix and just use the actual config for the particular device
<lopsided98>
that way it boots already configured for its use-case
<lopsided98>
in fact, some of my devices (RPi 0) never get rebuilt, they just new images every few months
<lopsided98>
*get new images
<Ashy>
ah ok
<Ashy>
samueldr: ah your cross-system repo looks nice, i might add a config for the rockpro64 there using lopsided98's kernels and then add a note to the wiki page linking to that
<samueldr>
current nixos-unstable doesn't build, but a fix is in staging
<samueldr>
I try and cross compile the installer images from time to time to check against regressions
<samueldr>
the main use of those I think would be to bootstrap yourself on an unsupported architecture, maybe a board
<samueldr>
in a more trustful manner, as long as cache.nixos.org and your nix/nixpkgs are deemed trustworthy :)
<lopsided98>
samueldr: are the cross-compiled images a lot bigger than the native ones?
<Ashy>
yeah using kernel forks isnt really safe, but i think it'd be nice to have a simple way to build images for boards that aren't working with upstream uboot/kernel just yet
<samueldr>
lopsided98: not sure
<samueldr>
2.4G for the armv6l image
<samueldr>
though a big inconvenience is that it's not compatible with native builds
<samueldr>
so, the first rebuild will kil
<samueldr>
kill*
<lopsided98>
I want to get enough packages cross-compiling that I can use cross-compiling for more than just bootstrapping
<samueldr>
I would like that too
<lopsided98>
then my remote x86_64 builders would do all the work
<samueldr>
right now up to X11 it's a mixed bag
<samueldr>
up to and excluding*
<samueldr>
but it's not that bad
<lopsided98>
One of the issues with cross right now is that there are a ton of unintended native references
<lopsided98>
which is why I was asking about image size
<Ashy>
oh yeah i had to disable x11 on the rockpro64 config to a full install to work, xf86-video-vmware was failing to build
<samueldr>
it looks like it's for about 2~400MiB
<Ashy>
sway worked though
<samueldr>
unrelated, that's something else to fix, X11 will work with a native build on aarch64
<samueldr>
it's because of the defaults in the option
<samueldr>
I really need to remember about that when I have time to write a fix
<samueldr>
right now UGH, trying to finalize the work on that new device bringup
<samueldr>
I really should be investing time into getting visual output on the device's screen ASAP, I think it will pay off for devices where there is no logging
orivej has joined #nixos-aarch64
ris has quit [Ping timeout: 246 seconds]
vika_nezrimaya has quit [Remote host closed the connection]
<samueldr>
amazing, got that new device working, though X11 with fbdev doesn't work yet, but ssh into stage-2 works to inspect
ryantrinkle has quit [Ping timeout: 245 seconds]
<Ashy>
nice, which device?
<samueldr>
remi note 7
<samueldr>
redmi*
<Ashy>
ah yeap sweet
<Ashy>
i'm pretty keen to pick up a pinephone when they launch finally
<samueldr>
and got X11 working (a bit earlier)
<samueldr>
through a gnarly hack, but I think it should be fine to enable as a "quirk"
<samueldr>
or better yet, figure out a solution
<samueldr>
other than the R and B color channels being switched, which I need to write a patch as usual, it seems to be mostly at parity with the z00t :D
<samueldr>
now I need to clean the mess up
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
<Ashy>
hmm interesting, the nixos 19.03 sd-image doesnt boot with lopsided98's 4.20.y kernel whereas the 20.03git does
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]