c0rnelius

I would suggest using a better SD card.
 
G12B:BL:6e7c85:2a3b91;FEAT:E0F83180:402000;POC:F;RCY:0;EMMC:0;READ:0;0. bl2_stage_init 0x01 bl2_stage_init 0x81 hw id: 0x0000 - pwm id 0x01 bl2_stage_init 0xc1 bl2_stage_init 0x02 L0:00000000 L1:20000703 L2:00008067 L3:14000000 B2:00402000 B1:e0f83180 TE: 53694 BL2 Built : 19:23:21, Sep 18 2020. g12b g9fde858 - gongwei.chen@droid11-sz Board ID = 12 Set A53 clk to 24M Set A73 clk to 24M Set clk81 to 24M A53 clk: 1200 MHz A73 clk: 1200 MHz CLK81: 166.6M smccc: 00011aa2 eMMC boot @ 0 sw8 s board id: 12 Load FIP HDR DDR from eMMC, src: 0x00010200, des: 0xfffd0000, size: 0x00004000, part: 0 Get wrong ddr fw magic! Error!! fw parse done PIEI prepare done 00000000 emmc switch 1 ok 00000000 emmc switch 2 ok NO find ddr boot_info from eMMC fastboot data verify result: 255 Cfg max: 12, cur: 1. Board id: 255. Force loop cfg LPDDR4 probe LPDDR4_PHY_V_0_1_22-Built : 14:57:26, Sep 1 2020. g12b g3c95fed - gongwei.chen@droid11-sz ddr clk to 1608MHz 00000000 emmc switch 0 ok dmc_version 0001 Check phy result INFO : End of CA training INFO : End of initialization INFO : Training has run successfully! Check phy result INFO : End of initialization INFO : End of read enable training INFO : End of fine write leveling INFO : End of read dq deskew training INFO : End of MPR read delay center optimization INFO : End of Write leveling coarse delay INFO : End of read delay center optimization INFO : Training has run successfully! Check phy result INFO : End of initialization INFO : End of MPR read delay center optimization INFO : End of write delay center optimization INFO : End of read delay center optimization INFO : End of max read latency training INFO : Training has run successfully! 1D training succeed Check phy result INFO : End of initialization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D read delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : End of 2D write delay Voltage center optimization INFO : Training has run successfully! soc_vref_reg_value 0x 0000001d 0000001c 0000001b 0000001e 0000001c 0000001c 0000001d 0000001c 0000001c 0000001a 0000001a 0000001b 00000019 0000001f 0000001b 0000001c 0000001b 0000001e 0000001c 0000001e 0000001a 0000001c 0000001c 0000001b 0000001c 0000001c 0000001b 0000001d 0000001d 0000001c 0000001b 0000001c dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0004 dram_vref_reg_value 0x 0000004d 2D training succeed auto size-- 65535DDR cs0 size: 2048MB DDR cs1 size: 2048MB DMC_DDR_CTRL: 00e00024DDR size: 3928MB cs0 DataBus test pass cs1 DataBus test pass cs0 AddrBus test pass cs1 AddrBus test pass non-sec scramble use zero key ddr scramble enabled 100bdlr_step_size ps== 403 result report boot times 0Enable ddr reg access 00000000 emmc switch 3 ok Authentication key not yet programmed get rpmb counter error 0x00000007 00000000 emmc switch 0 ok Load FIP HDR from eMMC, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0 Load BL3X from eMMC, src: 0x00078200, des: 0x01768000, size: 0x000bea00, part: 0 0.0;M3 CHK:0;cm4_sp_mode 0 MVN_1=0x00000000 MVN_2=0x00000000 [Image: g12b_v1.1.3390-6ac5299 2019-09-26 14:10:05 luan.yuan@droid15-sz] OPS=0x10 ring efuse init chipver efuse init 29 0b 10 00 01 25 0c 00 00 0c 37 32 34 54 31 50 [0.778675 Inits done] secure task start! high task start! low task start! run into bl31 NOTICE: BL31: v1.3(release):4fc40b1 NOTICE: BL31: Built : 15:58:17, May 22 2019 NOTICE: BL31: G12A normal boot! NOTICE: BL31: BL33 decompress pass ERROR: Error initializing runtime service opteed_fast <debug_uart> U-Boot 2026.01 (Jan 15 2026 - 07:25:48 -0500) bpi-m2s Model: BananaPi M2S SoC: Amlogic Meson G12B (A311D) Revision 29:b (10:2) DRAM: 2 GiB (total 3.8 GiB) Core: 401 devices, 31 uclasses, devicetree: separate MMC: mmc@ffe05000: 0, mmc@ffe07000: 1 Loading Environment from nowhere... OK PCIE-0: Link up (Gen1-x1, Bus0) In: usbkbd,serial Out: vidconsole,serial Err: vidconsole,serial Net: eth0: ethernet@ff3f0000 starting USB... Starting the controller USB XHCI 1.10 Bus usb@ff500000: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 8133 bytes read in 2 ms (3.9 MiB/s) ## Executing script at 08000000 U-boot default fdtfile: amlogic/meson-g12b-a311d-bananapi-m2s.dtb Current variant: 211 bytes read in 1 ms (206.1 KiB/s) Current fdtfile after armbianEnv: amlogic/meson-g12b-a311d-bananapi-m2s.dtb Mainline bootargs: root=UUID=45e1ab7d-9528-4d3b-8b8e-27c59e112250 rootwait rootfstype=ext4 splash=verbose console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=fe959640-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=memory 25338901 bytes read in 1073 ms (22.5 MiB/s) 42338816 bytes read in 1792 ms (22.5 MiB/s) 80849 bytes read in 6 ms (12.8 MiB/s) Working FDT set to 4080000 232 bytes read in 5 ms (44.9 KiB/s) Applying kernel provided DT fixup script (meson-fixup.scr) ## Executing script at 32000000 ## Loading init Ramdisk from Legacy Image at 13000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 25338837 Bytes = 24.2 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 04080000 Booting using the fdt blob at 0x4080000 Working FDT set to 4080000 Loading Ramdisk to 7e7d5000, end 7ffff3d5 ... OK Loading Device Tree to 000000007e758000, end 000000007e7d4fff ... OK Working FDT set to 7e758000 Starting kernel ... Armbian 26.2.1 Trixie ttyAML0 bananapim2s login: root Password: _ _ _ /_\ _ _ _ __ | |__(_)__ _ _ _ / _ \| '_| ' \| '_ \ / _` | ' \ /_/ \_\_| |_|_|_|_.__/_\__,_|_||_| v26.2.1 for Banana Pi M2S running Armbian Linux 6.18.15-current-meson64 Packages: Debian stable (trixie) Performance: Load: 12% Uptime: 1m Memory usage: 5% of 3.68G CPU temp: 44°C Usage of /: 5% of 29G Commands: Configuration: armbian-config Monitoring : htop root@bananapim2s:~#  

