All Activity

I'd start by comparing the device tree on a working and non-working image.

Ok, in case anyone's got any ideas about how to fix this, I'm happy to help if I can, but kernel repairs are a bit out of my league... It seems to reboot for different reasons - when it doesn't like something connected to the USB port, when doing a lot of disk I/O, etc. Here's a couple of the error logs from the terminal: INFO: task sgdisk:1567 blocked for more than 120 seconds. Tainted: G O 6.18.10-edge-sunxi64 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:sgdisk state:D stack:0 pid:1567 tgid:1567 ppid:1566 task_flags:0x400000 flags:0x00000018 Call trace: __switch_to+0xcc/0x180 (T) __schedule+0x348/0xaf8 schedule+0x38/0x110 io_schedule+0x40/0x60 folio_wait_bit_common+0x15c/0x390 folio_wait_bit+0x1c/0x30 folio_wait_writeback+0x4c/0xb8 __filemap_fdatawait_range+0x70/0xb0 filemap_fdatawait_keep_errors+0x24/0x58 sync_bdevs+0xb4/0x1a8 ksys_sync+0x64/0x98 __arm64_sys_sync+0x14/0x28 invoke_syscall.constprop.0+0x54/0xe8 do_el0_svc+0x44/0xc8 el0_svc+0x38/0x140 el0t_64_sync_handler+0x98/0xe0 el0t_64_sync+0x170/0x178 Kernel panic - not syncing: hung_task: blocked tasks CPU: 6 UID: 0 PID: 61 Comm: khungtaskd Tainted: G O 6.18.10-edge-sunxi64 #1 PREEMPT Tainted: [O]=OOT_MODULE Hardware name: Radxa Cubie A5E (DT) Call trace: show_stack+0x1c/0x30 (C) dump_stack_lvl+0x30/0x80 dump_stack+0x14/0x20 vpanic+0x2d4/0x308 panic+0x50/0x58 watchdog+0x278/0x718 kthread+0x134/0x1f8 ret_from_fork+0x10/0x20 SMP: stopping secondary CPUs Kernel Offset: disabled CPU features: 0x080000,00008000,48006281,0400701b Memory Limit: none ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]--- INFO: task systemd-udevd:285 blocked for more than 120 seconds. Tainted: G O 6.18.10-edge-sunxi64 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:systemd-udevd state:D stack:0 pid:285 tgid:285 ppid:1 task_flags:0x400100 flags:0x00000809 Call trace: __switch_to+0xcc/0x180 (T) __schedule+0x348/0xaf8 schedule+0x38/0x110 io_schedule+0x40/0x60 folio_wait_bit_common+0x15c/0x390 folio_wait_bit+0x1c/0x30 folio_wait_writeback+0x4c/0xb8 __filemap_fdatawait_range+0x70/0xb0 filemap_write_and_wait_range+0x90/0xc0 sync_blockdev+0x24/0x40 bdev_disk_changed+0x64/0x5c8 blkdev_get_whole+0xa4/0xf8 bdev_open+0x278/0x3b0 bdev_file_open_by_dev+0xdc/0x148 disk_scan_partitions+0x6c/0x150 blkdev_ioctl+0x664/0xfc0 __arm64_sys_ioctl+0x470/0xaa0 invoke_syscall.constprop.0+0x54/0xe8 do_el0_svc+0xa4/0xc8 el0_svc+0x38/0x140 el0t_64_sync_handler+0x98/0xe0 el0t_64_sync+0x170/0x178 INFO: task sgdisk:1465 blocked for more than 120 seconds. Tainted: G O 6.18.10-edge-sunxi64 #1 "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. task:sgdisk state:D stack:0 pid:1465 tgid:1465 ppid:1464 task_flags:0x400000 flags:0x00000008 Call trace: __switch_to+0xcc/0x180 (T) __schedule+0x348/0xaf8 schedule+0x38/0x110 io_schedule+0x40/0x60 folio_wait_bit_common+0x15c/0x390 folio_wait_bit+0x1c/0x30 folio_wait_writeback+0x4c/0xb8 __filemap_fdatawait_range+0x70/0xb0 filemap_write_and_wait_range+0x90/0xc0 bdev_release+0x19c/0x1b0 blkdev_release+0x18/0x30 __fput+0xd0/0x2e8 fput_close_sync+0x44/0x108 __arm64_sys_close+0x3c/0x88 invoke_syscall.constprop.0+0x54/0xe8 do_el0_svc+0x44/0xc8 el0_svc+0x38/0x140 el0t_64_sync_handler+0x98/0xe0 el0t_64_sync+0x170/0x178 Kernel panic - not syncing: hung_task: blocked tasks CPU: 1 UID: 0 PID: 61 Comm: khungtaskd Tainted: G O 6.18.10-edge-sunxi64 #1 PREEMPT Tainted: [O]=OOT_MODULE Hardware name: Radxa Cubie A5E (DT) Call trace: show_stack+0x1c/0x30 (C) dump_stack_lvl+0x30/0x80 dump_stack+0x14/0x20 vpanic+0x2d4/0x308 panic+0x50/0x58 watchdog+0x278/0x718 kthread+0x134/0x1f8 ret_from_fork+0x10/0x20 SMP: stopping secondary CPUs Kernel Offset: disabled CPU features: 0x080000,00008000,48006281,0400701b Memory Limit: none ---[ end Kernel panic - not syncing: hung_task: blocked tasks ]---

