c0rnelius

There is probs away to pull in those apt sources from Bianbu, but I haven't messed with it yet. Types: deb URIs: http://archive.spacemit.com/bianbu/ Suites: noble/snapshots/v2.2 noble-security/snapshots/v2.2 noble-porting/snapshots/v2.2 noble-customization/snapshots/v2.2 noble-updates/snapshots/v2.2 bianbu-v2.2-updates Components: main universe restricted multiverse Signed-By: /usr/share/keyrings/bianbu-archive-keyring.gpg Would need to go on gitee or mount one of their imgs and get that *-keyring.gpg

That's not bad honestly. The K1 series runs hot in general. If you add heavy lifting to thee equation it would require a fan. I have the MusePi Pro and BPI-F3 and both run hot.

https://github.com/armbian/build/pull/9323

Tried this?

Then stick with what you got going on.

sm1 and g12 share the same common dtsi file. Use that aml flash tool along with --soc=g12a and flash the android img. That should bring you back to where you were. That would be a full recovery.

@user03 For sm1 devices use --soc=g12a Another option which is something I recently had to do with my BPI-CM4 "if I recall correctly, I've also done so on a tvbox i b0rked" is use pyamlboot. sudo pip3 install pyamlboot Short the board and run; sudo boot-g12.py u-boot.bin # if you have a functional u-boot binary This won't actually flash anything, "atleast it didn't in my case?" it will just force the unit to load that boot binary. From there you should be able to hit the SPACEBAR and check ur options using `print` and `help`. Should see options like usbboot, usb_update, etc. Not saying you should use one of these, but... You may be able to find one online or inside the Android img for ur unit. https://github.com/pyavitz/debian-image-builder/tree/feature/files/boot/uboot/ac2xx Anyway. At least you got it booting from USB. Next step would be running a recovery on it.

If you can get the unit in the proper state by shorting, you can flash an android img or custom one using this tool; https://github.com/natinusala/linux-amlogic-toolkit Other repos that you may find useful: https://github.com/mluis/aml-flash-tool https://github.com/Stane1983/aml-linux-usb-burn

This unit on Armbian has bigger problems than the Ethernet not coming up. such as: I believe that stems from the current U-Boot being used. If I flash mine and use my DTS that comes up correctly and the ethernet. Sorry but bringing this unit up to snuff would take more time than I'm currently willing to put in right now. If a window opens up in the future, I'll look into it.

If I have the time I'll do a PR. I also ended up modifying and compiling a new hciattach_opi binary, to get bluetooth to come up.

6.12.y

Here is the opi3lts DTS I use. Eth, WIFI and BT work as they should. If someone feels like running a diff and making the adjustment. sun50i-h6-orangepi-3-lts.dts

@iav nice. Yeap. One fixes topology and the other pcie performance. Tested on the BananaPi BPI-CM4

https://lore.kernel.org/linux-amlogic/20251127170908.14850-1-18255117159@163.com/T/#t https://lore.kernel.org/linux-amlogic/176397825606.3590190.10935817124468233062.b4-ty@linaro.org/T/#t

Short of KIckPi opening a contract with Armbian and providing the units they want worked on. I don't see how?

I haven't personally had issue with 6.17.y, but 6.18.y is a mess on meson-g12. It is basically unusable in my opinion. PCIe is hosed, even the patch that kind of fixes the issue just makes the error go away and doesn't fix the underlining problem "performance". I also get topology errors, but as I haven't really seen anyone yet complain about that, I'm assuming its me. For my personal use, I will be sticking with 6.12.y until things get sorted.

The v2 uses a diff wifi chip: SKW wifi module VS6621S I have a patch for it, which came from KICKPI in the deb builder, but... I don't have a V2 to work any magic on it. chuanzz at one point contacted KICKPI and they sent him an archive that had a bunch of Armbian adds in it, including the patches and board.confs. But the HDD I had the archive on got erased by mistake, so yeah... I don't have the info anymore. I don't see the K2B REV2 getting official support here or by me, as its using a wifi chip that is just to obscure. Here is a u-boot-v2025.07 binary for the K2B REV2 u-boot-sunxi-with-spl.bin

If you are using the radxa-pkg github "which is the most up-to-date" know that its hardcoded to point to specific firmware. To get around this you need to create a file: This example is for an SDIO variant using the radxa dkms package cat > /etc/modprobe.d/aic8800-wireless.conf <<- EOT options aic8800_fdrv_sdio aicwf_dbg_level=0 custregd=0 ps_on=0 options aic8800_bsp_sdio aic_fw_path=/lib/firmware/aic8800_fw/SDIO/aic8800 EOT Also note that the AIC8800 firmware located in armbian-firmware is kind of old and probs not compat with the radxa builds.

Ur welcome.

Ok. Also I think these are wrong for the PI5: dtoverlay=disable-wifi dtoverlay=disable-bt I believe it's: dtoverlay=disable-wifi-pi5 dtoverlay=disable-bt-pi5 My notes on this: # Pi3 / ZERO2W dtoverlay=pi3-disable-wifi dtoverlay=pi3-disable-bt # PI5 dtoverlay=disable-wifi-pi5 dtoverlay=disable-bt-pi5 # Everything else dtoverlay=disable-wifi dtoverlay=disable-bt Back in the day, I read somewhere that Bluetooth can inhibit serial from functioning correctly on the Pi's. I've never seen it happen, but maybe using the wrong overlay is hindering it in some way? Worth looking into.

Does it work when you remove that HAT?

Same deal using Noble; https://paste.armbian.com/orexafoxen.less

I installed a fresh Trixie img to SD, made the adjustments I suggested, booted, upgraded and rebooted. root@rpi5b:~# ls /dev/ttyAMA* /dev/ttyAMA0 /dev/ttyAMA10 Still there.

Without it being enabled in the config.txt file `ttyAMA0` isn't visible under /dev, last I checked. pibox: ~ $ cat /boot/firmware/config.txt | grep "enable_uart*" enable_uart=1 pibox: ~ $ ls /dev/ttyAMA* /dev/ttyAMA0 /dev/ttyAMA10 I wouldn't use `raspi-config` on an img that isn't RASPIOS. I feel that is bound to produce failure.

Give serial priority console=tty1 console=serial0,115200