Michal Fita

As both Raspberry Pi OS and Armbian use the same guts to boot, that includes RPi firmware I'd expect their firmware is unable to work with RAM chip other than original 8GB one and its potentially done on purpose. RPi hardware designs are proprietary and agreed with Broadcom under high pile of NDAs and other legally binding agreements. I'm not saying it cannot be done, but you'd have to find someone able to reverse engineer the firmware and fix this for you, what may be legally grey area if not clear violation of the license (so you could be sued).

That's not documented on https://docs.armbian.com/User-Guide_Armbian_overlays/, I'll propose change when tested. However, so far it doesn't work. On RPi5's Raspberry OS enabling `dtparam=i2c_arm=on` in `/boot/firmware/config.txt` turns I²C on, but it doesn't on Armbian. I find it confusing overlays are in two distinct locations under `/boot`. More clues welcome.

sudo apt install linux-image-current-bcm2712=24.2.1 Would suffice for now.

Agree. My company can only cover costs for agreed Statement of Work and the price has to be agreed upfront. We can push limited number of hours invoiced for something important, but unfortunately we can't do donations - startups looks every penny both sides twice. Looks like images released aren't compatible with state of APT repositories: ~# apt show -a linux-image-current-bcm2712 Package: linux-image-current-bcm2712 Version: 24.2.5 Status: install ok installed Priority: optional Section: kernel Source: linux-6.6.23 Maintainer: Armbian Linux <info@armbian.com> Installed-Size: 155 MB Provides: linux-image, linux-image-armbian, armbian-current Armbian-Kernel-Version: 6.6.23 Armbian-Kernel-Version-Family: 6.6.23-current-bcm2712 Armbian-Original-Hash: 6.6.23-S8c3e-Dfed2-P0000-Ccc02H66b1-HK01ba-Vc222-Bd104-R448a Download-Size: unknown APT-Manual-Installed: yes APT-Sources: /var/lib/dpkg/status Description: Armbian Linux current kernel image 6.6.23-current-bcm2712 This package contains the Linux kernel, modules and corresponding other files. version "6.6.23" git revision "8c3e7a55220cb7cb13131bb8dccd37694537eb97" codename "Hurr durr Ima ninja sloth" drivers hash "fed24384_9f81b93f" patches hash "0000000000000000" .config hash "cc027d3a59f16119" .config hook hash "66b17b0d7f47b551" variables hash "c22207b66dc5dd57157df2cd7b9c20559b2ed8ac44b9c3c3b9704002c06b8921" framework bash hash "d1042705e60277e8" Package: linux-image-current-bcm2712 Version: 24.2.1 Priority: optional Section: kernel Source: linux-6.6.18 Maintainer: Armbian Linux <info@armbian.com> Installed-Size: 158 MB Provides: linux-image, linux-image-armbian, armbian-current Armbian-Kernel-Version: 6.6.18 Armbian-Kernel-Version-Family: 6.6.18-current-bcm2712 Armbian-Original-Hash: 6.6.18-S9e78-D6b4a-P0000-Cb2aaH4168-HK01ba-Vc222-B067e-R448a Download-Size: 27.4 MB APT-Sources: http://apt.armbian.com jammy/main arm64 Packages Description: Armbian Linux current kernel image 6.6.18-current-bcm2712 This package contains the Linux kernel, modules and corresponding other files. version "6.6.18" git revision "9e78addad23f9fc66b0c6399d9234e44a89d699a" codename "Hurr durr Ima ninja sloth" drivers hash "6b4abbc6_0b3d8cbf" patches hash "0000000000000000" .config hash "b2aa59cc79694025" .config hook hash "4168b2934f796ee8" variables hash "c22207b66dc5dd57157df2cd7b9c20559b2ed8ac44b9c3c3b9704002c06b8921" framework bash hash "067e1a10c790605d" `APT-Sources` field indicates only the latter is available on apt.armbian.com... I found https://armbian.site-meganet.com/apt/pool/main/l/linux-6.6.18/ only, no directory for 6.6.23 in there.

Gladly, just need to know where to start to trigger CI to build header's package for 24.2.5? Raspberry Pi 5 is not on the list. No, I expect to tell me what's wrong and give hint how this can be fixed. How much we'd have to pay to get this fixed?

And 6.6.30 bricks the unit... doesn't boot 🤦‍♂️ and I don't have serial cable to my RPi5. Fan remains spinning at full speed. Going back to reflash the SD Card with original image. Who can fix header package for the stable branch?

OK 🤦‍♂️ I had to unfreeze, do `apt update` manually, then I got update for `linux-headers-` to 24.5.0. So, `apt upgrade` did: ii linux-headers-current-bcm2712 24.5.0-trunk.530 arm64 Armbian Linux current headers 6.6.30-current-bcm2712 ii linux-image-current-bcm2712 24.5.0-trunk.530 arm64 Armbian Linux current kernel image 6.6.30-current-bcm2712 Possible bug in `armbian-config` not upgrading headers package?

