orivej has joined #nixos-aarch64
efraim has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
efraim has joined #nixos-aarch64
<samrose> Dezgeg: do you think that https://github.com/NixOS/nixpkgs/blob/release-18.09/nixos/modules/installer/cd-dvd/sd-image-aarch64.nix would build on qemu-system-aarch64 ?
<samrose> (I am going to try it now on raspberry pi 2)
<Dezgeg> it should work on qemu-system-aarch64 but it won't work on RPi 2
Thra11 has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 268 seconds]
Thra11 has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 252 seconds]
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 268 seconds]
lopsided98 has quit [Ping timeout: 252 seconds]
lopsided98 has joined #nixos-aarch64
<samrose> Dezgeg: hmm is there a supported machine it will work on? https://wiki.qemu.org/Documentation/Platforms/ARM#Supported_in_qemu-system-aarch64
<samrose> hmm. I don't kno what's going on yet but I am getting much further on this qemu-system-aarch64 using 'rpi2' than I did building on the actual bananapi m64 ...
<samrose> my guess is these modules that failed to load because they are not intended to be used with the aarch64 hardware: https://gitlab.com/snippets/1777334/raw
<samueldr> (404)
exarkun_ has quit [Quit: ZNC 1.7.1 - https://znc.in]
exarkun_ has joined #nixos-aarch64
<samrose> samueldr: oops sorry now it's public https://gitlab.com/snippets/1777334/raw
<samueldr> I really don't know what you're trying to achieve (maybe I missed a previous discussion related)
<samrose> samueldr: yes I am trying to use that command. I am trying to run the command in a machine running in qemu-system-aarch64. My goal in running it is to build an image that uses 4.19 kernel since you all mentioned these are stuck at 4.18.x https://www.cs.helsinki.fi/u/tmtynkky/nixos-arm/installer/
* samueldr is waiting on a repo update locally to check something
<samrose> if I can achieve building sd-image-aarch64-linux.img with 4.19 then I may be able to finally install on bananapi m64
<samueldr> though I must say I'll be executing the command on my pine64, which runs on aarch64, if it changes anything
<samrose> samueldr: I did get this command to execute on bananapim64 but it failed to build an image
<samrose> the build I just did on qemu-system-aarch64 made it much further, but it failed with https://gitlab.com/snippets/1777336/raw
<samrose> samueldr: I would of course love to know anything you learn about running it on pine64 in any case :)
<samueldr> hm, haven't customiser the file for 4.19, and running the nixos-18.09 one, right now
<samueldr> customied*
* samueldr restarts
<samueldr> one thing to learn: it'll take a good while until I knoew if it works :)
<samrose> samueldr: the only reason I was looking at 4.19 was due to the simple_fb issue I had a couple of weeks ago
<samueldr> first I'll build without customizing, see if it should work stock
* samueldr thinks
<samrose> yes, the good while issue was the other reason I was trying to see if I can speed up the build time by having more resources available
<samrose> ...by using qemu-system-aarch64
<samrose> (and throwing more ram and disk space at it)
sigtrm has quit [Ping timeout: 276 seconds]
sigtrm has joined #nixos-aarch64
<samueldr> samrose: what's your diff/patch for 4.19 in the image, default, stock, it built for me
<samueldr> (I want to try it the same way you are, just in case)
<samueldr> hmmm, no need to say anything
<samueldr> Copying g02rjp51wplrp7dl0a2gkr2rhd2353v8-linux-4.19.1-Image
<samueldr> without touching anything, since it's pkgs.linuxPackages_latest, it built using 4.19
<samrose> samueldr: ah ok. I am not sure on the build I did on the actual bananapim64, but on on qemu it is as you posted above
<samueldr> when you said "rpi2" earlier, what did you mean by that?
<samueldr> that you started qemu-system-aarch64 using its "raspi2" "machine"?
<samrose> yes, one of the supported platforms is rpi2 samueldr https://wiki.qemu.org/Documentation/Platforms/ARM#Supported_in_qemu-system-aarch64
<samueldr> if so, it probably means something different than either building on or for the raspberry pi 2
<samrose> chances are using that platform may have been my issue
<samueldr> AFAIUI, this sets QEMU with a couple default parameters, so uh, it could work
<samueldr> as long as it's qemu-system-aarch64 and not qemu-system-arm
<samueldr> not sure if those instructions work for qemu-system-aarch64, https://nixos.wiki/wiki/NixOS_on_ARM/QEMU
<samrose> yes, it's weird that qemu-system-aarch64 lists "rpi2" as a supported platform
<samueldr> yeah, looks like it "only" sets up parameters
<samueldr> and the raspi3 config seems to be the exact same
<samrose> samueldr: when you ran the https://github.com/NixOS/nixpkgs/blob/release-18.09/nixos/modules/installer/cd-dvd/sd-image-aarch64.nix#L2 on pine64 you used the release-18.09 branch yes?
<samueldr> nope, *-unstable
<samrose> ok
<samrose> I will try this later tonight or tomorrow on the bpi64 hardware. I was using a fork and branch of my own from my efforts to do u-boot buld
* samueldr starts the equivalent build on nixos-18.09
<samrose> *build
<samueldr> though I think the kernel will be 4.18 without patches
<samrose> I think you are right
<samueldr> unless someone backported 4.19... I really need to ask the one doing the updates about that
<samrose> samueldr: you are also the release manager of 18.09 yes? (just asking in general I thought I saw that somewhere)
<samueldr> yes :)
<samueldr> it's not an issue yet, but will be once 4.18 isn't maintained anymore, as it _latest then would be either an unmaintained, or downgraded (at that point it'll be a big issue)
<samueldr> my main issue is to synchronize thoughts with the human doing the updates to all branches :)
<samueldr> (and AFAIK they're not on IRC)
<gchristensen> seems to me _latest should stay latest
<samueldr> exactly
<gchristensen> nequissemes (sp?) sometimes gets on IRC
<samueldr> never caught 'em on IRC
<gchristensen> maybe before your time then :)
<samueldr> I mean, I'm not *always* on IRC either
<samueldr> and hide joins/parts!
<samueldr> 👀
<samrose> right on understood! many moving pieces @samueldr
<samrose> and many moving people