<Gaelan>
Are the ids of the aarch64 NixOS AMIs documented anywhere? I can find them in Amazon's search but I'd like to make sure I'm using the official builds
dstzd has joined #nixos-aarch64
<samueldr>
AFAIK there is no official aarch64 AMI, but I could be wrong
<angerman>
I haven't seen any in years, always had to build my own ones.
<Gaelan>
can AWS graviton2 instances not run armv6l binaries? I'm trying to use one to build some stuff for armv6l, and it's failing with illegal instruction
orivej has quit [Ping timeout: 264 seconds]
rajivr has joined #nixos-aarch64
<samueldr>
nope, it's stritcly AArch64
<samueldr>
and trying to build armv6 on AArch64 AFAIK is problematic when it supports 32 bit
<samueldr>
because of how it's armv8 32 bit
<samueldr>
though building armv7l could work... but there's issues with "personality" in the kernel
<samueldr>
but, you can run a KVM VM of armv7l to do so with not much loss
<samueldr>
(when the CPU supports 32 bit)
<samueldr>
not sure if the same could be done for armv6l
orivej has joined #nixos-aarch64
<Gaelan>
darn, guess I'm back to building on my pi
<Gaelan>
would be really nice to have cross-compiling to armv6l working again…
orivej has quit [Ping timeout: 240 seconds]
<noneucat>
my rockpro64 has bit the dust :( was nice while it lasted
h0m1 has quit [Quit: WeeChat 3.0]
h0m1 has joined #nixos-aarch64
<sphalerite>
noneucat: RIP
lgcl has joined #nixos-aarch64
<sphalerite>
What happened?
<noneucat>
not quite sure :( found it with the fan dead and now it won't boot past the first few steps of u-boot
<noneucat>
wondering what to replace it with..
<sphalerite>
m, maybe power supply issues? Can you power the fan directly?
<sphalerite>
Because if so maybe you can "fix" this with an ATX power supply
<noneucat>
i haven't considered the power supply now that i think about it
<noneucat>
pci is not being powered
<noneucat>
it did seem to be weird power wise
<sphalerite>
yeah maybe the pins are exposed enough that you can just shove your own voltage in there to get it running again
<Ke>
did you let it rest for sufficient amount of time
<Ke>
some devices do recover
<Ke>
though simpler things like minimal sbcs have lower footprint to store the bad energies
<Ke>
like drain all the capacitors, let all the extra heat out
<noneucat>
that is a good point also!
<noneucat>
i will see what happens tomorrow
<Ke>
if you have a multimeter, you can check the psu independently
<Ke>
though multimeter does not show, whether the voltage drops on load
<noneucat>
the psu seems to be holding it's voltage fine, but yeah it does not show how it does under load
<noneucat>
the board seems to be powered fine... just not doing anything haha
<clever>
sphalerite: the gcc shipped with raspi-os has some default flags, to force armv6, even on an armv8 cpu
<clever>
samueldr: oops, ^
<clever>
in theory, the pkgsCross in nixpkgs could do the same
<Ke>
wait what?
<Ke>
you mean to make everything rpi1 compatible?
<clever>
Ke: a dedicated pkgsCross target that is rpi1 compatible
<clever>
i believe pkgsCross.raspberrypi already is that
<Ke>
ah, ure
<clever>
the armv7l is named in a more generic way
<samueldr>
clever: but this won't be "native" compilation like i686 on x86_64
<samueldr>
which is what most people want when they want to build something on the wrong arch in backward compatible manners
<samueldr>
if you're going to cross-compile, you might just as well do it from x86_64
lgcl has quit [Read error: Connection reset by peer]
ib07 has quit [Ping timeout: 272 seconds]
Darkmatter66 has joined #nixos-aarch64
nbp has quit [Ping timeout: 265 seconds]
nbp has joined #nixos-aarch64
<clever>
samueldr: in the case of rpios, the "native" gcc forces armv6 by default, so it such a target could be made in nixpkgs, then import <nixpkgs> { system = "armv6l-linux"; } selects it...
<clever>
if the aarch64 cpu is also 32bit capable, it should work
<clever>
since v6 is a subset of v7
cole-h has quit [Ping timeout: 260 seconds]
justan0theruser has quit [Ping timeout: 268 seconds]
orivej has joined #nixos-aarch64
justan0theruser has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 240 seconds]
lgcl has joined #nixos-aarch64
orivej has joined #nixos-aarch64
justan0theruser has quit [Ping timeout: 240 seconds]
justanotheruser has joined #nixos-aarch64
alpernebbi has joined #nixos-aarch64
orivej has quit [Quit: orivej]
orivej has joined #nixos-aarch64
orivej_ has joined #nixos-aarch64
orivej has quit [Ping timeout: 246 seconds]
justanotheruser has quit [Read error: Connection reset by peer]
ryantrinkle has quit [Ping timeout: 240 seconds]
orivej_ has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
ryantrinkle has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
bridge[evilred] has quit [Remote host closed the connection]
bridge[evilred] has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
justanotheruser has quit [Ping timeout: 240 seconds]
lgcl has quit [Read error: Connection reset by peer]
alpernebbi has quit [Quit: alpernebbi]
cole-h has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
Darkmatter66 has joined #nixos-aarch64
v0|d has joined #nixos-aarch64
danielrf has quit [Quit: danielrf]
<samueldr>
sure, the compiler targets the right arch, but we're back at the problem of impurities during builds, with detection
veleiro has joined #nixos-aarch64
{^_^} has quit [Remote host closed the connection]
{^_^} has joined #nixos-aarch64
<veleiro>
https://paste.rs/QIt does anyone know why libaom is not compiling on 32bit arm?
ajs124 has quit [Quit: killed]
ajs124 has joined #nixos-aarch64
monk has joined #nixos-aarch64
<andi->
samueldr: you once posted a dd statement to "transform" the u-boot output into an SPI compatible way. I searched the log but didn't really find a thing.. Mind posting that again?