https://forums.kali.org/
 
There is an arm64 section.

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
 

Looks like the same thing REV 1.1 uses. My guess would be the GPIO or PINCTRL may be different on the REV2.
 
The problem is the schematic only shows 1.0 / 1.1
 
You could try shooting them an email in an attempt to obtain the v2 schematic?

 
Without it, you would just be guessing.

HOST
/dts-v1/; /plugin/; / { fragment@0 { target = <&usbotg>; __overlay__ { dr_mode = "host"; }; }; };  
OTG
/dts-v1/; /plugin/; / { fragment@0 { target = <&usbotg>; __overlay__ { dr_mode = "otg"; }; }; };  
By default it is set to peripheral.

@ScoreABSM
 
I have no clue what the HDMI audio errors are in the dmesg. I noticed them before as well. I know mainline doesn't actually have HDMI audio support yet. I'm not sure where these HDMI audio patches originated, but I assume the OrangePI repo. Of course, I could just be doing something wrong here on a DTS level?
 
Strange your getting chanspec errors. This was resolved on my end by updating the wireless-regdb.
You can try resolving it with this: "Put in your COUNTRYCODE"
extraargs=cfg80211.ieee80211_regdom=US or this
echo "options cfg80211 ieee80211_regdom=US" > /etc/modprobe.d/cfg80211.conf  
I'll disable the gpu by default.
 
No. I don't see how removing those RTC patches would be creating these errors. The chanspec one is well known. Also happens on RPI's. I have a HACK patch that disables the error, but thats not really a fix. When I ran tests with the GPU before I never saw those errors and that GPU patch was pulled from mainline. I believe? Pretty sure it is the same patch I use in my personal builds.
 
II'll say this. This is becoming endless. I'm getting ready to toss this SBC in the garbage
 

