<samrose>
samueldr: interesting, so what does the nixos that you have already installed on pine64 look like? what is the u-boot and image and process you used to install ?
<samueldr>
I was using, for a while, a usb ethernet interface
<samueldr>
then found a workable 4.14 kernel with patches
<samueldr>
since I added support for PINE A64-LTS the mainline image boots, but it had different issues, e.g. no networking and no HDMI, so at first I had to rely on serial to set things up
<samueldr>
(I should test 4.19 and update the page accordingly)
<samrose>
samueldr: I am not sure if I have no networking, but I had no hdmi, and serial crashes so unusable in my case
<samrose>
actually, the mainline image boots for me on bpim64 (although I cannot confirm for sure due to non functioning serial) and the simple_fb error crops up, then black screen of hdmi death (apprently)
<samrose>
I am trying on the qemu-system-aarch64 again but with nixos/nixpkgs repo, and will try unstable branch
<samrose>
I will also try the same on the hardware itself later today
orivej has joined #nixos-aarch64
<samrose>
samueldr: for whatever reason, building from master branch seems to be making it much further than the previous attempts I had made
<samrose>
(in the qemu-system-aarch64 approach)
orivej has quit [Ping timeout: 245 seconds]
das_j has quit [Ping timeout: 268 seconds]
das_j has joined #nixos-aarch64
das_j has quit [Ping timeout: 268 seconds]
das_j has joined #nixos-aarch64
<samrose>
samueldr: has a successful build generally taken a very long time for you?
<samueldr>
yes and no, depends on many factors, like the hardware
<samrose>
is it normal for this sd-image-aarch64 to compile device drivers like: "CC [M] drivers/gpu/drm/mediatek/mtk_mipi_tx.o" etc?
<samueldr>
if it has to compile the kernel yes
<samueldr>
and that can take... a gooooood while on enthusiast-class SBCs like those
<samrose>
ah ok. So it is compiling kernel ok.
<samueldr>
I don't have an approximation for that allwinner
<samueldr>
but on an armv7l, slower, older, it took ~14h
<samueldr>
(only for the kernel)
<samueldr>
though, imho, if it's building the kernel, it shouldn't fail unless while building the image it doesn't have enough ram or disk space
<samueldr>
(and for ram issues, swap or a swap file would help)
<samrose>
yeah, I am running this in qemu-system-aarch64, and although I gave it decent resources, I am not aware of any way to speed it up. Not a problem but just was trying to judge whether this looong build is normal
<samrose>
so far, no failure
<samueldr>
yeah, that's... that's going to be slow :)
<samrose>
on the actual bpi64, I was always adding a usb flash drive as swap device
<samrose>
I am going to let this qemu build roll
<samueldr>
depending on the failure, it may not be all in vain
<samrose>
it's been going since around 6 hours ago
<samueldr>
e.g. if the kernel built, and it fails for another reason, *at least* you won't need to rebuild the kernel
<samueldr>
and unless there are bugs in qemu, I wouldn't expect the kernel compilation to fail
<samrose>
yes, the more I try to get this working the more I learn, so it's positive direction overall
<samueldr>
kernel compilation is quite conservative in resources
<samrose>
I think I am going to fire up the device and try it there too
asymmetric has joined #nixos-aarch64
asymmetric has left #nixos-aarch64 [#nixos-aarch64]