pbb has quit [Quit: No Ping reply in 180 seconds.]
pbb has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
vika_nezrimaya has quit [Ping timeout: 258 seconds]
alp has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
nschoe has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
<loyon>
I tried to play with nixos on my raspberry pi 4, using an image someone did build, but everytime it starts it is always in "installer mode" sort to say.. I am wondering if it is th expecetd behavior or an issue with that image I am using?
<clever>
loyon: you need to create a configuration.nix yourself, and fill in a number of missing bits
<loyon>
clever: thanks that make sense. I have seen some `sdcard` aarch64 build on hydra (can't find them again sadly...), how does it relate to this? I mean I did see the procedure to create an image from scratch, but I'm wondering what is the usage of those hydra sdcard image.
<clever>
loyon: that is a pre-made sd image, with nixos fully installed, but configuration.nix is missing
alp has joined #nixos-aarch64
<clever>
2020-01-22 13:53:12< clever> Tenkawa: `nix-build '<nixpkgs/nixos/release.nix>' -A sd_image_raspberrypi4.aarch64-linux` for an rpi4 i believe
<clever>
2019-12-16 20:04:10< clever> nix-build '<nixpkgs/nixos/release.nix>' -A sd_image.aarch64-linux -Q
<fps>
then on the other hand this is an often reported bug [a problem with the bootloader installation not seeing the new system generation]
<clever>
loyon: these job names in hydra (which you can just build locally) contain the sd images for 64bit, rpi3 or rpi4
<loyon>
clever: ok that's pretty clever (no pun intended), could you give me direction where to find those images on hydra? can't find a link from the wiki (there is one to hydra homepage) or results, I'm feeling dumb but I can't find them again by browsing on hydra :-/
<fps>
there's an issue in the nixpkgs which has a fix for building the image in such a way that the new system generation gets booted
<loyon>
fps: that must be it, I think the image which I am using does not include recent fixes
<clever>
loyon: just paste sd_image into the search bar in hydra
<loyon>
clever: awesome, thanks a lot!
<loyon>
fps: yep I've seen that PR, now everything makes sense
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
Darkmatter66 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 240 seconds]
<bdju>
is there a recommended piece of hardware for running nixos-aarch64 on? how is the rockpro64?
<lopsided98>
bdju: the Raspberry Pi 3 has the best support
<bdju>
Ah, okay. I was hoping for something a bit newer, but that's good to know.
<clever>
bdju: the rpi4 also works, but i'm not sure what the rough edges are yet
<samueldr>
oem kernel tree, rather than mainline is the first one
<lopsided98>
you certainly can run it on other devices, but its just not as well supported
<samueldr>
different bootloader setup than the expected one is another
<samueldr>
the best supported platforms are those that are well supported on the defconfig of the mainline kernel
<samueldr>
any of those should work
<samueldr>
some assembly (the action, not the language) may be required for the bootloader of some platforms
<lopsided98>
I and others run NixOS on the RockPro64 but you have to manually install the bootloader and you might have to use a downstream kernel for full hardware support
<clever>
[ 2.164400] gpiomem-bcm2835 20200000.gpiomem: base mapped 20200000 to 0