monk has left #nixos-aarch64 ["Error from remote client"]
monk has joined #nixos-aarch64
cole-h has quit [Quit: Goodbye]
sds2 has quit [Read error: Connection reset by peer]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
veleiro has quit [Ping timeout: 272 seconds]
lovesegfault has quit [Quit: WeeChat 3.0]
sds2 has quit [Quit: sds2]
sds2 has joined #nixos-aarch64
sds2 has quit [Client Quit]
sds2 has joined #nixos-aarch64
lovesegfault has joined #nixos-aarch64
alp__ has quit [Ping timeout: 272 seconds]
julm has quit [Ping timeout: 256 seconds]
alp__ has joined #nixos-aarch64
zupo has joined #nixos-aarch64
julm has joined #nixos-aarch64
sds2 has quit [Remote host closed the connection]
justanotheruser has quit [Ping timeout: 240 seconds]
orivej has quit [Ping timeout: 240 seconds]
alp__ has quit [Ping timeout: 272 seconds]
alp_ has joined #nixos-aarch64
FRidh has quit [Ping timeout: 272 seconds]
FRidh has joined #nixos-aarch64
alpernebbi has joined #nixos-aarch64
FRidh has quit [Ping timeout: 264 seconds]
FRidh has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
orivej has joined #nixos-aarch64
alp_ has quit [Remote host closed the connection]
zupo has joined #nixos-aarch64
alp_ has joined #nixos-aarch64
FRidh has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
zupo has joined #nixos-aarch64
FRidh has quit [Ping timeout: 256 seconds]
zupo has quit [Ping timeout: 256 seconds]
FRidh has joined #nixos-aarch64
justanotheruser has joined #nixos-aarch64
FRidh has quit [Ping timeout: 240 seconds]
FRidh has joined #nixos-aarch64
zupo has joined #nixos-aarch64
_Adluc_ has joined #nixos-aarch64
zupo has quit [Ping timeout: 240 seconds]
<patagonicus>
Well, it has nothing to do with nix (yet?), but I managed to get root on my LaMetric Time "smart" clock. Has an armv7 processor at 1GHz. Allwinner sun4i/sun5i family.
<patagonicus>
Good news: Go cross compiling works just fine and you can control the display via /dev/fb0. Will have to figure out how I can make wifi work.
<simpson>
Fun!
<simpson>
I wish we had a sunxi club. (I wish I had the energy for sunxi club.)
<NickHu>
Ok so I got a nixos image built and booting off my pinebook pro, but it can't connect to wifi with `wlan0: Failed to initialize driver interface`
<NickHu>
Is this something that's known? Do I just have to work-around it by doing the initial rebuild while tethered to my phone or something?
<hexa->
NickHu: redistributable firmware enabled?
<NickHu>
I just ran the `./build.sh` script from the wip-pinebook-pro repo
zupo has joined #nixos-aarch64
<Ke>
btw. I also bought that honeycomb
<sphalerite>
:D
<sphalerite>
and now… we wait!
<sphalerite>
Ke: are you using your kevin much? Which kernel and AP firmware are you using? How much of its functionality works?
<Ke>
I have irrational belief that it will replace some of the other bonk I have causing even net reduction of hw
<sphalerite>
haha exactly same
<Ke>
Kevin got completely replaced by pbp, which has been mostly idle as well, last I was running was linux-5.4 with everything mostly working
<sphalerite>
I want it to replace my linksys wrt, my mini pc, my nanopi NAS hack (which will first be replaced by a helios64), and my fritzbox DSL modem
<sphalerite>
ah ok
<sphalerite>
I've got the idea of making my bob usable back in my head, and it's… nontrivial, by the looks of it
<Ke>
the external display was occasionally picky, but everything worked at least once
<Ke>
also I was not able to get reliable 4K output ever
<Ke>
but experience was definitely better than with pinebook
<sphalerite>
right… were you using depthcharge?
<Ke>
yes, as factory configuration
<sphalerite>
ah right
<sphalerite>
so no rollbacks?
<Ke>
pbp was fully self built
<sphalerite>
(boot-time rollbacks)
<Ke>
I haven't yet gotten to running nixos on anything with a gui
<Ke>
all interactive machines are still debian
<sphalerite>
ooooh right
<sphalerite>
hm ok
<sphalerite>
but debian with gui works that well on the kevin?
<Ke>
yes, almost no issues
<Ke>
apart from running out of memory with chromium+riot-web
<sphalerite>
wow ok, stock debian kernel?
<Ke>
but that's not technically even a bug, just lack of memory probably
<Ke>
I had one patch to throttle damage flush ioctl for performance, kernel was mostly mainline
<Ke>
well I had also some btrfs patches
<sphalerite>
hm. I wonder how much of my problems is down to differences between nixos/debian kernels, how much of it is due to my coreboot+uboot firmware, and how much of it is due to kevin vs bob >.<
<Ke>
also I could do one rollback with 2 different bootsources on Kevin, I did that with debian
<Ke>
also you can manually add even more, since you can backup boot from sd
<Ke>
just put it in reader and dd the rollback you want to boot partition
<sphalerite>
hm yeah
<sphalerite>
maybe I should go back to stock firmwar.e
<sphalerite>
Or at least something with depthcharge.
<sphalerite>
But u-boot is nice :(
<Ke>
or you can create recovery linux on the sd that does the rollback without external reader
<Ke>
u-boot is nice, if it works without extra serial console hw
<Ke>
I wanted to do u-boot on kevin, but never got around doing that, as it was my daily driver
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
<Ke>
right now I could, but I am really hoping pbp starts working almost equally well
<Ke>
the keyboard is such that it can't physically be as good as Kevin keyboard
<Ke>
many key combinations I use on other keyboards just do excessive ghosting on pbp matrix
rajivr has quit [Quit: Connection closed for inactivity]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
cole-h has joined #nixos-aarch64
ryantrinkle has quit [Remote host closed the connection]
ryantrinkle has joined #nixos-aarch64
zupo has joined #nixos-aarch64
<sphalerite>
Ke: also, are you in America, to have got your hands on a kevin?
<Ke>
no I just ordered it to Finland
<Ke>
did not even need a mail proxy
<sphalerite>
huh ok
<Ke>
just some seller on ebay or something, maybe amazon
<Ke>
this may differ now, as the device I believe was obsolete even back then, even more so now
<sphalerite>
hm fair enough
<sphalerite>
ah well, no point in me buying one anyway
<sphalerite>
I have enough devices to get working, don't need more
zupo has quit [Ping timeout: 260 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
alp_ has quit [Ping timeout: 272 seconds]
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
red[evilred] has joined #nixos-aarch64
<red[evilred]>
umm
<red[evilred]>
what's a kevin?
<sphalerite>
red[evilred]: samsung chromebook plus
<sphalerite>
rk3399-based chromebook
zupo has joined #nixos-aarch64
zupo has quit [Client Quit]
<Ke>
it's really solid device, most notable flaw is that the display is relatively heavy which makes it unbalanced for some use cases, where laptops are typically balanced
<Ke>
IIRC
<Ke>
haven'
<Ke>
t used it for a while
<samueldr>
too bad scarlet / dumo has that weirder display, with an incomplete driver :(
<Ke>
well right now I would drool over rk3588 and prepare for the sorrow of it being all problems, when it gets here
<red[evilred]>
so it makes a vaugly decent nixos laptop?
<sphalerite>
red[evilred]: if it works as well as Ke's does on debian, I guess so
<sphalerite>
red[evilred]: I have a gru-bob (closely related model, but from a different manufacturer), and it has a bunch of problems
<Ke>
I don't see why nixos should work any worse, I just don't yet know how to setup desktop on nixos
<colemickens>
It seems like if Microsoft brings Android apps to the desktop, without Gapps, that a whole bunch of apps that wouldn't otherwise care, might support non-Gapps devices??
<colemickens>
Sorry, not a lot of context, rumors are Microsoft is working to bring Android compat layer to Windows (again).
<colemickens>
And that it might lack Google Play Services.
<samueldr>
no discussion AFAIK
<samueldr>
and well... I'd think it's not about bringing APKs to windows, but bringing android apps to the MS store
<samueldr>
so while I would expect APKs to be sideloadable, it's not the goal there
<samueldr>
it's more likely they intend you to build against "msapps" or something along the line
<samueldr>
just like how on all the other non-google android runtimes you don't really have a replacement for the google play services
<samueldr>
you're expected to interface with that service's libraries if you need things like in-app purchases
zupo has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]