Active threads

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.

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

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.

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

OS is stable, errors you are experiencing are likely related to faulty HW component as @eselarm already exposed. And we would most likely notice such anomaly before it gets to you. There are thousands of users and this is the only report of this kind ... Boards are going to the market at high rate, while users support remains more or less the same in past 10 years https://docs.armbian.com/User-Guide_Board-Support-Rules/ Community builds and their upgrades are untested as size of Armbian can only cope with a small selection of boards we call as "standard support", where we have volunteers behind. Community builds are on Debian / Arch images level, but packed with more features. https://github.com/armbian/community?tab=readme-ov-file#purpose-of-this-repository For those - Armbian provides build and hosting infrastructure, place to meet - this forum - while everything else is anyone's problem.

@buzz89

Collabora is heading to Amsterdam with talks, demos, and workshops covering Embedded Linux, KernelCI, Bluetooth & Auracast, mainline video capture for Rockchip, and more. Join us to see our latest open source work in action! View the full article

Wifi chip model?

... straightforward and smooth.

Try this image https://github.com/NickAlilovic/build/releases/download/20250306/Armbian-unofficial_25.05.0-trunk_X98h_bookworm_edge_6.12.11_xfce_desktop.img.xz

Try to upload the old and new driver to an AI with you overlay included. Here it gives some suggestions for what you can try. The power sequence seems to be changed with the new driver and it might be too fast for your display. It suggests to put some parameters in the overlay to delay some parts, with higher chance with the first 3: Under "dsi0_panel: panel@0 {" prepare-delay-ms = <120>; reset-delay-ms = <50>; init-delay-ms = <150>; enable-delay-ms = <50>; disable-delay-ms = <50>; unprepare-delay-ms = <120>;

https://github.com/armbian/build/pull/8517 appears to fix my SFP problems.

I'm trying to install Armbian on the Tanix Tx1 Soc Allwinner H313 Mini TV Box, but this box doesn't have an SD card slot. How do I install Armbian on this box without an SD card?

@schunckt Yes, I should have clarified that drm-copy is an argument is for MPV, which according to the guide mentioned above should allow the frame-buffer to be accessed directly. It is worth noting that mpv makes use of ffmpeg under the hood. Tried with ffplay once but did not have much luck with it. last I checked VLC is not supported other than the legacy vaapi. Please see: https://linux-sunxi.org/Sunxi-Cedrus You can use the sample media from linaro: https://samplemedia.linaro.org/ Just to check are you using the ffmpeg-v4l2-request?

v25.8.1 for Rock 5B Plus running Armbian Linux 6.1.115-vendor-rk35xx

Hello everyone! Could you help find image for x96q v.5.1. which have stable wifi and ethernet?!

That's exactly what I did. I wrote a replacement for the .not_logged_in_yet file in my customize-image.sh with pre-set parameters, just like I create /root/provisioning.sh. I was just wondering if there were any other ways to do this.