All Activity

@bjorn it actually isn't necessary to make a new image from scratch, but that we'd need to figure out how to pass that 1.5GB memory size to u-boot, e.g. possibly a DTS overlay. then this means the procedure may possibly be: write the existing published image to sd card make a DTS overlay with the 1.5GB configured (a text file) - may need to be compiled into a DTB file update armbianEnv.txt to use the edited overlay and save them on the image sd card appropriately on booting up, the os should then boot normally as do any other boards. Unfortunately, no one yet has probed this and document the steps to do this successfully.

It is known that Coreelec modifies the boot and so armbian can not boot. You'll have to restore your device.

I don't care about wifi, if you be the wifi guy, please use this method to fix the wifi power management or communication: the process will be: compare two decompiled DTS. The old that wifi work and the new 6.6 without wifi and use it to fix the Board bring UP file

Yes you are right. It was working on the previous 1.1 image. There was the 6.1 kernel being active.

that's great Royk! so i can build Kodi following the official github guide, with GBM and GLES + patches 0001-windowing-gbm-Dynamic-plane-selection.patch / 0002-VideoLayerBridgeDRMPRIME-Use-crop-fields-to-render-t.patch ? or should i use a different configuration? thanks!

@Dbosco The same here until I compiled Kodi with the patch myself and everything works.

Hi! i've tried to apply the patch but i still have a black screen, maybe i did something wrong build: Armbian_24.2.4_Orangepi5_jammy_vendor_6.1.43_kde-neon-amazingfated_desktop After armbian wizard i did: apt update & upgrade reboot apt install kodi kodi-repository-kodi reboot start Kodi in GBM i've tested a video file, and black screen so i've quit from Kodi and i did the procedure below to apply the patches 0001-rga3_uncompact_fix.patch / 0002-vop2_rbga2101010_capability_fix.patch: % git clone -b rk-6.1-rkr1 https://github.com/amazingfate/linux-rockchip.git % cd linux-rockchip % wget https://github.com/hbiyik/ffmpeg-rockchip/wiki/patches/rockchip-kernel/0001-rga3_uncompact_fix.patch % wget https://github.com/hbiyik/ffmpeg-rockchip/wiki/patches/rockchip-kernel/0002-vop2_rgba2101010_capability_fix.patch % patch -p1 < 0001-rga3_uncompact_fix.patch patching file drivers/video/rockchip/rga3/rga3_reg_info.c Reversed (or previously applied) patch detected! Assume -R? [n] y % patch -p1 < 0002-vop2_rgba2101010_capability_fix.patch patching file drivers/gpu/drm/rockchip/rockchip_vop2_reg.c % make CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 rockchip_linux_defconfig % make KBUILD_IMAGE="arch/arm64/boot/Image" CROSS_COMPILE=aarch64-linux-gnu- ARCH=arm64 -j "$(nproc)" bindeb-pkg Results: dpkg-deb: building package 'linux-libc-dev' in '../linux-libc-dev_6.1.43-1_arm64.deb'. dpkg-deb: building package 'linux-image-6.1.43' in '../linux-image-6.1.43_6.1.43-1_arm64.deb'. dpkg-deb: building package 'linux-image-6.1.43-dbg' in '../linux-image-6.1.43-dbg_6.1.43-1_arm64.deb'. dpkg-genbuildinfo --build=binary -O../linux-upstream_6.1.43-1_arm64.buildinfo dpkg-genchanges --build=binary -O../linux-upstream_6.1.43-1_arm64.changes dpkg-genchanges: info: binary-only upload (no source code included) dpkg-source --after-build . dpkg-buildpackage: info: binary-only upload (no source included) Then I did % cd .. % sudo dpkg -i *.deb Results: Selecting previously unselected package linux-headers-6.1.43. (Reading database ... 183026 files and directories currently installed.) Preparing to unpack linux-headers-6.1.43_6.1.43-1_arm64.deb ... Unpacking linux-headers-6.1.43 (6.1.43-1) ... Selecting previously unselected package linux-image-6.1.43. Preparing to unpack linux-image-6.1.43_6.1.43-1_arm64.deb ... Unpacking linux-image-6.1.43 (6.1.43-1) ... Selecting previously unselected package linux-image-6.1.43-dbg. Preparing to unpack linux-image-6.1.43-dbg_6.1.43-1_arm64.deb ... Unpacking linux-image-6.1.43-dbg (6.1.43-1) ... Preparing to unpack linux-libc-dev_6.1.43-1_arm64.deb ... Unpacking linux-libc-dev:arm64 (6.1.43-1) over (5.15.0-102.112) ... Setting up linux-headers-6.1.43 (6.1.43-1) ... Setting up linux-image-6.1.43 (6.1.43-1) ... * dkms: running auto installation service for kernel 6.1.43 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area... make -j8 KERNELRELEASE=6.1.43 KERNEL_DIR=/lib/modules/6.1.43/build all... cleaning build area... v4l2loopback.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.43/updates/dkms/ depmod... [ OK ] update-initramfs: Generating /boot/initrd.img-6.1.43 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156b-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8156a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153c-1.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-4.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8153a-2.fw for built-in driver r8152 W: Possible missing firmware /lib/firmware/keyspan/usa49wlc.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa49w.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa19w.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa18x.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa19qw.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/mpr.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa19qi.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa19.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa28xb.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa28xa.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa28x.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/keyspan/usa28.fw for built-in driver keyspan W: Possible missing firmware /lib/firmware/bfubase.frm for built-in driver bfusb W: Possible missing firmware /lib/firmware/intel/ibt-12-16.ddc for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-12-16.sfi for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-11-5.ddc for built-in driver btintel W: Possible missing firmware /lib/firmware/intel/ibt-11-5.sfi for built-in driver btintel W: Possible missing firmware /lib/firmware/mrvl/sdsd8997_combo_v4.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8987_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sdsd8977_combo_v2.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8897_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8887_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8797_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8787_uapsta.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8688.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/mrvl/sd8688_helper.bin for built-in driver btmrvl_sdio W: Possible missing firmware /lib/firmware/rtl_bt/rtl8851bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8851bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852cu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bu_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852bu_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852au_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8852au_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8821a_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_config.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8761a_fw.bin for built-in driver btrtl W: Possible missing firmware /lib/firmware/rtl_bt/rtl8723a_fw.bin for built-in driver btrtl update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.43 Image Name: uInitrd Created: Tue Apr 16 13:06:04 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15405164 Bytes = 15044.11 KiB = 14.69 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.43 to /boot/uInitrd ln: failed to create symbolic link '/boot/uInitrd': Operation not permitted update-initramfs: Symlink failed, moving /boot/uInitrd-6.1.43 to /boot/uInitrd renamed '/boot/uInitrd-6.1.43' -> '/boot/uInitrd' update-initramfs: Armbian: done. Free space after deleting the package linux-image-6.1.43 in /boot: 67.7M Setting up linux-image-6.1.43-dbg (6.1.43-1) ... Setting up linux-libc-dev:arm64 (6.1.43-1) ... % reboot Tested Kodi again, and black screen Any suggestion? Thanks!!

