Active threads
Showing topics posted in for the last 365 days.
- Past hour
-
here is the full log dtb/amlogic/meson-gxl-s805x-p241.dtb copied -u-boot-s905x-s912 u-boot.ext then renamed it as u-boot.ext manually booted from sd card , then installed to emmc sudo /root/install-aml.sh previously i could save bootcmd as env , after this ,i couldnot save env ,from u-boot ------------------------------------------------------------------------------------------------------------------------------------------------------------ [ OK ] Reached target Reboot. [ 650.054096] watchdog: watchdog0: watchdog did not stop! [ 650.541411] reboot: Restarting system bl31 reboot reason: 0xd bl31 reboot reason: 0x0 system cmd 1. GXL:BL1:9ac50e:bb16dc;FEAT:BFFC39BE:100;POC:3;RCY:0;EMMC:0;READ:0;CHK:1F;READ:0;1.0;1.0;CHK:0; TE: 241336 BL2 Built : 10:47:34, Jan 14 2019. gxl g152d217 - guotai.shen@droid11-sz set vcck to 1120 mv set vddee to 1000 mv Board ID = 7 CPU clk: 984MHz DDR enable rdbi DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0 16bit @ 912MHz bist_test rank: 0 1b 00 37 27 0f 3f 1c 01 38 2b 11 45 27 27 27 27 27 27 27 27 27 27 27 27 693 - PASS Rank0: 1024MB-2T-13 AddrBus test pass! Set ddr ssc: ppm1000- eMMC boot @ 1 sw8 s emmc switch 3 ok BL2: rpmb counter: 0x00000020 emmc switch 1 ok OTP_ARB=00000001 Load FIP HDR from eMMC, src: 0x0000c200, des: 0x01700000, size: 0x00004000, part: 1 Load BL3x from eMMC, src: 0x00010200, des: 0x01704000, size: 0x000f4000, part: 1 NOTICE: BL3-1: v1.0(release):3bc3888 NOTICE: BL3-1: Built : 11:28:51, May 10 2019 [BL31]: GXL CPU setup! NOTICE: BL3-1: GXL secure boot! NOTICE: BL3-1: BL33 decompress pass mpu_config_enable:system pre init ok dmc sec lock MVN_1=0x01010100 MVN_2=0x01010000 [Image: gxl_v1.1.3375-8f9c8a7 2019-01-24 10:45:03 guotai.shen@droid11-sz] OPS=0x34 21 0d 34 00 25 ae dc 97 5b 00 83 fe 04 b3 53 02 [0.856523 Inits done] secure task start! high task start! low task start! INFO: BL3-2: ATOS-V2.4-238-g14a47cb #1 Tue Dec 3 07:25:46 UTC 2019 arm INFO: BL3-2: Chip: GXL Rev: D (21:D - 30:2) INFO: BL3-2: crypto engine DMA INFO: BL3-2: secure time TEE INFO: BL3-2: CONFIG_DEVICE_SECURE 0xb200000e U-Boot 2015.01-g186a540 (Mar 14 2020 - 17:11:46) DRAM: 1 GiB Relocation Offset is: 36e86000 register usb cfg[0][1] = 0000000037f51910 [CANVAS]canvas init boot_device_flag : 1 Nand PHY Ver:1.01.001.0006 (c) 2013 Amlogic Inc. init bus_cycle=6, bus_timing=7, system=5.0ns reset failed get_chip_type and ret:fffffffe get_chip_type and ret:fffffffe chip detect failed and ret:fffffffe nandphy_init failed and ret=0xfffffff1 MMC: aml_priv->desc_buf = 0x0000000033e866b0 aml_priv->desc_buf = 0x0000000033e889f0 SDIO Port B: 0, SDIO Port 😄 1 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 400000 emmc/sd response timeout, cmd8, status=0x1ff2800 emmc/sd response timeout, cmd55, status=0x1ff2800 co-phase 0x2, tx-dly 0, clock 400000 co-phase 0x2, tx-dly 0, clock 40000000 [mmc_startup] mmc refix success init_part() 282: PART_TYPE_DOS [mmc_init] mmc init success check_valid_dts() 248: Decrypt dtb: Sig Check -2 get_partition_from_dts() 71: ret -249 get_partition_from_dts() 74: ret -249 get_ptbl_from_dtb()-269: get partition table from dts faild mmc_device_init()-1251: get partition table from dtb failed get_ptbl_rsv()-491: magic faild MPT, ▒ mmc_device_init()-1278: dtb&rsv are not exist, no LPT source _find_partition_by_name()-198: do not find match in table env get partition info failed !! Using default environment In: serial Out: serial Err: serial reboot_mode=cold_boot itest - return true/false on integer compare Usage: itest [.b, .w, .l, .s] [*]value1 <op> [*]value2 [store]To run cmd[emmc dtb_read 0x1000000 0x40000] _verify_dtb_checksum()-2755: calc 79d92d6, store f26b0ab5 update_dtb_info()-2863: cpy 1 is not valid _verify_dtb_checksum()-2755: calc ab3aca1f, store f6004a13 update_dtb_info()-2863: cpy 0 is not valid dtb_read()-2972: total valid 0 emmc - EMMC sub system Usage: emmc dtb_read addr size emmc dtb_write addr size emmc erase dtb emmc erase key emmc fastboot_read addr size emmc fastboot_write addr size [store]decrypt dtb: Sig Check -2 vpu: error: vpu: check dts: FDT_ERR_BADMAGIC, load default parameters vpu: clk_level = 2 vpu: set clk: 200000000Hz, readback: 200000000Hz(0x501) vpu: vpu_clk_gate_init_off finish vpp: vpp_init hpd_state=0 vpp: vpp_matrix_update: 2 cvbs performance type = 6, table = 0 cvbs_config_hdmipll_gxl cvbs_set_vid2_clk Net: dwmac.c9410000[KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 MACADDR:02:5b:97:dc:ae:25(from chipid) Warning: dwmac.c9410000 MAC addresses don't match: Address in SROM is 4a:f1:62:3d:0c:33 Address in environment is 02:5b:97:dc:ae:25 CONFIG_AVB2: avb2 Start read misc partition datas! _find_partition_by_name()-198: do not find match in table misc Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read misc 0x33e75090 0x0 0x820] failed to store read misc. info->magic = info->version_major = 0 info->version_minor = 0 info->slots[0].priority = 0 info->slots[0].tries_remaining = 0 info->slots[0].successful_boot = 0 info->slots[1].priority = 0 info->slots[1].tries_remaining = 0 info->slots[1].successful_boot = 0 info->crc32 = 0 Magic is incorrect. boot-info is invalid. Resetting. save boot-info info->magic = info->version_major = 1 info->version_minor = 0 info->slots[0].priority = 15 info->slots[0].tries_remaining = 7 info->slots[0].successful_boot = 0 info->slots[1].priority = 14 info->slots[1].tries_remaining = 7 info->slots[1].successful_boot = 0 info->crc32 = -1075449479 _find_partition_by_name()-198: do not find match in table misc Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_write_ops,L110:cmd [store write misc 0x33e75090 0x0 0x820] failed active slot = 0 wipe_data=successful wipe_cache=successful upgrade_step=0 reboot_mode:::: cold_boot [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]fb_addr for logo: 0x3d800000 [OSD]check dts: FDT_ERR_BADMAGIC, load default fb_addr parameters [OSD]fb_addr for logo: 0x3d800000 [OSD]VPP_OFIFO_SIZE:0xfff00fff [CANVAS]addr=0x3d800000 width=3840, height=2160 _find_partition_by_name()-198: do not find match in table logo Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read logo 0x1080000 0x0 0x2000] Err imgread(L523):Fail to read 0x2000B from part[logo] at offset 0 There is no valid bmp file at the given address [OSD]osd_hw.free_dst_data: 0,719,0,575 [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 gpio: pin GPIOAO_2 (gpio 102) value is 1 Command: bcb uboot-command Start read misc partition datas! _find_partition_by_name()-198: do not find match in table misc Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read misc 0x33e75080 0x0 0x440] failed to store read misc. bcb - bcb Usage: bcb This command will run some commands which saved in misc partition by mark to decide whether execute command! Command format: bcb bcb_mark Example: /dev/block/misc partiton is saved some contents: uboot-command N/A setenv aa 11;setenv bb 22;setenv cc 33;saveenv; So you can execute command: bcb uboot-command [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 (Re)start USB... USB0: USB3.0 XHCI init start Register 2000140 NbrPorts 2 Starting the controller USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... init_part() 282: PART_TYPE_DOS 1 Storage Device(s) found fail in cmd [fatsize usb 0 factory_update_param.aml], rcode 1 File factory_update_param.aml not exist in Upan?? get upgrade version failed Hit Enter or space or Ctrl+C key to stop autoboot -- : 0 CONFIG_SYSTEM_AS_ROOT: systemroot system_mode: 1 [KM]Error:f[keymanage_dts_parse]L287:not a fdt at 0x0000000001000000 Start read misc partition datas! _find_partition_by_name()-198: do not find match in table misc Cannot find dev. amlmmc cmd <NULL> failed store - STORE sub-system Usage: store init flag store read name addr off|partition size read 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store write name addr off|partition size write 'size' bytes starting at offset 'off' to/from memory address 'addr', skipping bad blocks. store rom_write add off size. write uboot to the boot device store erase boot/data: erase the area which is uboot or data store erase partition <partition_name>: erase the area which partition in u-boot store erase dtb store erase key store disprotect key store rom_protect on/off store scrub off|partition size scrub the area from offset and size store dtb iread/read/write addr <size> read/write dtb, size is optional store key read/write addr <size> read/write key, size is optional store mbr addr update mbr/partition table by dtb [burnup]Err:store_read_ops,L63:cmd failed, ret=1, [store read misc 0x33e75090 0x0 0x820] failed to store read misc. info->magic = info->version_major = 0
-
Hi, welcome. Syncing forums and tags with supported boards is (still) a manual job and from time to time I either cannot keep up or miss things. Like in this case. I'll fix this later and then move appropriately. Until then feel free to state your question in "Beginners" using the "other" tag. Cheers
- Today
-
I tried Armbian_26.2.1_Nanopim4v2_trixie_current_6.18.8_minimal.img.xz, wrote it on TF card and it booted into Linux without any changes.
-
device x92 android tv, amlogic s912, armbian file: Armbian_5.84_Aml-s905_Debian_stretch_default_5.1.0-rc1_20190507.img
-
Hello, @Geoffrey F4FXLyou just saved me a lot of debugging time. I have multiple orange pi zero with h2+ and h3 and I had the same problem as you. With the reboot command, the sbc shutsdown but doesn't boot again, i need to reset the power for getting it booting again. On my side , this command extraargs=reboot=warm didn't worked but extraargs=reboot=watchdog worked perfectly. I just rebooted it 5 times in a row and it always rebooted well. My version : v25.11.2 for Orange Pi Zero running Armbian Linux 6.12.58-current-sunxi
-
Where is the RAM present in this setup box?
abhishek timalsina posted a topic in Allwinner CPU Boxes
-
Excelent! That works. I didn't, notice that pinctrl-rk805 was externalized and can't be loaded automatically. For now I've just add pinctrl-rk805 to /etc/initramfs-tools/modules and update-initramfs. Werner: device tree has no changes for a long time. Thanks!
-
Hi Brent; YES! I did figure it out, finally. The issue is that almost all information on the web is for the older pipewire and wireplumber which works completely differently than the new versions. Bookworm used the "old way" and Trixie uses these new versions for which there isn't much info. Compounding the issue is that most information is regarding desktop versions of Linux, not headless like I run. So, when you use bluetooth on linux, wireplumber auto-creates profiles and pw nodes. Or at least it's supposed to. It wasn't creating these profiles because I was missing a conf file which is only needed when your NOT running on desktop, AFAICT. Add this file: /etc/wireplumber/wireplumber.conf.d/50-bluez-no-seat.conf wireplumber.profiles = { main = { monitor.bluez.seat-monitoring = disabled } } If you do that, all of sudden, bluetooth "just works". Took forever to find that stupid little piece of information.
-
@sicxnull I ran into the same issue when flashing "Armbian-unofficial_26.02.0-trunk_Mxqpro_bookworm_current_6.12.65_minimal" (worked only in SD Card). The issue was gone when I switched to "Armbian-unofficial_25.05.0-trunk_X96q-lpddr3-v1-3_bookworm_edge_6.12.11_server" built by @Nick A
-
The Rock Pi S completely freezes during OOMs
brentr replied to solaris3308's topic in Radxa Rock Pi S
Could you send me just the (short) list of packages you installed atop the base Armbian distro rather than a dump of every installed package? The goal is to provide me a simply procedure I can use to replicate the freeze you observe. You might also try running repeating the "free" command to monitor memory usage just after you start your tests. I expect you will see the swap usage steadily increasing. If you disable swap, the system will likely start killing processes. -
Hello everyone, I have a Lemfo H96 Max V56 (8GB RAM / 64GB eMMC). Board PCB Version: HCY RK3566 - 1X32 - V13 - 2021-03-27 I am relatively new to the Linux world. So far, the only image I have managed to flash and boot successfully is an old Linaro Debian 10 (vendor image from 2019). However, this version lacks hardware acceleration (it runs on llvmpipe), which makes it unusable for my specific needs. My Goal: I want to run a modern Linux with a Desktop environment to use PortMaster and RetroArch. For this, I critically need a system with working Panfrost/Mali GPU drivers. The Problem: I have read through this thread, but I am finding it quite confusing to pinpoint exactly where to start given the various methods (Legacy vs Mainline/Chainloader). Also, it seems some file links are dead or pointing to empty repositories. Request: Could someone please guide me to the correct/updated files for my specific 8GB board? The correct MiniLoader/SPL (.bin) for RKDevTool. A working Desktop Image (.img) (Armbian Bookworm or Ubuntu) that supports GPU acceleration. I am already comfortable using RKDevTool and putting the device into Maskrom mode, so I just need the correct file set to avoid bricking the device. Thanks in advance for any help!
- Yesterday
-
I'm back at it, but this time I can boot by setting netplan wifi up. On reboot wifi never comes up. Do the following: Since end0 is reporting as "busy," let's see if forcing it back to eth0 helps udev clear the conflict. Edit /boot/armbianEnv.txt. Add or modify the extraargs line to include: extraargs=net.ifnames=0 biosdevname=0 Fix hash errors: # Remove the cached package lists that are causing the mismatch sudo rm -rf /var/lib/apt/lists/* # Create the partial directory again just in case sudo mkdir -p /var/lib/apt/lists/partial # Clean out the local repository of retrieved package files sudo apt clean # Update the package index again sudo apt update This is latest build.
-
BalenaEtcher has known issues and therefore not recommended. Use Armbian Imager or USBimager. Also verify that the downloaded image is good by utilizing the checksum. https://docs.armbian.com/User-Guide_Getting-Started/#download-and-verification https://github.com/armbian/imager https://bztsrc.gitlab.io/usbimager/
-
Will check it when i back to PC, will be away from pc for around a week
-
I do get multiple warnings while compiling the DTS file, about 50-100 warnings similar to this: ttt.dts:1752.3-32: Warning (gpios_property): /usb0-vbus:gpio: cell 0 is not a phandle reference ttt.dts:1764.3-32: Warning (gpios_property): /usb1-vbus:gpio: cell 0 is not a phandle reference ttt.dts:1776.3-32: Warning (gpios_property): /usb2-vbus:gpio: cell 0 is not a phandle reference ttt.dts:1823.4-34: Warning (gpios_property): /leds/led-3:gpios: cell 0 is not a phandle reference ttt.dts:1828.4-34: Warning (gpios_property): /leds/led-4:gpios: cell 0 is not a phandle reference The phandles are in this kind of format on the dts file: phandle = <0x20>; phandle = <0xc2>; phandle = <0x1c>; phandle = <0xc3>; phandle = <0xc4>; phandle = <0x16>; phandle = <0xc5>; example: Note: the usb0 vbus was originally disabled but I enabled it as the pcduino3 nano has a single regulator for all ports and it is attached to usb0 apparently. In the closing section of __symbols__, I have redirected all 3 regulators to usb0. I believe that the fact it is disabled is because they don't recommend powering the board through the OTG port as it can cause voltage drops when connecting devices as host. My setup will be a gadget with a wifi dongle in a USB A port, so voltage drops should not be a concern, this is just my assumption... usb0-vbus { compatible = "regulator-fixed"; regulator-name = "usb0-vbus"; regulator-min-microvolt = <0x4c4b40>; regulator-max-microvolt = <0x4c4b40>; enable-active-high; gpio = <0x17 0x01 0x09 0x00>; status = "okay"; phandle = <0xc2>;
-
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 ]---
-
Have Armbian for Tanix TX1 QHZIW_H313_TX1_EMCP_V2.0?
Nick A replied to Lesano's topic in Allwinner CPU Boxes
@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.
- Last week
-
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?
-
to get 32768 clk from GPIO1 D4 on RK3328
tparys replied to emresensoy's topic in Advanced users - Development
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. -
Is the NanoPC-T6 Plus compatible with the NanoPC T6 LTS image ?
Werner replied to magic_sam's topic in NanoPC T6 LTS
Probably a new product. Images are not compatible unless specifically marked as such. -
Efforts to develop firmware for H96 MAX M9 RK3576 TV Box 8G/128G
cmuki replied to Hqnicolas's topic in Rockchip CPU Boxes
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
