red[evilred] has quit [Quit: Idle timeout reached: 10800s]
<angerman>
samueldr: yea. I just have no idea what to do about it :-)
<angerman>
samueldr: I guess I could try a usbc eth dongle, but that might end up using the same driver again.
cole-h has quit [Ping timeout: 260 seconds]
<patagonicus>
I should really figure out why my system builds git just to download the odroid-xu3-bootloader source from Github. I already have git installed and the package is just using fetchFromGitHub.
<clever>
patagonicus: is it fetching submodules?
<clever>
fetchFromGitHub lacks submodule support, it will transparently switch to fetchgit when enabled
<patagonicus>
Ah, maybe. There's no submodules in the root as far as I can tell, but let me check.
<clever>
its less about whats in the repo, and more what args you passed to fetchFromGitHub
<patagonicus>
Then no. Just owner, repo, version and sha256.
<clever>
patagonicus: run nix-store -q --tree, on the .drv that your building, and then search it for the git it wanted to build
<patagonicus>
And, once again, things work better if you do them right. Now that I've managed to correctly install the bootloader on this microsd card, it actually boots. :)
adamzivcak has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
sds2_ has joined #nixos-aarch64
sds2 has quit [Ping timeout: 272 seconds]
sds2_ is now known as sds2
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
zupo 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
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
adamzivcak1 has joined #nixos-aarch64
adamzivcak has joined #nixos-aarch64
adamzivcak1 has quit [Ping timeout: 246 seconds]
zupo has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
adamzivcak has left #nixos-aarch64 [#nixos-aarch64]
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
justanotheruser has quit [Ping timeout: 272 seconds]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
DigitalKiwi has quit [Quit: quite.]
DigitalKiwi has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Remote host closed the connection]
alpernebbi has joined #nixos-aarch64
<sphalerite>
red[evilred]: any news from solidrun?
sds2 has joined #nixos-aarch64
<sphalerite>
oh, you got a dispatch date, I missed that
<sphalerite>
gchristensen: any news on the weird machines? I'll also continue trying to fix the thunderxes if you set up the reboot script again :)
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
<gchristensen>
reboot? ok
<gchristensen>
sphalerite: ^ I can get weird ones later today!
<sphalerite>
oh wait it might be booting from disk where i might have installed an ubuntu for $reasons >_<
<gchristensen>
ssh 74d546a1-7f1f-46b2-b271-263ad0474495@sos.ewr1.platformequinix.com should be your netboot
<sphalerite>
if it's booting from disk I'll just wipefs it and see if it starts netbooting again
<gchristensen>
it is set to alays boot from ipxe
<gchristensen>
back in a bit
<sphalerite>
well I've destroyed the ubuntu so it should hopefully start netbooting again ^^
<sphalerite>
`yep that fixed it
<gchristensen>
cool
<gchristensen>
though, it should have booted to ipxe anyway
<gchristensen>
the "always ipxe" is supposed to override the disk always
<sphalerite>
:/
<sphalerite>
oh, did you only just set it when I said that?
<gchristensen>
reboot? ok
<sphalerite>
!! nixpkgs-built kernel with ubuntu config is working!
justanotheruser has joined #nixos-aarch64
<sphalerite>
next steps: enable IKCONFIG, rebuild, test, compare.
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
<gchristensen>
reboot? ok
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
sds2 has quit [Ping timeout: 264 seconds]
monk has joined #nixos-aarch64
sds2 has joined #nixos-aarch64
cirno-999 has quit [Ping timeout: 256 seconds]
cirno-999 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
<gchristensen>
sphalerite: can you make a new key for me? ... otherwise I need to revoke that key I added already .....
<gchristensen>
also for these new machines I can't do anything but add your ipxe url -- they have no support for alpine :/ but I have it on good authority that the old-old kernel we were finding success with worked on them. this weird hardware is called 2a5
zupo_ has joined #nixos-aarch64
<sphalerite>
gchristensen: alright, can you give it a different URL so I can continue the thunderx hacking? Maybe /2a5.ipxe
<gchristensen>
yep
<gchristensen>
can you send me a different public key?
<sphalerite>
gchristensen: or maybe you can invite me to the "project"/"workspace"/whatever it's called? I have a packet.com account which I assume is still usable on equinix
<gchristensen>
'irc.freenode.#nixos-aarch64 *reboot? ok' > ~/.weechat/weechat_fifo); old="$new"; done) which does a reboot / sentinel device? :)
<sphalerite>
yeah will do
sds2 has joined #nixos-aarch64
<gchristensen>
thanks I started to and then got to the loop part and then I had babyhands
lopsided98 has quit [Quit: No Ping reply in 180 seconds.]
lopsided98 has joined #nixos-aarch64
<gchristensen>
I might be able to sort it
<gchristensen>
nope
<samueldr>
sphalerite: sorry, those changes relevant to me how?
sds2 has quit [Quit: sds2]
alpernebbi has quit [Quit: alpernebbi]
sds2 has joined #nixos-aarch64
ornxka has quit [Ping timeout: 240 seconds]
ornxka has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
monk has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
<sphalerite>
samueldr: because mobile-nixos does a lot of initramfs things and uses cross-compilation. Though I'm not sure, maybe you don't use makeInitrd at all :)
<samueldr>
I don't recall if i uses the upstream NixOS one still
<samueldr>
if it uses*
<samueldr>
thanks
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
unclechu has joined #nixos-aarch64
<unclechu>
hey, can you tell if i can install nixos on my raspberry pi 1?
<samueldr>
kind of, but not in the most useful manner
<samueldr>
the main issue being that it lacks a binary cache for prebuilt derivations
<samueldr>
then, since you need to build for armv6, you either need to cross-compile, or build on native hardware
<samueldr>
the latter being mostly prohibitive as native hardware has memory and speed limitations
<unclechu>
samueldr: i’d like to build it locally on my x86_64 machine and then just upload the ready-to-use image to the pi
<samueldr>
cross-compilation it not totally working fine, but issues are not specific to the raspberry pi (1)
<samueldr>
I haven't tested it for a small while, but other users reported successes still
<samueldr>
this should contain all workarounds needed by september 12th
monk has left #nixos-aarch64 ["Error from remote client"]
<unclechu>
samueldr: so about this `cross-system` repo. do i get it right, i can build locally all that i need and then just upload the produced image to an sd card?
<samueldr>
yep, this cross-compiles the usual sd cards from Nixpkgs
<unclechu>
say i just patch `configuration.nix` with the options i need and then run `./build.sh --argstr system armv6l-linux`?
<unclechu>
at least it sounds simple. thanks, let me try it
<samueldr>
and yeah, you could add to configuration.nix; but note that the default sd images from Nixpkgs make it an installer image
<samueldr>
automatic login
<samueldr>
forced users creation
<samueldr>
you might want to further customize, but those customizations are not really specific to cross-compilation
<unclechu>
samueldr: it looks like it builds an installer and i can do anything else from inside the pi?
<samueldr>
you "could", but it comes back to the problem of native builds and there not being any binary cache
<samueldr>
so the first rebuild on-device would be native and start from scratch
monk has joined #nixos-aarch64
<unclechu>
samueldr: can i run such an image locally in a VM or QEMU to test it locally first?
<samueldr>
maybe
<samueldr>
I've never had success when I tried a few years back, but things changed
<samueldr>
(and I probably didn't understand it enough to actually know what failed at that tim)
<samueldr>
time*
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<sphalerite>
unclechu: have you used NixOS on other devices before? If not, I'd strongly recommend doing that to get a feel for it, rather than going the most painful possible route right from the get-go :D
<unclechu>
sphalerite: i’m using it right now
<unclechu>
otherwise i wouldn’t dare for such a journey
<sphalerite>
good :)
<sphalerite>
running it on hardware is probably easier than running it in a VM.