#nixos-aarch64 on 2020-11-08

2019-09-27 17:31 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://status.nixos.org/grafana/d/5LANB9pZk/per-instance-metrics?orgId=1&refresh=30s&var-instance=147.75.77.190

00:08 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

00:10 zupo has joined #nixos-aarch64

00:37 zupo has quit [Ping timeout: 260 seconds]

00:46 zupo has joined #nixos-aarch64

00:57 zupo has quit [Ping timeout: 256 seconds]

00:59 zupo has joined #nixos-aarch64

01:08 zupo has quit [Ping timeout: 240 seconds]

01:09 zupo has joined #nixos-aarch64

01:26 monk has left #nixos-aarch64 [#nixos-aarch64]

01:34 zupo has quit [Ping timeout: 265 seconds]

01:34 zupo has joined #nixos-aarch64

01:51 cole-h has quit [Quit: Goodbye]

01:53 cole-h has joined #nixos-aarch64

01:57 ashkitten has quit [Quit: WeeChat 2.9]

01:57 monk has joined #nixos-aarch64

02:00 ashkitten has joined #nixos-aarch64

02:08 zupo_ has joined #nixos-aarch64

02:08 zupo has quit [Ping timeout: 246 seconds]

02:15 <samueldr> hmm, I don't have the time to investigate, but with the pinephone, nixpkgs-420f89ceb267b461eed5d025b6c3c0e57703cc5c has X11 going fine, but nixpkgs-34ad166a830d3ac1541dcce571c52231f2f0865a segfaults

02:20 monk has left #nixos-aarch64 ["Error from remote client"]

02:27 monk has joined #nixos-aarch64

02:33 h0m1 has quit [Ping timeout: 264 seconds]

02:35 h0m1 has joined #nixos-aarch64

03:08 superherointj has quit [Quit: Leaving]

03:44 andi- has quit [Remote host closed the connection]

03:48 andi- has joined #nixos-aarch64

04:12 orivej has quit [Ping timeout: 256 seconds]

04:24 ninjin has quit [Remote host closed the connection]

04:25 ninjin has joined #nixos-aarch64

04:35 ninjin has quit [Quit: OS upgrade]

05:57 alp has joined #nixos-aarch64

06:26 ib07 has quit [Ping timeout: 240 seconds]

06:27 ib07 has joined #nixos-aarch64

06:30 ib07 has quit [Max SendQ exceeded]

06:30 ib07 has joined #nixos-aarch64

07:03 alp has quit [Ping timeout: 272 seconds]

07:11 justanotheruser has quit [Ping timeout: 264 seconds]

07:20 alp has joined #nixos-aarch64

07:23 <craige> My Pi3 images have recently started failing "ERROR: Did not find a cmdline Flattened Device Tree" I've struggled to find what in my configs is causing this failure. Has anyone bumped up against this before?

07:34 cole-h has quit [Ping timeout: 260 seconds]

07:36 alp has quit [Ping timeout: 272 seconds]

07:57 ib07 has quit [Ping timeout: 240 seconds]

07:59 zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

07:59 ib07 has joined #nixos-aarch64

08:00 zupo has joined #nixos-aarch64

08:02 justanotheruser has joined #nixos-aarch64

08:03 ib07 has quit [Max SendQ exceeded]

08:03 ib07 has joined #nixos-aarch64

08:06 ib07 has quit [Max SendQ exceeded]

08:06 ib07 has joined #nixos-aarch64

08:09 orivej has joined #nixos-aarch64

08:13 alp has joined #nixos-aarch64

08:22 zupo has quit [Ping timeout: 256 seconds]

08:23 zupo has joined #nixos-aarch64

08:33 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

08:36 TheNumb has quit [Ping timeout: 240 seconds]

08:37 elvishjerricco has quit [Ping timeout: 244 seconds]

08:37 dsal has quit [Ping timeout: 268 seconds]

08:37 lukego has quit [Ping timeout: 246 seconds]

