<patagonicus>
I'm trying again at the commit hash mentioned again. Is this a known problem? Should I open an issue againts nixpkgs? Should I bother bisecting to find where it breaks (if it works with the older commit)?
zupo has joined #nixos-aarch64
<patagonicus>
*commit hash mentioned above. Maybe I shouldn't nix right after waking up. :D
<patagonicus>
Oh. Reading it again I might have patched the wrong package (systemd vs. systemd-boot). Trying that should be faster as most of the packages should be already built.
<patagonicus>
Nope, there's no systemd-boot package, I guess it's part of systemd.
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cole-h has quit [Quit: Goodbye]
irminsul has quit [Quit: Leaving]
alp_ has joined #nixos-aarch64
<patagonicus>
"-r--r--r-- 1 root root 800M Jan 1 1970 result/sd-image/nixos-sd-image-20.09pre-git-armv7l-linux.img.bz2" Woo! Now to see if it actually boots.
<patagonicus>
That … doesn't look great. :/ uboot finds /boot/extlinux/extlinux.conf, but then says "SCRIPT FAILED: continuing" and tries to PXE boot.
<patagonicus>
Weird, must have been a bad flash. After putting it into my laptop again I couldn't mount the root fs, but writing the same image again it's now booted.
<bigvalen[m]>
Yeah, I re-wrote the flash a few times. sometimes it worked, sometimes...no.
<patagonicus>
I've never had that problem with MicroSD cards before.
<patagonicus>
Anyway, happy with NixOS because it was super easy to add htop and tmux and also disable the image compression. :)
alp_ has quit [Ping timeout: 272 seconds]
alp_ has joined #nixos-aarch64
zupo has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 240 seconds]
PirBoazo has quit [Quit: Bonne Fin de Journée]
Thra11 has joined #nixos-aarch64
alp_ has quit [Ping timeout: 272 seconds]
Thra11 has quit [Ping timeout: 240 seconds]
<patagonicus>
samueldr: Not that I mind much, but why is Nix rebuilding everything on the first nixos-rebuild? Is it because the derivations are different due to having the cross compiler set?
<srk>
exactly
orivej has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
la-s has left #nixos-aarch64 ["User left"]
Thra11 has joined #nixos-aarch64
adisbladis has quit [Remote host closed the connection]
adisbladi has joined #nixos-aarch64
<patagonicus>
Hmmhmm. So building the image on a native armv7 machine shouldn't have that problem, right? Not that I'm really thinking about that on my RPi, but (if I can get everything to work) I'm thinking of having a 3 machine "cluster" of Odroid HC2 and could just set them up to build an installer once a month or so just in case I need it.
<patagonicus>
(Or in case someone else wants to rum NixOS on armv7 and doesn't want to spend the time building the image)
<patagonicus>
Thinking about it, once I've rebuilt the system for the RPi, building the SD image shouldn't take that much longer, actually.
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<srk>
correct. ideally we would get same outputs from cross toolchain as native ones and switch to intensional store that cares about hashes of the outputs not the inputs but that will take some time to get there :)
<patagonicus>
:)
<srk>
problem with building on rpi is usually RAM and I/O, small cluster or even a single solid armv7 board with 8GB ram and SATA would do
<patagonicus>
Yeah, it took me a bit when getting started with Nix to realize that it stores by hash of the input, not output, but it makes sense until we can get everything to built reproducible (which would be amazing).
<patagonicus>
Well, the HC2 only has 2GB of RAM, but I'd have three of them with an HDD each. Main goal is storage for backups, so I'm going for high capacity rather than storage speed.
<srk>
(I was using imx6 in Novena laptop for building things natively until recently when I've tried cross compiling and it was near flawless and faster)
<srk>
like most things are fine building with 2GB or even less but there are few that need more, like llvm, firefox.. :)
<ar>
lx2k is reasonably fast for compiling things, but that's a bit pricy
<srk>
depends heavily on what you actually need
<srk>
ar: yup but aarch64 and needs a vm for armv7l
<ar>
oh, armv7l. haven't needed that
<patagonicus>
Yeah, I was mostly thinking of providing the base installer. Probably also one with a couple of extra packages (I really like having tmux and htop, for example). If people really want to run firefox on armv7 they can build it themselves. :P
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
<srk>
hopefully :D I haven't even tried yet, my guess is it would take several days natively since full kernel build is roughly 8 hours. cross could work provided are deps are building fine
<srk>
^all
orivej_ has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
<patagonicus>
Hey, I used to try running Gentoo on RPis (RPi1 even), I'm pretty sure Nix is going to be less pain and at least won't take longer. :D
<thefloweringash>
building firefox on armv7 is trickier than it seems, since the build doesn't fit in the address space without careful tweaking
<Ke>
thefloweringash: how's upstream support on that SoC right now?
<Ke>
is it honeycomb or what?
<thefloweringash>
shamefully I'm still running a vendor kernel, but it was officially supported as of 5.6 without some peripherals
<patagonicus>
OH, right, I remember firefox having to switch to building 32bit Windows binaries on 64bit Windows because it needed a bigger address space.
<thefloweringash>
yeah, honeycomb
<Ke>
how about boot fw?
<Ke>
I guess it needs the raminit blob, but has the rest been upstreamed?
<thefloweringash>
also still using vendor boot fw
orivej has quit [Ping timeout: 265 seconds]
orivej_ has joined #nixos-aarch64
<thefloweringash>
did nixpkgs stop backporting the latest kernels to current stable? looks like linux_latest is still 5.6 on 20.03
vika_nezrimaya has joined #nixos-aarch64
<thefloweringash>
for making armv7l viable in the longer term there's an effort to run a similar build vm on the hydra builders. the current issue preventing us from doing so is, as I understand it, a limitation of the deployment mechanism for the builders
<thefloweringash>
the netboot a large initrd, and putting two systems in there pushes it over some mysterious limit
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
alp_ is now known as alp
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
adisbladi is now known as adisbladis
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<bigvalen[m]>
Huh. The configuration.nix used by the sdcard isn't in /etc/nixos, like I expected.
orivej_ has joined #nixos-aarch64
<bigvalen[m]>
As samueldr suggested, it would need a rebuild of a lot of packages from source anyway, maybe that's not a big deal.
orivej has quit [Ping timeout: 256 seconds]
<patagonicus>
bigvalen[m]: There's a setting that's set somewhere explicitly to NOT copy the config. I'm currently trying with a mix of what's recommendend on the Nixos on ARM wiki page, what's set by the cross-system repo and some stuff I want installed. But it's going to take a while.
<patagonicus>
https://pastebin.com/PPTMJsTr that's what I'm going with. I can report back if that works or not. Currently building GCC, that's gonna take a while. :)
orivej has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 260 seconds]
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Read error: Connection reset by peer]
AmandaC_ has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
AmandaC has quit [Ping timeout: 256 seconds]
evils_ has joined #nixos-aarch64
evils has quit [Ping timeout: 258 seconds]
orivej_ has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
alp has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 260 seconds]
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 265 seconds]
Thra11 has joined #nixos-aarch64
evils_ is now known as evils
<patagonicus>
I should have put the prometheus node exporter on the image before I started rebuilding everything. Then I'd get some nice graphs out of it.
<{^_^}>
patchelf#216 (by delroth, 3 days ago, merged): Improve the default section alignment choice (> 4K page size compat)
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Cadey>
samueldr: is it possible to rebuild the aarch64 install image so that it has a bigger /boot partition for raspi4? 128 MB is getting too small. I'd like at least 512 MB (I have a 128 GB card).
<srk>
you can make it larger by changing sdImage.firmwareSize
<patagonicus>
Cadey: if you already have a running system you can also change it, but it's going to a bit cumbersome. If you haven't customized it much yet, rebuilding the image is going to be faster.
PirBoazo has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
quinn has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
FRidh has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 246 seconds]
alp has quit [Ping timeout: 272 seconds]
jwaksbaum[m] has joined #nixos-aarch64
<samueldr>
Cadey: it is possible
<samueldr>
oops, there are replies already
vika_nezrimaya has quit [Ping timeout: 264 seconds]
<samueldr>
bigvalen[m], patagonicus: that setting wouldn't actually copy the same config, so it's not even useful in a sense where `nixos-rebuild switch` would not be a no-op, which brings in a false sense of "everything will be working"
<bigvalen[m]>
While I noticed that, empirically.... what is the actual reason ? Should it not request the same derivations again ?
<samueldr>
there is no way to know all of the inputs to a configuration file to write them out IIRC
<samueldr>
or something along the way
<samueldr>
and if we simply add imports = [ <nixpkgs/path/to/profile/sd-image.nix> ] # with the right path, it ends up confusing for end-users
<samueldr>
as this will force the nixos user, and the installation profile
<samueldr>
the solution is to use nixos-generate-config
<bigvalen[m]>
aaaah.
orivej has quit [Ping timeout: 260 seconds]
orivej_ has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
bennofs_ has joined #nixos-aarch64
bennofs has quit [Ping timeout: 240 seconds]
orivej_ has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
FRidh has quit [Ping timeout: 258 seconds]
FRidh has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
orivej has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 264 seconds]
atopuzov[m] has quit [Quit: authenticating]
atopuzov[m] has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
FRidh has quit [Ping timeout: 246 seconds]
FRidh has joined #nixos-aarch64
FRidh has quit [Client Quit]
orivej_ has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
<samueldr>
got a reply from the dev working on eDP on the PBP; couldn't reproduce still, but it looks like it will be soon enough™ on the u-boot mailing lists
<jwaksbaum[m]>
"samueldr" (https://matrix.to/#/@freenode_samueldr:matrix.org): sorry if I missed something, but what's the status of that? The pine people told me no one has uboot display working, is that getting worked on?
<samueldr>
it's being worked on
<samueldr>
by people external to pine and even their community AFAIUI
<samueldr>
everything I know is public knowledge, I know nothing more