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 [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-aarch64
zarel has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
zarel has quit [Ping timeout: 256 seconds]
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
WilliButz has quit [Quit: bye]
WilliButz has joined #nixos-aarch64
zupo has quit [Ping timeout: 265 seconds]
zupo has joined #nixos-aarch64
orivej has quit [Quit: No Ping reply in 180 seconds.]
orivej has joined #nixos-aarch64
alp has quit [Ping timeout: 246 seconds]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Thra11 has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 265 seconds]
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
<Thra11>
samueldr: Still a long way from understanding exactly what's going on, but it looks like there might be something broken in dtc-1.5.1 (the version in the 20.03 nixpkgs I'm using). My overlay seems to apply with dtc-1.6.0 (haven't tested it yet, but the changes are visible in the fdtdump of the output).
orivej_ has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
<Thra11>
1.5.1 was refusing to apply the overlay because it couldn't find a __symbols__ node in it, but it didn't add a __symbols__ node unless I added some spurious labels to the overlay (despite using the `-@` argument). With the spurious labels, it would silently "apply" it with no visible change to the output.
alp has quit [Ping timeout: 264 seconds]
orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Read error: Connection reset by peer]
orivej_ has joined #nixos-aarch64
alp has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
orivej_ has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 260 seconds]
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Thra11 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
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…]
orivej has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
<Thra11>
Thanks to the dtb overlay, SPI is now actually working on my Orange Pi Zero Plus2! This feels like more of an achievement than it should. Now I just have to rewrite some half-arsed python libraries that refuse to work on anything except RPi, and I'll be able to use an e-ink screen with it...
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sphalerite>
hack the u-boot, hack-hack the u-boot!
<sphalerite>
Thra11: \o/
<sphalerite>
Do you have a specific plan for it?
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
<Thra11>
sphalerite: Am planning to use it to display vivarium stats/graphs like temperature and humidity.
<sphalerite>
ooh neat
<sphalerite>
what kind of vivarium?
orivej has quit [Ping timeout: 256 seconds]
orivej_ has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 258 seconds]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
<Thra11>
sphalerite: We have a rescue cornsnake.
<Thra11>
It used to live in a school. I can appreciate the attempt to provide interest for the kids, but the idea that a teacher would have time to take proper care of an animal once they've finished all their teaching and marking and writing reports on their teaching and marking is somewhat laughable.
cole-h has joined #nixos-aarch64
orivej has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 256 seconds]
<Thra11>
Unfortunately, the python code that's meant to drive the display doesn't provide a good abstraction between SPI code (required to talk to the display) and using the Raspberry Pi GPIO for SPI (shouldn't be compulsory), so it'll need hacking/rewriting.
orivej has quit [Ping timeout: 256 seconds]
orivej has joined #nixos-aarch64
<Thra11>
Apart from that, I'm loving the whole NixOS on little "embedded" devices thing. It's so much easier to experiment and develop stuff without ending up with a messy system where you can't remember what was a failed experiment and what was an essential change that made it work.
orivej has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
alp has quit [Ping timeout: 265 seconds]
<sphalerite>
Thra11: just remember to commit your code, otherwise you'll end up with the same thing again :D
<Thra11>
sphalerite: my config/overlays, you mean?
<sphalerite>
yes
<Thra11>
Good point! (although even without commits it's easier to investigate a NixOS config than to work out what commands were run to set up a conventional linux system)
<sphalerite>
it's called .bash_history Thra11
<sphalerite>
:p
<sphalerite>
yeah no I absolutely agree
<sphalerite>
got to love nixos
<sphalerite>
and nix
<sphalerite>
I'm currently very glad I have it for my attempts at firmware dev :D
<Thra11>
.bash_history doesn't help you if you use zsh! :p
orivej has quit [Ping timeout: 256 seconds]
orivej_ has joined #nixos-aarch64
<Thra11>
"Why does your system setup involve installing that package then removing it again? Well... I'm using my bash history as a guide."
<njha>
hmm... I tried to do a `nixos-rebuild switch --upgrade` and it's trying to upgrade my kernel again
<Thra11>
njha: Is your system using a versioned kernel (e.g. linux_5_6), or linux_latest?
<njha>
Thra11: I have `boot.kernelPackages = pkgs.linuxPackages_odroid_n2_5_6;` set
<njha>
so its a versioned kernel
<njha>
but it's trying to upgrade to the one from nixos-20.03
<samueldr>
are you sure it's trying to upgrade to one from nixos-20.03?
<{^_^}>
nixops#260 (by wmertens, 5 years ago, open): Support building fully remotely
<samueldr>
I literally have no reason not to use it, I just don't have a park I "manage" with it, and am satisfied with just going to the machine and rebuilding
<njha>
I have three devices, but I think it would be more convenient to type `deploy` from my local machine
<njha>
than it is to ssh into every one, make a change, nixos-rebuild
<samueldr>
how's the N2 as an SBC? (do you have enough experience with diverse devices to compare with?)
<simpson>
njha: I used to use nixops. Still do, kind of; I have a deployment that is mostly torn down now but might still have a few lingering members. I've been shopping for something to manage a homelab, and I'm not going to use nixops.
<simpson>
I've considered Morph, which is more reasonable about inducting user-facing machines into the fold without requiring one machine to be elected queen bee.
<njha>
samueldr: hmm... I haven't used much else other than raspberry pis or a Jetson TK1/TX2
<njha>
but the N2 seems fast to me, I've been running a k8s cluster on them for a while
<samueldr>
I see it's amlogic, IIRC amlogic are generally well-supported by mainline, and seeing that repo only applies a couple patches on top of mainline, that seems right
<njha>
runs a rails app and a minecraft server (8ish player cap, 1.15.2) pretty well
<njha>
simpson: ooh, morph looks good
<njha>
do you know if it builds on the remote machine?
<simpson>
njha: I'm still examining, but AFAIK Morph builds on the same local machine that it runs on.
<njha>
rip :(
<grw1>
simpson: it will build remote if nix.distributedBuilds is enabled, same as nixops i think
<grw1>
i use it to deploy to various SBC, works well for me
<simpson>
grw1++
<{^_^}>
grw1's karma got increased to 1
orivej has joined #nixos-aarch64
orivej_ has quit [Ping timeout: 264 seconds]
zupo has joined #nixos-aarch64
ashkitten has quit [Quit: WeeChat 2.8]
ashkitten has joined #nixos-aarch64
<sphalerite>
So, uh, how does a PWM backlight without a PWM work? \:|
<sphalerite>
(specifically, the backlight in rk3399-gru-chromebook.dtsi in linux and u-boot)
<sphalerite>
How does linux know how to control it?
<clever>
sphalerite: not directly an answer, but one of my laptops had a backlight controller on the panel, that the pc would talk to somehow
<clever>
sphalerite: and if the ribbon cable was loose, the cmds just got lost, and the brightness would be stuck at the current level (potentially off)
<clever>
so i had to wiggle the ribbon, then change the level again
<clever>
but once configured, the connection could be lost, and it would just hold the level
<sphalerite>
how convenient
<sphalerite>
but you seem like you might know device tree things!
<clever>
ive been dabbling in it a bit
orivej_ has joined #nixos-aarch64
<sphalerite>
aaah I see
<sphalerite>
I was looking in the wrong place :)
orivej has quit [Read error: Connection reset by peer]
<clever>
sphalerite: lately, ive been working on booting nixos on the rpi, without any blobs
<sphalerite>
rk3399-gru-bob.dts sets the backlight's pwms property
<clever>
sounds like a sane thing for it to do
<sphalerite>
riiiight, because it's a different pwm pin from model to model
<clever>
and if everything is working right, the bootloader should pass you a dtb explaining those differences
<clever>
and the same kernel will just work anywhere
<sphalerite>
yep
<sphalerite>
ah shit, u-boot doesn't have a driver for the cros ec pwm.
<samueldr>
either coreboot or depthcharge should have one
<samueldr>
if it's coreboot, maybe it can be set and forgotten so u-boot doesn't even know about it?
<samueldr>
if it's depthcharge, porting time I guess
<sphalerite>
had a quick look in coreboot, now looking at linux