orivej has quit [Ping timeout: 264 seconds]
orivej has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 244 seconds]
h0m1 has joined #nixos-aarch64
orivej has quit [Ping timeout: 256 seconds]
knerten1 has joined #nixos-aarch64
knerten has quit [Ping timeout: 240 seconds]
ryantrinkle has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 256 seconds]
ryantrinkle has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
ryantrinkle has quit [Ping timeout: 256 seconds]
<colemickens> samueldr: do you have any more purchasing advice for someone with PP and PBP on the way?
<samueldr> colemickens: the proper serial cable from pine64 is a good idea
<samueldr> though making your own is trivial
<samueldr> way more trivial
<samueldr> (though be careful about voltage)
<colemickens> okay.
<samueldr> it's a nice-to-have, compared to the pixel debug cable
<samueldr> otherwise, I don't really know
<colemickens> okay, cool, I figured but you know, shipping being what it is here :S
<samueldr> yeah :/
<samueldr> the thing that's really helpful with a serial cable for either of those is that when things figuratively hit the fan, you get a peek in
<samueldr> with the pinephone there's no graphical u-boot (yet)
<samueldr> I figure it's gonna come at some point though
<samueldr> I have suspicions that someone (unrelated to the person working on the PBP's) is
<samueldr> but I won't say since I'm heavily inferring :)
cole-h has quit [Quit: Goodbye]
<Ke> samueldr: colemickens about the voltage: pine64 ships occasionally wrong voltage themselves, so do verify, if you can
<Ke> I got 5V adaptor and was not the only one either
FRidh has joined #nixos-aarch64
criptonauta_ has quit [Quit: Leaving]
orivej has joined #nixos-aarch64
<sphalerite> can confirm, making a pinephone serial cable is easy if you have the relevant equipment and basic soldering experience
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
<Ke> I did solder mine from the pine adaptor and a existing 3v3 ttl adaptor I had
quinn has quit [Quit: ZNC 1.8.1 - https://znc.in]
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
bdju has quit [Read error: Connection reset by peer]
bdju has joined #nixos-aarch64
alp has joined #nixos-aarch64
<misuzu> https://bitbucket.org/thefloweringash/alex-config/src/master/build-vm.nix this works flawlessly on my rpi4 (with minor tweaks), thank you thefloweringash!
alp has quit [Ping timeout: 272 seconds]
<misuzu> used this instead of copying host's store - now vm is starting very fast!
<colemickens> misuzu: can I be nosy? what's the build-vm.nix for?
<colemickens> just to run a VM on the rpi as a systemd serivce I guess?
<misuzu> colemickens: you can use this as native armv7l builder
<colemickens> oh ok
h0m1 has quit [Ping timeout: 260 seconds]
h0m1 has joined #nixos-aarch64
alp has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
knerten2 has joined #nixos-aarch64
knerten1 has quit [Ping timeout: 256 seconds]
<thefloweringash> misuzu: hey, glad that vm config helps! I used to use overlayfs but found that it breaks go's tests so switched over to the completely flat and boring ext4 single volume
<Thra11> thefloweringash: I based my armv7l build vm on your config too, so thanks from me as well!
bennofs has joined #nixos-aarch64
WilliButz has quit [Remote host closed the connection]
WilliButz has joined #nixos-aarch64
<Thra11> I ended up changing the startup service from DynamicUser to a fixed user, as I wanted to create the disk image on an external drive, not in /tmp (my host rootfs doesn't have much space and /tmp is a tmpfs)
WilliButz has quit [Remote host closed the connection]
WilliButz has joined #nixos-aarch64
bennofs has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
Mic92 has quit [Quit: WeeChat 2.8]
Darkmatter66_ has joined #nixos-aarch64
Darkmatter66 has quit [Ping timeout: 256 seconds]
veleiro has quit [Ping timeout: 256 seconds]
nschoe has joined #nixos-aarch64
orivej has joined #nixos-aarch64
nschoe has quit [Ping timeout: 256 seconds]
orivej has quit [Ping timeout: 264 seconds]
alp has joined #nixos-aarch64
nschoe has joined #nixos-aarch64
t184256 has left #nixos-aarch64 [#nixos-aarch64]
t184256 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
zupo_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 240 seconds]
cole-h has joined #nixos-aarch64
zupo_ has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
orivej has joined #nixos-aarch64
alp has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
<samueldr> would another shared store scheme like 9p or nfs work better than overlayfs?
<samueldr> oh, uh, no
<samueldr> since overlayfs doesn't actually write out of the VM
<samueldr> so it's not a drop-in replacement
FRidh has quit [Quit: Konversation terminated!]
cole-h has quit [Quit: Goodbye]
alp has quit [Ping timeout: 272 seconds]
nschoe has quit [Ping timeout: 272 seconds]
alp has joined #nixos-aarch64
<misuzu> thefloweringash: did you use overlayfs only for /nix/store or for entire root?
<misuzu> tests is executed inside TMPDIR so overlayfs on /nix/store should not break them
quinn has joined #nixos-aarch64
<thefloweringash> Just for the nix store. IIRC the build directory is inside the nix store to handle hardlinks.
<thefloweringash> Thra11: glad it's useful for you too :-)
<misuzu> thefloweringash: thanks!
Darkmatter66_ has quit [Ping timeout: 240 seconds]
Darkmatter66 has joined #nixos-aarch64
t184256 has left #nixos-aarch64 ["Disconnected: Replaced by new connection"]
t184256 has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
colemickens_irc has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
tilpner has quit [Remote host closed the connection]
tilpner has joined #nixos-aarch64
alp has joined #nixos-aarch64
mvnetbiz_8 has quit [Read error: Connection reset by peer]
mvnetbiz_8 has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<colemickens> https://forum.pine64.org/showthread.php?tid=8439 seems like uboot in SPI -> NVME is possible (soon?)?
<colemickens> for the PBP, that is
<samueldr> yes it should be
<samueldr> I don't have the hw to test (no nvme drive)
<samueldr> so I haven't blindly added things to the u-boot for it
<samueldr> hacking on u-boot is relatively trivial though
<samueldr> you would first erase the SPI flash
<samueldr> and then just burn it to SD
orivej has quit [Ping timeout: 256 seconds]
<colemickens> samueldr: I was a bit confused, the "new" stuff then is a change to uboot that allows it to also work from SPI the same way it already did from SD?
<colemickens> from the same build, I guess, even.
<samueldr> colemickens: "new" from whom?
<samueldr> there's different things
<colemickens> I guess I mean the update in that thread, RE: upstream uboot.
<samueldr> I believe all that is found after "--------" is the old post
<samueldr> they seem to have prefixed it with an update
<colemickens> right, pre-update it seems like it wasn't upstreamed
<colemickens> but the upstream uboot at that time seemed to still work on the pbp, just not from the SPI
<colemickens> or I have a misunderstanding, maybe
<samueldr> I'm not sure about the timeline
<samueldr> but IIRC straight upstream needs tweaks for SPI to work
<colemickens> hm ok
<samueldr> looks like it's config though
<colemickens> oh yeah, I see that same patch in the u-boot-build-scripts repo that builds upstream
<colemickens> cool, tons of stuff ready to play with when hw arrives