<samueldr> armv6l on raspberry pi1 family (so, zeroes too)
<samueldr> armv7l on raspi2
<samueldr> aarch64 on raspi3
<samueldr> and then, whatever order you prefer :)
<clever> the v7 and aarch64 chips are a little weird when booting v6
<clever> raspbian has a v7 kernel, with a v6 userland to solve that
<clever> but i can see that being a pain to build with nix
<samueldr> oh, no need to mix-and-match there's no real reason on nixos :)
<samueldr> well, with 16MB free the system can boot :) fixing the PR
<samueldr> I'd like someone with enough knowledge about the things it touches to review #51207 :)
<{^_^}> https://github.com/NixOS/nixpkgs/pull/51207 (by samueldr, 1 day ago, open): sd-image: Slims the ext4 filesystem even more.
<samueldr> mainly, filesystems, ext4, and booting
<samueldr> with this, the output size will be small enough so that hydra builds will succeed again
<clever> fdisk: cannot open /dev/sde: Input/output error
<clever> hmmm, the 8g uSD from a random rpi wont read
<samueldr> yay
<samueldr> this is always fun :/
<samueldr> I have, kicking around, a dubious "32GB" sd card
<samueldr> which reports as 34GB
<samueldr> no I'm not using it for anything important :)
<clever> with a different uSD->sd adapter, it does read
<samueldr> I always had some SD cards behave differently depending on their readers, too :/
<bobvanderlinden> i'm hearing from a friend that we might be able to straighten out all /dev/tty devices by fixing the device trees of the images
<samueldr> it's the stock mainline images
<clever> samueldr: there is sd, sdhc, and sdxc i think
<samueldr> mainline device trees*
<samueldr> clever: yeah, but both readers are for the same spec :)
<clever> beyond a certain size, the protocol changes, because the block#'s have too many bits
<samueldr> I'm thinking one must be noisy and just over or near the limits the spec sets
<samueldr> so some cards will behave fine, and some not in it
<clever> and before i can even read the card, it vanishes
<clever> samueldr: cloning this old uSD, incase it has anything of use
<bobvanderlinden> hmm, older rpis do not use dts from mainline i suppose?
<samueldr> armv6 ones won't
<samueldr> AFAIK
bobvanderlinden has quit [Ping timeout: 256 seconds]
srk has quit [Ping timeout: 246 seconds]
srk has joined #nixos-aarch64
srk has quit [Ping timeout: 250 seconds]
srk has joined #nixos-aarch64
orivej has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
orivej has quit [Ping timeout: 268 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 250 seconds]
chris| has quit [Quit: ZNC 1.7.1 - https://znc.in]
chris| has joined #nixos-aarch64
Thra11 has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 250 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
Thra11 has joined #nixos-aarch64
samrose has joined #nixos-aarch64
<samrose> samueldr: I figured out troubles with serial console, and actually got 4.18 nixos image to boot on bananapi m64
<samrose> still no hdmi output
<samueldr> samrose: what were the troubles?
<samueldr> and yeah, both 4.18 and 4.19 fail at hdmi here on the Pine A64-LTS too
<samrose> I wasn't aware of the correct speed to set on the serial console
<samueldr> 115200 :)
<samrose> right indeed
<samrose> uboot is displaying output on hdmi
<samueldr> other than "wait for 4.20 hoping they fix it" I don't really know for the bananapi :/
<samrose> A colleague figured if I can find the correct place to setenv with booatargs in uboot build, I might get the terminal console in hdmi, which is all I need
<samueldr> or alternatively, find a downstream-based kernel for it
<samueldr> which boot args do you want to add?
<samueldr> you can modify the extlinux/extlinux.conf (IIRC) file in the NIXOS_BOOT partition
<samrose> it was the last line in this image https://imgur.com/a/AYBYr0t
<samrose> samueldr: you think that line likely should live inthe extlinux/extlinux.conf file of NIXOS_BOOT?
orivej has joined #nixos-aarch64
<samrose> (I wasn't sure myself)
<samueldr> I'd bet a 50% chance it works, and only with increasing odds if that image uses a mainline linux kernel, which I would doubt
<samueldr> but yeah
<samueldr> those are kernel command line options
<samueldr> you can add those to `APPEND`
<samueldr> repeating them shouldn't cause issues
<samrose> in this case, I'd be trying those args on the sd-aarch64 img /kernel (not the ubuntu image you see in the link)
<samueldr> right
<samrose> We were examining the ubuntu image to try and figure out how they achieved hdmi
<samueldr> pi@bpi-iot-ros-ai:~$ uname -a
<samueldr> Linux bpi-iot-ros-ai 3.4.39-BPI-M3-Kernel #4 SMP PREEMPT Thu Nov 17 08:10:07 UTC 2016 armv7l armv7l armv7l GNU/Linux
<samueldr> (found randomly online)
<samueldr> if it's a 3.4 kernel, on that ubuntu image, results may vary wildly
<samrose> you are right I believe, they are not using a mainline kernel directly, but have just grabbed the source for the kernel, crammed it into their repo and build the image
<samrose> the company that manufactures bananapi and builds these ubuntu images doesn't even submit their drivers back up to kernel.org
<samueldr> (as is usual with allwinner boards :()
<samrose> ah ok, I wasn't aware. I am (obviously :) ) a newbie to all of this
<samueldr> more often than not, it's what happens
<samrose> likely wouldn't have made it this far if not for the nix tool chain to build all this stuff saving lots of time
<samueldr> at least the boards are similar enough that when contributors contribute changes for one, often few changes are needed for mainlining another board
<samrose> this was the repo I found for their ubuntu/debian/etc builds for the m64 https://github.com/BPI-SINOVOIP/BPI-M64-bsp
<samrose> they are actually using kernel 3.10
<samueldr> you may be able to use something like this to build it https://nixos.wiki/wiki/NixOS_on_ARM/PINE_A64-LTS#Downstream_kernel
<samueldr> oooh boy
<samueldr> I find this genuinely funny
<samueldr> it seems they've been using another user's fork of the kernel for their builds
<samrose> yeah ::insert captain picard facepalm meme here::
<samueldr> it's still perfectly valid and legit
<samueldr> though it's a bit annoying in some ways
<samrose> I wasn't aware either way, but it seemed to create a lot of obscurity
<samrose> (for me anyway :) )
<samueldr> those non-upstream kernels are always a bother, and especially bad when they don't keep the git history around
<samrose> So it looks like this is what builds the extlinux.conf file you were mentioning above? https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/system/boot/loader/generic-extlinux-compatible/extlinux-conf-builder.sh
<samueldr> though I'd recommend you manually edit your existing sd card's files instead of going through a long compilation to find out the right params :)
<samrose> yes, yes good advice
orivej has quit [Ping timeout: 246 seconds]
samrose has quit [Ping timeout: 268 seconds]
FRidh has quit [Quit: Konversation terminated!]
orivej has joined #nixos-aarch64
samrose has joined #nixos-aarch64
Thra11 has quit [Ping timeout: 250 seconds]