How this helps `apt` recognize what to install from the repository? But yes, I gave it a try... reinstalling `linux-headers-current-bcm2712` reinstalls 24.2.1 with 6.6.18 in it. I used `armbian-config` as suggested... and ended up with: hi linux-headers-current-bcm2712 24.2.1 arm64 Armbian Linux current headers 6.6.18-current-bcm2712 hi linux-image-current-bcm2712 24.5.0-trunk.530 arm64 Armbian Linux current kernel image 6.6.30-current-bcm2712 What's actually even worse. More hints?

My system has `linux-image-current-bcm2712` package installed with version 24.2.5 which I believe is the current Arbian release. I installed `linux-headers-current-bcm2712`, but this package has version 24.2.1. So I end up with system running `6.6.23-current-bcm2712` with headers for `6.6.18-current-bcm2712` and I can't build extra drivers in result. Any hints? I love technical forums that don't understand markdown, it makes life so much easier...

Raspberry OS has weird quirks that automate the process of setting up the system for using cameras, but I'm looking for clean way to set up the device tree to use the imx219 camera. Anyone knows what overlays to enable to get this to work on Armbian? Additionally where's the location of device tree overlays sources for Raspberry Pi 5 on Armbian?

Whoa. I'm not representing Rockchip in anyway - just need to use RK3566 in a project. Without these drivers the support for the chip is incomplete from the perspective of the Armbian user. I don't have powers, energy and money to push particular chip drivers into mainline - there are several vendors our there who don't have theirs and Ubuntu still doing distros for these (👀 Xilinx/AMD). If that's the case what's the usefulness of Armbian for average tinkerer who want to run Rockchip based SBC with CSI-2 cameras? In Windows world you take the installer and add drivers to the system - in Linux world at best someone could cook DKMS package with extra set, but that's at the moment probably significantly more effort than set of patches for Armbian's build. Money, money, money. SBC makers doesn't pay them enough to justify effort required and they probably deliver customized kernels as part of paid support to they customers under NDAs. These things happen probably in violation of GPL license, but no one is willing to pay layers to chase this especially as 5.10 is out to the world. I don't have to PR my changes if you don't like such approach. That, however, doesn't change my need to do this as I need to boot the board with CSI-2 support and working GPU 🤷

Thanks @Igor. How to provide information that OrangePi 3B for example boots on Edge? We could run GPU stuff on it with success. I find it useful it allows board customization w/o maintaining whole kernel fork. However, it's maybe we started from official Ubuntu for Xilinx? Looks like I have to. I need Rockchip's MIPI CSI2 drivers to connect camera to OrangePi 3B and Radxa Zero 3E.

I believe this question goes to @rpardini as maintainer of patches for Rockchip series in the `build` repo: I'm trying connect camera to Orange Pi 3B (yes, it boots from community support on edge kernels), but spent 2h digging to find no drivers for CSI2 from Rockchip's fork are ported to patches for recent kernels (for example: https://github.com/armbian/linux-rockchip/blob/rk-5.10-rkr6/drivers/phy/rockchip/phy-rockchip-csi2-dphy.c and corresponding device trees to instantiate these drivers). This is a little chicken egg problem as I need recent kernels to have access to open source GPU drivers - they're not present on 5.10 based original system images for OrangePi 3B. I created a DT overlay for imx219 camera, but it cannot work as right references don't exist on Armbian yet. I could help with porting these, but I need to know the procedure - that's some amount of drivers I can figure out based on `compatible = ` entries from Rockchip's device trees. I probably need to get them built with 6.6 and 6.7, then generate patches with these and PR changes. Any more hints appreciated. I'm interested in having both MIPI CSI2 and GPU working on these boards for now: OrangePi 3B (that one I have on my desk) Radxa Zero 3E Radxa Zero 3W Thank you. How you can live with forum not supporting humanly Markdown?

I found it very confusing that Armbian doesn't seem to follow the Ubuntu/Debian traditional scheme for naming kernel modules: linux-image-*, linux-modules-* and linux-headers-*. I need them to cross compile out-of-tree kernel module in `schroot`. Armbian seem to have only `linux-image-edge-rockchip64` and `linux-headers-edge-rockchip64`. What's the reasoning behind such design decision? Moreover, I've noticed kernel packages incorporate all the logic that make the board bootable, instead having more generic kernel binaries and relying on `flash-kernel` tool that both Ubuntu and Debian widely use. I wonder why not? What are chances in future `linux-image-*` could be split and have matching `linux-modules-*` package as upstream? Is there any maintained roadmap to figure out most recent supported numbered kernel package, so I could have Orange Pi 3B board with fixed (pinned) kernel version out-of-the-box? Thank you.