at kernel 6.6 your wifi work? how? I think wifi was wrong.... thats the current DTS: You can Use it to compare with the original DTB -> DTS file and figure out any error on This DTS file that bring board UP

I dont know about overlays I have uploaded new bluetooth images to drive @pocosparc https://forum.armbian.com/topic/28895-efforts-to-develop-firmware-for-h96-max-v56-rk3566-8g64g/?do=findComment&comment=187569

Yes it was working before as the kernel itself reported that the bin files are missing. Now I am not sure how the kernel was compiled. So it will automatically parse from the config and driver bin files and then create the wlan0 interface?

I dont wanna take this risks with drivers, you can create a Github Pull Request to armbian too. your wifi was working? dont need any fix? i think you wont need to change DTB anymore, just need the kernel 6 binary to brcm4335

What do you want to say with this? This is how I added the tx/rx DMA IRQ names, yes. I don't know why the overlay (if it already exists), was not active on my Rockshit device.

I'm uploading all bluetooth updated images again sudo apt-get install device-tree-compiler you can: dtc -I dtb -O dts h96-tv-box-3566.dtb -o h96-tv-box-3566.dts edit the DTS file to work with wifi and reverse it: dtc -I dts -O dtb -o H96-tvbox-3566-wifi.dtb H96-tvbox-3566-wifi.dts apply it on device i think you will need to find the brcmfmac4335-sdio.firefly,rk3566-roc-pc.bin for kernel 6.6 it was working on 6.2

