All Activity

@Piotr s im using the same warpme patches so it’s odd that it doesn’t boot. To show more information on your console screen change your loglevel to 7 in armbianEnv.txt. The file is located at the root directory of your sdcard.

Unfortunately boot stops at 'Starting kernel' . However LED inside is pulsing, so it may be possible that only console stream is corrupt. U-Boot 2025.01-armbian-2025.01-S6d41-P7151-H8869-V004f-Bb703-R448a-dirty (Apr 02 2025 - 21:10:39 -0400) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: hechuang,x96-q LPDDR3 DRAM: 1 GiB Core: 58 devices, 20 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4021000: 3, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 No USB device found Net: apply fix for AC300 ephy bb version bug ... using AC300 emac1 ephy default config ... eth0: ethernet@5030000 starting USB... No USB controllers 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 4641 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 202 bytes read in 2 ms (98.6 KiB/s) Load fdt: /boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb 37577 bytes read in 5 ms (7.2 MiB/s) Working FDT set to 4fa00000 Failed to load '/boot/dtb/allwinner/overlay/sun50i-h616-fixup.scr' 15484849 bytes read in 649 ms (22.8 MiB/s) 42621440 bytes read in 1781 ms (22.8 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x42b50000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15484785 Bytes = 14.8 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 4913b000, end 49fff771 ... OK Loading Device Tree to 00000000490c9000, end 000000004913afff ... OK Working FDT set to 490c9000 Starting kernel ...

Updates should now be ok, aren't they?

After about 45 minutes of no change from the blue circle of death I pulled the power cable out and rebooted. This time I selected the Armbian Noble build - that seemed to complete successfully - although I wasn't monitoring the whole process but when I came back it must have completed the install and rebooted. Unfortunately it was only giving a blank screen. I tried several reboots and would get the initial blue lights come on and then nothing further. Eventually I had to remove the NVMe and reformat it as a clean EXT drive and reinsert. Now I'm back to being able to boot back into the RoobiOS installation GUI. I think that next I'll try just selecting the RADXA OS and then install Open Media Vault on top of that.

@darcyg @ Hqnicolas 使用了你的rk3576-h96-m9s。dts rk3576-h96-m9s-linux.dtsiarmsom-sige5-rk3576_defconfig 预算Armbian-unofficial_25.11.0-trunk_H96-m9_bookworm_vendor_6.1.115-backported-mesa.img gup可以工作，kodi 4K硬件加速。 1、关机不断电，电源灯亮 2、3.5音频无设备 无输出 3、无wifi蓝牙 4、kodi https://github.com/armsurvivors/kodi-rockchip-deb 硬件共享 https://drive.google.com/drive/folders/1lzLwm9NhxZ_0_mghKG4A0XQ6NNsU9sn-?usp=drive_link

Hi, my feedback for fancontrol service here : for 2.5Gbits, i don't use. for rk3399-kobol-helios64.dtb-6.12.xx-L2-hs400-opp, same has i writed up: "It is better to have a good solution in time than a perfect one too late.", my helios64 going to the trash without this workaround.

Hi, To my side, below work in root but not with systemd service: # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu #INTERVAL=10 INTERVAL=30 FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MAXTEMP=/dev/fan-p6/pwm1=50 /dev/fan-p7/pwm1=50 MINSTART=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20 MINSTOP=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20 MINPWM=20 To my side, below work in root and with systemd service: # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 FCTEMPS=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=/sys/devices/virtual/thermal/thermal_zone0/hwmon0/temp1_input MINTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=40 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=40 MAXTEMP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=50 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=50 MINSTART=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20 MINSTOP=/sys/devices/platform/p6-fan/hwmon/hwmon6/pwm1=20 /sys/devices/platform/p7-fan/hwmon/hwmon5/pwm1=20

At some point we will bump edge to 6.17. These bumps always take time since our patchset on top always needs adjustments. There are 3rd party ppa's for newer mesa. I suggest to use kisak since those are briefly tested. Otherwise go for oibaf which are automated untested, therefore latest mesa packages. In terms of Debian, no clue if there is a similar apt repo for such.

If you used edge, revert to 6.15

My apologies. I started working on this board again and just spent 3 wasted hours getting angry at the previous wipe eMMC instructions only to realize *I* had the wrong version of RKDevTool. Protip - do not do any hardware development angry, hungry, in a rage, or pressed for time. Wow. Here is the issues with your "erase eMMC" instructions (apparently partly taken from the guide to getting Linux on the T95 Plus): -Config file was loaded, loader, parameters and uboot were written. Board usually does not restart when this is done, restarted once out of my many attempts. -There are no instructions about "wipe_part", what partitions to destroy, or how to do this. Using your version of RKDevTool, no partitions are loaded which then appear in the Download Image window (as I assume they are supposed to). -Flashing the other Miniloader file is met with a Waiting for Device Success prompt, which never completes. These instructions obviously worked the first time I did this several months ago. I don't know what at all could have changed, and I'm pretty frustrated as I'm trying to recover from another OMV system crashing and trying to recover data, so the use was/is pretty urgent, and given this forum, it could be a few days before a replay so my system is now sitting hostage to these instructions.

I'm a bit embarassed to say they are confusing to me. I am going to ask Grok and see if it can help me, thank you

Last try of 6.12 1 or 2 weeks ago, was still with display failure. 6.1 works fine, now, with both HDMI out and I believe SATA working at each boot. I believe than since your last change SATA works far better with 6.1 vendor kernel. I'm mainly using the 6.16rc7 armbian kernel on archlinux now where I compile time to time last mesa git, to take benefits of more GL features, Vulkan 1.4 support + zink, however some softwares like obs studio, blender, wings3D, GTK4-demos fails with zink, due to problems with broken DRI. X11 have some slowdown too, but Wayland is perfectly smooth with mainline kernel + mesa drivers. noticed that 6.16.0 was compiled with GCC11, where 6.16rc7 was compiled with GCC13.3, there is a lot of optimizations in perfs between the two GCC releases, and Debian13 is now shiped with GCC 14.2. kernel 6.17rc1 bring AV1 accelerated video on RK3588. and rc2 is now released, I don't know if there are projects to upgrade mainline kernel and/or Debian version? Debian is sadely shipped with Mesa 25.1.0. Vulkan 1.4 support was reached with Mesa 25.2. It is however maybe more stable, I didn't tried 25.1.0 stable?

https://forum.banana-pi.org/t/bpi-r4-eeprom/17836/13 suggests we should figure out how to give the info to uboot? or it already does generate it for us in one case? I can say I find eth0's local-mac-address in the running device tree, but the other two mac@ entries lack it. root@ratatosk:/boot# dtc /proc/device-tree 2>/dev/null |grep -PA 10 'mac@[0-9] ' mac@2 { phy-mode = "usxgmii"; compatible = "mediatek,eth-mac"; status = "okay"; pcs-handle = <0x3a 0x3b>; managed = "in-band-status"; phys = <0x3c>; reg = <0x02>; openwrt,netdev-name = "sfp-wan"; sfp = <0x3d>; }; -- mac@0 { phy-mode = "internal"; local-mac-address = [22 16 68 60 40 c2]; mac-address = [22 16 68 60 40 c2]; compatible = "mediatek,eth-mac"; status = "okay"; reg = <0x00>; phandle = <0x2c>; fixed-link { full-duplex; -- mac@1 { phy-mode = "usxgmii"; compatible = "mediatek,eth-mac"; status = "okay"; pcs-handle = <0x36 0x37>; managed = "in-band-status"; phys = <0x38>; reg = <0x01>; openwrt,netdev-name = "sfp-lan"; sfp = <0x39>; };

I don't think it's an SD card issue. Performance wise it's about twice the requirement. And if it was a bad block, I doubt the issue would be the same across two different images. As for logs... where? I tried running "sudo dmesg -T --color=always --level=err,warn | more" and nothing about AdGuard came up. I checked the AdGuardHome.yaml file and confirmed bind_host was set to 0.0.0.0 (I also tried setting it to 192.168.0.6... no improvement). The command "sudo netstat -tulnp | grep 3000" said command not found, and "journalctl -u AdGuardHome" came back with no entries.

new Ubuntu/netplan bug: https://bugs.launchpad.net/netplan/+bug/2120999

https://github.com/canonical/netplan/pull/278 <-- related netplan PR

maybe not a strictly a systemd bug... but a netplan stupidity. root@ratatosk:~# ethtool --show-permaddr eth1 Permanent address: not set https://github.com/systemd/systemd/pull/14448/files <-- PR that created this systemd match feature

Latest armbian update 25.11 trunk 45 also breaks boot...

Thx for your reply. Yes i tried both together. And just one. No difference. # Enable DRM VC4 V3D driver dtoverlay=vc4-kms-v3d # Enable the Touch Display 2 DSI panel dtoverlay=vc4-kms-dsi-ili9881-7inch

making a copy of the file from /run/, changing the YAML to use MAC, then diff root@ratatosk:~# netplan generate root@ratatosk:~# diff -purN /run/systemd/network/10-netplan-eth1.network /root/netplan-eth1-namematch.network --- /run/systemd/network/10-netplan-eth1.network 2025-08-19 20:10:54.900000038 +0000 +++ /root/netplan-eth1-namematch.network 2025-08-19 20:10:36.980000037 +0000 @@ -1,5 +1,5 @@ [Match] -PermanentMACAddress=6a:c9:72:53:13:d5 +Name=eth1 [Network] EmitLLDP=true feels like a systemD bug ☹️

@Piotr sTry this image https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X96q-lpddr3_bookworm_edge_6.12.11_xfce_desktop.img.xz to fix Ethernet you need to edit this file https://github.com/NickAlilovic/build/blob/v20250306/patch/u-boot/u-boot-h616/159-add-x96-q-lpddr3-v1.3-defconfig.patch. Change 16 to 0. Then compile a new image. +&mdio1 { + rmii_phy: ethernet-phy@0 { + compatible = "ethernet-phy-ieee802.3-c22"; + reg = <0>; + }; +}; more information can be found here

Ok, so using the match name *does* work, still makes no sense. root@ratatosk:~# head /etc/netplan/20-ethLAN.yaml network: version: 2 renderer: networkd ethernets: eth1: match: #macaddress: '6a:c9:72:53:13:d5' name: eth1 #set-name: ethLAN addresses: [ "192.168.88.253/23" ] root@ratatosk:~# networkctl list IDX LINK TYPE OPERATIONAL SETUP 1 lo loopback carrier unmanaged 2 eth0 ether degraded unmanaged 3 eth1 ether routable configured 4 eth2 ether off unmanaged 5 wan dsa off unmanaged 6 lan1 dsa routable configured 7 lan2 dsa off unmanaged 8 lan3 dsa off unmanaged 8 links listed.

The eth0/lan1 MAC does change... the eth1/eth2 MACs do not change. I've checked over multiple reboot cycles. 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 6a:c9:72:53:13:d5 brd ff:ff:ff:ff:ff:ff 4: eth2: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether 32:b0:1b:6f:4e:e9 brd ff:ff:ff:ff:ff:ff root@ratatosk:~# uptime 20:05:19 up 5 min, 1 user, load average: 0.13, 0.39, 0.21 just rebooted, the MACs are stable 🐴 I could try reconfiguring the netplan config to use the name [like with lan1] instead of MAC... but that will of course mean I can't rename.

Weird. Check logs and verify matching - mac - if not changing random - is usually safest way. I haven't played under network manger lately ... perhaps there lies the problem or network devices gets up with a delay. I will try to recreate during week.

rules in /etc/udev/rules.d did *nothing*. tried with 00 prefix and 99 prefix. udevadm test-builtin net_setup_link didn't mention the filepath either. But I could make it do stuff with /etc/systemd/network/foo.link, which is what's current[ly not deleted yet from previous attempts]. Which makes it even weirder that it still won't rename at boot. Note that the problem is a lot less the renaming and more that networkd refuses to manage the interfaces, even if I give up on renaming,