Darkmatter66_ has quit [Ping timeout: 265 seconds]
henry_ has joined #nixos-aarch64
<samueldr>
you never know when I'll be and if I am, you'd better just ask in case it happens to be later
<samueldr>
qy[m]1: but right now I am
<qy[m]1>
well it sort of requires us to be on at the same time. can you give me +h for just a second so i can set an icon for the matrix room? :)
<qy[m]1>
the lack of icon frustrates me :p
<samueldr>
I don't have special rights for the room
<qy[m]1>
oh
<qy[m]1>
ah well
<colemickens>
+1 for more matrix icons
<qy[m]1>
:)
h0m1 has quit [Ping timeout: 246 seconds]
h0m1 has joined #nixos-aarch64
pbb has quit [Ping timeout: 272 seconds]
h0m1 has quit [Ping timeout: 240 seconds]
h0m1 has joined #nixos-aarch64
henry_ has quit [Quit: henry_]
teto has quit [Ping timeout: 246 seconds]
<colemickens>
random thought: seems like getting flutter running on (nixos) mobile (linux) would be a boon, if it winds up taking off.
dsal has joined #nixos-aarch64
<dsal>
Do folks in here know anything about armv7 machines? I'm trying to resurrect an orange pi
<samueldr>
maybe some do, though note that armv7 has a poor coverage in the cache
<simpson>
This is a good channel for that, but you may have to wait a while for a reply. FWIW I don't recall any work with Orange Pis, but from what clever has said, it seems like everybody's a winner with Allwinner today.
<dsal>
Heh. yeah. I got it into u-boot, but it just wants to pxeboot from there.
<samueldr>
it's likely a "good sign", it's likely the default u-boot generic loader thing is working as expected, but cannot find an OS to boot
<dsal>
Yeah. I think I've made progress. I don't know how to use this boot loader, though.
<dsal>
Eventually, web pages will load and I'll know more things.
<qy[m]1>
I got nix on my raspi2s
<qy[m]1>
But it was a real pain
<dsal>
That uboot manual chapter that describes storage devices only says that it does, but it really doesn't.
orivej has joined #nixos-aarch64
<dsal>
I hacked something together horribly.
<dsal>
booted into u-boot, then rewrote the card, rescanned it, and booted the card.
<samueldr>
not so bad, just as if you used a second sd card
<samueldr>
u-boot is fully resident in memory, it doesn't need to re-read the storage device it was started from
<dsal>
I don't quite know how to start this, though. Trying to install onto USB flash.
<dsal>
Yeah, I have no idea what I'm doing, but I'm writing files to this SSD, so at least bits will roll.
<dsal>
I guess it wants a network. That's not going to happen... I got pretty close, anyway. heh
<asbachb>
Hej. Can someone confirm that it's possible to have an remote builder for aarch64 which is x86_64 and maybe a working configuration?
zupo has joined #nixos-aarch64
<sphalerite>
asbachb: not really
<sphalerite>
asbachb: you can cross-build (any x86_64 machine including the local one can do that), but you'll have a completely distinct set of derivations
<sphalerite>
asbachb: you can also use qemu-user, but it's terribly slow
<sphalerite>
do we have a factoid for that..?
<sphalerite>
,qemu-user
<asbachb>
sphalerite: I guess qemu build should be faster than build on raspberry pi directly.
<srk>
or binfmt?
<srk>
not sure how to set that up but that should allow you to be able to run arm binaries transparently
<samueldr>
srk: mark what as broken? the raspberry pi 4 in general? :)
<gchristensen>
lmao
<samueldr>
srk: the generic image works on all devices supported by the mainline kernel, as long as it is supported by the aarch64 defconfig
<samueldr>
(and I don't know what's the port for the console, but since it's the downstream kernel from the rpi foundation, it must be whatever it is as documented for their kernel)
<srk>
idk, maybe a warning in nixos/modules/installer/cd-dvd/sd-image-raspberrypi4.nix
<samueldr>
a warning for?
<samueldr>
that image should work on a pi4
<hexa->
pretty sure it works, i just can't interact with it :)
<srk>
I would test but don't have pi4
<samueldr>
I haven't tested it recently, but it did work when it was added, and I would be surprised to see that it would stop working
<samueldr>
though I'm not sure that serial was verified
<srk>
well, things break :) I think SPI might be broken around ~5.4
<samueldr>
that image is using the downstream kernel from the rpi foundation
<samueldr>
which makes me think it's unlikely to be broken
<hexa->
ah, so I can follow generic serial guides for the rpi4?
<hexa->
like for raspbian
<samueldr>
I believe so
<samueldr>
since it's their kernel fork
<hexa->
> console=serial0,115200
<{^_^}>
error: syntax error, unexpected ',', expecting ';', at (string):71:19
<srk>
samueldr: yeah, that was about mainline
<srk>
hexa-: not ttyAMA0? :)
<hexa->
yep serial0 works
<srk>
cool!
<hexa->
will update the wiki shortly
teto has joined #nixos-aarch64
<clever>
samueldr: sent you a link on discord about some pixel uefi stuff
<samueldr>
imbusho or zhuowei zhang were working on that, well, either one of them, don't quite remember
<clever>
> it's just... the pixel did so well. they're using UEFI now, on pixel phones. but not... quite. UEFI loads linuxloader.efi (inside the FV). They just about got there. Had they just stopped at "pixel uses UEFI to boot" we would be fine
<{^_^}>
error: syntax error, unexpected ELLIPSIS, expecting ')', at (string):296:10
<clever>
[3:02 PM]
<samueldr>
ah, just that, yeah, it's known that qualcomm are using UEFI since a small while
<clever>
is it in the mask rom, or an SPL on some flash media?