Simon-renegade Posted December 7, 2022 Posted December 7, 2022 I've tried to run Armbian on HK1RBOX V2 with the latest Jammy version (Nov 30,2022). I just replaced the dtb with the one extracted from HK1RBOX V2 firmware. Here is the result -- Jammy XFCE desktop with kernel 4.19 -- Work fine. Need to copy wifi driver from the original firmware to have wifi function. Jammy XFCE desktop with kernel 5.19 -- Blocked. The boot message is as below. Looks like there are something wrong with the dtb compatibility Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x412fd050] [ 0.000000] Linux version 5.19.17-station-p2 (root@c0ef8c0946a8) (aarch64-linux-gnu-gcc (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 8.3.0, GNU ld (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) 2.32.0.20190321) #22.11.1 SMP PREEMPT Wed Nov 30 11:18:30 UTC 2022 [ 0.000000] Machine model: Rockchip RK3566 BOX DEMO V10 ANDROID Board [ 0.000000] earlycon: uart8250 at MMIO32 0x00000000fe660000 (options '') [ 0.000000] printk: bootconsole [uart8250] enabled [ 0.000000] efi: UEFI not found. [ 0.000000] OF: reserved mem: invalid size property in 'rknpu' node. [ 0.000000] Reserved memory: created CMA memory pool at 0x0000000010000000, size 8 MiB [ 0.000000] OF: reserved mem: initialized node linux,cma, compatible id shared-dma-pool [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000000efffffff] [ 0.000000] NUMA: NODE_DATA [mem 0xef805a40-0xef807fff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000200000-0x00000000efffffff] [ 0.000000] DMA32 empty [ 0.000000] Normal empty [ 0.000000] Movable zone start for each node [ 0.000000] Early memory node ranges [ 0.000000] node 0: [mem 0x0000000000200000-0x00000000083fffff] [ 0.000000] node 0: [mem 0x0000000009400000-0x00000000efffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x00000000efffffff] [ 0.000000] On node 0, zone DMA: 512 pages in unavailable ranges [ 0.000000] On node 0, zone DMA: 4096 pages in unavailable ranges [ 0.000000] psci: probing for conduit method from DT. [ 0.000000] psci: PSCIv1.1 detected in firmware. [ 0.000000] psci: Using standard PSCI v0.2 function IDs [ 0.000000] psci: Trusted OS migration not required [ 0.000000] psci: SMC Calling Convention v1.2 [ 0.000000] percpu: Embedded 30 pages/cpu s83048 r8192 d31640 u122880 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: GIC system register CPU interface [ 0.000000] CPU features: detected: Virtualization Host Extensions [ 0.000000] CPU features: detected: Qualcomm erratum 1009, or ARM erratum 1286807, 2441009 [ 0.000000] CPU features: detected: ARM errata 1165522, 1319367, or 1530923 [ 0.000000] alternatives: patching kernel code [ 0.000000] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 963080 [ 0.000000] Policy zone: DMA [ 0.000000] Kernel command line: root=UUID=5413fab1-29d3-4294-9172-2033521dfdbd console=ttyFIQ0 console=tty0 rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian earlycon=uart8250,mmio32,0xfe660000 [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes, linear) [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes, linear) [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] Memory: 3765676K/3913728K available (17024K kernel code, 2880K rwdata, 7016K rodata, 4224K init, 721K bss, 139860K reserved, 8192K cma-reserved) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] trace event string verifier disabled [ 0.000000] rcu: Preemptible hierarchical RCU implementation. [ 0.000000] rcu: RCU event tracing is enabled. [ 0.000000] rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=4. [ 0.000000] Trampoline variant of Tasks RCU enabled. [ 0.000000] Tracing variant of Tasks RCU enabled. [ 0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies. [ 0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4 [ 0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0 [ 0.000000] GICv3: GIC: Using split EOI/Deactivate mode [ 0.000000] GICv3: 320 SPIs implemented [ 0.000000] GICv3: 0 Extended SPIs implemented [ 0.000000] Root IRQ handler: gic_handle_irq [ 0.000000] GICv3: GICv3 features: 16 PPIs [ 0.000000] GICv3: CPU0: found redistributor 0 region 0:0x00000000fd460000 [ 0.000000] ITS [mem 0xfd440000-0xfd45ffff] [ 0.000000] GIC: enabling workaround for ITS: Rockchip RK3568 force no_local_cache [ 0.000000] ITS@0x00000000fd440000: allocated 8192 Devices @24d0000 (indirect, esz 8, psz 64K, shr 0) [ 0.000000] ITS@0x00000000fd440000: allocated 32768 Interrupt Collections @24e0000 (flat, esz 2, psz 64K, shr 0) [ 0.000000] ITS: using cache flushing for cmd queue [ 0.000000] ITS ALLOCATE PROP WORKAROUND [ 0.000000] GICv3: using LPI property table @0x00000000024f0000 [ 0.000000] GIC: using cache flushing for LPI property table [ 0.000000] GICv3: CPU0: using allocated LPI pending table @0x0000000002500000 [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 0.000000] clk: couldn't get assigned clock 0 for /clock-controller@fdd00000 [ 0.000000] rockchip_clk_of_add_provider: could not register clk provider [ 0.000000] rockchip_clk_of_add_provider: could not register clk provider [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns [ 0.000000] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001086] Failed to get pclk for 'rk_timer' [ 0.002034] Console: colour dummy device 80x25 [ 0.002495] printk: console [tty0] enabled [ 0.002882] printk: bootconsole [uart8250] disabled
SteeMan Posted December 7, 2022 Posted December 7, 2022 First read the FAQ post about Armbian and TV Boxes: https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first Second, DTB files are kernel version specific since they are the mapping from the hardware to the kernel code. So you can't take a dtb from an old kernel and expect it to work on a new one (especially when the old kernel is a heavily patched/android based kernel and the new one is mainline - as they will have very different implementations of basic support for these boards).
tmm1 Posted December 10, 2022 Posted December 10, 2022 Try adding `keep_bootcon` to the kernel command line to see more details
ewww Posted December 13, 2022 Posted December 13, 2022 @Simon-renegade I believe it's HK1 RBox R2, isn't it?
Recommended Posts