00:21 <Armbian-Discord> <l​anefu> Sup

00:22 <IgorPec> europe is sleeping ;)

00:24 <Armbian-Discord> <l​anefu> Most of Europe

00:24 <Armbian-Discord> <l​anefu> One man doesn't know his own timezone

00:24 <IgorPec> haha

00:24 <IgorPec> i am just about to crash

00:24 <Armbian-Discord> <l​anefu> Possibly several men

00:25 <Armbian-Discord> <l​anefu> Cool nobody has screamed about mirror so I think we had a productive day on that front

00:25 <nekomancer[m]> seems so

00:26 <IgorPec> yeah, it was. i hope everything still works

00:27 <IgorPec> i am building beta images for the 3rd time now, alternative method. seems ok

00:27 <IgorPec> with docker

00:27 <lanefu> I hear some fans spinning

00:28 <IgorPec> here as well. we need another threadripper ;)

00:29 <lanefu> Haha. Anyway we have some more compute to utilize fortunately

00:29 <lanefu> My big server in Texas is almost ready

00:30 <IgorPec> arm64?

00:38 <Armbian-Discord> <l​anefu> 56 thread xeon

00:38 <Armbian-Discord> <l​anefu> It's the twin brother to my current big server

00:39 <Armbian-Discord> <l​anefu> Lanecloud

00:39 <IgorPec> ahaa, yeah you mentioned

00:39 <nekomancer[m]> xeon. so art-house.

00:39 <Armbian-Discord> <l​anefu> That dumb arm64 box is in Canada

00:39 <IgorPec> btw, i have changed PSU in threadripper setup and push it up for +20% and +200W on load

00:40 <IgorPec> it can be pushed even higher, but power consumption become ridiculos

00:40 <Armbian-Discord> <l​anefu> Hahaha that's just insane

00:40 <IgorPec> yeah, its totally crazy, but it works. and it stable

00:41 <Armbian-Discord> <l​anefu> Which is so awesome

00:43 <IgorPec> https://github.com/armbian/build/actions/runs/1580438207

00:43 <IgorPec> 48m

00:43 <IgorPec> CLI targets are build on public runners

00:44 <IgorPec> now i can crash ;)

00:50 <lanefu> Cya

00:50 <lanefu> Ha 48 min!

01:36 <stipa> heh

01:36 <stipa> good for solitaire

07:46 <IgorPec> once we add arnm server to CI, this time will go down at least for half

07:47 <IgorPec> one arm64 assembly can take 45m, while x86 on x86 is less then 10m

08:05 <lanefu> Let me see what resources my oracle VM has

08:09 <lanefu> Haha 24 gig

08:09 <IgorPec> memory?

08:09 <lanefu> Yeah

08:09 <IgorPec> that is plenty

08:09 <lanefu> 45 gig disk.

08:10 <IgorPec> but this is paid by usage or fixed?

08:10 <lanefu> I think I can add more its just fiddly

08:10 <lanefu> It's their free tier

08:10 <IgorPec> aha

08:11 <IgorPec> running two runners at one host? any troubles with that?

08:11 <IgorPec> we don't need virtualization

08:11 <lanefu> 1 runner per host

08:12 <lanefu> My tooling doesn't play nice with multiple

08:13 <lanefu> Ping is 10ms to my house I could mount my cache over network lol

08:13 <lanefu> I'll see if I can add disk tomorrow then add it

08:16 <IgorPec> yeah, no rush, get some sleep ;)

08:16 <IgorPec> just an idea for future improvements

08:17 <lanefu> Lol I'm upgrading it to hirsute from my phone

08:18 <IgorPec> https://rencanamu.id/assets/file_uploaded/editor/1466126335-tablet-hdc.jpg :)

08:20 <lanefu> Lol

14:32 <stipa> yeah, it seems like it's perfect time for google glasses

14:40 <e3ef13f4ff44> any update with OPi Zero 2?

14:44 <lanefu> that's a blanket question but maybe kprasadvnsi can answer a specific question

14:45 <e3ef13f4ff44> what is working what's not :P

14:46 <stipa> e3ef13f4ff44: switch to nightly and check

14:50 <kprasadvnsi> <e3ef13f4ff44> "any update with OPi Zero 2?" <- Not much progress. OPi ported wifi drivers to 5.13 so that would be next.

17:59 <lanefu> woohoo my QuartCM4 moduel came

19:34 <stipa> lanefu: ?

19:39 <lanefu> the Quartz64 compute module

19:39 <lanefu> i wanted to get more hardware that i don't have time for

20:41 <stipa> lanefu: i see that one

20:50 <stipa> Input Power: DC 12V

20:51 <stipa> Model "A"