Dear Ryzer, Alas, the device tree updsate didn't change anything. Here is the process that uses a lot of CPU: 13.0 0.0 0:05.51 kworker/0:14+events_freezable_power_ Google says it is related to power state changes, and from kernel 6, power saving settings have been more aggressive in Linux, so that's why I am trying to set up a Buster-based system.

Ryzer, Thank you for your suggestions. I will try the update for the device tree, but with otg as value, the board will be a storage device for my dashcam. I am trying to get a Buster release with kernel 6.6.75 to compile under armbian build, but so far, the compilation fails because there is no availale package for base-files. I did put the file in the cache/sources folder (which worked for a bullseye version), but nothing works for the buster version. So far, the biggest progress was achieved by commenting out or adding the following in armbianEnv.txt (no updates in modules.conf, config.txt or cdmline.txt). With those updates, the drive and folders show up instantly upon activating hte gadget, I can navigate the folders, but writing is a hit and miss (using libcomposite, not g_mass_storage) #overlay_prefix=sun7i-a20 param_usb_device_mode=otg overlays=dwc2 (instead of the usual dtoverlays) With those parameters, Windows file explorer and Windows Explorer no longer crash. The top command shows 13% CPU usage for a kworker process related to power. A google search found that this may be due to a device/driver continuously requesting a power state change (conflict between drivers?). No errors in dmesg regarding dwc2. Here are the final line: [ 75.627225] loop0: detected capacity change from 0 to 83886080 [ 75.628674] loop0: p1 [ 76.067022] loop0: detected capacity change from 0 to 83884032 [ 76.519886] FS-Cache: Loaded [ 76.784125] Key type cifs.spnego registered [ 76.784185] Key type cifs.idmap registered [ 76.787080] CIFS: Attempting to mount //192.168.0.1/Tesladrive [ 76.893017] CIFS: decode_ntlmssp_challenge: authentication has been weakened as server does not support key exchange [ 78.023297] loop0: detected capacity change from 0 to 83886080 [ 78.023757] loop0: p1 [ 78.568262] loop0: detected capacity change from 0 to 83884032 [ 79.642716] Mass Storage Function, version: 2009/09/11 [ 79.642755] LUN: removable file: (no medium) and usb related lines: [ 4.097675] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver [ 4.097739] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 5 [ 4.115390] usb usb5: Manufacturer: Linux 6.6.75-legacy-sunxi musb-hcd [ 4.115403] usb usb5: SerialNumber: musb-hdrc.1.auto [ 20.084995] systemd[1]: Reached target usb-gadget.target - Hardware activated USB gadget.

