00:34 <c0rnelius> At what point in the boot process do armbian-hardware-optimization run? Is this done with a systemd service?

00:37 <c0rnelius> never mind, I found it.

01:07 <Armbian-Discord> <a​guapi> 'hola'

01:07 <Armbian-Discord> <a​guapi> --hola

01:08 <Armbian-Discord> <a​guapi> Hola

01:09 <Armbian-Discord> <a​guapi> -- hola

01:10 <Armbian-Discord> <a​guapi> -- probando traductor

01:11 <Armbian-Discord> <a​guapi> --Bier ;)

01:20 <Armbian-Discord> <a​guapi> Hola. Mi placa rock pi4b solo funciona un puerto usb

01:21 <Armbian-Discord> <a​guapi> Con la imagen hirsute 5.13 kernel de armbian

02:33 <stipa> E: The repository 'http://beta.armbian.com focal Release' no longer has a Release file.

02:33 <stipa> Certificate verification failed: The certificate is NOT trusted. The certificate chain uses expired certificate. Could not handshake: Error in the certificate verification. [IP: ....

02:34 <stipa> cand do update

02:42 <stipa> the translator bot doesn't work for peeps on discord

02:42 <stipa> since their nick is in front of the line

02:43 <stipa> -- Hola. Mi placa rock pi4b solo funciona un puerto usb

02:43 <ArmbianHelper> Hi there. My rock pi4b board only works one usb port [es~>eng]

02:43 <stipa> -- Con la imagen hirsute 5.13 kernel de armbian

02:43 <ArmbianHelper> With hirsute 5.13 kernel image from armbian [es~>eng]

02:45 <stipa> a​guapi try 5.12

02:56 <stipa> a​guapi come to IRC if you want to use translator bot, it doesn't work on Discord

03:10 <fizikz> good news, i can confirm (nightly) kernel 5.4.150 fixes the memory performance issue on the odroid hc2

03:12 <fizikz> any idea when 5.4.150 comes to stable?

05:39 <IgorPec> fizikz: https://docs.armbian.com/Process_Release-Model/

05:54 <fizikz> IgorPec: kernel revisions are often updated between releases, no?

05:58 <Armbian-Discord> <I​gorPec> its manual work

06:00 <Armbian-Discord> <I​gorPec> i simply don't have time to deal with this. even for this official release cycle we don't have a volunteer yet

06:05 <fizikz> kk

06:20 <IgorPec> fizikz: actually we have some automation on this, but i have been refactoring complete CI https://github.com/armbian/build/pull/3173 for past few weeks and this part was not addressed

10:50 <BluesBoy> hi, I have an olimex a20 micro board and I'm using the latest bullseye image with desktop, randomly the desktop freezes and I see this: https://pastebin.com/iGpZuVPf in dmesg

10:51 <BluesBoy> is this a known problem and if yes, is there a solution?

10:51 <Armbian-Discord> <I​gorPec> did you check forums? no idea

10:52 <BluesBoy> I did, haven't seen this issue

10:57 <Armbian-Discord> <I​gorPec> then this is the procedure https://www.armbian.com/bugs/

11:34 <stipa> IgorPec: what about my update error above, is it my fault or ?

11:35 <Armbian-Discord> <I​gorPec> on beta repository?

11:35 <stipa> yes

11:35 <Armbian-Discord> <I​gorPec> doing some changes, could be related

11:35 <stipa> nightly

11:35 <stipa> ok

11:36 <Armbian-Discord> <I​gorPec> didn't notice that things broke down . will check on when possible

11:36 <stipa> i noticed this morning

12:49 <Armbian-Discord> <x​p> Hey, just to follow up on my issue last night about bluetooth on the NanoPi Neo Air. I tried 'Armbian_5.93_Nanopiair_Debian_buster_next_4.19.64' to see if a legacy build might work and while '/sys/class/bluetooth' is now present at boot, bluetoothctl is showing no controllers available. For now I think I'll go back to the stock image from Friendlyarm but thank you all for trying to help

12:56 <stipa> yw

13:16 <Armbian-Discord> <I​gorPec> xp legacy kernels based images for Air are 3.4.y kernel based, where this could work, but not recommended. Everything else is mainline. We didn't use hacky approach as per FriendlyArm did, so modern kernel needs some additional work and bluetooth was never a priority.

13:23 <Armbian-Discord> <x​p> Aye that's fair enough, the Armbian use case is to be generic as possible over multiple SBCs so it'd be a tall order to accommodate all the edge case differences between them

13:24 <Armbian-Discord> <I​gorPec> keeping hardware features operational on moving kernel is simply costly problem

13:24 <Armbian-Discord> <I​gorPec> which is why vendors doesn't deal with that

13:24 <Armbian-Discord> <x​p> Yeah and the ones that do are 3x the price

13:24 <Armbian-Discord> <x​p> or more

13:25 <Armbian-Discord> <I​gorPec> yes. with a reason

13:26 <Armbian-Discord> <x​p> It's a shame because the NanoPi form factor is great but the OS image support is really non-standard and clumsy

13:26 <Armbian-Discord> <I​gorPec> it is shame, nobody asks us: "can you fix this and we will cover the time you will lost fixing that"

13:27 <Armbian-Discord> <I​gorPec> this is general problem

13:28 <Armbian-Discord> <I​gorPec> on top on things we already fix https://docs.armbian.com/User-Guide_FAQ/#development-time

13:28 <Armbian-Discord> <x​p> The incentives aren't aligned. One thing you could look at is something like quadratic funding

13:29 <Armbian-Discord> <I​gorPec> you need this to be fixed

13:29 <Armbian-Discord> <I​gorPec> 🙂

13:31 <Armbian-Discord> <I​gorPec> our organisation is too small to arrange all this and also work on this

13:32 <Armbian-Discord> <I​gorPec> which is why there is a donation button, one can provide recurrent subscription ... and that's about it. if we need to expand this, we have to stop coding and do that ...

13:39 <Armbian-Discord> <x​p> I'm not sure what the answer is but it sounds like you need to find a different model, maybe its quadratic funding maybe its something else. Right now I thinks its easier, quicker and cheaper for me to just use the Friendlyarm image and modify my devops script to apply an overlay to it

13:50 <Armbian-Discord> <I​gorPec> but we don't need to fix this bug. you do. it is a lot cheaper to say - use friendly arm software

14:07 <Armbian-Discord> <x​p> hypothetically how much do you think it would cost to fund mainline bluetooth support being added to the NanoPi Neo Air board and what is your estimate on how long it would take?

14:36 <Armbian-Discord> <T​onymac32> Not knowing the scope of the issue, can't estimate. More than I would want to pay for sure, even if it only took a few hours. 🤔

15:05 <lanefu> more than soldering a usb bluetooth module

15:10 <c0rnelius> I've been trying to get that to work on the NEO Plus2 for several months.

15:11 <steev> isn't it just a matter of getting the dts bits correct?

15:11 <c0rnelius> More to it than that I believe.

15:13 <c0rnelius> Here is the patch I was testing at the time on 5.10.y -> https://github.com/pyavitz/debian-image-builder/blob/backup-080621/patches/allwinner/nanopi/nano_pi_neo_plus2_bluetooth.disable

15:13 <c0rnelius> I got bluetooth I think to come up like once or twice but it would make the board unstable.

15:14 <c0rnelius> So I just gave up.

15:15 <steev> as it happens, i have a neo plus2 and would like bluetooth to work so i might poke at it. though, why the heck is it touching the rtc driver?

15:16 <c0rnelius> I can't recall now? That was 12 months go :)

15:16 <stipa> there's bunch of non logical stuff in driver code

15:16 <stipa> especially one without comments

15:17 <c0rnelius> take out the rtc bit see what happens?

15:17 <steev> eventually, i'm building a new 5.14 for my c630 first

15:18 <stipa> is there any point in using JTAG with SBCs?

15:19 <steev> if you're not doing development, no

15:19 <stipa> more like, fixing crap

15:20 <stipa> i've look around and there's ome kind of muxing on the gpio port

15:21 <stipa> i have no idea how to make jtag + sbc connection

15:21 <stipa> in uboot maybe?

15:22 <stipa> i guess i first have to activate jtag somewhere

15:22 <stipa> it's not directly available on power up

15:30 <stipa> i guess that everything that's in the soc could be accessed with jtag

15:30 <stipa> maybe not chips outside of it

15:31 <stipa> if i'm not mistaken with jtag registers can be switched in real time

15:32 <stipa> a wild guess

17:01 <IgorPec> werner: i have clicked upgrade on forum. hope its ok ;)

17:10 <Armbian-Discord> <W​erner> There is only one way to find out 😛