c0rnelius

Really anyone here with a little patch and git know how could attempt to do a PR and add it to the legacy branch, which is still 6.12.y.
Everything one would need is sitting in the deb builder and in armbian./build. Not sure Armbian would let you just add it to legacy though? Maybe.
 
Why don't I? I don't want anything to do with supporting the REV2 beyond the efforts I've made.
 
The REV1 was a curious buy, as I was already working on the BPI-M4-Zero and wanted another H618 to work on that had an ETH port. Also, it was only like $25 at the time.
 

@WINEDSWanna do a PR?
 

REV1
wireless: AIC8800.
 
REV2
wireless: SKW VS6621S
ethernet: Maxio MAExxxx PHY
 

I can confirm:
sun50i-h618-kickpi-k2b-debian-trixie-6.12.103-arm64-ext4-2026-08-17-0923.img
eth0 and wlan0 is up.

Some NVMe's just don't play nice with some units. I have one such NVMe, which is why I rarely try to use it. Also u-boot is not set up to look for an infinite amount of $devnum. Currently it is hard coded to look for nvme 0:1. So I suggest moving the NVMe to the first available.  
 
According to the boot log you have more than one PCIE link up
[   1.438] PCIE-0: Link up (Gen2-x2, Bus0) <-- Thats where you want to attach the NVMe
[   1.600] PCIE-2: Link up (Gen2-x2, Bus2)
 
Honestly though. It looks like the NVMe you are trying to use isn't compat.

Setting pcie_aspm=off makes the drive work in the top slot albeit one order of magnitude slower than in the bottom slot.
If I swap the kernel parameter with pcie_aspm.policy=performance, I've got a working drive and it's operating at normal speed. Thanks a bunch!
 
Seeing that there are differences in behavior between the two M.2 slots, does that mean they're connected differently?
 

@sven-ola https://lore.kernel.org/spacemit/20260310161853.3900605-1-gaohan@iscas.ac.cn/T/#t
 
Sometime soon-ish I'll be doing another PR with early SD card and CPU freq scaling support. The above link should at least get you boot from eMMC or NVMe.
 

Looks like the same adjustment that was made for EDGE needs to be done so for CURRENT.

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.
 

Ur welcome.

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
 

This works for me. Edit it to fit the commands you want to be able to run.
sudo tee /etc/sudoers.d/010_$USER-nopasswd <<EOF ${USER} ${HOSTNAME} = (root) NOPASSWD: /sbin/shutdown ${USER} ${HOSTNAME} = (root) NOPASSWD: /sbin/poweroff ${USER} ${HOSTNAME} = (root) NOPASSWD: /sbin/reboot EOF  

@c0rnelius I would like to report back with the news of full success:
 
I have updated cmdline.txt to start with:
console=tty1 console=ttyAMA0,115200 earlycon=pl011,0x107d001000,115200n8  
And also added the following to config.txt:
usb_max_current_enable=1 enable_uart=1 dtparam=uart0 dtparam=uart0_console dtparam=pciex1 dtparam=pciex1_gen=3 dtoverlay=disable-wifi-pi5 dtoverlay=disable-bt-pi5  
All this with the HAT+ (in the picture above) still connected.
The early boot console also works, and I also get a login prompt, which is all I wanted.
After this I tried replacing ttyAMA0 to serial0 in cmdline.txt, to see if there is any difference, but they both seemed to work in the end.

Finally there is a proper tor-browser available for arm64/aarch64:
 
1. Goto https://nightlies.tbb.torproject.org/nightly-builds/tor-browser-builds/
2. Navigate into: tbb-nightly.<date>/nightly-linux-aarch64/ 
3. Download tor-browser-linux-aarch64-tbb-nightly.<date>.tar.xz
4. Unpack with tar -Jxvf and run tor-browser/start-tor-browser.desktop
 
Yay!
 