Tried creating an overlay and changing it to; peripheral?
 
 
/dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h2-plus", "allwinner,sun8i-h3"; fragment@0 { target = <&usb_otg>; __overlay__ { dr_mode = "peripheral"; }; }; };  

`sudo modprobe i2c-dev` ?

Find the /dev/node `lsblk`
 
Flashing options:
eMMC: sudo dd if=u-boot.bin of=/dev/mmcblkX bs=512 seek=1 SDCARD: sudo dd if=u-boot.bin.sd.bin of=/dev/mmcblkX conv=fsync bs=1 count=442 sudo dd if=u-boot.bin.sd.bin of=/dev/mmcblkX conv=fsync bs=512 skip=1 seek=1  
 
u-boot.bin u-boot.bin.sd.bin

https://github.com/armbian/build/pull/7694
 
patrick@rpi4b:~$ dmesg | grep brcmfmac [ 3.443168] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 3.444363] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 3.444650] usbcore: registered new interface driver brcmfmac [ 3.673499] brcmfmac: brcmf_c_process_txcap_blob: no txcap_blob available (err=-2) [ 3.673793] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Apr 15 2021 03:03:20 version 7.45.234 (4ca95bb CY) FWID 01-996384e2 [ 8.815477] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled  

@jak Try this one.
 
/dts-v1/; /plugin/; / { fragment@0 { target = <&i2c2>; __overlay__ { status = "okay"; }; }; fragment@1 { target = <&uart_A>; __overlay__ { status = "disabled"; }; }; };  
Result in my case:
bananapi: ~ $ sudo i2cdetect -y 2 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --  

Read the post and check the PR link
 
and or follow the fellas post below.
 
The IMGs need to be updated, so currently that's the only remedy as far as I know.
 

@Eloy Bote Falcon
 
Try this pre-compiled binary. I'm gonna need to re-write some of that patch to work with armbian.
sun50i-h618-bananapi-m4-zero-v2.dtb

@vimal
 
try this patch with the github driver.
0001-sdio-wifi-fixups.patch

I suspect the issue is the version of U-Boot currently on the eMMC. When the board boots, if U-Boot is found on the eMMC, that is what will be used to do the initial boot. If an SDCARD is detected with a viable OS, it will then attempt to load it. It may be that the version of U-Boot "BSP?" on the eMMC is not compatible with Armbian and needs to be dd'd off.
 
I just flashed this to SD to test. Came up fine.
____ ____ _ __ __ ____ ____ | __ )| _ \(_) | \/ |___ \/ ___| | _ \| |_) | | | |\/| | __) \___ \ | |_) | __/| | | | | |/ __/ ___) | |____/|_| |_| |_| |_|_____|____/ Welcome to Armbian 24.5.3 Bookworm with Linux 6.6.36-current-meson64 System load: 10% Up time: 1 min Memory usage: 4% of 3.69G IP: CPU temp: 37°C Usage of /: 4% of 29G [ Menu-driven system configuration (beta): sudo apt update && sudo apt install armbian-config ]  
 

Try adding it this way.
extraargs=swiotlb=0  

Kali is in a lot of ways a polished SID with all of their own custom bits added. It can be debootstrap'd just like Debian, Devuan and Ubuntu. I did find some services didn't work on boot; 'ssh avahi bluetooth ntp'. But there could be some option they have I'm not aware of to allow those services to start out of the box. Creating a custom service to start those does the trick though.
 
I would think adding this as an option could be doable, but the question then becomes who wants to handle the support required to maintain it?
 

sudo nano /etc/asound.conf
pcm.!default {     type hw     card 2 } ctl.!default {     type hw     card 2 } save and reboot
 
https://www.alsa-project.org/wiki/Asoundrc

It is more than likely a u-boot issue caused by a specific patch; https://github.com/armbian/build/blob/main/patch/u-boot/v2022.10/meson64-boot-usb-nvme-scsi-first.patch
https://github.com/armbian/build/blob/main/config/boards/radxa-zero.conf#L17
 
You would need to build u-boot with this patch disabled, flash it to the unit and see if it solves the problem.

Give it a whirl and let me know.
 
lsusb Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 001 Device 003: ID 0bda:a811 Realtek Semiconductor Corp. RTL8811AU 802.11a/b/g/n/ac WLAN Adapter Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub  
 
 
meson-g12b-bananapi-cm4-waveshare-usb.dts