00:14 <Armbian-Discord> <G​IDDY> are these tests useful ?

00:14 <Armbian-Discord> <G​IDDY> https://github.com/armbian/autotests

07:01 <Armbian-Discord> <I​gorPec> @GIDDY the only test script that is currently in use is https://github.com/armbian/build/actions/workflows/smoke-tests.yml -> https://github.com/armbian/scripts/blob/master/.github/workflows/smoke-tests.yml

07:48 <Armbian-Discord> <m​ulti_io> I'm trying to compile in a VM (in UTM) on an m1 Mac, and it doesn't even compile u-boot

07:48 <Armbian-Discord> <m​ulti_io> ```

07:48 <Armbian-Discord> <m​ulti_io> == u-boot make clearfog_defconfig ==

07:48 <Armbian-Discord> <m​ulti_io> == u-boot make ==

07:48 <Armbian-Discord> <m​ulti_io> ccache: error: Could not find compiler "arm-linux-gnueabihf-gcc" in PATH

07:48 <Armbian-Discord> <m​ulti_io> ccache: error: Could not find compiler "arm-linux-gnueabihf-gcc" in PATH

07:48 <Armbian-Discord> <m​ulti_io> dirname: missing operand

07:48 <Armbian-Discord> <m​ulti_io> ```

07:48 <Armbian-Discord> <m​ulti_io> is this supported?

07:49 <Armbian-Discord> <m​ulti_io> (this is an ARM VM, obviously)

07:50 <Armbian-Discord> <I​gorPec> arm64 can build most of the things, but u-boot

07:52 <Armbian-Discord> <m​ulti_io> so it can't compile an arm64 u-boot binary on an arm64 machine? 😅

07:53 <Armbian-Discord> <m​ulti_io> anyway, what I take from this is that building on an arm64 machine isn't really supported for now? You need an amd64 machine?

07:54 <Armbian-Discord> <I​gorPec> it can, but you will need to fix compilation issues due to compiling old code with new compiler

07:54 <Armbian-Discord> <I​gorPec> its an expense

07:56 <Armbian-Discord> <m​ulti_io> why does it work on amd64? Is the arm compiler package an older compiler version there?

07:57 <Armbian-Discord> <I​gorPec> because most of arm hw support (back then in 100%) was developed on x86 with cross compilation tools that we are still dragging with in some (luckily small) cases

07:57 <Armbian-Discord> <I​gorPec> and this is one of them

07:59 <Armbian-Discord> <I​gorPec> and that is not all. in some cases we have proprietary tools for packing u-boot + closed bootloader that comes in x86 binary form only.

08:01 <Armbian-Discord> <I​gorPec> and until / if those tools are reverse engineered, you need to follow vendors directives

12:15 <Armbian-Discord> <J​ason123> Building an image takes a few mins sometimes on my ryzen 5 desktop but on arm it would take much longer

12:15 <Armbian-Discord> <J​ason123> And some arm hardware is really not great

14:20 <Armbian-Discord> <T​onymac32> "some" 😂

14:25 <Armbian-Discord> <T​onymac32> For packaging it will be better since our x86 stuff is single threaded via qemu

14:25 <Armbian-Discord> <T​onymac32> But otherwise, yeah

14:33 <Armbian-Discord> <r​pardini> plug: armbian-next should build most stuff successfully on arm64

14:34 <Armbian-Discord> <r​pardini> and I will personally go to great lengths to fix if it doesn't and you prove it 😉

14:40 <Armbian-Discord> <I​gorPec> @Jason123 on quick dirty not scientific manual compare of https://github.com/armbian/cache/actions/runs/3714264095/ it looks that 16gb rockpi 5 with 2 runners is 2x faster then 128gb 5950x with a few more (qemu assembly of armhf)

14:55 <Armbian-Discord> <J​ason123> oops

14:56 <Armbian-Discord> <J​ason123> oh so cross compiling is slower in theory?

14:59 <Armbian-Discord> <I​gorPec> this is packages assembly

15:00 <Armbian-Discord> <I​gorPec> yes, overhead ... but you can't compare arm cores vs intel just like that

15:01 <Armbian-Discord> <I​gorPec> ryzen core performance is way better, so we compress all images exclusively on big x86 iron

15:10 <Armbian-Discord> <M​anoftheSea> are the tools to package u-boot with closed blobs really arch specific? I thought they were scripts or were simple concatenation. Hm, too bad.

15:29 <Armbian-Discord> <T​enkawa> no.. I haven't used an x86/64 to build an ARM soc in 2 years

15:30 <Armbian-Discord> <T​onymac32> Some are

15:30 <Armbian-Discord> <T​onymac32> But usually a cross method is created because no one wants to put up with that

15:30 <Armbian-Discord> <T​enkawa> exactly

15:31 <Armbian-Discord> <T​onymac32> But again it's work no one but the assholes who make the processors should be doing 😂

15:31 <Armbian-Discord> <T​enkawa> a "physical" x86 however is not needed

