<ehmry>
what is the procedure for dealing with packages that don't build for aarch64 and for which one does not have time to fix? mark broken?
alp has quit [Ping timeout: 244 seconds]
alp has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 258 seconds]
ryantrinkle has joined #nixos-aarch64
zupo has joined #nixos-aarch64
iwq has quit [*.net *.split]
makefu has quit [*.net *.split]
sigtrm has quit [*.net *.split]
iwq has joined #nixos-aarch64
sigtrm has joined #nixos-aarch64
makefu has joined #nixos-aarch64
hpfr has quit [Quit: authenticating]
hpfr has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
orivej has quit [Quit: orivej]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
veleiro has quit [Ping timeout: 256 seconds]
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
bennofs__ has joined #nixos-aarch64
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
bennofs_ has quit [Ping timeout: 256 seconds]
alp has quit [Ping timeout: 246 seconds]
orivej has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
<samueldr>
that should be fine, if there's a discussion (e.g. bug or PR comment) it's nice to also link to it in a comment
cole-h has joined #nixos-aarch64
alp has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
cript0nauta has quit [Ping timeout: 265 seconds]
cript0nauta has joined #nixos-aarch64
cript0nauta has quit [Read error: Connection reset by peer]
cript0nauta has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
alp has quit [Ping timeout: 240 seconds]
Thra11 has joined #nixos-aarch64
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 256 seconds]
zeta_0 has joined #nixos-aarch64
<zeta_0>
i'm finally able to get nixos to build on my raspberry pi 4, but for some reason, i'm struggling to get a desktop environment working, xmonad threw build errors, next i'm going to try gnome and plasma, have any been able to get a desktop environment working with this setup?
<zeta_0>
samueldr: ^
<samueldr>
a few months back I was
<samueldr>
but, first, before even playing around with desktop environments, please work on getting ssh working in a way you can just copy/paste things on the pi
<samueldr>
you're going to work way faster on the problem rather than copy/pasting things by hand
<zeta_0>
samueldr: i got ssh working last night and copied and pasted everything, but now when i try to ssh again it asks for a password, which i don't remember setting one up, so that's strange.
<samueldr>
let me guess at your issue
<samueldr>
you had the ssh key set in the config for the sd image build
<zeta_0>
samueldr: emacs's tramp package sound good, but i couldn't get it to work.
<samueldr>
but you did not configure it in the configuration.nix on the device
<zeta_0>
samueldr: let me double check on that, one second !
<zeta_0>
samueldr: in configuration.nix for openssh.authorizedKeys.keys = [ "ssh-ed25519 ..." ]; i substituted ... with my ed key.
<zeta_0>
samueldr: i think i'm close though, one i can get xmonad and xorg for my kyb layout, the rest shouldn't be too difficult to setup, then i'll be good to go.
<samueldr>
then I wouldn't know, sorry, too many possibilities
<zeta_0>
samueldr: do you know of anyone that has a similar setup to mine? that way they can show me the way they set it up.
<samueldr>
I don't know of any
<zeta_0>
samueldr: by when will the support for nixos on raspberry pi 4 be better, currently it still seems very experimental !
<samueldr>
that's a loaded question :/
<samueldr>
first of all, the current images are using the raspberry pi foundation's kernel fork because *they* don't support mainline linux
<samueldr>
and then I'm pretty sure your issues are not raspberry pi specific, at least the build issues are simply aarch64-linux specific
<samueldr>
and the general answer is "whenever someone gets around to it"
<samueldr>
AFAIK there is no one employed by the NixOS distribution to work on support for aarch64 linux desktop
<samueldr>
so, to answer the complete question, there will not be "support" for nixos on raspberry pi for the near term
<zeta_0>
samueldr: oh ok, i see, well i'm going to try to at least get any desktop environment working on my nixos pi setup, and then from there, i'll tinker with it and try to get xmonad working on it.
<samueldr>
also note that until recently the raspberry pi foundation only supported 32 bit linux
<samueldr>
and their 64 bit support is still experimental
<zeta_0>
samueldr: i think my sd card has 4 gigs of memory, is that enough memory for my setup?
<samueldr>
storage space, unlikely to be enough, that's real tight
<zeta_0>
because for xmonad, gcc threw an out of memory error.
<samueldr>
but out of memory is different than out of disk space
<zeta_0>
samueldr: so will running nixos-collect-garbage -d every once in a while and setting the nix garbage collector service to do this once a month help keep my pi from running out of memory, because 4 gigs does not seem like much for an os like nixos on a pi.
<samueldr>
4GB of disk space is likely not going to cut it, even with garbage collection
<samueldr>
you would be hard pressed to fit two generations after a stdenv rebuild
<zeta_0>
samueldr: ok, well i guess i'm going to have to order another sd card soon.
<zeta_0>
samueldr: i ran raspbian on my pi for 6 months on my pi without any issues, so i don't see why nixos would give me issues, but ya a bunch of generations will hog up a lot of memory !
julm has quit [Remote host closed the connection]
julm has joined #nixos-aarch64
Ultrasauce has quit [Quit: Ultrasauce]
Ultrasauce has joined #nixos-aarch64
cole-h has quit [Ping timeout: 256 seconds]
cole-h has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
Thra11 has quit [Ping timeout: 260 seconds]
cole-h has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
zeta_0 has quit [Quit: rcirc on GNU Emacs 26.3]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
knerten1 has joined #nixos-aarch64
tilpner has quit [Ping timeout: 265 seconds]
knerten has quit [Remote host closed the connection]
sigtrm has quit [Quit: No Ping reply in 180 seconds.]
sigtrm has joined #nixos-aarch64
<colemickens>
maybe if I get administrative nonsense done today I'll come back to rpi4+uefi experiments.
Thra11 has joined #nixos-aarch64
<samueldr>
colemickens: I expect uefi+rpi4 to (at some point) just work, I guess the issues I had the last time were because I tried to boot of usb
<samueldr>
and lots changed since
<samueldr>
what I'd like to see is u-boot+rpi4, even with their kernel fork
<colemickens>
will uboot fit in rpi4 spi?
<samueldr>
probably not
<colemickens>
that would be appealing, maybe even more so than the uefi...
<samueldr>
I'm talking about a setup just like the raspberry pi 3
<samueldr>
IIRC the SPI is ridiculously small
* colemickens
nods
<samueldr>
but I agree, if they had put something like a 16MiB SPI for hacker's purposes, that would have been amazing
<samueldr>
it would have elevated the rpi4 from "don't bother" to "good"
<samueldr>
(I *really* dislike their custom boot chain, which is a form of vendor lock-in)
tilpner has joined #nixos-aarch64
* colemickens
nods
<colemickens>
at least there's Nix to bind all of the pieces together.
<colemickens>
In fact, I can't imagine trying to get something cohesive out the door without NIx, just in terms of managing patchsets, which uboot+kernels are compatible, et.c