08:37 claudiii has quit [Ping timeout: 260 seconds]

08:37 chessai has quit [Ping timeout: 260 seconds]

08:37 NekomimiScience has quit [Ping timeout: 264 seconds]

08:37 davidtwco has quit [Ping timeout: 264 seconds]

08:37 blackriversoftwa has quit [Ping timeout: 240 seconds]

08:38 taktoa[c] has quit [Ping timeout: 240 seconds]

08:38 angerman has quit [Ping timeout: 244 seconds]

08:38 alunduil has quit [Ping timeout: 260 seconds]

08:38 c00w has quit [Ping timeout: 260 seconds]

08:38 prusnak has quit [Ping timeout: 260 seconds]

08:38 jackdk has quit [Ping timeout: 264 seconds]

08:38 cstrahan has quit [Ping timeout: 246 seconds]

08:38 feepo has quit [Ping timeout: 260 seconds]

08:51 alp has quit [Ping timeout: 246 seconds]

08:51 lgcl has joined #nixos-aarch64

08:52 lukego has joined #nixos-aarch64

08:52 davidtwco has joined #nixos-aarch64

08:52 claudiii has joined #nixos-aarch64

08:52 jackdk has joined #nixos-aarch64

08:52 NekomimiScience has joined #nixos-aarch64

08:52 dsal has joined #nixos-aarch64

08:53 blackriversoftwa has joined #nixos-aarch64

08:53 taktoa[c] has joined #nixos-aarch64

08:53 prusnak has joined #nixos-aarch64

08:53 c00w has joined #nixos-aarch64

08:53 angerman has joined #nixos-aarch64

08:53 TheNumb has joined #nixos-aarch64

08:53 cstrahan has joined #nixos-aarch64

08:56 elvishjerricco has joined #nixos-aarch64

08:56 alunduil has joined #nixos-aarch64

08:57 chessai has joined #nixos-aarch64

09:00 feepo has joined #nixos-aarch64

09:02 lgcl has quit [Quit: leaving]

09:05 FRidh has joined #nixos-aarch64

09:10 claudiii has quit [Ping timeout: 264 seconds]

09:11 claudiii has joined #nixos-aarch64

09:11 angerman has quit [Ping timeout: 272 seconds]

09:12 TheNumb has quit [Ping timeout: 272 seconds]

09:13 angerman has joined #nixos-aarch64

09:14 TheNumb has joined #nixos-aarch64

09:19 zupo has joined #nixos-aarch64

09:31 lgcl has joined #nixos-aarch64

09:38 alpernebbi has joined #nixos-aarch64

10:00 chessai has quit [Read error: Connection reset by peer]

10:00 chessai has joined #nixos-aarch64

10:00 lukego has quit [Read error: Connection reset by peer]

10:00 lukego has joined #nixos-aarch64

10:26 justanotheruser has quit [Ping timeout: 244 seconds]

11:04 alpernebbi has quit [Read error: Connection reset by peer]

11:15 pbb has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]

11:17 pbb has joined #nixos-aarch64

11:17 alpernebbi has joined #nixos-aarch64

11:25 lgcl has quit [Remote host closed the connection]

11:37 alp has joined #nixos-aarch64

12:04 monk has left #nixos-aarch64 ["Error from remote client"]

12:04 monk has joined #nixos-aarch64

12:09 vika_nezrimaya has joined #nixos-aarch64

12:16 alp has quit [Ping timeout: 240 seconds]

12:16 rajivr has joined #nixos-aarch64

13:11 <gchristensen> we have several 96-core cavium thunderx machines which can't find their disks anymore on nixos. I'm not inclined to sink time in them. anyone want to try figuring it out?

13:17 <clever> gchristensen: did it work before? and can the old ami still find disks?

13:18 <clever> [root@system76:~]# ls -l /sys/block/

13:18 <clever> lrwxrwxrwx 1 root root 0 Nov 8 09:18 mmcblk0 -> ../devices/pci0000:00/0000:00:1c.4/0000:02:00.0/rtsx_pci_sdmmc.0/mmc_host/mmc0/mmc0:aaaa/block/mmcblk0

