ryantrinkle has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
FRidh has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
FRidh has quit [Quit: Konversation terminated!]
orivej has joined #nixos-aarch64
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has quit [Ping timeout: 246 seconds]
alj[m] has joined #nixos-aarch64
<alj[m]> Hello! I'm trying to get nixos to work on my ODROID-C1, can anyone help?
mthst has quit [Ping timeout: 246 seconds]
mthst has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 245 seconds]
sphalerite has quit [Quit: reboot time!]
sphalerite has joined #nixos-aarch64
sphalerite has quit [Quit: WeeChat 2.2]
sphalerite has joined #nixos-aarch64
<andi-> alj[m]: maybe state the error you are seeing :-)
jtojnar has quit [Ping timeout: 258 seconds]
<alj[m]> So I can't get it to boot. I'm trying to build the hardkernel u-boot sources right now, with no success so far
jtojnar has joined #nixos-aarch64
<alj[m]> I'm having trouble getting the right toolchain going. mainly i suffer from an issue regarding functions being defined more than once... but i have no idea how to fix that
<alj[m]> So my question is: How do I get it to boot?
<andi-> It sounds more like your question is how do you get the specific u-boot fork to build and then boot?
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-aarch64
tilpner has quit [Remote host closed the connection]
<samueldr> I have an ODROI-C1 (non plus) and IIRC you're forced to use hardkernel's fork from whatever older fork of u-boot it was
<samueldr> unless it changed in the ~year since I looked, the C1 will not be supported in u-boot mainline
tilpner has joined #nixos-aarch64
<gchristensen> "Thank you! I count on NixOS as a canary for all sorts of things - you are always fast on the uptake on new software, and also your test and build infrastructure is solid enough that if there is a problem generally you find it. All the other distros are super-laggy by comparison."
<clever> :D
<andi-> That case is very interesting.. I would never have thought that bind has platform dependent atomic code... (well had..)
<samueldr> andi-: was it the issue and/or my mention of it in #nixos-dev that got you looking?
<andi-> samueldr: you mentioning it
<samueldr> thanks
<samueldr> checking if what I did was useful
<andi-> I am very happy to do research into those topics.. Kinda fun. Just not always have the time to watch hydra / read issues
<samueldr> I usually check my hydra dashboard page daily or twice daily
<samueldr> which has tested, and the iso+sd for both main 64 bit platforms
<samueldr> among misc things
<andi-> I used to do that for a few months and then got kinda tired :/
<samueldr> don't know if I'll tire myself, but I don't get concerned until there's a new row of Xes
<andi-> I'll bookmark your dashboard that looks useful :-)
<samueldr> and I have a userstyle to make the timeouts more obvious
<samueldr> the more subdued red Xes are timeouts
<samueldr> those I generally ignore
<andi-> wouldn't an hour-glass or something fit better?
<samueldr> that's what I was thinking about
<samueldr> though I had a clockface in mind but I think that would be more about "queued" or something
<andi-> you could probably use a display: none, :before { text: .... } hack
<samueldr> or a PR to hydra
<andi-> yeah
<andi-> Maybe having some kind of notification into an IRC channel would be helpful? "Jobset release-19.03-small failed: tested timed out" or similar
<sphalerite> we used to get emails from hydra
<sphalerite> until one fateful day... :D
<samueldr> failure would easily become the new normal though :/
<samueldr> like we'd be used to seeing new_kernel fail for aarch64, so it'd be easy to miss the new x86_64 failure
<samueldr> iso_minimal_new_kernel*
<samueldr> heh, manual build is broken looks like
<andi-> mhmm maybe an i3 status bar entry wouldn't be too bad
<andi-> just for a few jobsets and polled infrequently
zupo has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
<alj[m]> <samueldr "I have an ODROI-C1 (non plus) an"> how did you do it?
<samueldr> I didn't
<samueldr> sorry for being a bummer :|
<alj[m]> oh. well thats fun :D
<samueldr> since it's armv7 it wasn't worth much effort imho
<samueldr> (due to the binary cache not having armv7 builds)
<samueldr> also, at that time I had less experience and wouldn't really have known how to boot on that older u-boot release
<samueldr> well, to boot nixos*
<alj[m]> well i have two of these boards now. i cant ship them back.
<alj[m]> i'll keep trying to get uboot to build under nix, because i kindof really need them to run nixos... if that doesnt work ill switch to ubuntu or something...
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
<gchristensen> samueldr: want to upstream your user style? :)
<gchristensen> oh not very accessible actually
<samueldr> exactly, it'd need more differentiation
<gchristensen> yeah
<samueldr> oh, and it would be better not to rely on the alt text, there's no i18n in hydra, but if there was it would fail (but yeah, trivial)
orivej has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 245 seconds]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]