(I'm sure you can compile it too from their github page)

@twwn
 
Add to rk3566-radxa-zero-3.dtsi -->  snps,usb2-lpm-disable;
https://github.com/armbian/build/blob/main/patch/kernel/archive/rockchip64-6.12/dt/rk3566-radxa-zero-3.dtsi#L495
 
&usb_host0_xhci { dr_mode = "peripheral"; + snps,usb2-lpm-disable; status = "okay"; };  
See if it makes a difference.
 
Information:
https://www.kernel.org/doc/Documentation/devicetree/bindings/usb/dwc3.txt

Ur welcome.

Try this overlay
 
/dts-v1/; /plugin/; / { fragment@0 { target = <&ehci0>; __overlay__ { status = "okay"; }; }; fragment@1 { target = <&ohci0>; __overlay__ { status = "okay"; }; }; fragment@2 { target = <&usbotg>; __overlay__ { dr_mode = "host"; }; }; };  
sunxi-usb-host-mode.dts

Endless …
Garbage 😉
 

@ScoreABSM
https://github.com/pyavitz/binary/releases/download/images/Armbian-unofficial_25.08.0-trunk_Bananapim4zero_trixie_current_6.12.35.img.xz

The issue appears to be two things.
 
These two patches and the current defconfig(s) being used.
drv-rtc-sun6i-support-RTCs-without-external-LOSCs.patch
drv-rtc-sun6i-Add-Allwinner-H616-support.patch
 
When I disable those patches and use my own defconfig everything works as it should.
https://paste.armbian.com/tixixocubu
 
The hard part here would be figuring out exactly what in the defconfig(s) are either breaking things or missing. Also if I disable those patches, what does it break on other units? I'm under the impression these patches were rejects from the original h616 bring up in mainline. But I could be wrong?
 

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"; }; }; };  

@ScoreABSM
 
https://github.com/armbian/build/pull/8339
 

I use a 12v 3a PSU "Barrel"
 
patrick@bananapif3:~$ dmesg | grep pcie [ 0.322772] k1x-dwc-pcie ca400000.pcie: has no power on gpio. [ 0.325025] k1x-dwc-pcie ca400000.pcie: host bridge /soc/pcie@ca400000 ranges: [ 0.325065] k1x-dwc-pcie ca400000.pcie: IO 0x009f002000..0x009f101fff -> 0x009f002000 [ 0.325088] k1x-dwc-pcie ca400000.pcie: MEM 0x0090000000..0x009effffff -> 0x0090000000 [ 0.425212] k1x-dwc-pcie ca400000.pcie: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 4G [ 0.525297] k1x-dwc-pcie ca400000.pcie: PCIe Gen.2 x2 link up [ 0.525837] k1x-dwc-pcie ca400000.pcie: PCI host bridge to bus 0001:00 [ 0.543059] pcieport 0001:00:00.0: PME: Signaling with IRQ 65 [ 0.543510] pcieport 0001:00:00.0: AER: enabled with IRQ 65 [ 0.544202] k1x-dwc-pcie ca800000.pcie: has no power on gpio. [ 0.546446] k1x-dwc-pcie ca800000.pcie: host bridge /soc/pcie@ca800000 ranges: [ 0.546484] k1x-dwc-pcie ca800000.pcie: IO 0x00b7002000..0x00b7101fff -> 0x00b7002000 [ 0.546510] k1x-dwc-pcie ca800000.pcie: MEM 0x00a0000000..0x00afffffff -> 0x00a0000000 [ 0.546525] k1x-dwc-pcie ca800000.pcie: MEM 0x00b0000000..0x00b6ffffff -> 0x00b0000000 [ 0.646655] k1x-dwc-pcie ca800000.pcie: iATU: unroll T, 8 ob, 8 ib, align 4K, limit 4G [ 1.647016] k1x-dwc-pcie ca800000.pcie: Phy link never came up [ 1.647233] k1x-dwc-pcie ca800000.pcie: PCI host bridge to bus 0002:00 [ 1.654489] pcieport 0002:00:00.0: PME: Signaling with IRQ 69 [ 1.654939] pcieport 0002:00:00.0: AER: enabled with IRQ 69 patrick@bananapif3:~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS mmcblk2 179:0 0 14.6G 0 disk ├─mmcblk2p1 179:1 0 508M 0 part └─mmcblk2p2 179:2 0 14.1G 0 part mmcblk2boot0 179:8 0 4M 1 disk mmcblk2boot1 179:16 0 4M 1 disk zram0 250:0 0 1.9G 0 disk [SWAP] nvme0n1 259:0 0 238.5G 0 disk ├─nvme0n1p1 259:1 0 508M 0 part /boot └─nvme0n1p2 259:2 0 238G 0 part /  

sudo modprobe i2c-dev ?

If the u-boot on the unit supports USB Boot, yes. 
 
GXL:BL1:9ac50e:bb16dc;FEAT:ADFD318C:0;POC:3;RCY:0;EMMC:800;NAND:81;SD:800;USB:8;LOOP:1;EMMC:800;NAND:81;SD:800;USB:8;LOOP:2;EMMC:800;NAND:81;SD:800;USB:8;LOOP:3;EMMC:0;READ:0;0.0;CHK:0; The above looks like USB Mode. This Mode is for flashing vendor or custom imgs to the unit via USB. This is for recovery.