15:31 <Armbian-Discord> <T​onymac32> I'm a very physical being

15:31 <Armbian-Discord> <T​onymac32> 🤣🤣🤣

15:32 <Armbian-Discord> <T​enkawa> your loss

15:32 <Armbian-Discord> <T​enkawa> lol

15:33 <Armbian-Discord> <T​onymac32> I have 30 cores available for these tasks, no big deal 😄

15:34 <Armbian-Discord> <T​onymac32> (the kids don't know what their computers do when they are sleeping)

15:34 <Armbian-Discord> <T​enkawa> lol

15:34 <Armbian-Discord> <T​enkawa> haahaa

15:35 <Armbian-Discord> <T​enkawa> When you going to teach them the "right" way to use the computer?

15:35 <Armbian-Discord> <T​heBug> Hey guys, we are officially announcing the Armbian Config refactoring project - https://forum.armbian.com/topic/25132-armbian-configurator-refactor-project/ -- Please check it out and if you want to get involved apply for the open volunteer / paid development positions available ( https://forum.armbian.com/staffapplications/application/14-bash-developer/ ).

15:36 <Armbian-Discord> <T​enkawa> I got such a young start....I had a computer before I could walk... (I could read before most though)

15:41 <c0rnelius> does it need to be driven using dialog or can whiptail be used?

15:45 <Armbian-Discord> <T​heBug> @c0rnelius If you have question about the project please ask them in the thread there and we will try to address so it doesn't get asked over and over

15:45 <c0rnelius> k

15:51 <Armbian-Discord> <T​heBug> Thanks 🙂

20:20 <popolon> hi

20:21 <popolon> I looked at the kernel version of the image from RadXa, (5.10.66), downgraded in armbian-config to this kernl, and now have HDMI display

20:21 <popolon> the problem was with the 5.10.155 if I'm not wrong

20:33 <[TheBug]> oddly that means nothing to me at least since I have no idea what board you are talking about

20:34 <[TheBug]> but glad it is working for you now

20:34 <popolon> The default ubuntu firefox in snapd doesn't allow to really disable google and add own search engine??? WTF

20:34 <popolon> Radxa Rock5 Model B (RK3588)

20:35 <[TheBug]> ahh well there will be tons of issues with stuff for that probably over time lol

20:35 <[TheBug]> especially if your living on the edge

20:35 <[TheBug]> and those are all edge builds if I recall

20:35 <popolon> mesa seems to work already nicely :). The current problem with driver was mainly due to not know hw limits of this model, the change from Alyssa few days ago should resolve this

20:36 <popolon> @Thebug: I know, I know :) (closed source kernel etc...)

20:36 <popolon> already work pretty well, hope boot will be merged in 6.3, most things seem to be in 6.2

20:37 <popolon> sudo add-apt-repository ppa:mozillateam/ppa

20:37 <popolon> :)

20:38 <popolon> https://www.omgubuntu.co.uk/2022/04/how-to-install-firefox-deb-apt-ubuntu-22-04

20:43 <Armbian-Discord> <I​gorPec> our desktop should have apt firefox & chromium

20:50 <popolon> oops, my bad, I see that on Arch too the last firefox doesn't have anymore the option to add personnal search engine? in the parameters => search

20:51 <Armbian-Discord> <I​gorPec> in any case, we don't tackle browsers in any way. except setting home page - if that still works

20:51 <popolon> only to what ff suggest by their extension market

20:52 <popolon> I thought that was the snapd Ubuntu package, sorry.

20:53 <Armbian-Discord> <I​gorPec> we are trying to remove ubuntu influence from our builds as much as possible

20:54 <popolon> very nice thing ! Thank you very much for your work

21:06 <Armbian-Discord> <E​feCTN> Really cool

21:06 <Armbian-Discord> <E​feCTN> Like mint

21:08 <popolon> is it possible to totally purge snapd, without problem ?

21:09 <Armbian-Discord> <I​gorPec> snapd is not even installed

21:09 <Armbian-Discord> <I​gorPec> and yes, you can remove it after too

21:14 <[TheBug]> if you install a meta package that uses a snap it will auto install snapd whether you tell it to or not

21:19 <popolon> it looks like gnome is installed by snap

21:19 <popolon> maybe this is after some changes I made in armbian-config

21:28 <popolon> Linux rock-5b 5.10.110-rockchip-rk3588, after an apt upgrade, the system reinstalled it and again no HDMI. will test other one, and freeze to the most recent I can

23:00 <popolon> tried XFCE image as restarting from scratch to be sure, and just understood 5.10.110-rockchip-rk3588, is the current default kernel, that don't have HDMI output in my case. There is only 5.10.110 and 5.10.72 on armbian-config, on .72 display work (Armbian logo at boot, terminal) but unable to run lightdm(X) or weston (wayland)

23:00 <popolon> I sent a system diag

23:01 <popolon> maybe need "full firmware package", ok