Thanks @ag123 Sadly I don't think I have the skill set to tinker it or make my self image to put on it. But what you say is almost certainly correct since I went into the Orange Pi OS build tool chain and looked and it seemed to be just switch. I have for now put Debian on it which seems to work very well. (Though I have bit of a backdoor trust issues with OS coming directly from Orange Pi) But I will keep eyes open if image will be made at some point then I can least help test it.

Hi everyone, I'm new in this forum. I'm trying to boot armbian on a Mecool KM1 tv box. It's an armlogic S905X3 with 4GB ram,, 32Gb storage. Cant find a viable uboot and dtb combination for it as the usb flashdrive or microSD card simply won't boot. I can, however, run coreelec with no issues. Does anybody had any success with this box? Thanks

Hello! I have a Zero2 board with 1GB of RAM. I compiled a Debian 12 desktop image for Zero2 using Armbian and I want to play online videos through a web browser. Unfortunately, the results have been disappointing as the performance for 1080p videos is very slow. I tried using swap, but it didn't help. I also attempted to play 1080p videos using MPV and VLC. MPV can still play the videos, but it feels sluggish, and VLC gets stuck on the screen until the playback is finished. I would like to know how to configure Zero2 on Linux to achieve video acceleration. I'm new to this, so I would appreciate some guidance. Thank you!

This is how @ning enable the LED and InfraRed https://github.com/zhangn1985/linux-stable/commit/eb97929f95b1af3257b74528159a5d55a6409bba I will try it out. In his repo I have also seen that he implemented the right keystrokes for it. Will need to check this one. For the dts I edited it right on the machine - the file that Armbian in settingsEnv is pointing at. Can you try dmesg at your side if you see any errors that uart1 DMAs have no name and therefore it wont be active? I am not sure how this overlays work, but if I remember correctly - I read somewhere that Rockchip does not support overlays. Do you know how to turn them on? Do they need to be compiled against the "main" dtb file? Why these patches need to be external. There are already lots of dtb files in that brcm folder or in a worst case they can be setup in a special deb package, whereas the dependancies to it could be managable. I think this is the RPi way of working and if there is a driver update, you get a new "firmware" debian package. @Hqnicolas To start fiddling with the WiFi I need to recompile the whole kernel once again or is there a quicker route?

