ArmbianHelper changed the topic of #armbian to: armbian - Linux for ARM development boards | | Github: | Commits: #armbian-commits | Developer talk: #armbian-devel | Forum/Twitter feed: #armbian-rss | Type 'help' for help | Logs: ->
rhagu has quit [Quit: Leaving]
<Armbian-Discord> <l​anefu> Sup
<IgorPec> europe is sleeping ;)
<Armbian-Discord> <l​anefu> Most of Europe
<Armbian-Discord> <l​anefu> One man doesn't know his own timezone
* nekomancer[m] the last of us
<IgorPec> haha
<IgorPec> i am just about to crash
<Armbian-Discord> <l​anefu> Possibly several men
<Armbian-Discord> <l​anefu> Cool nobody has screamed about mirror so I think we had a productive day on that front
<nekomancer[m]> seems so
<IgorPec> yeah, it was. i hope everything still works
<IgorPec> i am building beta images for the 3rd time now, alternative method. seems ok
<IgorPec> with docker
<lanefu> I hear some fans spinning
<IgorPec> here as well. we need another threadripper ;)
<lanefu> Haha. Anyway we have some more compute to utilize fortunately
<lanefu> My big server in Texas is almost ready
<IgorPec> arm64?
<Armbian-Discord> <l​anefu> 56 thread xeon
<Armbian-Discord> <l​anefu> It's the twin brother to my current big server
<Armbian-Discord> <l​anefu> Lanecloud
<IgorPec> ahaa, yeah you mentioned
<nekomancer[m]> xeon. so art-house.
<Armbian-Discord> <l​anefu> That dumb arm64 box is in Canada
<IgorPec> btw, i have changed PSU in threadripper setup and push it up for +20% and +200W on load
<IgorPec> it can be pushed even higher, but power consumption become ridiculos
<Armbian-Discord> <l​anefu> Hahaha that's just insane
<IgorPec> yeah, its totally crazy, but it works. and it stable
<Armbian-Discord> <l​anefu> Which is so awesome
<IgorPec> 48m
<IgorPec> CLI targets are build on public runners
<IgorPec> now i can crash ;)
<lanefu> Cya
<lanefu> Ha 48 min!
alekksander has quit [Quit: Konversation terminated!]
<stipa> heh
<stipa> good for solitaire
elroo has quit [Ping timeout: 256 seconds]
Guest64873 has joined #armbian
Guest64873 has left #armbian [#armbian]
Malditron has quit [Quit: Konversation terminated!]
<IgorPec> once we add arnm server to CI, this time will go down at least for half
<IgorPec> one arm64 assembly can take 45m, while x86 on x86 is less then 10m
<lanefu> Let me see what resources my oracle VM has
<lanefu> Haha 24 gig
<IgorPec> memory?
<lanefu> Yeah
<IgorPec> that is plenty
<lanefu> 45 gig disk.
<IgorPec> but this is paid by usage or fixed?
<lanefu> I think I can add more its just fiddly
<lanefu> It's their free tier
<IgorPec> aha
<IgorPec> running two runners at one host? any troubles with that?
<IgorPec> we don't need virtualization
<lanefu> 1 runner per host
<lanefu> My tooling doesn't play nice with multiple
<lanefu> Ping is 10ms to my house I could mount my cache over network lol
<lanefu> I'll see if I can add disk tomorrow then add it
<IgorPec> yeah, no rush, get some sleep ;)
<IgorPec> just an idea for future improvements
<lanefu> Lol I'm upgrading it to hirsute from my phone
<lanefu> Lol
alekksander has joined #armbian
chris has joined #armbian
chris is now known as Guest7
Proxysna has joined #armbian
Proxysna has quit [Remote host closed the connection]
Guest7 has quit [Quit: Guest7]
alekksander has quit [Read error: Connection reset by peer]
alekksander has joined #armbian
<stipa> yeah, it seems like it's perfect time for google glasses
<e3ef13f4ff44> any update with OPi Zero 2?
<lanefu> that's a blanket question but maybe kprasadvnsi can answer a specific question
<e3ef13f4ff44> what is working what's not :P
<stipa> e3ef13f4ff44: switch to nightly and check
<kprasadvnsi> <e3ef13f4ff44> "any update with OPi Zero 2?" <- Not much progress. OPi ported wifi drivers to 5.13 so that would be next.
archetech has joined #armbian
alekksander has quit [Quit: Konversation terminated!]
smcavoy_ has quit [Ping timeout: 268 seconds]
smcavoy has joined #armbian
<lanefu> woohoo my QuartCM4 moduel came
oida has joined #armbian
invisiblek has joined #armbian
alekksander has joined #armbian
<stipa> lanefu: ?
alekksander has quit [Quit: Konversation terminated!]
<lanefu> the Quartz64 compute module
<lanefu> i wanted to get more hardware that i don't have time for
alekksander has joined #armbian
Redentor has joined #armbian
Redentor has quit [Remote host closed the connection]
crabbedhaloablut has quit [Quit: No Ping reply in 180 seconds.]
<stipa> lanefu: i see that one
<stipa> Input Power: DC 12V
<stipa> Model "A"
crabbedhaloablut has joined #armbian
TRS-80 has joined #armbian
alekksander has quit [Quit: Konversation terminated!]
<Armbian-Discord> <i​nvisiblek> I see a few months back some talk about dropping some devices ( 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
<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.
<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"?
<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.
threenp1111111 has joined #armbian
samythemany11117 has joined #armbian
threenp11111111 has joined #armbian
samythemany11110 has joined #armbian
threenp111111 has quit [Ping timeout: 276 seconds]
samythemany11114 has quit [Ping timeout: 276 seconds]
samythemany11117 has quit [Ping timeout: 276 seconds]
threenp1111111 has quit [Ping timeout: 276 seconds]
archetech has quit [Quit: Konversation terminated!]
<Armbian-Discord> <l​anefu> @invisiblek take a look at this section
<Armbian-Discord> <l​anefu> Ideally you'd have a dedicated device for testing.
<Armbian-Discord> <i​nvisiblek> yea, that's kinda what i figured
<Armbian-Discord> <l​anefu> We can probably panhandle to get you a dedicated test board if you want to be a maintainer
<Armbian-Discord> <l​anefu> What country are you in?
<Armbian-Discord> <i​nvisiblek> us
<Armbian-Discord> <l​anefu> Sweet
<Armbian-Discord> <i​nvisiblek> kk, i'll have to let you guys know
<Armbian-Discord> <l​anefu> K ping us in the #onboarding channel
<Armbian-Discord> <i​nvisiblek> cool, thanks
<Armbian-Discord> <l​anefu> Also if you have more questions let us know
archetech has joined #armbian
<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
<Armbian-Discord> <i​nvisiblek> i may hold tight and let it go csc if nobody takes over. at least for now
<Armbian-Discord> <l​anefu> Yeah it's easy to build CSC images
<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
<Armbian-Discord> <l​anefu> Yeah I'll benefit from most rk3399 stuff
<Armbian-Discord> <l​anefu> Kernel is shared
<Armbian-Discord> <i​nvisiblek> right, and it's mainline
<Armbian-Discord> <l​anefu> Really nuances in uboot and device tree stuff
<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
<Armbian-Discord> <i​nvisiblek> right
<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)
<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
<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?
<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.
<TRS-80> Yes. Since I only know how to beat the drum, that is what I focus on so far. :)
<Armbian-Discord> <i​nvisiblek> c0rnelius: yes pretty much. I would expect it to be a fairly low-effort-required device to keep going
<c0rnelius> Would be my opinion as well.
<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
<Armbian-Discord> <T​onymac32> Trs-80 my Kasa smart plug randomly reappeared on my home assistant
<Armbian-Discord> <T​onymac32> And I'm confused
<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.
<TRS-80> Tonymac32 lots of these things have auto config abilities to make things easier, do you think maybe that is the case?
<TRS-80> broadcast to LAN, etc.
<c0rnelius> But what about the people that are gonna now start supporting said boards to keep them in the Armbian lineup?
<Armbian-Discord> <T​onymac32> Yeah but they closed the local api port
<Armbian-Discord> <T​onymac32> Unless they reopened it
<TRS-80> Oh is Kasa some proprietary thing? In that case usually they are phoning out to do the auto config.
<Armbian-Discord> <T​onymac32> TP-Link lol
<TRS-80> Anyway, consumer things usually work that way, phoning out, to make things "easier."
<Armbian-Discord> <T​onymac32> ,barf
<Armbian-Discord> <T​onymac32> c0rnelius what about them?
<Armbian-Discord> <T​onymac32> I don't understand the question
<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