23:04 <Armbian-Discord> <i​nvisiblek> I see a few months back some talk about dropping some devices (https://github.com/armbian/build/pull/3148) and wondering what a maintaining role entails. Specifically regarding the rockpro64. I've got quite a bit of experience maintaining android devices (CyanogenMod and the later LineageOS). At one point I was juggling at least a dozen devices. Those days have passed and I don't really have the time to maintain a desk

23:04 <Armbian-Discord> full devices anymore, but as I've been working with this rockpro64 lately and really liking the armbian ecosystem, I'm wondering what sort of responsibilities would be expected of as a maintainer of an armbian device.

23:05 <Armbian-Discord> <i​nvisiblek> Are we talking like "you better be updating that thing daily/weekly and making sure things don't break" or more of a "keep relatively up to date with edge and make the call to hold back a device if something comes up"?

23:07 <Armbian-Discord> <i​nvisiblek> I am planning to run this device 24/7 as basically a NAS. Updating/troubleshooting occasionally (once/twice a month?) would be acceptable for me to handle. Much more than that might be a bit much for me these days.

23:33 <Armbian-Discord> <l​anefu> @invisiblek take a look at this section https://docs.armbian.com/User-Guide_Board-Support-Rules/#criteria-for-supported

23:34 <Armbian-Discord> <l​anefu> Ideally you'd have a dedicated device for testing.

23:35 <Armbian-Discord> <i​nvisiblek> yea, that's kinda what i figured

23:35 <Armbian-Discord> <l​anefu> We can probably panhandle to get you a dedicated test board if you want to be a maintainer

23:35 <Armbian-Discord> <l​anefu> What country are you in?

23:35 <Armbian-Discord> <i​nvisiblek> us

23:35 <Armbian-Discord> <l​anefu> Sweet

23:36 <Armbian-Discord> <i​nvisiblek> kk, i'll have to let you guys know

23:36 <Armbian-Discord> <l​anefu> K ping us in the #onboarding channel

23:36 <Armbian-Discord> <i​nvisiblek> cool, thanks

23:37 <Armbian-Discord> <l​anefu> Also if you have more questions let us know

23:38 <Armbian-Discord> <i​nvisiblek> csc seems to really be about good enough for what i'm going to need here. that link is very helpful

23:39 <Armbian-Discord> <i​nvisiblek> i may hold tight and let it go csc if nobody takes over. at least for now

23:39 <Armbian-Discord> <l​anefu> Yeah it's easy to build CSC images

23:39 <Armbian-Discord> <i​nvisiblek> as long as i can expect some semblance of security patches and build other things occasionally myself, i may be good. probably still send any patches up though

23:40 <Armbian-Discord> <l​anefu> Yeah I'll benefit from most rk3399 stuff

23:40 <Armbian-Discord> <l​anefu> Kernel is shared

23:40 <Armbian-Discord> <i​nvisiblek> right, and it's mainline

23:40 <Armbian-Discord> <l​anefu> Really nuances in uboot and device tree stuff

23:41 <Armbian-Discord> <l​anefu> For a device like this its probably more like looking for performance regressions and if course things that brick it lol

23:41 <Armbian-Discord> <i​nvisiblek> right

23:48 <TRS-80> @invisiblek FWIW, I was considering taking up the role as well. But I don't really know what I am doing. lol I think some others may be interested as well. Point being, maybe 2-3 co-maintainers might "many hands make light work" (hopefully)

23:50 <TRS-80> even if you don't commit to the role, any patches you might submit to fix your own problems will of course help everyone and be greatly appreciated

23:50 <c0rnelius> As there really that much of a diff between that are rk3399 and the others? They share the same DTSI file correct? So from there wouldn't it just be corrections to the dts and some other onboard whatnots concerning wifi/bt if thats even there?

23:50 <Armbian-Discord> <i​nvisiblek> TRS-80 yea, that could work too. I recall seeing you mention this on the pine64 channels mentioning this a couple months ago when i was just getting started on this board.

23:51 <TRS-80> Yes. Since I only know how to beat the drum, that is what I focus on so far. :)

23:51 <Armbian-Discord> <i​nvisiblek> c0rnelius: yes pretty much. I would expect it to be a fairly low-effort-required device to keep going

23:52 <c0rnelius> Would be my opinion as well.

23:53 <TRS-80> hence me considering it as well, I figured it would be a good spot to learn; also where 2-3 co-maintainers would work well, like a junior (myself) with a mentor; although in general the channel and community are here, too

23:55 <Armbian-Discord> <T​onymac32> Trs-80 my Kasa smart plug randomly reappeared on my home assistant

23:56 <Armbian-Discord> <T​onymac32> And I'm confused

23:56 <c0rnelius> Basically my dislike of this new Armbian approach to support is what I read, yesterday. FREE FREE FREE and the complaining about it. Yes, Armbian does receive donations and not just from users.

23:57 <TRS-80> Tonymac32 lots of these things have auto config abilities to make things easier, do you think maybe that is the case?

23:57 <TRS-80> broadcast to LAN, etc.

23:57 <c0rnelius> But what about the people that are gonna now start supporting said boards to keep them in the Armbian lineup?

23:57 <Armbian-Discord> <T​onymac32> Yeah but they closed the local api port

23:57 <Armbian-Discord> <T​onymac32> Unless they reopened it

23:58 <TRS-80> Oh is Kasa some proprietary thing? In that case usually they are phoning out to do the auto config.

23:58 <Armbian-Discord> <T​onymac32> TP-Link lol

23:58 <TRS-80> Anyway, consumer things usually work that way, phoning out, to make things "easier."

23:59 <Armbian-Discord> <T​onymac32> ,barf

23:59 <Armbian-Discord> <T​onymac32> c0rnelius what about them?

23:59 <Armbian-Discord> <T​onymac32> I don't understand the question

23:59 <TRS-80> Hence the philosophy of NoT, or Network of Things, i.e., restrict them to their own network segment where they cannot get out to WAN