This will take some time since it takes a few hours to upgrade, so maybe someday this week. I will not leave this thread without the final outcome, even if I will give up and do a fresh install. I remember it took me forever to configure autologin, samba and x11vnc for some reason (can't remember, it was 3 years ago). So my lazy ass just wants to upgrade. But looking at my log from serial interface I can see that /boot is there, not sure what it is inside though, at least it seems to have boot script (boot.scr is found). First one to fail is /boot/uInitrd. this is where I have to look. And also what Werner said too.

@bjorn the "1.5G issue" is a known issue, few of us has time to work on that for now. if you scroll a little back, you would find this comment The problem is in *u-boot*, the 'solution' is to pass a parameter to u-boot to tell u-boot the memory size of the board. None of us has tried it in the meantime, and among the options is to make a DTS overlay that has the memory size (not tested) and perhaps update armbianEnv.txt to load that overlay https://docs.armbian.com/User-Guide_Armbian_overlays/ this has to be manually done for every board that u-boot cannot detect the memory size (because the dram controller is *undocumented*, the current memory probe is at best a hack, and it works for 'whole numbers' dram sizes 1G, 2G, 4G) You could give that a shot by exploring that solution, just that none (of us, including yourself) has worked it yet.

I'm trying to figureout what you change on DTS to edit the Github PR in that way. Just add: dma-names = "tx\0rx"; as you can see: https://github.com/hqnicolas/build/blob/9d0d690fe33a022c302ac538c4ecdd3dcacb482d/patch/kernel/archive/rockchip64-6.6/overlay/rockchip-rk3568-hk-uart1.dts#L12 Other boards have the same patch and I copy it: https://github.com/hqnicolas/build/blob/main/patch/kernel/archive/rockchip64-6.6/dt/rk3566-h96-tvbox.dts about the file, I just add it to the wifi external patch: Wifi Driver: https://drive.google.com/file/d/1VQLWxnhH06bAy7Nlg0xMWwLBmuOrUc_J/view?usp=sharing

This is how @ning enable the LED and InfraRed https://github.com/zhangn1985/linux-stable/commit/eb97929f95b1af3257b74528159a5d55a6409bba Nice @pocosparc Now I know why this device has an battery controller enabled, that's a tablet project I don't want to add pré-compiled files to a linux repo, This way, Wifi fix will need to be an unnoficial patch. I think this patch can be applyed by PR on armbian I just Soldered the SDCard Slot

@Hqnicolas Nice Job! Sorry I was away for the weekend and I already see that I need to reflash the board. Well I needed to start again with the version 1.2 - I started with Bluetooth and made it work - Although still not sure what is physically written on the chip and how it behaves. I have hcy6335, which in turn should be AP6335 containing the BCM4335 and for Bluetooth BCM4339. Somehow the chip gets represented as hci0: BCM4335A0 (002.001.006) build 0000. I am attaching the hcd file to this post that needs to be copied to the /lib/firmware/brcm. I also changed the dtb for the uart1 as there is no UART1 DMA mode possible otherwise. One just needs to add the dma-names to serial@fe650000 node: serial@fe650000 { compatible = "rockchip,rk3568-uart\0snps,dw-apb-uart"; reg = <0x00 0xfe650000 0x00 0x100>; interrupts = <0x00 0x75 0x04>; clocks = <0x0e 0x11f 0x0e 0x11c>; clock-names = "baudclk\0apb_pclk"; dmas = <0x24 0x02 0x24 0x03>; dma-names = "tx\0rx"; pinctrl-0 = <0x91 0x92 0x93>; pinctrl-names = "default"; reg-io-width = <0x04>; reg-shift = <0x02>; status = "okay"; phandle = <0x10a>; bluetooth { compatible = "brcm,bcm43438-bt"; clocks = <0x94 0x01>; clock-names = "lpo"; device-wakeup-gpios = <0x95 0x11 0x00>; host-wakeup-gpios = <0x95 0x10 0x00>; shutdown-gpios = <0x95 0x0f 0x00>; max-speed = <0x16e360>; pinctrl-names = "default"; pinctrl-0 = <0x96 0x97 0x98>; vbat-supply = <0x23>; vddio-supply = <0x63>; }; }; These are now the dmesg logs that I am getting [ 16.268929] Bluetooth: hci0: BCM: chip id 82 [ 16.269548] Bluetooth: hci0: BCM: features 0x2f [ 16.272162] Bluetooth: hci0: BCM4335A0 [ 16.272173] Bluetooth: hci0: BCM4335A0 (002.001.006) build 0000 [ 16.274413] Bluetooth: hci0: BCM4335A0 'brcm/BCM4335A0.hcd' Patch [ 17.114840] systemd[1]: Finished Armbian memory supported logging. [ 17.152605] systemd[1]: Starting Journal Service... [ 17.299179] systemd[1]: Started Journal Service. [ 17.339995] systemd-journald[632]: Received client request to flush runtime journal. [ 17.369055] Bluetooth: hci0: BCM: features 0x2f [ 17.372008] Bluetooth: hci0: BCM4335B0 JF-LTE MurataXJ AFH_LimitPwr_EDR 2STOPBIT-0343 [ 17.372025] Bluetooth: hci0: BCM4335A0 (002.001.006) build 0353 [ 17.482709] RPC: Registered named UNIX socket transport module. [ 17.482729] RPC: Registered udp transport module. [ 17.482733] RPC: Registered tcp transport module. [ 17.482736] RPC: Registered tcp-with-tls transport module. [ 17.482740] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 18.604874] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 18.604896] Bluetooth: BNEP filters: protocol multicast [ 18.604914] Bluetooth: BNEP socket layer initialized [ 18.647499] Bluetooth: MGMT ver 1.22 ... [ 23.677339] Bluetooth: RFCOMM TTY layer initialized [ 23.677399] Bluetooth: RFCOMM socket layer initialized [ 23.677430] Bluetooth: RFCOMM ver 1.11 h96-tvbox-3566-wifi:~:% hciconfig -a hci0: Type: Primary Bus: UART BD Address: 43:35:B0:07:1F:AC ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING RX bytes:4846 acl:0 sco:0 events:556 errors:0 TX bytes:71684 acl:0 sco:0 commands:556 errors:0 Features: 0xbf 0xfe 0xcf 0xff 0xdf 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: PERIPHERAL ACCEPT Name: 'h96-tvbox-3566-wifi' Class: 0x6c0000 Service Classes: Rendering, Capturing, Audio, Telephony Device Class: Miscellaneous, HCI Version: 4.0 (0x6) Revision: 0x161 LMP Version: 4.0 (0x6) Subversion: 0x4106 Manufacturer: Broadcom Corporation (15) h96-tvbox-3566-wifi:~:% bluetoothctl Agent registered [CHG] Controller 43:35:B0:07:1F:AC Pairable: yes [bluetooth]# show Controller 43:35:B0:07:1F:AC (public) Name: h96-tvbox-3566-wifi Alias: h96-tvbox-3566-wifi Class: 0x006c0000 Powered: yes Discoverable: no DiscoverableTimeout: 0x000000b4 Pairable: yes UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb) UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb) UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb) UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb) UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb) Modalias: usb:v1D6Bp0246d0540 Discovering: no Roles: central Roles: peripheral Advertising Features: ActiveInstances: 0x00 (0) SupportedInstances: 0x05 (5) SupportedIncludes: tx-power SupportedIncludes: appearance SupportedIncludes: local-name [bluetooth]# scan on Discovery started [CHG] Controller 43:35:B0:07:1F:AC Discovering: yes [NEW] Device 4C:BA:D7:02:F5:B7 4C-BA-D7-02-F5-B7 @ning @Hqnicolas UART1 speed is set to max-speed = <1500000>; but according to the datasheet (still no clue if it is the right one) we can go up to 4 MBit/s. Another thing is the schematics that I found somewhere on the internet, but still they are using some AP6xxx wifi/BT chip. Need to dive into this, but hey, now we see the missing components needed for SD-Card slot. Heartbeat is a nice thing, but I will try to enable the backlight blue LEDs, WiFi runniung, and then try to get some HDMI audio out of this thing. BCM4335A0.hcd p562297-AP6335 datasheet_V1.3_02102014.pdf ROC-3566-PC-V10-20210419.pdf