@billymore The "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)" error indicates that the Linux kernel could not locate or mount the root file system during startup. . This is commonly caused by a missing or corrupted initial RAM filesystem (initramfs), an incorrect root= boot parameter write 0x4ff00000 rootfs.cpio.lzma.uboot

@Jain Ziad I'm currently working on hardware acceleration, though I can't say yet if it will outperform the official Radxa builds since it uses the same drivers. I'll keep the community updated on the results.

Hello, I'm new to this forum and I hope I'm not mistaken in making this request. I wanted to ask if it would be possible to add support for installing Armbian on the UniFi CloudKey Gen1. It uses an MT7623, very similar to the BPI R2, which appears to already be supported. Below is information about the UC-CK hardware: FCC ID, Datasheet MT7623AI 2GB DDR 16GB internal storage Micro SD slot (1) 10/100/1000 Ethernet Port

Hello Armbian-Community! TL;DR I've successfully enabled the Rockchip RK3568 NPU (0.8 TOPS INT8) on the ODROID-M1 with 8GB RAM running Armbian 6.18.9-current-rockchip64. The only thing needed to make this work for everyone is a 1-line kernel patch in Armbian build that I've already submitted: https://github.com/armbian/build/pull/9403 Once this patch is merged into Armbian, the DKMS modules will work out-of-the-box on all RK3568 boards. The Problem 1. Hardkernel and Rockchip provide NPU patches for quite old kernel versions: rockchip <= 6.6 hardkernel <= 5.10 2. IOMMU page table allocation bug — On systems with >4GB RAM, the kernel's IOMMU allocates page tables above 4GB, but the NPU can only access the first 4GB of physical memory, causing DMA mapping failures and inference timeouts The Solution 1. Kernel Patch (1 line!) - .gfp_flags = 0, + .gfp_flags = GFP_DMA32, This forces IOMMU page tables to be allocated below 4GB, fixing NPU operation on 8GB boards. 2. DKMS Driver Package I've created a complete DKMS package that: - Includes DT overlays for NPU, IOMMU, power-domain, and clock configuration - Supports dynamic frequency scaling (100 MHz - 1000 MHz) - Provides `/dev/dri/renderD129` (DRM/GEM interface) for RKNN Runtime - Would compile against Armbian's stock kernel headers with the above patch merged The Questions 1. What would be the best way to provide those modules for installation in the armbian system? 2. Has someone a 4 GB version of the M1 and could test the modules?

