monk has left #nixos-aarch64 ["Error from remote client"]
justanotheruser has quit [Ping timeout: 265 seconds]
justanotheruser has joined #nixos-aarch64
monk has joined #nixos-aarch64
zuh0 has joined #nixos-aarch64
rajivr has joined #nixos-aarch64
LnL has quit [Quit: exit 1]
LnL has joined #nixos-aarch64
LnL has quit [Ping timeout: 256 seconds]
LnL has joined #nixos-aarch64
ehmry has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
justanotheruser has quit [Ping timeout: 260 seconds]
h0m1 has quit [Quit: WeeChat 3.0]
h0m1 has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
justanotheruser has joined #nixos-aarch64
h0m2 has joined #nixos-aarch64
h0m1 has quit [Ping timeout: 240 seconds]
tbech has quit [Ping timeout: 272 seconds]
justanotheruser has quit [Ping timeout: 272 seconds]
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
justanotheruser has joined #nixos-aarch64
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-aarch64
<Ke> what's the question?
cole-h has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-aarch64
veleiro has joined #nixos-aarch64
red[evilred] has joined #nixos-aarch64
<red[evilred]> Ke (IRC): Delivery dates / notifications
<red[evilred]> We both have orders pending
<red[evilred]> and I'm not going to speak for sphalerite (IRC) - but I'm impatient ;-)
alp has joined #nixos-aarch64
orivej has quit [Ping timeout: 272 seconds]
alp has quit [Ping timeout: 260 seconds]
zupo has quit [Ping timeout: 246 seconds]
zupo has joined #nixos-aarch64
alp has joined #nixos-aarch64
orivej has joined #nixos-aarch64
FRidh has quit [Ping timeout: 264 seconds]
FRidh has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
<patagonicus> I ordered a pinephone yesterday. :)
<patagonicus> No idea when it'll get here, though. Maybe I'll get a tracking number next week.
<sphalerite> red[evilred]: nope nothing
<sphalerite> red[evilred]: though I'm a lot more impatient for my helios64 :p
<red[evilred]> understood
tbech has joined #nixos-aarch64
alp has joined #nixos-aarch64
FRidh has quit [Ping timeout: 260 seconds]
FRidh has joined #nixos-aarch64
ehmry has joined #nixos-aarch64
<angerman> Just in case anyone is curious, it appears the x820 v3 sata enclosure doesn’t work with nixOS using uboot on an rpi3. Going the non-uboot route made it boot. Got some help from clever.
greizgh has quit [Quit: greizgh]
greizgh has joined #nixos-aarch64
alp has quit [Ping timeout: 272 seconds]
tbech has quit [Quit: WeeChat 2.9]
orivej has quit [Ping timeout: 260 seconds]
alpernebbi has joined #nixos-aarch64
alp has joined #nixos-aarch64
ehmry has quit [Read error: Connection reset by peer]
ehmry has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
zupo has quit [Quit: Textual IRC Client: www.textualapp.com]
red[evilred] has quit [Quit: Idle timeout reached: 10800s]
zupo has joined #nixos-aarch64
alp has quit [Ping timeout: 264 seconds]
<angerman> Ohh ASUS revives the tinker board with an RK3399?
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
FRidh has quit [Quit: Konversation terminated!]
<Ke> heh, it's not like we had enough rk3399 sbcs
alp has joined #nixos-aarch64
<angerman> Yea. A new board with rk3399 *now* feels weird. But it most likely will work out almost out of the box unless they did something really odd.
<thefloweringash> is there a trendy new chip to replace the rk3399?
<sphalerite> ^ this would be really nice
<thefloweringash> I see a "RK3588" on a rockchip roadmap, but can't tell if it actually exists yet
<angerman> Something with twice the cores and support for up to 32G would be welcome.
monk has left #nixos-aarch64 ["Error from remote client"]
orivej has joined #nixos-aarch64
monk has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
FRidh has joined #nixos-aarch64
cole-h has joined #nixos-aarch64
<sphalerite> danielrf[m]++ awesome that nixos beat debian to the pinecube!
<{^_^}> danielrf[m]'s karma got increased to 6
monk has left #nixos-aarch64 ["Error from remote client"]
veleiro has quit [Ping timeout: 240 seconds]
alp has quit [Ping timeout: 272 seconds]
ehmry has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
monk has joined #nixos-aarch64
monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
Acou_Bass has quit [Quit: ZNC 1.8.1 - https://znc.in]
Acou_Bass has joined #nixos-aarch64
alp has joined #nixos-aarch64
rajivr has quit [Quit: Connection closed for inactivity]
alp has quit [Ping timeout: 272 seconds]
alpernebbi has quit [Quit: alpernebbi]
<samueldr> there's the rk3399 pro apparently
<samueldr> I didn't have any success in finding more info
<samueldr> but IIRC it's pin incompatible with the RK3399, but allows more than 4GB of RAM to be used
<samueldr> nah, compatible
<samueldr> though (1) hard to find info (2) not even sure it actually is made still, everything seems out of stock https://www.seeedstudio.com/ROCK-PI-N10-Model-C-RK3399Pro-8GB-LPDDR3-64GB-eMMC-p-4381.html
WilliButz has quit [Remote host closed the connection]
<samueldr> (but yeah, that's not like a real new hotness)
<hexa-> there is supposed to be a successor in 2021
<samueldr> yeah
<hexa-> rk3588 iirc
<samueldr> (it was mentioned beforehand)
<hexa-> oh right, thx
WilliButz has joined #nixos-aarch64
<samueldr> it feels wrong though how it seems no one is making new SoC designs for the SBC segment
<samueldr> hmmmm, wrong, amlogic kinda are, but they really do set-top boxes and not SBCs
<samueldr> ah, I didn't know allwinner had announced things
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Acou_Bass has quit [Quit: ZNC 1.8.1 - https://znc.in]
Acou_Bass has joined #nixos-aarch64
orivej has quit [Ping timeout: 260 seconds]
alp has joined #nixos-aarch64
wavirc22_ has quit [*.net *.split]
evils has quit [*.net *.split]
quinn has quit [*.net *.split]
bridge[evilred] has quit [*.net *.split]
betaboon has quit [*.net *.split]
nbp has quit [*.net *.split]
<danielrf[m]> sphalerite: Thanks!
zupo has joined #nixos-aarch64
wavirc22_ has joined #nixos-aarch64
bridge[evilred] has joined #nixos-aarch64
evils has joined #nixos-aarch64
quinn has joined #nixos-aarch64
betaboon has joined #nixos-aarch64
nbp has joined #nixos-aarch64
<danielrf[m]> Since the NixOS image is the only one available for the pinecube, some people are getting their first taste of NixOS through that
iwq has quit [Ping timeout: 264 seconds]
<danielrf[m]> Starting with a 128MB ram pinecube on armv7l probably wouldn't be my first recommendation to some of these people starting using nixos though haha
iwq has joined #nixos-aarch64
<samueldr> lol
tilpner_ has joined #nixos-aarch64
tilpner has quit [Ping timeout: 260 seconds]
tilpner_ is now known as tilpner
<sphalerite> samueldr: I thought the only difference between the regular rk3399 and the pro was the AI accelerator thing
<samueldr> it seems it also allows using more RAM
<samueldr> I literally learned of that yesterday while looking at board offers from a vendor
<sphalerite> ah ok
<LinuxHackerman> nice
<dstzd> pretty sure the pro only allows "split" ram for the NPU not actually addressing the full space
<dstzd> but i could be wrong
<samueldr> plausible
<sphalerite> hm, maybe I flip between applications too much. To split "ah ok" and "nice" across my two identities…
<samueldr> hard facts are hard to come by
<sphalerite> danielrf[m]: hm true, they'll have to install nix on their desktops to even be able to deploy it…
<sphalerite> danielrf[m]: I guess it's better than if they start on an rpi though.
<samueldr> (or use the nix docker image?)
<samueldr> hopefully the non-alpine docker image comes soon, it'd be helpful for non-nix-users to properly validate using nix from the official docker image for some uses
<sphalerite> is that being worked on?
<samueldr> AFAIK yes
<samueldr> >> Adam 4 started working on adding Docker images as a Hydra build artifact. The current official Docker image is based on an Alpine Dockerfile, which can’t be built by Hydra and has some quirks. Using dockerTools.buildLayeredImage instead is probably the way forward.
<sphalerite> oh nice
<sphalerite> is that Adam as in adisbladis ?
<samueldr> yes
<samueldr> in the discourse post Adam links to adisbladis' github profile
<sphalerite> ah yes
FRidh has quit [Quit: Konversation terminated!]
alp has quit [Ping timeout: 272 seconds]
justanotheruser has quit [Ping timeout: 260 seconds]
justanotheruser has joined #nixos-aarch64
alp has joined #nixos-aarch64
orivej has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]