#nixos-aarch64 on 2019-06-12

2018-09-23 16:56 gchristensen changed the topic of #nixos-aarch64 to: Get access to the NixOS Community aarch64 build box: https://github.com/nix-community/aarch64-build-box ... todo: https://hydra.nixos.org/jobset/nixpkgs/trunk#tabs-jobs build box status: https://monitoring.nix.ci/d/hkRCcV0mk/instance-metrics?var-instance=aarch64.nixos.community&orgId=1

00:32 <samueldr> ToxicFrog: you said vc4 was enough for early modesetting, was this with kernel 5.1?

00:32 <ToxicFrog> samueldr: it was with kernel 4.19

00:33 <ToxicFrog> I haven't tried it with 5.x yet and am not fiddling with it tonight

00:33 <ToxicFrog> But I will report back once I do

00:34 <samueldr> right, it might not be enough with 5.1

00:34 <samueldr> (testing my changes before doing the PR)

00:34 * ToxicFrog nods

00:34 <ToxicFrog> I'll give it a run tomorrow if I can and let you know how it goes

01:21 <samueldr> weird, doesn't work either for 4.19

01:41 jackdk has joined #nixos-aarch64

03:34 orivej has quit [Ping timeout: 245 seconds]

03:49 clever has quit [Ping timeout: 248 seconds]

03:50 jackdk has quit [Ping timeout: 248 seconds]

03:50 {^_^} has quit [Ping timeout: 252 seconds]

03:51 jackdk has joined #nixos-aarch64

03:56 clever has joined #nixos-aarch64

03:56 clever has quit [Changing host]

04:00 orivej has joined #nixos-aarch64

04:03 {^_^} has joined #nixos-aarch64

04:12 <samueldr> though, with the three modules I tracked down, it works, tested with sd card and can see the resizing happen before modules end up loading

04:12 <samueldr> "vc4" "bcm2835_dma" "i2c_bcm2835"

04:21 orivej has quit [Ping timeout: 245 seconds]

04:56 orivej has joined #nixos-aarch64

05:18 orivej has quit [Ping timeout: 264 seconds]

05:33 orivej has joined #nixos-aarch64

05:44 orivej has quit [Ping timeout: 248 seconds]

06:11 * DigitalKiwi can't get an f2fs raspberry pi 3 to boot :(

06:11 <DigitalKiwi> i know it's possible my raspbian does it

06:11 <DigitalKiwi> but i can't figure out how to make nixos do it :(

07:00 v0|d has joined #nixos-aarch64

07:06 kvaster_ has joined #nixos-aarch64

07:35 kvaster_ has quit [Ping timeout: 246 seconds]

07:42 kvaster_ has joined #nixos-aarch64

07:49 zupo has joined #nixos-aarch64

07:52 kvaster_ has quit [Ping timeout: 245 seconds]

07:57 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

08:02 Thra11 has quit [Ping timeout: 245 seconds]

08:06 ryantrinkle has quit [Ping timeout: 268 seconds]

08:16 zupo has joined #nixos-aarch64

08:30 zupo has quit [Read error: Connection reset by peer]

08:32 zupo has joined #nixos-aarch64

08:38 kvaster_ has joined #nixos-aarch64

08:44 kvaster_ has quit [Ping timeout: 248 seconds]

08:54 kvaster_ has joined #nixos-aarch64

08:58 zupo has quit [Read error: Connection reset by peer]

09:11 zupo has joined #nixos-aarch64

09:17 kvaster_ has quit [Quit: Konversation terminated!]

09:17 kvaster_ has joined #nixos-aarch64

09:46 Acou_Bass has quit [Ping timeout: 258 seconds]

10:09 Acou_Bass has joined #nixos-aarch64

10:15 Acou_Bass has quit [Quit: byeeeeeeeeeeeeeee]

10:16 Acou_Bass has joined #nixos-aarch64

10:19 mthst has quit [Ping timeout: 258 seconds]

10:39 zupo_ has joined #nixos-aarch64

10:41 zupo has quit [Ping timeout: 245 seconds]

10:58 mthst has joined #nixos-aarch64

11:22 v0|d has quit [Ping timeout: 248 seconds]

11:28 zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

11:35 orivej has joined #nixos-aarch64

11:57 zupo has joined #nixos-aarch64

12:17 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

12:23 orivej has quit [Ping timeout: 272 seconds]

13:20 orivej has joined #nixos-aarch64

14:11 kvaster_ has quit [Ping timeout: 246 seconds]

14:12 <ToxicFrog> F2FS?

14:13 <samueldr> Flash-Friendly File System

14:15 <DigitalKiwi> they could have named it three effs

14:15 <DigitalKiwi> or f3s

14:19 kvaster_ has joined #nixos-aarch64

14:31 mthst has quit [Quit: the bouncer died]

14:34 mthst has joined #nixos-aarch64

14:38 orivej has quit [Ping timeout: 248 seconds]

15:43 mthst has quit [Ping timeout: 258 seconds]

15:44 mthst has joined #nixos-aarch64

16:29 Thra11 has joined #nixos-aarch64

16:36 mthst- has joined #nixos-aarch64

16:37 mthst has quit [Ping timeout: 250 seconds]

16:38 Thra11 has quit [Ping timeout: 268 seconds]