@tERBO I run xfce4 when my HDMI works and I find it runs ok. But yeah YouTube videos play very bad for me in general. Maybe hardware acceleration isn't working?

😄👍

Thank you everyone, I appreciate getting feedback from so many experts! Let me answer by point, hopefully some of my experience might be useful @Igor I get your point, Kali is mostly userspace and the convenience to have everything packaged (and rolling) in the same place - the only thing Armbian lacked was wifi injection capabilities which I solved by placing kali kernel patches in userpatches/kernel/archive/sunxi64-6.6 -rw-r--r-- 1 alex alex 17K apr 13 19:55 dwav-usb-mt-driver.patch -rw-r--r-- 1 alex alex 4,8K apr 13 19:55 kali-wifi-injection.patch -rw-r--r-- 1 alex alex 2,3K apr 13 19:55 wireless-carl9170-Enable-sniffer-mode-promisc-flag-t.patch Got them fresh from Kali's GitLab repo (an they're compatible up to kernel 6.6) Now, here's my build config file: userpatches/config-opi03.conf BOARD=orangepizero3 BRANCH=current RELEASE=trixie DEST_LANG="it_IT.UTF-8" COMPRESS_OUTPUTIMAGE=sha,xz KERNEL_CONFIGURE=no BSPFREEZE=yes CLEAN_LEVEL=debs,images,cache BUILD_DESKTOP=no BUILD_MINIMAL=yes BUILD_EXTERNAL=yes EXTERNAL_NEW=compile INSTALL_HEADERS=yes NO_APT_CACHER=yes ARTIFACT_IGNORE_CACHE=yes #KERNEL_GIT=shallow ENABLE_EXTENSIONS=kali HOST=opi03 #LOCALVERSION=-kali and here's my output from sudo apt update && sudo apt list --updateable pt-utils/kali-rolling 2.7.12+kali1 arm64 [aggiornabile da: 2.7.12] apt/kali-rolling 2.7.12+kali1 arm64 [aggiornabile da: 2.7.12] base-files/kali-rolling 1:2024.1.0 arm64 [aggiornabile da: 24.2.1-13-trixie] bluetooth/kali-rolling 5.71-1+kali1 all [aggiornabile da: 5.71-1] bluez/kali-rolling 5.71-1+kali1 arm64 [aggiornabile da: 5.71-1] command-not-found/kali-rolling 23.04.0-1+kali3 all [aggiornabile da: 23.04.0-1] dpkg/kali-rolling 1.22.4+kali2 arm64 [aggiornabile da: 1.22.4] init-system-helpers/kali-rolling 1.66+kali1 all [aggiornabile da: 1.66] init/kali-rolling 1.66+kali1 arm64 [aggiornabile da: 1.66] libapt-pkg6.0/kali-rolling 2.7.12+kali1 arm64 [aggiornabile da: 2.7.12] libbluetooth3/kali-rolling 5.71-1+kali1 arm64 [aggiornabile da: 5.71-1] libdpkg-perl/kali-rolling 1.22.4+kali2 all [aggiornabile da: 1.22.4] libpolkit-agent-1-0/kali-rolling 124-1+kali1 arm64 [aggiornabile da: 124-1] libpolkit-gobject-1-0/kali-rolling 124-1+kali1 arm64 [aggiornabile da: 124-1] linux-headers-current-sunxi64/trixie 24.2.1 arm64 [aggiornabile da: 24.2.1] linux-image-current-sunxi64/trixie 24.2.1 arm64 [aggiornabile da: 24.2.1] polkitd/kali-rolling 124-1+kali1 arm64 [aggiornabile da: 124-1] As you can see there are Armbian packages being overriden by Kali's counterpart: how may I know there's no "Frankestein" effect under the hood? I'd feel much safer knowing that Kali packages have been bootstrapped during image build itself - If I select "Bookworm" with "kali-extension.sh", the list gets much longer So I tried: Bootstrapping a kali snapshot rootfs (no kernel, no headers, no firmware, no u-boot, no dtbs, and no u-boot-menu, then proceeded installing: -rw-rw-r-- 1 alex alex 21K apr 14 11:55 armbian-bsp-cli-orangepizero3_24.2.1_arm64__1-PC13d1-Ve726-He72f-Ba537-R6632.deb -rw-rw-r-- 1 alex alex 1,7M apr 14 11:55 armbian-bsp-cli-orangepizero3-current_24.2.1_arm64__1-PC13d1-Ve726-He72f-Ba537-R6632.deb -rw-rw-r-- 1 alex alex 133K apr 14 11:53 armbian-config_24.2.1_all__1-SAfb17-B0293-R448a.deb -rw-rw-r-- 1 alex alex 225M apr 14 11:55 armbian-firmware_24.2.1_all__1-SA6b6f-B90f5-R448a.deb -rw-rw-r-- 1 alex alex 414M apr 14 11:54 armbian-firmware-full_24.2.1_all__1-SA6b6f-SMfbef-B90f5-R448a.deb -rw-rw-r-- 1 alex alex 2,4M apr 14 11:52 linux-dtb-current-sunxi64_24.2.1_arm64__6.6.16-Seb3e-D6b4a-P5d69-Cc165Hfe66-HK01ba-Vc222-B067e-R448a.deb -rw-rw-r-- 1 alex alex 94M apr 14 11:52 linux-headers-current-sunxi64_24.2.1_arm64__6.6.16-Seb3e-D6b4a-P5d69-Cc165Hfe66-HK01ba-Vc222-B067e-R448a.deb -rw-rw-r-- 1 alex alex 149M apr 14 11:52 linux-image-current-sunxi64_24.2.1_arm64__6.6.16-Seb3e-D6b4a-P5d69-Cc165Hfe66-HK01ba-Vc222-B067e-R448a.deb -rw-rw-r-- 1 alex alex 911K apr 14 11:52 linux-u-boot-orangepizero3-current_24.2.1_arm64__2024.01-S866c-P6305-H7b37-Vb97c-B11a8-R448a.deb It works a charm and no potential messing between package repos/distributions are present (hopefully), as the above packages are in a locally hosted repo which I manually added to Kali rootfs But this is a tedious work, manual and I can't say if it's good or not, to be honest it works great I'd feel it would be done the "right" way by integrating kali distrib into build scripts @going I'll definitely test KEEP_ORIGINAL_OS_RELEASE=yes and report back @c0rnelius Kali network services, especially avahi being able to broadcast services, thus giving away a penetration tester "presence", are disabled by default - in the past HCIUART was disabled by default too due to some reason I can't remember; nevertheless everything can be (re-)enabled, unmasked, etc by standard means - Kali does even include some fancy cryptroot-luks kernel patches that automatically "destroy" data on boot when full-disk-encryption is active in case of specific passwords being passed (like a dead man's switch I suppose) Thank you for your support guys!