zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 260 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
monk has left #nixos-aarch64 [#nixos-aarch64]
zupo has quit [Ping timeout: 265 seconds]
zupo has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-aarch64
ashkitten has quit [Quit: WeeChat 2.9]
monk has joined #nixos-aarch64
ashkitten has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 246 seconds]
<samueldr> hmm, I don't have the time to investigate, but with the pinephone, nixpkgs-420f89ceb267b461eed5d025b6c3c0e57703cc5c has X11 going fine, but nixpkgs-34ad166a830d3ac1541dcce571c52231f2f0865a segfaults
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 264 seconds]
h0m1 has joined #nixos-aarch64
superherointj has quit [Quit: Leaving]
andi- has quit [Remote host closed the connection]
andi- has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
ninjin has quit [Remote host closed the connection]
ninjin has joined #nixos-aarch64
ninjin has quit [Quit: OS upgrade]
alp has joined #nixos-aarch64
ib07 has quit [Ping timeout: 240 seconds]
ib07 has joined #nixos-aarch64
ib07 has quit [Max SendQ exceeded]
ib07 has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
justanotheruser has quit [Ping timeout: 264 seconds]
alp has joined #nixos-aarch64
<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?
cole-h has quit [Ping timeout: 260 seconds]
alp has quit [Ping timeout: 272 seconds]
ib07 has quit [Ping timeout: 240 seconds]
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ib07 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
ib07 has quit [Max SendQ exceeded]
ib07 has joined #nixos-aarch64
ib07 has quit [Max SendQ exceeded]
ib07 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
alp has joined #nixos-aarch64
zupo has quit [Ping timeout: 256 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
TheNumb has quit [Ping timeout: 240 seconds]
elvishjerricco has quit [Ping timeout: 244 seconds]
dsal has quit [Ping timeout: 268 seconds]
lukego has quit [Ping timeout: 246 seconds]
claudiii has quit [Ping timeout: 260 seconds]
chessai has quit [Ping timeout: 260 seconds]
NekomimiScience has quit [Ping timeout: 264 seconds]
davidtwco has quit [Ping timeout: 264 seconds]
blackriversoftwa has quit [Ping timeout: 240 seconds]
taktoa[c] has quit [Ping timeout: 240 seconds]
angerman has quit [Ping timeout: 244 seconds]
alunduil has quit [Ping timeout: 260 seconds]
c00w has quit [Ping timeout: 260 seconds]
prusnak has quit [Ping timeout: 260 seconds]
jackdk has quit [Ping timeout: 264 seconds]
cstrahan has quit [Ping timeout: 246 seconds]
feepo has quit [Ping timeout: 260 seconds]
alp has quit [Ping timeout: 246 seconds]
lgcl has joined #nixos-aarch64
lukego has joined #nixos-aarch64
davidtwco has joined #nixos-aarch64
claudiii has joined #nixos-aarch64
jackdk has joined #nixos-aarch64
NekomimiScience has joined #nixos-aarch64
dsal has joined #nixos-aarch64
blackriversoftwa has joined #nixos-aarch64
taktoa[c] has joined #nixos-aarch64
prusnak has joined #nixos-aarch64
c00w has joined #nixos-aarch64
angerman has joined #nixos-aarch64
TheNumb has joined #nixos-aarch64
cstrahan has joined #nixos-aarch64
elvishjerricco has joined #nixos-aarch64
alunduil has joined #nixos-aarch64
chessai has joined #nixos-aarch64
feepo has joined #nixos-aarch64
lgcl has quit [Quit: leaving]
FRidh has joined #nixos-aarch64
claudiii has quit [Ping timeout: 264 seconds]
claudiii has joined #nixos-aarch64
angerman has quit [Ping timeout: 272 seconds]
TheNumb has quit [Ping timeout: 272 seconds]
angerman has joined #nixos-aarch64
TheNumb has joined #nixos-aarch64
zupo has joined #nixos-aarch64
lgcl has joined #nixos-aarch64
alpernebbi has joined #nixos-aarch64
chessai has quit [Read error: Connection reset by peer]
chessai has joined #nixos-aarch64
lukego has quit [Read error: Connection reset by peer]
lukego has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 244 seconds]
alpernebbi has quit [Read error: Connection reset by peer]
pbb has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
pbb has joined #nixos-aarch64
alpernebbi has joined #nixos-aarch64
lgcl has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
vika_nezrimaya has joined #nixos-aarch64
alp has quit [Ping timeout: 240 seconds]
rajivr has joined #nixos-aarch64
<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?
<clever> gchristensen: did it work before? and can the old ami still find disks?
<clever> [root@system76:~]# ls -l /sys/block/
<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
<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
<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
<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
<gchristensen> alpine works
<clever> gchristensen: what does alpine show for the above?
<gchristensen> giving it a go
<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?
<gchristensen> this is the packet c2.large.arm
<gchristensen> (waiting for it to reboot)
<clever> ah, better serial console then
<gchristensen> yea
<clever> aws's serial has a massive latency and is read-only
<clever> packet.net has basically no latency, and is bi-directional
<gchristensen> yup
<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
<clever> and what does `lspci -nn` say?
<clever> for 0001:00:08.0 i believe
<srk> or compare modules / dmesg
<gchristensen> hah
<clever> also, what changed to break it, nixos, or did packet.net change out the card?
<gchristensen> nixos
<clever> ah, so you could also bisect nixpkgs, if you had to
<clever> [root@amd-nixos:~]# ls -l /sys/block/sda/device/driver
<clever> lrwxrwxrwx 1 root root 0 Nov 8 09:40 /sys/block/sda/device/driver -> ../../../../../../../bus/scsi/drivers/sd
<gchristensen> not likely to do that :P
<clever> this says that the "sda" device is tied to the "sd" driver
<clever> [root@amd-nixos:~]# lspci -nn
<clever> 00:11.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD/ATI] SB7x0/SB8x0/SB9x0 SATA Controller [AHCI mode] [1002:4391] (rev 40)
<clever> but its also part of this pci dev
<clever> [root@amd-nixos:~]# lspci -d 1002:4391 -v
<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])
<clever> Kernel driver in use: ahci
<clever> which is using the ahci driver
<clever> attacking from both ends (pci dev and sda), reveals the invisible link between ahci and sd
<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
<clever> gchristensen: are those the logs from alpine?
<gchristensen> YEA
<gchristensen> yea
<clever> 00:08.0 Class 0106: 177d:a01c ahci
<clever> 00:08.0 Class 0106: 177d:a01c ahci
<clever> i think your lspci is missing a layer to the topology
<clever> but its definitely using ahci for both drives
monk has left #nixos-aarch64 ["Error from remote client"]
<clever> and sd as with mine
monk has joined #nixos-aarch64
<clever> next step would be to check lsmod inside the broken nixos stage-1
<gchristensen> clever: want to PR some debugging lines? https://github.com/grahamc/packet-nix-builder/blob/master/system.nix#L9
<gchristensen> cycle time is long, so add all you can and try to avoid little mistakes :P
<clever> gchristensen should be as simple as just `lsmod ; lspci -nnk` i think
<clever> no way to get interactive on the sos console?
<gchristensen> it can be if we add an interactive bit :)
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
vika_nezrimaya has quit [Ping timeout: 260 seconds]
dstzd has quit [Quit: ZNC - https://znc.in]
dstzd has joined #nixos-aarch64
alp has quit [Ping timeout: 268 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cole-h has joined #nixos-aarch64
Raito_Bezarius has quit [Ping timeout: 272 seconds]
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 260 seconds]
Raito_Bezarius has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
zupo has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
ib07 has quit [Ping timeout: 240 seconds]
ib07 has joined #nixos-aarch64
<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?
<simpson> Like, maybe I *want* it to run hot~
alp has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
adisbladis has quit [Ping timeout: 256 seconds]
adisbladis has joined #nixos-aarch64
alp has quit [Ping timeout: 260 seconds]
julm has quit [Ping timeout: 240 seconds]
<hexa-> that would be an Intel Pentium 4 if memory serves
julm has joined #nixos-aarch64
<samueldr> simpson: what usual-sins do you want to opt-out? maybe that'll help
<samueldr> because all I'm thinking is all SBCs are sinful
zupo has quit [Ping timeout: 258 seconds]
zupo has joined #nixos-aarch64
Darkmatter66_ has quit [Ping timeout: 240 seconds]
Darkmatter66 has joined #nixos-aarch64
<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.
<samueldr> yeah, but what "sins" did you have in mind, other than hot running?
<samueldr> since you want it to be the only sin!
<samueldr> you might want a Power Mac G5 for all I know ;)
<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.
<samueldr> though the wind speed could affect uh... the whole environment
<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
<samueldr> nothing to describe the known pitfalls
cole-h has quit [Quit: Goodbye]
cole-h has joined #nixos-aarch64
<simpson> Yeah. And I understand the desire to not simply recommend that everybody buy a specific board, since it promotes a monoculture.
<samueldr> yeah
<samueldr> and also, people can't recommend boards they haven't tried :)
<samueldr> or: shouldn't!
<samueldr> you might also want to figure out your accessories for monitoring
<samueldr> is it usb? i²c? something else you need gpio headers?
<samueldr> how's it gonna interface with the OS? proprietary kernel-level drivers?
<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
<samueldr> the raspberry pi is quite sinful in needing vendor forks
<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.
<samueldr> I don't even know about any of those sensors, so maybe boring usb sensors work fine already :)
<samueldr> probably a thing to figure out before the board
<samueldr> that could limit what you end up being able to use
<simpson> Yeah, I guess. Certainly different boards have different power requirements and powered busses, at a minimum.
<samueldr> right, how do you want to provide power? PoE? some boards have that more built-in than other
alp has joined #nixos-aarch64
Darkmatter66 has quit [Read error: Connection reset by peer]
Darkmatter66 has joined #nixos-aarch64
ryantrinkle has quit [Quit: Leaving.]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Quit: Leaving.]
ryantrinkle has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
ryantrinkle has quit [Quit: Leaving.]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Quit: Leaving.]
ryantrinkle has joined #nixos-aarch64
zarel has joined #nixos-aarch64
ryantrinkle has quit [Client Quit]
zarel_ has quit [Ping timeout: 260 seconds]
alp has quit [Ping timeout: 244 seconds]
ryantrinkle has joined #nixos-aarch64
zupo has joined #nixos-aarch64
ryantrinkle has quit [Client Quit]
ryantrinkle has joined #nixos-aarch64
zupo has quit [Ping timeout: 260 seconds]
<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
ryantrinkle has quit [Quit: Leaving.]
<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
<samueldr> so you could reboot to Mobile NixOS by asking to reboot to recovery from Android
<samueldr> uh no, forget that last line, I don't think this uses the BCB
zupo has joined #nixos-aarch64
<samueldr> I guess that all depends on whether the bootloader itself clears the BCB
<samueldr> there's not much upstream docs that I found
<samueldr> this is the u-boot docs about their implementation
<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
<samueldr> if the BCB isn't cleared by the bootloader, any further boots would go straight to the recovery
<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?
<samueldr> and no, qualcomm devices don't use that https://lwn.net/Articles/504721/
<samueldr> AFAIK it's handled through their PMIC
<samueldr> (for simple `reboot recovery`)
<samueldr> though that hook could end up being useful
zupo has quit [Ping timeout: 265 seconds]
ib07 has quit [Ping timeout: 240 seconds]
zupo has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64