rajivr has joined #nixos-aarch64
Darkmatter66 has quit [Read error: Connection reset by peer]
Darkmatter66 has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
<lovesegfault> clever: Cleaned up that code quite a bit today: https://github.com/lovesegfault/hyperpixel-init
<lovesegfault> there's now a short and sweet gpio module and another short "hyperpixel" one that does that config magic
<lovesegfault> and a nice readable main
knerten2 has joined #nixos-aarch64
knerten1 has quit [Ping timeout: 260 seconds]
justanotheruser has quit [Ping timeout: 272 seconds]
Acou_Bass has quit [Ping timeout: 256 seconds]
Acou_Bass has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
aforemny has quit [Ping timeout: 260 seconds]
aforemny has joined #nixos-aarch64
<lovesegfault> I have to say, I'm at a big loss with Nix & cross compilation
<lovesegfault> Even if I set `crossSystem` it's like "nope, I want x86"
cole-h has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 260 seconds]
<julm> https://xnux.eu/log/ megi's PinePhone Development Log
<julm> ^ has some considerations wrt. electrical/thermal safety that may be relevant for nixos-mobile
<samueldr> yeah, before being side-tracked on working on the website I was rebasing and testing in depth on top of their work
<samueldr> I "poked" the modem with their tree
<samueldr> and was reading about how it runs an android-type-based system
<samueldr> (not really android)
<samueldr> with fastboot available!
<samueldr> a distro on the pinephone could realistically brick your modem
<samueldr> trivially even
<samueldr> by installing trash
<samueldr> or worse (worse?) bug your modem!
<samueldr> but at the same time, it's "good"
<samueldr> as it would allow a distro to add programs to the modem that listens to event
<samueldr> imagine a push events system
<samueldr> the pinephone is in deep sleep
<samueldr> but your modem can wake it on push events!
justanotheruser has joined #nixos-aarch64
kahiru has quit [Read error: Connection reset by peer]
kahiru has joined #nixos-aarch64
justan0theruser has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 246 seconds]
kahiru_ has joined #nixos-aarch64
kahiru has quit [Ping timeout: 265 seconds]
<Ke> how long does it take to build nixos kernel with 4x a72 at 1.3GHz?
<samueldr> on an RK3399 IIRC it takes ~4h
<samueldr> not what you asked for, but I never compiled it on a pi4
<samueldr> though I/O access will really affect build times
<samueldr> so if it builds on an SD card expect much longer builds
<samueldr> IIRC I went from 12 hours to 4 hours only by finally getting an SSD rather than using a usb pen drive
<samueldr> (a good pen drive! better than the SD cards I had laying around)
<ar> i wonder if compiling in ram would be viable on the 8GB model…
<samueldr> it might, actually
<samueldr> though still, file I/O can be problematic
<samueldr> it _really_ changed how the RK3399 build feels
kahiru_ has quit [Ping timeout: 246 seconds]
kahiru has joined #nixos-aarch64
<Ke> samueldr: this is mcbin, not rpi
<samueldr> ah, sorry for assuming
<Ke> though a vm on mcbin
<samueldr> so I hope you have better storage then :)
<Ke> I think I can assume everything is mostly read from memory
<Ke> there's 16G of it
<samueldr> it might help :)
<Ke> backing nonvolatile is sata ssd
<Ke> I am hoping to run nixos natively here soon
<Ke> this was the system, where systemd-boot can't load nixos kernel
<Ke> I am now trying out grub-efi
kahiru has quit [Ping timeout: 240 seconds]
kahiru has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
kahiru_ has joined #nixos-aarch64
kahiru has quit [Ping timeout: 256 seconds]
kahiru_ has quit [Ping timeout: 258 seconds]
kahiru has joined #nixos-aarch64
kahiru has quit [Read error: Connection reset by peer]
kahiru has joined #nixos-aarch64
<srk> lovesegfault: what's the problem with cross compilation?
<srk> I've managed to patch nixus to be able to deploy rpi from x86 machine yesterday
<srk> I'm hittin a weird issue again with it though, where it waits for input indefinitely during extlinux chooser
<srk> ah, that only happens with timeout 0, nvm
<julm> samueldr: all right cool
<julm> samueldr: also, have you seen : https://xnux.eu/p-boot-demo/ ?
kahiru has quit [Ping timeout: 260 seconds]
kahiru has joined #nixos-aarch64
simpson has quit [Ping timeout: 244 seconds]
simpson has joined #nixos-aarch64
orivej has joined #nixos-aarch64
kahiru has quit [Read error: Connection reset by peer]
kahiru has joined #nixos-aarch64
kahiru has quit [Ping timeout: 272 seconds]
Darkmatter66 has quit [Ping timeout: 260 seconds]
pinkieval has quit [Ping timeout: 260 seconds]
Darkmatter66 has joined #nixos-aarch64
pinkieval has joined #nixos-aarch64
<betaboon> samueldr: seems like mainline (5.4.62) on rpi4-64bit does not yet fully work, gets stuck at "random: lvm: uninitialized urandom read (4 bytes read)"
<srk> I've tried 5.8 like an hour ago with raspberrypi bootloader but no console output at all
<betaboon> srk: with the mentioned version i do get console output on the gpios, (but i had the console defined in the cmdline.txt)
<srk> ah, that's what I was missing probably
<srk> trying with 4.19 now /o\
<betaboon> srk: with the `boot.kernelPackages = pkgs.linuxPackages_rpi4` it works fine.
<betaboon> but i need to try a newer one to get a touchscreen connected via dsi working :D
<srk> yeah, ideally I don't want to deal with archaic kernel
<srk> still no output, pff
<betaboon> srk: what console did you set ?
<srk> betaboon: in config.txt?
<betaboon> in the cmdline.txt
<srk> only have console=ttyAMA0 in boot.kernelParams
<betaboon> srk: check on the boot partition of your sd-card
<srk> ah, I might be missing arm_64bit=1 as well
<betaboon> i always had to change the cmdline.txt first to get initial console output
<srk> and possibly even enable_uart=1
<betaboon> srk: are you using the hydra image ?
<srk> no, cross compiling
lafa has joined #nixos-aarch64
<srk> works \o/
<betaboon> \o/
<betaboon> O
<betaboon> ||
<srk> / \
<srk> ehm :D
<betaboon> so you're on 4.19 now ?
<srk> yup, now I'm gonna retest with 5.8
orivej has quit [Ping timeout: 256 seconds]
<betaboon> I know that raspbian is booting into 5.4.51 but only im armv7 32bít mode
<srk> no output at all with 5.8
<betaboon> same with 5.7
<srk> hmm, maybe with u-boot it could work
<betaboon> i wonder if it would work with the linux-5.4 branch of raspberry/linux
justan0theruser has quit [Ping timeout: 246 seconds]
<betaboon> srk: how exactly are you crosscompiling the image ?
<srk> betaboon: I need to take a break and I'll commit the stuff and publish it
<betaboon> srk: thanks :D
smrtak[m] has quit [*.net *.split]
orivej has joined #nixos-aarch64
smrtak[m] has joined #nixos-aarch64
<srk> smrtak[m]: ^
<srk> ,locate libnuma.so
<{^_^}> Found in packages: numactl
<srk> ,locate libnuma.so.1
<{^_^}> Found in packages: numactl
Darkmatter66 has quit [Ping timeout: 240 seconds]
Darkmatter66 has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
orivej has joined #nixos-aarch64
lafa has quit [Read error: Connection reset by peer]
lafka has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
WilliButz has quit [Remote host closed the connection]
<samueldr> julm: yes, seen p-boot, probably won't end up using it because it'd mean implementing a device-specific bootloader thing, rather than the generic u-boot one
<samueldr> I'd rather trade a few seconds of boot for a common boot scheme, than "rice" 4 seconds out of the boot time
<julm> samueldr: well, I was pointing out this because maybe at some point nixos-mobile could be added to the list of testable distros
<samueldr> there are some difficulties
<samueldr> and it's not like it is a "product" or "appliance" distro, like let's say sailfish or ubports
<samueldr> you could make Mobile NixOS whatever you want
<samueldr> so it doesn't really fit well in such a collection
<julm> 'k
rajivr has quit [Quit: Connection closed for inactivity]
justanotheruser has joined #nixos-aarch64
WilliButz has joined #nixos-aarch64
justan0theruser has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 240 seconds]
<Ke> no luck with nixos grub efi either
<Ke> maybe should learn to hack that u-boot in, or try debian grub
<samueldr> since all distros end up applying myriad patches on grub
<samueldr> it's highly possible one has a "better" distro of grub
<samueldr> Ke: try opensuse
<samueldr> they are really pushing for EFI on ARM
<samueldr> they were a big part of the effort to get u-boot just-compliant-enough to boot EFI IIRC
<samueldr> (I meant, try to somehow get an EFI grub from opensuse to see if it runs, if it runs then import the patchset or something like that)
justan0theruser has quit [Ping timeout: 260 seconds]
justanotheruser has joined #nixos-aarch64
aforemny has quit [Ping timeout: 272 seconds]
aforemny has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 246 seconds]
justanotheruser has joined #nixos-aarch64
noonien has quit [Ping timeout: 272 seconds]
noonien has joined #nixos-aarch64
blackriversoftwa has quit [Write error: Connection reset by peer]
blackriversoftwa has joined #nixos-aarch64
c00w has quit [Read error: Connection reset by peer]
c00w has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 246 seconds]