jackdk_ has joined #nixos-aarch64
jackdk has quit [Disconnected by services]
jackdk_ is now known as jackdk
alunduil has joined #nixos-aarch64
alunduil has quit [Client Quit]
alunduil has joined #nixos-aarch64
alunduil has quit [Client Quit]
elvishjerricco has quit [Ping timeout: 258 seconds]
elvishjerricco has joined #nixos-aarch64
elvishjerricco has quit [Max SendQ exceeded]
elvishjerricco has joined #nixos-aarch64
jackdk_ has joined #nixos-aarch64
jackdk has quit [Disconnected by services]
jackdk_ is now known as jackdk
womfoo has joined #nixos-aarch64
<womfoo> hi guys, are there instructions handy to run nixos on roc-rk3399-pc somewhere?
<womfoo> i found {makefu,samueldr}/ROC-RK3399-PC-overlay but this gives me 4.2mb combined.img and im not really sure how to use it properly.
<womfoo> all i tried is dding this on top of the aarch64 sdimage from hydra but i couldnt see any UART output or LEDs turn on. UART/LEDs work when im on firefly ubuntu sdimage.
<womfoo> im still new to arm sbcs so please excuse these basic questions :-)
womfoo has quit [Remote host closed the connection]
orivej has joined #nixos-aarch64
womfoo has joined #nixos-aarch64
<tilpner> womfoo: This seems relevant-ish https://nixos.wiki/wiki/NixOS_on_ARM/Firefly_AIO-3399C
kai_w has joined #nixos-aarch64
<womfoo> tilpner: thanks and yes i did come across that but it was focused on using a tool for flashing firmware from a pc
<womfoo> vs creating a bootable sdcard
<tilpner> I don't have any rk3399 devices, I just linked that because it was using the overlay
<tilpner> If there's a community channel for your device, they'd probably know better
<womfoo> no worries. im just getting confused with this flashing terminology esp when the docs mention partitions.
<womfoo> last time i flashed something was 'firmware' for simpler devices like dvd-writer :-D
<sphalerite> womfoo: yeah rockchip calls it flashing even when the flash is just part of an sd card
<sphalerite> should be harmless :)
womfoo` has joined #nixos-aarch64
womfoo has quit [Ping timeout: 259 seconds]
jtojnar has joined #nixos-aarch64
<womfoo`> sphalerite: yes indeed
<samueldr> womfoo`: right now I wasn't able to boot NixOS on the ROC-RK3399-PC; still waiting on news from libre.computer for mainline progress :(
<samueldr> as for using it... damn me, I didn't write it up, it's probably written with `dd if=... of=... bs=512 seek=64`
<samueldr> u-boot will work
<samueldr> last time I tested our mainline image (with latest kernel) it booted up to stage-2 and froze
<samueldr> didn't really debug as I am waiting on a confirmation that it should or shouldn't work
jtojnar has quit [Quit: jtojnar]
orivej has quit [Ping timeout: 245 seconds]
orivej has joined #nixos-aarch64
jackdk has quit [Remote host closed the connection]
Thra11 has joined #nixos-aarch64
<gchristensen> hi friends, do we trust DigitalKiwi sufficiently to be a trused aarch64 community build user?
<gchristensen> samueldr: ^
<samueldr> (I don't know)
<gchristensen> (me either)
thefloweringash has quit [Ping timeout: 264 seconds]
thefloweringash has joined #nixos-aarch64
<gchristensen> I don't love the security model there :)
<gchristensen> for example making people untrusted but giving them shell access means they can't poison the store with fake drvs, but also they have shell access
zupo has joined #nixos-aarch64
<gchristensen> I might be able to forward on a code to get the 11" pinebook if anybody is in need of an aarch64 laptop-like-thing to experiment, hack, and learn with
<samueldr> finally got mine (code) in the same batch I guess
<gchristensen> it isn't mine to give away, I don't have a code
<gchristensen> but this other person might give it up
<samueldr> (which now makes me think, with the appropriate tweaks and firmware installed to the board it would be possible to have a universal image that boots on the pinephone and pinebook)
<gchristensen> :O
<samueldr> both based on the same base hardware sopine/pine a64-lts
<samueldr> the main issue is making it useful on both
<samueldr> which, if the device handles providing the firmware, + passes the appropriate device tree, then the hardware will be detected appropriately
<gchristensen> nice
* samueldr hopes the post hasn't lost the package
<samueldr> still stuck between cities since last week :(
<gchristensen> ouch :/
womfoo` has quit [Remote host closed the connection]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
womfoo has joined #nixos-aarch64
<womfoo> samueldr: no worries. are the libre.computer folks responsive? i would love to help test or join an irc/slack if there is one.
<samueldr> there's the #librecomputer channel, womfoo, though I haven't poked 'em lately, waiting on news elsewhere (e.g. their forums)
<samueldr> understand that I am only a backer, no affiliation with them
orivej has quit [Ping timeout: 246 seconds]
<womfoo> thanks! ill have a look there. im also just a backer via indiegogo.
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
womfoo has quit [Remote host closed the connection]
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
jackdk has joined #nixos-aarch64
orivej has quit [Ping timeout: 250 seconds]