Hello, 4GB version. - Detecting meteors in GMN network (https://globalmeteornetwork.org/) - monitor other x64 machine and reset by power cycle (via gpio). rock64 is rock stable

Hello since kernel 6.12 led (heartbeat and mmc activity) on board rock64 don't work. I've created issue in dietPI github: https://github.com/MichaIng/DietPi/issues/7618 but DietPI is using armbian kernel. Now I'm using recent armbian with kernel 6.11.0-edge-rockchip64. Any idea how to restore led activity on recent kernels?

The sysfs GPIO interface does not allow you to create clock outputs as-is. You'd do better seeing if that pin can be exposed through the sysfs PWM interface. I know the NanoPi M4V2's fan controller works this way (RK3399), and you can set the duty cycle. But you'd have to check if PWM is supported on that pin, and can be used in the way you're hoping. Failing that, it is possible to bit-bang the GPIO lines yourself if you're willing to write some C code. You can use Kernel Timers for fairly accurate timing, as long as you set High Scheduler Priority and Real Time Scheduler Class. Note that kernel timers only have a user specified resolution of 1ns, so you might not hit that frequency exactly.

Probably a new product. Images are not compatible unless specifically marked as such.

Regarding the vendor kernel I also managed to get the GPU going with some AI help, but the HDMI hotplug issue persists. Will probably revisit it in the future. (the dtb should go in packages/blobs/h96-m9_original.dtb and the defconfig in patch/u-boot/legacy/u-boot-radxa-rk35xx/deconfig) h96-m9.csc h96-m9_original.dts h96-m9-rk3576_defconfig h96-m9_original.dtb

I'm trying to get a clock signal of 32768 from the GPIO1 D4 pin of the rk3328 CPU, but I haven't been able to. I've tried everything, from `overlay dts` to `armbian-add-overlay`, but I can't get any output. I can set the value to 1 or 0 using the `echo 1 > /sys/class/gpio/gpio60/value` command, but the system doesn't give a clock output. Please help. Thank you in advance.

I'm moving forward. I managed to get the FEL - a true Male A <> Male A USB cable is required. FEL mode is now working. I'm able to transfer the u-boot-sunxi-with-spl.bin of Armbian but TX1 is booting on Android immediately (based on Armbian-unofficial_26.02.0-trunk_X96q-v5-1_bookworm_current_6.12.64_minimal.img - u-boot-sunxi-with-spl.bin extracted). This means that I don't have the possibility to boot on the Armbian USB drive (flashed with u-boot-sunxi-with-spl.bin) Similarly, I tried with another image based on MiniArch (MiniArch-20240715-6.18.7-board-h313.tanix_tx1-SD-Image.img.xz). I was able to transfer those MiniArch via FEL: sunxi-fel -v -p uboot bootloader/u-boot-sunxi-with-spl.bin write 0x40200000 Image write 0x4fa00000 dtbs/allwinner/sun50i-h313-tanix-tx1.dtb write 0x4fc00000 load-kernel.scr Original made Load-kernel.scr in the MiniArch-20240715-6.18.7-board-h313.tanix_tx1-SD-Image.img.xz : setenv bootargs console=ttyS0,115200 root=/dev/sda2 rw rootwait ram=1024M debug booti 0x40200000 - 0x4fa00000 With the MiniArch FEL, the TX1 is not booting on Android and I can see 4 penguins with cursor. I updated the load-kernel.scr to have some verbose by changing the console: setenv bootargs console=tty1 console=ttyS0,115200 root=/dev/sda2 rw rootwait rootdelay=60 ram=1024M debug loglevel=7 booti 0x40200000 - 0x4fa00000 Result: MiniArch bootloader and FEL transfer writes allow to boot. USB devices are detected (USB Hub, USB drive, keyboard) but nothing happens further, or it ends up with a kernel panic. Output of the Linux TX1 console after MiniArch FEL transfer sequence: 1.651121] sunxi-mc 4022000.mmc: initialized, max. request size: 2048 KB, u [ top_ops) 1.655936] sunti-drm display-engine: bound 6510000.tcon-top Cops sunBi_tcon_ 1.973277] mnc2: new high speed DDR MMC card at address 0001 _tcon_ops) 1.9745881 sunfi-drm display-engine: bound 6515000. lcd-controller Cops sunti 1.9789521 mncblk2: mmc2:0001 HAGZe@ 14.7 GiB 1.9825631 sunBi-du-hdmi 6000000.hdmi: Detected HDMI TX controller u2.12a wi th HDCP (DWC HDMI 2.0 TX PHY) p17 1.990428] mncblk2: p1 p2 p3 p1 p5 p6 p? p8 p9 p10 p11 p12 p13 p14 p15 p16 [ iver 1.991663] sunBi-du-hdmi 6000000.hdmi: registered Designbare HDMI I2C bus dr 1.998192] mncblkbooto: mnc2:0001 HAGZed 4.00 MiB 1.999521] sunti-drn display-engine: bound 6000000.hdmi Cops sunBi_du hami_o ps) 2.007404] mncblk2boot1: mnc2:0001 HAGZes 4.00 MiB 2.012147] [drm] Initialized sunfi-drm 1.0.0 for display-engine on minor o 2.723997] Console: switching to colour frane buffer device 240x67 2.7468481 sunti-den display-engine: larm] fb0: sunti-drodrufb frame buffer device 2.7554683 2.7573363 usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.18 of_cis_init 2.7599291 sunxi-nuc 4021000.mmc: allocated mnc-purseg 2. 763866] ush usb3: New USE device strings: Mfr=3, Product=2, SerialNumber=1 2.766352] of_cfs_init: 0K 2.771541] usb usb3: Product: Generic Platform OHCI controller 2.7789161 clk: Disabling unused clocks 2.781535] usb usb3: Manufacturer: Linux 6.18.7 ohci_hcd 2.785297] sunxi-nnc 4021000.mnc: initialized, max. request size: 16384 KB, uses new tinings mode 2.7875991 PM: genpd: Disabling unused power domains 2.7914431 usb usb3: SerialNumber: 5101400 .usb 2.8161741 check access for rdinit=/init failed: -2, ignoring 2.816738] hub 3-0:1.0: USB hub found [2.822049 Waiting 90 sec before mounting root device... 2.831452] hub 3-0:1.0: 1 port detected 2.8428851 mnc1: new high speed SDIO card at address 0001 7.4519021 usb 3-1: new full-speed USB device number 2 using ohci-platform 7.6636101 usb 3-1: New USB device found, idVendor=0a05, idProduct=7211, bcdDevice= 1.00 7.6718951 usb 3-1: New USB device strings: Mfr=0, Product=1, Seria lNumber=0 7.679084] usb 3-1: Product: USBZ.0 HUB 7.684782J hub 3-1:1.0: USB hub found 7.6896091 hub 3-1:1.0: 4 ports detected 8.115235] usb 3-1.1: new full-speed USB device number 3 using ohci-platform 8.224936] usb 3-1,1: not running at top speed; connect to a high speed hub 8.266936] usb 3-1.1: New USB device found, idVendor=059f, idProduct=1022, bcdDevice= 1.00 8.2753821 8.282744] USD 3-1,1: New USB device strings: Mfral, Product=2, SerialMunber=3 usb 8.2871451 usb 3-1.1: Product: LaCie lanaKey 8.2912791 usb 3-1.1: Manufacturer: LaCie 3-1.1: SerialNumber: 97e0bfb3cfe007 8.501898] แรง 3-1.2: new full-speed USB device number 4 using ohci-platform 8.6079401 8.6163791 usb 3-1.2: New USB device found, idVendor=0318, idProduct=2808, bcdDevice= 2.00 3-1.2: New USB device strings: Mfr=0, Product=1, Seria lNumber=0 8.6237581 usb 3-1.2: Product: 2.4G Composite Devic 8.711901] uSb 3-1.3: new low-speed USB device number 5 using ohci-platform 8.847941] usb 8.8563831 usb 3-1.3: New USB device found, idVendor=04f2, idProduct=0403, bcdDevice= 1.65 3-1.3: New USB device strings: Mfr=1, Product=2, Seria lNumber=0 8.865882] usb 3-1.3: Product: USB Keyboard 8.8722631 usb 3-1.3: Manufacturer: Chicony 12.851997] sun501-h6-prcm-ppu 7010250. power-controller: sync_state() pending due to 1800000. gpu If I wait, I ended up seeing a kernel panic : Kernel panic - not suncing: UFS: Unable to mount rout fs ; on unknoun-block(0,0) 93.6966821 b30d 93.696690] 03.7097151 b30e 93.7097231 93.7224501 b30f 93.7227581 93.7357951 b310 93.735804] 33.748859] b311 163B4 mncblk2p9 а0085546-4166-744a-a353-fca9272bBe4d 163B4 mncblk2p10 а0085546-4166-741a-a353-fca9272bBete 16384 mncblk2p11 a0085546-4166-744a-a353-fca9272bBe4f 16384 mmcblkZp12 а0085546-4166-744a-a353-fca9272bBe50 512 mmcblk2p13 a0085546-4166-744a-a353-fca9272bBe51 15872 mncblk2p14 a0085546-4166-744a-a353-fca9272bBe52 163B4 mncblk2p15 a0085546-4166-744a-a353-fca9272bBe53 16384 mncblk2p16 а0085546-4166-744a-a353-fca9272bBe54 11423727 mmcblk2p17 a0085546-4166-744a-a353-fca9272bBe55 93.748867] 93.761944] b320 4096 mmcblkZbooto 93.7619521 (driver?) 93.7121621 b340 4096 mmcblk2boot1 93.7121121 (driver?) 99.7835151 List of all bdeu filesystems: 33.7895001 exts 93.7895061 ext4 93.793371] extz 33.7972031 ufat 93.8010141 msdos 93.8048091 93.8120251 Kernel panic - not suncing: UFS: Unable to mount rout fs ; on unknoun-block(0,0) 93.8221681 CPU: 2 UID: 0 PID: 1 Comm: swapper/0 Tainted: G 6.18.7 #1 PREEMPT 56ea6Zc682B4f70bf2 93.9338801 -1 end Kernel panic - not syncing: UFS: Unable to mount root fs on unknown-block(0,0) }— 93.836517] Tainted: [WI-WARN 93.841380] Hardware name: Tanix TX1 (DT) 93.8472801 Call trace: 93.8515981 show_stack+0x24/0x70 (C) 93.857135] dump_stack_lul+0x74/0x94 93.8626511 dump _stack+0x14/0x24 93.8677961 upanic+0x104/0x2d4 93.872767] panic +0x5c/0x64 93.877447] mount root gener ic+0x14/0x29B 93.8834131 mount_root +0x16c/0x188 93.8886741 prepare _namespace +0x1cc/0x22c 93.8945131 kernel_init_frecable+0x264/0x284 93.900587] kernel_init+0x1c/0x140 93.905767] ret_from_fork+0x10/0x20 93.9110311 MP: stopping secondary CPU: 93.9166281 Kernel Offset: disable 93.9217681 CPU features: At this stage, I'm stuck with the TX1 : - Armbian Image - no boot success - FEL difficult - MiniArch - boot started but stuck Any help would be appreciated.

Dear all, I just received my new NanoPC-T6 Plus from FriendlyElec: https://www.friendlyelec.com/index.php?route=product/product&path=69&product_id=315 I couldn't find a dedicated image for this SBC, is it compatible with the one for the NanoPC T6 LTS (same board, upgraded LPDDR5 RAM) ? https://www.armbian.com/nanopct6-lts/ Best regards, Magic Sam

the tft is working well on stock orangepi image but when I try the prebuilt armbian images or build it myself it look like this my dts file: 35Lcd.dts

I've gotten it working. I'll detail the steps soon, but it's not difficult. I just want to confirm that running it this way I can boot from sd/usb/nvme/eMMC/Network, and see if changing the boot order works.

This is not working for me either. I had audio initially working with the "Radxa OS" (Ubuntu 24.04), but after a few reboots, seems to lose audio and reverts to "Dummy Output" audio placeholder for the Output Device. No luck at all with sound on Armbian even after following the instructions laid out here. Would be nice to get audio working reliably for the Q6A on Armbian as its my favorite SBC to date, but no sound is a show stopper.

It appears there would have been no problem with the Logitech Unifying Dongle that uses Bluetooth. I ended up buying a Logitech Keyboard/Mouse combination that is practically identical except uses WiFi protocol rather than Bluetooth as per the suggestion of the vendor of the HamClock Quadra4K. PeeSHaw.... Prices have come down I guess... I found it at the local Wally World for $19.95 on sale... Crazy! I was asking because I had an older Logitech Bluetooth mouse and dongle and was thinking I would just use them and get the keyboard... Thank you for the help!

It works, I'm soooo happy with this. Big thank you!!!

Not excited AT ALL about Allwinner, but there are few (actually none that I've found?) choices for low-priced, "higher performance" SBCs with WiFi 6, BT 5.4, USB3, GB Ethernet, PoE and a small size and factory case. I'll take anything rockchip in a heartbeat I much prefer their chips. My go-to has been the RockPI-S, but it's low performance CPU, WiFi 4, BT 4, 100M Ethernet, USB2, and getting pretty old. AFAIK, there's nothing out there that checks all the boxes, sadly.

@NicoD I download and extract the Wine-Proton prebuilt binaries, then let Box64 do the rest. This is the script I used (You might want to change the directories)

There was a commit 4 days ago on that repo metioned above: https://github.com/joilg/x88pro/commit/a6630814a98b39ec39dc22108c01e35f5d456395 Anyone noticed? Anyone tried it? Any change?