<angerman>
samueldr: that looks a tad bit saber. It still makes me question this whole computer business.
cole-h has joined #nixos-aarch64
orivej has quit [Ping timeout: 265 seconds]
orivej has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 246 seconds]
h0m1 has joined #nixos-aarch64
orivej has quit [Ping timeout: 264 seconds]
veleiro has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 240 seconds]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
adamzivcak has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
adamzivcak has quit [Client Quit]
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Ping timeout: 260 seconds]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
cole-h has quit [Ping timeout: 246 seconds]
zupo has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 256 seconds]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 260 seconds]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<angerman>
can I ask nix for the kernel config it ended up using?
<qyliss>
angerman: the kernel package has a "configfile" attribute
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
<angerman>
Thanks. I’m trying to figure out which config makes the mmc work :)
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<angerman>
meh... so something with the device tree is causing the issue booting from the emmc.
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
orivej has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
Darkmatter66 has joined #nixos-aarch64
<patagonicus>
Yikes. I added build dependencies to my HC2 images so they can install things without having to rebuild everything from scratch and that changed the size of the image from <3GB to 12GB. Oh, well, guess it makes sense (and in the general case I won't need it since it's mostly for migrating/replacing a single machine so it can just fetch the stuff
<patagonicus>
from the other three).
<angerman>
Alright, I think I’m going to try and use Armbian kernels instead, this is not going anywhere productive.
<colemickens>
pxe/tftp being slow, is that pxe's fault or tftp's fault? I think it's tftp, but if so, why does u-boot not support loading over http in addition to tftp?
<colemickens>
I guess I could send grub2 over instead of uboot, grub2 can load over http
fooker has quit [Ping timeout: 260 seconds]
fooker has joined #nixos-aarch64
zupo has joined #nixos-aarch64
adamzivcak has joined #nixos-aarch64
adamzivcak has quit [Ping timeout: 246 seconds]
<LinuxHackerman>
colemickens: yeah I think it's tftp. I think ipxe might be a better choice than grub for that.
<LinuxHackerman>
though it's a couple years back that I last used grub for network booting
<colemickens>
ipxe seems like a ratsnest for aarch64 though.
<colemickens>
I think I've got a good plan to test tomorrow.
Darkmatter66 has quit [Ping timeout: 240 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
<LinuxHackerman>
oh, I missed that this is aarch64. I still have more confidence that it would work than grub though :)
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
tilpner has quit [Quit: tilpner]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
tilpner has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<clever>
LinuxHackerman: wrong nick on the irc client? different from usual
<LinuxHackerman>
clever: this is my matrix identity :p
<sphalerite>
clever: I'm still sphalerite on the other side
<clever>
ahhh
sds2 has quit [Client Quit]
<clever>
dont see the matrix side talking much, so it stood out as diff
sds2 has joined #nixos-aarch64
<Asmadeus>
colemickens: ipxe supports http which is said to be much faster for pxe boot
<Ke>
I guess noone got any honeycomb-news
<gchristensen>
Asmadeus: tftp has a theoretical maximum transfer speed of, like, less than 2MBytes/s
<delroth>
anyone here using NixOS on a Honeycomb LX2K board? wondering if there's anything I should be looking at re: kernel compatibilty, bootloader support, etc.
srk has quit [Remote host closed the connection]
srk has joined #nixos-aarch64
<LinuxHackerman>
delroth: thefloweringash has been for a long time now, and a couple more of us have LX2Ks on the way which we plan to use nixos on
<delroth>
I'll see what I can do to update it to latest software versions
srk has quit [Remote host closed the connection]
srk has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
cole-h has quit [Client Quit]
cole-h has joined #nixos-aarch64
<patagonicus>
Hmm. Tried building the 5.4.y odroid kernel, but I just get a "[../Makefile:179: sub-make] Error 2"
<samueldr>
check the logs, the actual error could be hundreds of lines up
<samueldr>
using `nix log`, which uses `less`, I usually search for `error:` (including the colon)
<samueldr>
most compiler errors will include `error:` at the start
adamzivcak has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<patagonicus>
Ah, good idea. Looks like it's not finding a file. Maybe it's one of the patches I just copied from the 4.* version.
<patagonicus>
No, they just change some binary paths that the kernel uses while running.
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
<patagonicus>
It's something mali GPU drivers and the HC2 doesn't have any graphics, so I just need to figure out the right config option to disable. ¯\_(ツ)_/¯
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zarel has quit [Ping timeout: 264 seconds]
zarel has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
ekleog_ is now known as ekleog
<gchristensen>
reboot? ok
zupo has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
adamzivcak has joined #nixos-aarch64
adamzivcak has quit [Ping timeout: 246 seconds]
<hexa->
and again I'm building basic stuff like nss on my rpi4b
<hexa->
i'm on nixos-20.09
<hexa->
actually it's been building stuff for 17 hours now
<gchristensen>
I don't suppose you'd be interested in helping make some weird aarch64 hardware boot nixos?
<gchristensen>
we can extend our aarch64 capacity significantly if we can get them going
<hexa->
I'm not very familiar with aarch64 besides running it on my rpi
<hexa->
last I heard you guys were bisecting nixos 20.03?
<Ke>
thefloweringash: do you use gpu like radeon and what is the latest kernel you have used
<gchristensen>
yeah
<gchristensen>
I think the 20.03 issue was solved, but that wasn't the weird hardware
<hexa->
oh boy
<gchristensen>
the weird hardware is hardware of which approximately 1 rack worth was manufactured
<hexa->
with what flaw?
<gchristensen>
I don't think there was a specific flaw, just that it was a pre-release run
<hexa->
but it's not booting? :)
<gchristensen>
it might be a trivial issue
<Ke>
I guess that repo uses linux-4.19
<hexa->
I have little knowledge of uboot, hardware bringup etc., not sure what I could contribute
adamzivcak has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
<sphalerite>
gchristensen: I'm intrigued, but not sure whether I can contribute much useful effort
<sphalerite>
I'm more or less out of ideas for the thunderx
<sphalerite>
definitely willing, just doubting on the able front :D
<samueldr>
did we at least re-configure the hydra builders to use the working older kernel?
<LinuxHackerman>
yes
<gchristensen>
reboot? ok
<sphalerite>
actually that gives me one more idea: try a _newer_ kernel
adamzivcak1 has joined #nixos-aarch64
<samueldr>
good thinking, we're about to get an LTS
adamzivcak2 has joined #nixos-aarch64
adamzivcak2 has left #nixos-aarch64 [#nixos-aarch64]
adamzivcak1 has quit [Ping timeout: 240 seconds]
<sphalerite>
oh, it works better! Though not well, by the looks of it :/
<sphalerite>
wait, wtf.
<sphalerite>
no. Why.
<sphalerite>
the kernel takes a lot longer to pass on to the initramfs, and… it still hangs up like that
<sphalerite>
my next idea is bisecting the kernel, but that'll be, uh, fun…
<samueldr>
at least manually pick which stable .0 release introduced the issue
<samueldr>
before goint all git bisect
<sphalerite>
yeah that's the idea
ryantrinkle has quit [Ping timeout: 240 seconds]
<gchristensen>
reboot? ok
Darkmatter66 has joined #nixos-aarch64
<hexa->
yeah, that doesn't sound like me
<hexa->
LinuxHackerman++
<{^_^}>
LinuxHackerman's karma got increased to 4
<hexa->
sorry, sounded more appropriate than giving praise to sphalerite
<sphalerite>
hehe
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
<sphalerite>
how do I consolidate my identity…
<gchristensen>
reboot? ok
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<hexa->
by rebooting
<gchristensen>
there you go
ryantrinkle has joined #nixos-aarch64
<sphalerite>
ha! Latest alpine does the hanging thing too
<hexa->
:o
<hexa->
it's not us then!
<patagonicus>
Another file not found for an include? I wonder if odroid is doing weird things with the 5.4 kernel.
<patagonicus>
Also means I can rebuild again. Sigh. Maybe I should try building outside of nix first, but since it's late I'll just add a config option for the broken module and let it run over night for now.
<gchristensen>
reboot? ok
Darkmatter66 has quit [Quit: ZNC 1.7.5 - https://znc.in]
<patagonicus>
Ah, hmm. The include is <osdep_service.h> and that file is available in ../include relative to the file including it. So, maybe some nix build related thing?
Darkmatter66 has joined #nixos-aarch64
<samueldr>
patagonicus: yes they are doing weird things if it's not mainline
<patagonicus>
Well, I knew that much, but I'm curious why random stuff is breaking that's not related to their hardware. :D
<samueldr>
and in this case, it's their build that is bad if they do the thing where they assume headers at are -I :)
<samueldr>
possibly incomplete backports
<samueldr>
and tested stricly only with their own defconfig
<patagonicus>
Ah, possible.
<patagonicus>
Interesting. It looks like the commit that added the driver also added it to their defconfig, so I suspect they build it. But that also means that it's probably not a pure mainline kernel.
<patagonicus>
Also, sigh, they commited a .gitignore in the driver directory.
<samueldr>
vendors gonna vend
<patagonicus>
Yeah, I don't feel bad disabling this module. I hope at least their kernel config option actually disables it.
<samueldr>
if it's header lookup with <> you should rather patch it
<patagonicus>
When I have some more time (so either if I get bored at work, on the weekend or maybe when my vacation starts).
<patagonicus>
But, yeah, if I can fix it without too much work I'll do that.
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 240 seconds]
adamzivcak has joined #nixos-aarch64
<sphalerite>
gchristensen: so what's the current status of the weird machines?
<gchristensen>
unsure :) want access?
<sphalerite>
sure :D
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
<gchristensen>
cool, I can do that tonight
<gchristensen>
reboot? ok
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<gchristensen>
reboot? ok
<gchristensen>
reboot? ok
<gchristensen>
reboot? ok
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<sphalerite>
hm ok I've tried debian, alarm and alpine. None of them have a working kernel ≥ 5.4.
<sphalerite>
It would be really good to get a hold of the tree and config used for packet's alpine :(