16:45 <DigitalKiwi> samueldr: is there anything special i should have to do to nixos-install for a raspberry pi

16:45 <samueldr> I don't think so, other than ensuring you set up u-boot right

16:46 <samueldr> (unless you're not using u-boot at all, then ensuring the kernel and config.txt are set up right)

16:51 <DigitalKiwi> how do you set up u-boot right is there a wiki

16:51 <DigitalKiwi> that's probably what i'm not doing

16:52 Thra11 has joined #nixos-aarch64

16:53 <samueldr> there's not really any information right now since it's kinda expected that one would use the sd imag

16:53 <samueldr> sd image*

16:54 <samueldr> an easy shortcut is copying the FAT32 partition content of sd_image to a new FAT32 partition

16:54 <samueldr> I'm not sure if u-boot can read F2FS, if it cannot you will need to have the FAT32 partition big enough to fit a couple generations

16:54 <samueldr> 120MiB (the current default) is a bit small

16:55 <DigitalKiwi> does raspbian use u-boot

16:55 <samueldr> no

16:55 <DigitalKiwi> oh

16:55 <samueldr> if u-boot can read F2FS then you can just put u-boot and the required files and let it read the generations from the partition

16:55 <samueldr> raspbian doesn't have "generations" either, so the kernel and initrd are on the FAT32 partition I would bet

16:56 <samueldr> the fact NixOS has generations makes NixOS peculiar compared to the usual arm board setups

16:56 <DigitalKiwi> i'm suspecting it can't read f2fs might be the problem

16:58 <DigitalKiwi> how big are generations is it just the kernel or

16:58 <samueldr> yeah, looks like u-boot doesn't support f2fs

16:58 <samueldr> kernel and initrd

16:59 <samueldr> it will not duplicated initrd and kernels if they are the same store path

16:59 <DigitalKiwi> i have my vfat 1GB

16:59 <samueldr> but if you're e.g. working on improving the initrd it will take as much space as n * size

17:00 <DigitalKiwi> i only have 32GB micro sd cards so i GC quite often

17:01 <samueldr> DigitalKiwi: https://github.com/NixOS/nixpkgs/blob/037dd9b7969f8cfb88e2582bd8830b5cc0de1b5f/nixos/modules/installer/cd-dvd/sd-image-aarch64.nix#L30-L51

17:01 <samueldr> this is how the image builds the FAT32 partition

17:02 <samueldr> there's also these options: https://nixos.org/nixos/options.html#raspberr

17:02 <samueldr> which looks like it will update the files as needed https://github.com/NixOS/nixpkgs/blob/release-19.03/nixos/modules/system/boot/loader/raspberrypi/uboot-builder.sh

17:03 <samueldr> so you might be able to just create the FS and mount it without needing to know how to set it up

18:01 mthst- has quit [Ping timeout: 252 seconds]

18:01 mthst has joined #nixos-aarch64

18:21 zupo has joined #nixos-aarch64

18:24 mthst has quit [Ping timeout: 258 seconds]

18:36 * DigitalKiwi can't figure it out

18:37 <DigitalKiwi> something says unknown filesystem i don't know if it's u-boot or what

18:38 <DigitalKiwi> and it's a pain to test because it's normally headless and i don't have an hdmi screen handy

18:40 mthst has joined #nixos-aarch64

18:45 mthst has quit [Ping timeout: 258 seconds]

18:59 mthst has joined #nixos-aarch64

18:59 orivej has joined #nixos-aarch64

19:11 mthst has quit [Ping timeout: 258 seconds]

19:54 <DigitalKiwi> samueldr: what does raspbian use instead of u-boot btw?

19:54 <samueldr> their firmware handles loading *something*, which can be a kernel directly

19:55 <samueldr> in our case *something* is u-boot

19:55 <samueldr> so raspbian is configured to load the kernel

19:55 <samueldr> it's not like they have to handle useful thing like generations and boot options

19:55 <samueldr> boot options are handled in config.txt

20:10 <gchristensen> samueldr: do you ever do the WoA calls?

20:11 <samueldr> no, happens while I should be concentrating/working on $client stuff

20:11 <samueldr> (sometimes unsuccessfully)

20:11 <gchristensen> aye :)

20:11 <samueldr> though I check back on what's shared

20:11 <gchristensen> often interesting things there.

20:12 <samueldr> funny how the Khadas VIM 3 lists eMMC being on-board as an advantage vs. an expandable socket

20:15 <samueldr> and another reason is zoom, having to install that to jump in to listen is relatively high friction

20:26 Thra11 has quit [Ping timeout: 246 seconds]

20:43 Thra11 has joined #nixos-aarch64

21:12 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

21:18 <duncan> Isn't eMMC typically faster than your average SD card at least/

21:18 <samueldr> in my experience it is

21:18 <samueldr> well, the chips could have been

21:18 <samueldr> but what they compared to is eMMC too

21:18 <samueldr> but on a carrier board

21:18 <samueldr> so you can switch the eMMC module

21:19 <samueldr> I really like that concept, that made it possible to make my pinebook a 64GiB pinebook by using the eMMC I had for the pine64

21:27 Thra11 has quit [Ping timeout: 248 seconds]

22:29 v0|d has joined #nixos-aarch64

22:36 {^_^} has quit [Remote host closed the connection]

22:36 {^_^} has joined #nixos-aarch64