13:18 <clever> lrwxrwxrwx 1 root root 0 Nov 3 22:15 nvme0n1 -> ../devices/pci0000:00/0000:00:1d.0/0000:04:00.0/nvme/nvme0/nvme0n1

13:19 <clever> lrwxrwxrwx 1 root root 0 Nov 8 09:17 sda -> ../devices/pci0000:00/0000:00:11.0/ata1/host0/target0:0:0/0:0:0:0/block/sda

13:19 <clever> gchristensen: with a cmd like this on a working machine, you can identify exactly which pci-dev the block-dev comes from, and then work out which drivers are involved

13:19 <gchristensen> alpine works

13:20 <clever> gchristensen: what does alpine show for the above?

13:21 <gchristensen> giving it a go

13:25 <clever> gchristensen: i assume the problem is on aws, and its failing to mount the rootfs? does the aws serial console still show errors from stage-1?

13:26 <gchristensen> this is the packet c2.large.arm

13:26 <gchristensen> (waiting for it to reboot)

13:26 <clever> ah, better serial console then

13:26 <gchristensen> yea

13:26 <clever> aws's serial has a massive latency and is read-only

13:27 <clever> packet.net has basically no latency, and is bi-directional

13:27 <gchristensen> yup

13:37 <gchristensen> ...hrm lrwxrwxrwx 1 root root 0 Nov 8 13:36 sda -> ../devices/platform/soc@0/849000000000.pci/pci0001:00/0001:00:08.0/ata1/host0/target0:0:0/0:0:0:0/block/sda

13:39 <clever> and what does `lspci -nn` say?

13:39 <clever> for 0001:00:08.0 i believe

13:39 <srk> or compare modules / dmesg

13:39 <gchristensen> hah

13:39 <clever> also, what changed to break it, nixos, or did packet.net change out the card?

13:40 <gchristensen> nixos

13:40 <clever> ah, so you could also bisect nixpkgs, if you had to

13:40 <clever> [root@amd-nixos:~]# ls -l /sys/block/sda/device/driver

13:40 <clever> lrwxrwxrwx 1 root root 0 Nov 8 09:40 /sys/block/sda/device/driver -> ../../../../../../../bus/scsi/drivers/sd

13:40 <gchristensen> not likely to do that :P

13:41 <clever> this says that the "sda" device is tied to the "sd" driver

13:41 <clever> [root@amd-nixos:~]# lspci -nn

13:41 <clever> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] (rev 40)

13:41 <clever> but its also part of this pci dev

13:41 <clever> [root@amd-nixos:~]# lspci -d 1002:4391 -v

13:41 <clever> 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] (rev 40) (prog-if 01 [AHCI 1.0])

13:41 <clever> Kernel driver in use: ahci

13:41 <clever> which is using the ahci driver

13:42 <clever> attacking from both ends (pci dev and sda), reveals the invisible link between ahci and sd

13:42 <clever> ahci deals with the pci end of the link, but then passes a generic scsi interface off to sd, which deals with creating a block device

13:42 <gchristensen> https://gist.github.com/grahamc/0fbdf4b364b2f73e2ebba92cff484741

13:44 <clever> gchristensen: are those the logs from alpine?

13:45 <gchristensen> YEA

13:45 <gchristensen> yea

13:46 <clever> 00:08.0 Class 0106: 177d:a01c ahci

13:46 <clever> i think your lspci is missing a layer to the topology

13:46 <clever> but its definitely using ahci for both drives

13:47 monk has left #nixos-aarch64 ["Error from remote client"]

13:47 <clever> and sd as with mine

13:47 monk has joined #nixos-aarch64

13:47 <clever> next step would be to check lsmod inside the broken nixos stage-1

13:56 <gchristensen> clever: want to PR some debugging lines? https://github.com/grahamc/packet-nix-builder/blob/master/system.nix#L9

