justanotheruser has quit [Ping timeout: 240 seconds]
rajivr has joined #nixos-aarch64
<zeta_0>
hello, is anyone here, i need some help with an issue ?
<Jake[m]>
I'm here
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
<zeta_0>
Jake[m]: hello there, i'm having trouble getting nixos working on my raspberry pi 4, do you think that you'll be able to help me with this issue ?
<Jake[m]>
Yeah i actually think I can. I have a raspberry pi 4 myself with nixos on it
<zeta_0>
oh, that sounds good, the 1st link is the github repo that i used to build nixos, and the 2nd link explains my issue.
<zeta_0>
Jake[m]: what installation/build method did you use to put nixos on your raspberry pi 4 ?
t184256 has left #nixos-aarch64 ["Error from remote client"]
<Jake[m]>
I don't use HDMI on the raspberry pi though I don't know why it wouldn't work.
<Jake[m]>
I would build an image that had ssh enabled, plug it into your router, ssh into it and from there you can modify the configuration and run nixos-rebuild to recompile on the pi itself.
<Jake[m]>
Getting the display working gave me trouble.
<samueldr>
zeta_0: I haven't looked at the links yet, but are you using the raspberrypi 4 specific kernel and booting using the raspberry pi bootloader scheme?
<samueldr>
(rather than the aarch64 default of using u-boot)
<Jake[m]>
If you decide to do it the way I suggested, you should add services.openssh.enable = true; to the configuration, and while your at it you can add a public ssh key if you want with users.users.root.openssh.authorizedKeys.keys
<zeta_0>
samueldr: uh, i don't remember, i just followed the instructions on this github link, and added the changes corresponding to the raspberry pi 4, would you like me to pastebin any of the files, so you can see the changes that i made ? https://github.com/Robertof/nixos-docker-sd-image-builder
t184256 has joined #nixos-aarch64
<samueldr>
if you can pastebin the output of `git diff` it'd help
<samueldr>
I'm not familiar with that repo so I'm currently looking
<zeta_0>
Jake[m]: i'm pretty sure that, i already did those steps, but i did not connect my pi to my router, i just ran a nixos-rebuild switch and nixos-garbage-collect -d
<zeta_0>
samueldr: one second
<samueldr>
you made the image, then generated a new config on the pi, right?
<Jake[m]>
<zeta_0 "Jake: i'm pretty sure that, i al"> Wait were you connected to the pi? What machine did you run nixos-rebuild switch on?
<samueldr>
and rebuilt that config, and *that* config gives you the cursor, right?
<samueldr>
is the configuration on the raspberry pi using : boot.kernelPackages = pkgs.linuxPackages_rpi4;
<Jake[m]>
Oh I understand, my bad. Connecting to the router will just give you a way to fix whatever you did without reflashing if all you did was mess up the display.
<zeta_0>
hold on, before i answer your questions let me paste bin the output of `git diff` in that cloned github repo.
<zeta_0>
samueldr Jake[m]: sorry that i took so long, here's the output of the `git diff`: https://dpaste.org/Fh5e
<samueldr>
alright, so I figure that this image boots fine, right?
<samueldr>
if so, it is inconsequential that it came from Robtertof's docker tooling
<zeta_0>
Jake[m] samueldr: i built the image from the github repo, then dd'd the image on the sd card, then put it in the pi, then i ran nixos-rebuild switch on the pi.
<zeta_0>
i'm thinking maybe i should start over, maybe i missed something or made a mistake.
<samueldr>
we'll need the configuration.nix you rebuilt into on the pi
<samueldr>
since it's likely there that the issue lies
<zeta_0>
samueldr: is there easy way to wirelessly remote into the pi with a laptop, that way i can copy the configuration.nix code into my laptop and paste bin it ?
<samueldr>
mount the ext4 partition of the pi on your computer
<samueldr>
you can read it :)
<Jake[m]>
Yeah it's not clear it's even turning on so that's not gonna fly
<zeta_0>
there's a lot of code on there, i need to copy it, i actually manually typed out the nix code on the pi, which was very time consuming and painful, the letters were small and the brightness was hurting my eyes.
<zeta_0>
hold on, let me figure out how to get onto the terminal 1st.
<zeta_0>
i'm going as fast as i can, thanks for having patience.
<Jake[m]>
<zeta_0 "there's a lot of code on there, "> Oof that sounds really hard. Next time if you connect to the internet you can copy it over without typing.
<zeta_0>
Jake[m]: ya, that's a much better way to do it.
<samueldr>
or use a usb drive to copy the files over :|
<samueldr>
that must have been painful to copy
<zeta_0>
ok, `alt+f2` brought me to the nix-pi login screen, let me try to sign into the terminal.
<zeta_0>
damn, i can't sign into su, is there another keyboard shortcut to get into `root` ?
<zeta_0>
i was procrastinating doing this stuff because i knew that it would be painful to setup.
<Jake[m]>
Wait you used su or root as the user name?
<zeta_0>
Jake[m]: root
<zeta_0>
and i made it into root finally
<zeta_0>
whew
<zeta_0>
ok, now i'm going to take the sd card out of the pi, and place it into my laptop with my usb adapter.
<samueldr>
though, since you had root login working, I figure that means that the kernel is okay, since it booted in a way where you could login into the root account on the console
<Jake[m]>
Wait if you're able to login on the pi it's fine.
<samueldr>
so it must be something about how your gnome is starting (or failing to start)
<samueldr>
(if I understand the problem)
<samueldr>
depending on the display manager, you should try to find out its logs
<zeta_0>
yeah the `nixos-rebuild switch` command worked on the pi without any errors, that's why i figured it was something else.
<zeta_0>
i initially tried with xmonad, but it through an alsa-mixer is not compatible with aarch64, i then tried the default plasma config that was already there, and it stayed stuck compiling, maybe a should have waited longer, but it was already compiling for 4 hours.
<zeta_0>
typo: threw, not through.
<samueldr>
yeah, some of the packages sometimes end up not being able to build due to misallocation of resources on Hydra :/
<samueldr>
(maybe not misallocation, but something close)
<zeta_0>
well, what apps are you guys using for your desktop environment for nixos on your raspberry pi 4, Jake[m] is usin pi 4, but i'm not sure what samueldr is using.
<samueldr>
I'm not using a raspberry pi 4 graphically at all
<Jake[m]>
Neither am I, sorry if said something confusing
<samueldr>
though on my pinebook pro (another aarch64 machine) I use X11 and awesome, a big ball of messy configs, no real desktop environment
<Jake[m]>
On my pinebook pro I use swaywm on Wayland
<samueldr>
in theory, it could work just as well as x86_64, but in practice it depends on upstream software support (is the thing you intend to run able to, even outside NixOS, run on aarch64), and then there's the cached build availability that sometimes is hit or miss
* colemickens
wants nixos 2 for cheap nixos-powered aws graviton spot instances for aarch64 build power
<colemickens>
s/nixos/nixops
<zeta_0>
ok, i'll try out the other window managers that you recommended.
<samueldr>
colemickens: leaving the end-user in charge of the spotty cache is a failing of the NixOS project!
<Jake[m]>
"zeta_0" (https://matrix.to/#/@freenode_zeta_0:matrix.org): I think you already got past most of what's in that link
<Jake[m]>
All you're missing is the window manager right?
<colemickens>
samueldr: aww, do we really have big problems with aarch64 coverage? Do we just lack build power?
<samueldr>
colemickens: misallocation mostly, rather than lack of build power AFAIK
<colemickens>
samueldr: for the most part I've largely only needed it for fairly esoteric personal stuff
<samueldr>
ah, then it's fine
<samueldr>
but we don't cover -stable properly, I think
<samueldr>
not sure though
<zeta_0>
Jake[m]: i think so, i'm not sure.
<zeta_0>
Jake[m]: the configuration.nix code on those other instructions are a little different, so i thought i'd take a look.
<samueldr>
colemickens: the main issue I see is things like firefox end up being built on a machine that is already loaded with other trivial and less trivial builds, which ends up causing a ~1h build to fail after more than 4h
<zeta_0>
well for now, i'll try out different window managers.
<samueldr>
colemickens: that's the main misallocation I've seen, which a system like TAGS as described by g//christensen would help
* colemickens
nods, I saw your comment on graham's idea for addressing that I think
<samueldr>
zeta_0: if you see a white cursor flashing, it's likely not the WM, but the display server, either X11 or wayland (?)
<samueldr>
so if e.g. it was X11, I'd expect anything running on X11 to fail the same way
<samueldr>
colemickens: though I guess a quick win could be trivial, reserve one machine for non-trivial builds, one at a time
<samueldr>
colemickens: mark non-trivial builds as non-trivial only
<samueldr>
but my experience with Hydra and how it relates to distributing jobs is lacking just enough that I don't really know what to do
<zeta_0>
i'm using X11, so i'm guessing that might be the issue.
<samueldr>
you'd have to find out which service provides the display manager, then get its logs to know what failed
<samueldr>
trying anything hapazardly is like playing whack-a-mole blindfolded
<samueldr>
with the logs you're (hopefully) going to have something that may point toward the problem
<samueldr>
if it's lightdm, it's somewhere under /var/log
<samueldr>
I believe all other display managers logs to the system journa;
<samueldr>
journal*
<zeta_0>
samueldr: ok, i'm going to comment out gdm and rebuild, so it will default from lightdm, if it still does not work, then i'll try out plasma or another window manager.
<samueldr>
hmm, isn't gdm using wayland?
<samueldr>
(or is that still not done in NixOS?)
<zeta_0>
i have no idea. i use xmonad on my laptop, so i don't know anything about gdm or wayland.
<samueldr>
you might be able to see the issue by using (as root or using sudo) journalctl -b0 --unit gdm or journalctl -b0 --unit display-manager
<Jake[m]>
<samueldr "hmm, isn't gdm using wayland?"> I think it can but I couldn't get it working But you also don't need a login manager to run sway you can just exec sway after logging in (that's what I do)
<samueldr>
Jake[m]: yeah, I really meant *gdm* is using wayland, not that wayland has to use a display manager :)
t184256 has left #nixos-aarch64 ["Error from remote client"]
zeta_0 has quit [Ping timeout: 264 seconds]
<Jake[m]>
<samueldr "Jake: yeah, I really meant *gdm*"> Oh yes. Haha I read it and after struggling and failing to get the gnome login manager working, I was sure that's what you were talking about.
t184256 has joined #nixos-aarch64
zeta_0 has joined #nixos-aarch64
<zeta_0>
Jake[m] samueldr: when i unplugged the ethernet cable, to connect it to the pi, i got kicked off irc, but i'm back.
<zeta_0>
that change made some progress, it's not stuck on a blank screen with a cursor, now X11 throws the error: `failed to start x11 server, see systemctl status display-manager.service for details`
<samueldr>
that's kind of a good sign
<zeta_0>
samueldr: thanks for pasting the logs.
<samueldr>
if it's lightdm, you'll have to fish under /var/log for the logs
<zeta_0>
ok, i'll run the systemctl command 1st, to see what that returns, then i'll look in /var/log, like you recommend.
<zeta_0>
samueldr: ok, so i'm in /var/log/lightdm, and i'm looking the the lightdm.log file.
<samueldr>
the X something file next to it might be more helpful, searching for (EE) in it should reveal X11 errors
<zeta_0>
samueldr: ok, i'm looking in x-0.log, there's a lot of stuff in there, [looking for EE]
<samueldr>
you can include the parens
<samueldr>
X11 "tags" messages with (XX), where XX depend on the log level, EE for errors
<zeta_0>
samueldr: ok, i found some EE's and they are throwing errors, give me one second to type them out.
t184256 has left #nixos-aarch64 ["Error from remote client"]
<zeta_0>
samueldr: (EE) open /dev/dri/card0, no such file or directory, do devices detected, fatal server error, no screens found, please also check the log file at /var/log/X.0.log for additional information, server terminated with error (1) closing log file.
<zeta_0>
so i guess i'll now look in: `/var/log/X.0.log`, to see what's in there.
<zeta_0>
samueldr: in `/var/log/X.0.log`, there's more (EE) errors, and there's also red parts, which might be important ?
t184256 has joined #nixos-aarch64
<samueldr>
I couldn't say for sure
<zeta_0>
samueldr: thanks, for the help, i give up for now and will continue with this some other time.
<samueldr>
a tip for next time
<zeta_0>
samueldr++ Jake[m]++
<{^_^}>
Jake[m]'s karma got increased to 1
<{^_^}>
samueldr's karma got increased to 257
<samueldr>
figure out a way to get connected via ssh
<samueldr>
less manually typing things out
<zeta_0>
samueldr: ok, thanks for the tip.
<zeta_0>
later guys, thanks again for the help.
veleiro has joined #nixos-aarch64
pbb has quit [Remote host closed the connection]
pbb has joined #nixos-aarch64
zeta_0 has quit [Quit: rcirc on GNU Emacs 26.3]
alp has joined #nixos-aarch64
veleiro` has joined #nixos-aarch64
veleiro has quit [Ping timeout: 265 seconds]
orivej_ has quit [Ping timeout: 260 seconds]
alp has quit [Ping timeout: 272 seconds]
alp has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
t184256 has left #nixos-aarch64 ["Error from remote client"]
t184256 has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
alp has joined #nixos-aarch64
FRidh has quit [Ping timeout: 258 seconds]
FRidh has joined #nixos-aarch64
FRidh has quit [Ping timeout: 265 seconds]
FRidh has joined #nixos-aarch64
Dezgeg has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
FRidh has joined #nixos-aarch64
veleiro`` has joined #nixos-aarch64
alp has quit [Remote host closed the connection]
alp has joined #nixos-aarch64
veleiro` has quit [Ping timeout: 265 seconds]
veleiro`` has quit [Ping timeout: 240 seconds]
t184256 has left #nixos-aarch64 ["Error from remote client"]
t184256 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Thra11>
samueldr: I notice the device page on mobile.nixos.org and the device directory in the repo refer specifically to the braveheart edition of the pinephone. Do you expect there to be any changes required for later revisions?
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
v0|d has quit [Remote host closed the connection]
Darkmatter66 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
alp has quit [Ping timeout: 244 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
alp has joined #nixos-aarch64
<sphalerite>
holy crap, my NAS can finally reboot
<sphalerite>
only weeks before I get my helios64 xD
<Ke>
wonder if I should get it too
<sphalerite>
well they're starting to ship this week
<sphalerite>
I wonder if the order numbers are serial
<sphalerite>
mine is 3963
<Ke>
I guess they will still sell it later on too
<sphalerite>
they're going through them in the order received
<Ke>
yup
<sphalerite>
once I get it I'll make sure to report my experience here :)
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<leonardp>
sphalerite: do you know which ARM SoC is inside the helios64
<leonardp>
rk3399... didn't find it on their homepage, google helped 😪
<jasom>
samueldr: saw you have a pine64 pro in scrollback; how is X11 support on it? I have an odroid-c2 and couldn't even get the modeswitching driver to work, so I'm stuck on fbdev which is dog-slow.
<samueldr>
panfrost modesetting has light issues, but generally works
<samueldr>
pinebook pro, rk3399
<samueldr>
issues might be resolved with a mesa upgrade to whatever they call their in-development branches
zupo has quit [Ping timeout: 240 seconds]
<jasom>
maybe; the weird thing is the drm driver loads and i have devices in /dev/dri but Xorg gives me a "no devices" error when I try using modesetting
<samueldr>
that's amlogic
<jasom>
still way better than 2 years ago when you needed to use amlogic's patches against 3.0
<samueldr>
I wonder which driver should be used
<samueldr>
and if it is enabled in our config
<jasom>
of course the project for getting amlogic in mainline kernel was called "meson" which is also the name of an xorg build system so googling for the two together is not particularly useful
<srk>
I've had to add few options to make modesetting work on imx6 - https://paste.rs/Hjn
<jasom>
srk: thanks I'll try messing with that.
<samueldr>
jasom: zgrep /proc/config.gz DRM_MESON
<samueldr>
oops
<samueldr>
other way around
<samueldr>
looks like they're built
<samueldr>
though I'm not sure that's the right one for you
bennofs__ has joined #nixos-aarch64
bennofs_ has quit [Ping timeout: 240 seconds]
alp has quit [Ping timeout: 272 seconds]
zupo has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
justanotheruser has quit [Ping timeout: 240 seconds]
justanotheruser has joined #nixos-aarch64
FRidh has quit [Quit: Konversation terminated!]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
quinn has joined #nixos-aarch64
alp has joined #nixos-aarch64
alp has quit [Ping timeout: 240 seconds]
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…]