<DC-IRC> [Discord] <rpardini> Hey AF. I got my rpi4b out of the drawer for this.
<DC-IRC> [Discord] <rpardini> Built `BOARD=rpi4b BRANCH=current` and got a `6.6.72-current-bcm2711`
<DC-IRC> [Discord] <rpardini> Did `apt install linux-headers-current-bcm2711` followed by `apt install v4l2loopback-dkms`...
<DC-IRC> [Discord] <rpardini> Then did `modprobe v4l2loopback` and got in dmesg:
<DC-IRC> [Discord] <rpardini> ```
<DC-IRC> [Discord] <rpardini> v4l2loopback: loading out-of-tree module taints kernel.
<DC-IRC> [Discord] <rpardini> v4l2loopback driver version 0.13.2 loaded
<DC-IRC> [Discord] <rpardini> ```
<DC-IRC> [Discord] <amazingfate> I have checked that rpi kernel doesn't have this issue
<DC-IRC> [Discord] <rpardini> so seems to work.
<DC-IRC> [Discord] <amazingfate> there is a mainline commit to 6.6.54
<DC-IRC> [Discord] <rpardini> Indeed. Excellent work finding it. Super thanks
<DC-IRC> [Discord] <rpardini> I think the bcm2711 kernel is a moving target, as we point to RPi foundation's repo branch `rpi-6.6.y` and they rebase/merge fixes without us doing anything.
<DC-IRC> [Discord] <amazingfate> Yes, I have created a pr to remove mainline lts kernel tags from sunxi and meson. But that's under discussion.
<DC-IRC> [Discord] <rpardini> Yeah. Leo (theGoing) wants to do things his way for sunxi. He can either bump the tag, take an extra patch, or opt-out of BTF.
<DC-IRC> [Discord] <rpardini> For meson (32-bit)... the tag is there due to some bug from long ago. But again is the same situation.
<DC-IRC> [Discord] <rpardini> Could we backport the needed patches into armbian/linux-rockchip? Then we can de-opt-out from BTF and life goes on
<DC-IRC> [Discord] <amazingfate> Sure, and chainsx will backport the patch to phytium-embedded
<DC-IRC> [Discord] <rpardini> Excellent. Thanks again!
<DC-IRC> [Discord] <igorpec> for sunxi we don't have much options - If Leo stops but we are at branch, it will fall apart very fast ... there are too many patches.
<DC-IRC> [Discord] <rpardini> Simplest is to allow him to do his way/pace, when he reaches the version with fix all will be fine.
<DC-IRC> [Discord] <rpardini> Until then simply disable BTF for sunxi
<DC-IRC> [Discord] <amazingfate> He is bumping to 6.6.72, so BTF issue should be fixed.
<DC-IRC> [Discord] <igorpec> yeah, i will merge those. let him do how he think is the best.
<DC-IRC> [Discord] <igorpec> i started moving current to 6.12 at UEFI, what to do with EDGE here?
<DC-IRC> [Discord] <rpardini> 6.13, I'd say -- if lucky patches should just apply
<DC-IRC> [Discord] <rpardini> I'll do it eventually if you don't
<DC-IRC> [Discord] <rpardini> For bcm2711 / rpi, I'd say keep current at 6.6.y for w
<DC-IRC> [Discord] <rpardini> For bcm2711 / rpi, I'd say keep current at 6.6.y for now
<DC-IRC> [Discord] <rpardini> it's too crazy upstream
<DC-IRC> [Discord] <igorpec> uefi, there are little patches
<DC-IRC> [Discord] <rpardini> uefi I think the only patch that might break is Phytium network shit
<DC-IRC> [Discord] <rpardini> is old DTB vs ACPI subject that will never be solved
<DC-IRC> [Discord] <igorpec> yes, that can be simply left out, disable
<DC-IRC> [Discord] <rpardini> if it breaks just disable
<DC-IRC> [Discord] <igorpec> let me complete this pr
<DC-IRC> [Discord] <rpardini> it's only me and another guy with working Phytium D2000's I think
<DC-IRC> [Discord] <igorpec> yeah, not worth the troubles. i am also disabling that weird visionfive stuff
<DC-IRC> [Discord] <rpardini> yeah. those riscv64's have gone nowhere, interest skyrocket at launch but then died
<DC-IRC> [Discord] <igorpec> i will leave families, just disable targets.
<DC-IRC> [Discord] <rpardini> yeah nice so people can resurrect one day if they want
<DC-IRC> [Discord] <igorpec> for armbian-config i have some hard decisions ... armbian repo / no armbian repo question
<DC-IRC> [Discord] <igorpec> should we leave this pulling from github repo in production
<DC-IRC> [Discord] <rpardini> I've... not too many opinions on that.
<DC-IRC> [Discord] <rpardini> I just need minimal/cloud images to be clean-ish of any external repos
<DC-IRC> [Discord] <rpardini> so as long as one can disable easily could be ext repo in my view
<DC-IRC> [Discord] <rpardini> GH repo is github-pages?
<DC-IRC> [Discord] <igorpec> yes
<DC-IRC> [Discord] <rpardini> if those get too many hits, GH won't be too happy
<DC-IRC> [Discord] <rpardini> but too many hits means extreme success too
<DC-IRC> [Discord] <igorpec> i can mirror that output directly to armbian apt
<DC-IRC> [Discord] <rpardini> for now I'd say it's fine
<DC-IRC> [Discord] <igorpec> just the problem is that build FW does not include armbian repo at certain time , while i need to install this from armbian repo
<DC-IRC> [Discord] <rpardini> hmm. the (old) armbian-config is an artifact right?
<DC-IRC> [Discord] <igorpec> not anymore with this PR
<DC-IRC> [Discord] <igorpec> old yes
<DC-IRC> [Discord] <rpardini> cos if you do the new one as a new artifact (armbian-configng or something) then everything falls into place
<DC-IRC> [Discord] <rpardini> but also ties configng to armbian/build
<DC-IRC> [Discord] <rpardini> I guess you want to have independent releases
<DC-IRC> [Discord] <igorpec> hmm, well, armbian-config generation is now fully outside
<DC-IRC> [Discord] <igorpec> yes, i don't want to tie versioning to FW
<DC-IRC> [Discord] <igorpec> as this has little in common
<DC-IRC> [Discord] <igorpec> here we would need to add repo and install via apt
<DC-IRC> [Discord] <rpardini> hmm I see, but repo is not enabled "yet" at that spot
<DC-IRC> [Discord] <rpardini> maybe can find a later spot to do it
<DC-IRC> [Discord] <igorpec> to install later. that would do
<DC-IRC> [Discord] <rpardini> oh and if it is not standard armbian repo, then also need to add that repo to sources
<DC-IRC> [Discord] <igorpec> i can add auto-adding to standard repo
<DC-IRC> [Discord] <igorpec> perhaps that would be best
<DC-IRC> [Discord] <igorpec> so we don't drag yet another distro to users
<DC-IRC> [Discord] <igorpec> so we don't drag yet another repo to users
<DC-IRC> [Discord] <rpardini> I see yeah might be. standard repo mixes up externals with build-produced artifacts though, which always leads to confusion. but if done in a late-enough spot during image build should be fine
<DC-IRC> [Discord] <igorpec> ok, late. where?
<DC-IRC> [Discord] <rpardini> I'm looking.... wait
<DC-IRC> [Discord] <rpardini> so order is
<DC-IRC> [Discord] <rpardini> - `get_or_create_rootfs_cache_chroot_sdcard()`
<DC-IRC> [Discord] <rpardini> - `install_distribution_specific()`
<DC-IRC> [Discord] <rpardini> - `install_distribution_agnostic()`
<DC-IRC> [Discord] <rpardini> - `customize_image()` - has hooks for extension
<DC-IRC> [Discord] <rpardini> - `create_sources_list_and_deploy_repo_key()`
<DC-IRC> [Discord] <rpardini> there's nothing "later" than that except cleanup stuff
<DC-IRC> [Discord] <rpardini> lets create one
<DC-IRC> [Discord] <rpardini> no, lets create 2 spots
<DC-IRC> [Discord] <rpardini> one runs always, right before cleanups
<DC-IRC> [Discord] <rpardini> one only runs if SKIP_ARMBIAN_REPO is unset (default)
<DC-IRC> [Discord] <rpardini> so you can do all with extension and enable it by default
<DC-IRC> [Discord] <igorpec> when skip_armbian_repo is not applied, so you get clean images
<DC-IRC> [Discord] <rpardini> now the main problem in computer science, _naming things_
<DC-IRC> [Discord] <rpardini> `post_repo_customize_image` ?
<DC-IRC> [Discord] <igorpec> here we have armbian.apt enabled, ok
<DC-IRC> [Discord] <igorpec> 🫘 🥕 time 😉 l8r
<DC-IRC> [Discord] <igorpec> i am not sure to understand how to put this together, extension that gets enabled around there or a new function (file) similar as this https://github.com/armbian/build/blob/main/lib/functions/rootfs/customize.sh
<DC-IRC> [Discord] <rpardini> I send PR soon as test is done
<DC-IRC> [Discord] <rpardini> https://github.com/armbian/build/pull/7719
<DC-IRC> [Discord] <rpardini> wtf my PRs have duplicate summary 3x on GH Discord previews...
<DC-IRC> [Discord] <rpardini> @igorpec this might work https://github.com/armbian/build/pull/7719
<DC-IRC> [Discord] <igorpec> and now adding this way? https://github.com/armbian/build/pull/7716/files
<DC-IRC> [Discord] <igorpec> i am a bit rusted in extension hooking
<DC-IRC> [Discord] <rpardini> oh ok here you are adding gh-pages repo
<DC-IRC> [Discord] <igorpec> ah, we said without
<DC-IRC> [Discord] <rpardini> but general idea is correct
<DC-IRC> [Discord] <igorpec> ok, removing that part then
<DC-IRC> [Discord] <rpardini> yeah you can just do install only directly in `post_armbian_repo_customize_image`
<DC-IRC> [Discord] <rpardini> if gh-pages repo is wanted, you can do that too, but use a `custom_apt_repo` to write sources list
<DC-IRC> [Discord] <rpardini> and apt-update will be called for you at the correct time
<DC-IRC> [Discord] <rpardini> also dont' forget to enable extension
<DC-IRC> [Discord] <igorpec> where we have place for those commons?
<DC-IRC> [Discord] <rpardini> I think a popular place is main-config.sh
<DC-IRC> [Discord] <rpardini> can do some conditional, enable only for non-minimal, etc
<DC-IRC> [Discord] <rpardini> only has to be before `initialize_extension_manager` otherwise anywhere is good
<DC-IRC> [Discord] <igorpec> ok
<DC-IRC> [Discord] <igorpec> lets try and test
<DC-IRC> [Discord] <rpardini> later we can look into the dependencies of new armbian-config and see if we can speed up things by adding deps to rootfs
<DC-IRC> [Discord] <igorpec> it is very low on dependencies now
<DC-IRC> [Discord] <igorpec> i think jusst jq, whiptail is outside defatuils
<DC-IRC> [Discord] <rpardini> yeah should be fine -- adding those to cli packages rootfs will make installing during image stage much faster
<DC-IRC> [Discord] <rpardini> but for later when more stable maybe
<DC-IRC> [Discord] <rpardini> hmm btw I see maybe configng package itself is adding a sources.list
<DC-IRC> [Discord] <igorpec> yes, it does, hmm
<DC-IRC> [Discord] <igorpec> there are pros and cons having this on a live repo
<DC-IRC> [Discord] <igorpec> faster delivery of tools. its still under heavy development but also has many checks so we don't ship broken builds
<DC-IRC> [Discord] <rpardini> maybe instead of package, use a simple wrapper and then git...
<DC-IRC> [Discord] <rpardini> in wrapper can decide about BETA or such and pull either from main or stable branch one day
<DC-IRC> [Discord] <rpardini> I dunno, sincerely.
<DC-IRC> [Discord] <igorpec> yeah, i know 😉
<DC-IRC> [Discord] <rpardini> I just wanted to point out the pkg itself is deploying a source, which is great for installing manually, but not so much for images
<DC-IRC> [Discord] <igorpec> i will make use of those new hooks and get it done later today
<DC-IRC> [Discord] <rpardini> all those are multi-year-long straightening of old code across rootfs and image building so bugs might arise, let me know