13:58 <gchristensen> cycle time is long, so add all you can and try to avoid little mistakes :P

13:58 <clever> gchristensen should be as simple as just `lsmod ; lspci -nnk` i think

13:58 <clever> no way to get interactive on the sos console?

13:59 <gchristensen> it can be if we add an interactive bit :)

14:01 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

14:04 zupo has joined #nixos-aarch64

15:08 alp has joined #nixos-aarch64

15:09 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

15:11 vika_nezrimaya has quit [Ping timeout: 260 seconds]

15:32 dstzd has quit [Quit: ZNC - https://znc.in]

15:32 dstzd has joined #nixos-aarch64

16:01 alp has quit [Ping timeout: 268 seconds]

16:28 zupo has joined #nixos-aarch64

16:35 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

16:49 cole-h has joined #nixos-aarch64

16:49 Raito_Bezarius has quit [Ping timeout: 272 seconds]

16:54 Darkmatter66_ has joined #nixos-aarch64

16:55 Darkmatter66 has quit [Ping timeout: 260 seconds]

17:02 Raito_Bezarius has joined #nixos-aarch64

17:42 FRidh has quit [Quit: Konversation terminated!]

17:48 zupo has joined #nixos-aarch64

17:52 rajivr has quit [Quit: Connection closed for inactivity]

18:07 ib07 has quit [Ping timeout: 240 seconds]

18:17 ib07 has joined #nixos-aarch64

18:29 <simpson> Question which the hardware repos don't have an answer for: Is there a good choice for a well-supported board whose only sin is running a little hot?

18:30 <simpson> Like, maybe I *want* it to run hot~

18:30 alp has joined #nixos-aarch64

18:50 justanotheruser has joined #nixos-aarch64

18:59 adisbladis has quit [Ping timeout: 256 seconds]

19:01 adisbladis has joined #nixos-aarch64

19:18 alp has quit [Ping timeout: 260 seconds]

19:20 julm has quit [Ping timeout: 240 seconds]

19:20 <hexa-> that would be an Intel Pentium 4 if memory serves

19:27 julm has joined #nixos-aarch64

19:39 <samueldr> simpson: what usual-sins do you want to opt-out? maybe that'll help

19:39 <samueldr> because all I'm thinking is all SBCs are sinful

20:21 zupo has quit [Ping timeout: 258 seconds]

20:24 zupo has joined #nixos-aarch64

20:52 Darkmatter66_ has quit [Ping timeout: 240 seconds]

20:52 Darkmatter66 has joined #nixos-aarch64

20:58 <simpson> samueldr: I want to monitor the atmospheric conditions around an outdoor flower pot. I would very much appreciate it if, as a side effect, there were a little bit of extra heat from the board which kept the flowers not-freezing.

20:59 <samueldr> yeah, but what "sins" did you have in mind, other than hot running?

20:59 <samueldr> since you want it to be the only sin!

20:59 <samueldr> you might want a Power Mac G5 for all I know ;)

21:00 <simpson> Oh, I was hoping that it was well-supported, I guess. I think I want something cheap and small? But who doesn't want cheap and small.

21:00 <samueldr> though the wind speed could affect uh... the whole environment

21:01 <samueldr> right, so I think with this description you'd be fine with pretty much anything that mainline supports well, though that in itself is a hard question to answer as we don't really have a "validation suite" yet

21:01 <samueldr> nothing to describe the known pitfalls

21:01 cole-h has quit [Quit: Goodbye]

21:02 cole-h has joined #nixos-aarch64

21:02 <simpson> Yeah. And I understand the desire to not simply recommend that everybody buy a specific board, since it promotes a monoculture.

21:03 <samueldr> yeah

21:03 <samueldr> and also, people can't recommend boards they haven't tried :)

21:04 <samueldr> or: shouldn't!

21:04 <samueldr> you might also want to figure out your accessories for monitoring

21:04 <samueldr> is it usb? i²c? something else you need gpio headers?

21:04 <samueldr> how's it gonna interface with the OS? proprietary kernel-level drivers?

21:05 <samueldr> like, if you go with accessories expecting a raspberry pi, you might have a harder time with anything else; and even with a raspberry pi using mainline

21:05 <samueldr> the raspberry pi is quite sinful in needing vendor forks

21:05 <simpson> Sure. I was hoping to use standard boring USB sensors, but you're entirely right that it's only 2020 and Linux might not support everything.

21:06 <samueldr> I don't even know about any of those sensors, so maybe boring usb sensors work fine already :)

21:06 <samueldr> probably a thing to figure out before the board

21:06 <samueldr> that could limit what you end up being able to use

21:07 <simpson> Yeah, I guess. Certainly different boards have different power requirements and powered busses, at a minimum.

21:07 <samueldr> right, how do you want to provide power? PoE? some boards have that more built-in than other

21:49 alp has joined #nixos-aarch64

22:02 Darkmatter66 has quit [Read error: Connection reset by peer]

22:03 Darkmatter66 has joined #nixos-aarch64

22:26 ryantrinkle has quit [Quit: Leaving.]

22:35 ryantrinkle has joined #nixos-aarch64

22:48 ryantrinkle has quit [Quit: Leaving.]

22:52 ryantrinkle has joined #nixos-aarch64

22:54 zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]

22:57 ryantrinkle has quit [Quit: Leaving.]

22:59 ryantrinkle has joined #nixos-aarch64

23:04 ryantrinkle has quit [Quit: Leaving.]

23:06 ryantrinkle has joined #nixos-aarch64

23:08 zarel has joined #nixos-aarch64

23:09 ryantrinkle has quit [Client Quit]

23:09 zarel_ has quit [Ping timeout: 260 seconds]

23:12 alp has quit [Ping timeout: 244 seconds]

23:13 ryantrinkle has joined #nixos-aarch64

23:14 zupo has joined #nixos-aarch64

23:15 ryantrinkle has quit [Client Quit]

23:17 ryantrinkle has joined #nixos-aarch64

23:27 zupo has quit [Ping timeout: 260 seconds]

23:28 <samueldr> hmmm, using the BCB on Android, we might be able to do an almost proper "switch" for the recovery boot for devices without A/B

23:28 ryantrinkle has quit [Quit: Leaving.]

23:29 <samueldr> I think that way one could manually select the recovery boot to boot into the Mobile NixOS stage-1, which would show the recovery GUI; that GUI could allow setting the BCB to ask for recovery or erase commands from the BCB

23:29 <samueldr> so you could reboot to Mobile NixOS by asking to reboot to recovery from Android

23:29 <samueldr> uh no, forget that last line, I don't think this uses the BCB

23:29 zupo has joined #nixos-aarch64

23:30 <samueldr> I guess that all depends on whether the bootloader itself clears the BCB

23:30 <samueldr> there's not much upstream docs that I found

23:30 <samueldr> https://www.xypron.de/u-boot/android/bcb.html

23:30 <samueldr> this is the u-boot docs about their implementation

23:31 <samueldr> I'll have to try, but it could be useful in the future to allow end-users to dual boot android and Mobile NixOS

23:32 <samueldr> if the BCB isn't cleared by the bootloader, any further boots would go straight to the recovery

23:32 <samueldr> I guess the danger is if the BCB isn't cleared and the recovery image is broken, it wouldn't allow to go back to the main system?

23:35 <samueldr> and no, qualcomm devices don't use that https://lwn.net/Articles/504721/

23:35 <samueldr> AFAIK it's handled through their PMIC

23:35 <samueldr> (for simple `reboot recovery`)

23:35 <samueldr> though that hook could end up being useful

23:38 zupo has quit [Ping timeout: 265 seconds]

23:39 ib07 has quit [Ping timeout: 240 seconds]

23:45 zupo has joined #nixos-aarch64

23:49 ryantrinkle has joined #nixos-aarch64