jock Posted September 12, 2021 Author Share Posted September 12, 2021 40 minutes ago, Wester_Minsk said: backup original android or my armbian? Android 0 Quote Link to comment Share on other sites More sharing options...
Wester_Minsk Posted September 12, 2021 Share Posted September 12, 2021 https://disk.yandex.by/d/RYIADV5cMwpOmA 2 Quote Link to comment Share on other sites More sharing options...
fabiobassa Posted September 12, 2021 Share Posted September 12, 2021 @Wester_Minsk Your contribute is highly appreciated, don't worry ! If you like to continue experiment is ok ! Let me ask you : have you electronic skills ? Would you be able to connect a uart /ttl converter to those wonderfull uart pads I see int he photos ? спасибо 0 Quote Link to comment Share on other sites More sharing options...
Wester_Minsk Posted September 12, 2021 Share Posted September 12, 2021 2 часа назад, fabiobassa сказал: @Wester_Minsk Your contribute is highly appreciated, don't worry ! If you like to continue experiment is ok ! I'm not worried, I just didn't want to bother you, unless absolutely necessary. I will continue working with pleasure. I am interested in this topic. 2 часа назад, fabiobassa сказал: @Wester_Minsk Let me ask you : have you electronic skills ? Would you be able to connect a uart /ttl converter to those wonderfull uart pads I see int he photos ? I have a modest experience, but I can handle it. I'm friends with a soldering iron. I have: ch340 usb ttl, RS485 to UART, TTL to RS485, USB to RS485. 0 Quote Link to comment Share on other sites More sharing options...
Wester_Minsk Posted September 12, 2021 Share Posted September 12, 2021 del 0 Quote Link to comment Share on other sites More sharing options...
fabiobassa Posted September 13, 2021 Share Posted September 13, 2021 @Wester_Minsk ch340 should be ok. Remember the speed of rockchip is NON STANDARD at 1500000, yes 1 million 500000 ! It will be interesting : full bootlog of android full bootlog with sd inserted but android still present in eemc full bootlog of armbian in emmc full bootlog of armbian in emmc plus sd inserted In few words the most case we have, the better understanding of things ! 0 Quote Link to comment Share on other sites More sharing options...
Wester_Minsk Posted September 13, 2021 Share Posted September 13, 2021 37 минут назад, fabiobassa сказал: @Wester_Minsk ch340 should be ok. Remember the speed of rockchip is NON STANDARD at 1500000, yes 1 million 500000 ! It will be interesting : full bootlog of android full bootlog with sd inserted but android still present in eemc full bootlog of armbian in emmc full bootlog of armbian in emmc plus sd inserted In few words the most case we have, the better understanding of things ! I'll try to figure it out. Give me a hint, how to read these logs? Maybe there is a manual or a link to the topic with such works? 0 Quote Link to comment Share on other sites More sharing options...
jock Posted September 13, 2021 Author Share Posted September 13, 2021 @Wester_Minskthanks for the firmware and photos. I had a quick look into the device tree and it looked quite standard to me: no particular hardware like Power Management ICs or other significant differences from regular tv boxes. I will take a deeper look and check other compatibility things soon! 2 Quote Link to comment Share on other sites More sharing options...
fabiobassa Posted September 13, 2021 Share Posted September 13, 2021 @Wester_Minsk Quote Give me a hint, how to read these logs? Usually programs such as putty, extraputty and other putty derivatives have the ability to export logs captured in real time on the uart to a file called putty.log Then copy paste here or upload somewhere @jock or myself can have a look 0 Quote Link to comment Share on other sites More sharing options...
Wester_Minsk Posted September 13, 2021 Share Posted September 13, 2021 Logs complete Android.log Armbian eMMC.log Armbian sdcard.log 1 Quote Link to comment Share on other sites More sharing options...
jock Posted September 14, 2021 Author Share Posted September 14, 2021 @Wester_Minsk thanks for the logs. I extracted the ddrbin from the backup you posted above and made an image with that. The ddrbin is the thingy that initializes the DDR memory, an initialization with bad timings may be harmful for the system stability, so give a shot to this experimental image (it's a debian bullseye with command line only): https://users.armbian.com/jock/rk3318/Armbian_21.11.0-trunk_Rk3318-box_bullseye_current_5.10.64_minimal.img.xz edit: if you try this on sdcard, be sure to erase the eMMC completely first! 2 Quote Link to comment Share on other sites More sharing options...
Wester_Minsk Posted September 14, 2021 Share Posted September 14, 2021 Ok, I'll test it. Thanks 0 Quote Link to comment Share on other sites More sharing options...
Wester_Minsk Posted September 15, 2021 Share Posted September 15, 2021 14 hours up time on eMMC, with Doker +HA + Pihole load. At the beginning there was one freeze, after which I removed the parameter "rk3318-box-emmc-hc200" from the armbian-config. Then it works stably. This is already much better than it was, the changes are obvious. I will pick up a good sdcard, and start from it to eliminate the eMMC problem and continue testing. 3 Quote Link to comment Share on other sites More sharing options...
jock Posted September 15, 2021 Author Share Posted September 15, 2021 15 minutes ago, Wester_Minsk said: 14 hours up time on eMMC, with Doker +HA + Pihole load. At the beginning there was one freeze, after which I removed the parameter "rk3318-box-emmc-hc200" from the armbian-config. Then it works stably. This is already much better than it was, the changes are obvious. I will pick up a good sdcard, and start from it to eliminate the eMMC problem and continue testing. Cool, thanks for reporting! My box was also stable for hours with your ddrbin, so I think I will promote it as the new default 1 Quote Link to comment Share on other sites More sharing options...
hexdump Posted September 17, 2021 Share Posted September 17, 2021 @jock - do you have this extracted ddrbin somewhere in your repos already? i was not able to find it yet ... 1 Quote Link to comment Share on other sites More sharing options...
jock Posted September 17, 2021 Author Share Posted September 17, 2021 1 hour ago, hexdump said: @jock - do you have this extracted ddrbin somewhere in your repos already? i was not able to find it yet ... Nope, not yet, I'm a bit busy with rk3288 at the moment, but here you go: ddrbin_v1.16.bin 2 Quote Link to comment Share on other sites More sharing options...
Ben N Voutour Posted September 20, 2021 Share Posted September 20, 2021 is there an option to boot from USB 3.0 hdd? and not sure how many devices have 2GB ram and some have 4GB 0 Quote Link to comment Share on other sites More sharing options...
lucky62 Posted September 20, 2021 Share Posted September 20, 2021 1 hour ago, RetroFan90 said: is there an option to boot from USB 3.0 hdd? and not sure how many devices have 2GB ram and some have 4GB My box x88 pro 10 is booting from USB 3.0 HDD but only from USB 2.0 port. USB 3.0 is not supported by U-boot, I think... 0 Quote Link to comment Share on other sites More sharing options...
jock Posted September 20, 2021 Author Share Posted September 20, 2021 Nope, USB 3.0 is not supported at all in u-boot, and USB 2.0 support is a bit lousy on rk3318/rk3328 too. U-boot non-core code is not the best, it's just "good enough" to let basic things work. 0 Quote Link to comment Share on other sites More sharing options...
maximilliangreat Posted September 20, 2021 Share Posted September 20, 2021 Hi! I have several rk3318 boxes at hands (H96 Max, X88 Pro) - all of them android 10. I've tried to burn Buster legacy and Focal mainline to sdcard, but no success - it still boots into android. But when I burn Multitool image to same sdcard, all boxes boots fine to multitool. Maybe I'm doing something wrong? I used balenaetcher to burn sdcard. The boxes are not mine, so I cannot dissassembe them or reflash emmc. 0 Quote Link to comment Share on other sites More sharing options...
AlwinLub Posted September 20, 2021 Share Posted September 20, 2021 I've got a HK1 Max with a RK3318 (ordered a 3328, but got a 3318 delivered). X11 works, but it has screen tearing issues. The HDMI output stops completely (as in no signal) when adding a new cvt mode via xrandr. I'm using the build with the supplied drivers, and i was wondering if maybe things will run better under Wayland/Weston. It needs to run a Python Kivy-app with many animations, so screen tearing is not ideal. I have no clue how to install/compile wayland/weston, but i got something running which returns the following error: [15:00:37.291] weston 5.0.0 https://wayland.freedesktop.org Bug reports to: https://gitlab.freedesktop.org/wayland/weston/issues/ Build: unknown (not built from git or tarball) [15:00:37.292] Command line: weston [15:00:37.296] OS: Linux, 4.4.213-rockchip64, #5 SMP Fri Apr 16 17:25:31 UTC 2021, aarch64 [15:00:37.301] Using config file '/home/user/.config/weston.ini' [15:00:37.304] Output repaint window is 7 ms maximum. [15:00:37.308] Loading module '/usr/lib/aarch64-linux-gnu/libweston-5/drm-backend.so' [15:00:37.333] Failed to load module: /usr/lib/aarch64-linux-gnu/libweston-5/drm-backend.so: undefined symbol: gbm_bo_get_offset [15:00:37.333] fatal: failed to create compositor backend I would really appreciate If somebody would like to point me in the right direction. dmesg output: Spoiler [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.4.213-rockchip64 (root@armbianbuild) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) ) #5 SMP Fri Apr 16 17:25:31 UTC 2021 [ 0.000000] Boot CPU: AArch64 Processor [410fd034] [ 0.000000] Reserved memory: failed to reserve memory for node 'drm-logo@00000000': base 0x0000000000000000, size 0 MiB [ 0.000000] Reserved memory: failed to reserve memory for node 'secure-memory@20000000': base 0x0000000020000000, size 0 MiB [ 0.000000] On node 0 totalpages: 1043968 [ 0.000000] DMA zone: 16312 pages used for memmap [ 0.000000] DMA zone: 0 pages reserved [ 0.000000] DMA zone: 1043968 pages, LIFO batch:31 [ 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: MIGRATE_INFO_TYPE not supported. [ 0.000000] psci: SMC Calling Convention v1.1 [ 0.000000] PERCPU: Embedded 20 pages/cpu @ffffffc0fdf26000 s42152 r8192 d31576 u81920 [ 0.000000] pcpu-alloc: s42152 r8192 d31576 u81920 alloc=20*4096 [ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: enabling workaround for ARM erratum 845719 [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 1027656 [ 0.000000] Kernel command line: root=UUID=16e726f1-23f5-4c1b-8638-1e5a8db51cf8 rootwait rootfstype=ext4 console=ttyS2,1500000 console=tty1 consoleblank=0 loglevel=1 ubootpart=c0616ed8-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [ 0.000000] PID hash table entries: 4096 (order: 3, 32768 bytes) [ 0.000000] Dentry cache hash table entries: 524288 (order: 10, 4194304 bytes) [ 0.000000] Inode-cache hash table entries: 262144 (order: 9, 2097152 bytes) [ 0.000000] software IO TLB: mapped [mem 0xf4e00000-0xf8e00000] (64MB) [ 0.000000] Memory: 3991284K/4175872K available (12350K kernel code, 1582K rwdata, 6740K rodata, 1216K init, 1964K bss, 184588K reserved, 0K cma-reserved) [ 0.000000] Virtual kernel memory layout: modules : 0xffffff8000000000 - 0xffffff8008000000 ( 128 MB) vmalloc : 0xffffff8008000000 - 0xffffffbdbfff0000 ( 246 GB) .init : 0xffffff8009330000 - 0xffffff8009460000 ( 1216 KB) .text : 0xffffff8008080000 - 0xffffff8008c90000 ( 12352 KB) .rodata : 0xffffff8008c90000 - 0xffffff8009330000 ( 6784 KB) .data : 0xffffff8009460000 - 0xffffff80095eb808 ( 1583 KB) vmemmap : 0xffffffbdc0000000 - 0xffffffbfc0000000 ( 8 GB maximum) 0xffffffbdc0008000 - 0xffffffbdc3fc0000 ( 63 MB actual) fixed : 0xffffffbffe7fb000 - 0xffffffbffec00000 ( 4116 KB) PCI I/O : 0xffffffbffee00000 - 0xffffffbfffe00000 ( 16 MB) memory : 0xffffffc000200000 - 0xffffffc0ff000000 ( 4078 MB) [ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1 [ 0.000000] Hierarchical RCU implementation. [ 0.000000] Build-time adjustment of leaf fanout to 64. [ 0.000000] RCU restricting CPUs from NR_CPUS=8 to nr_cpu_ids=4. [ 0.000000] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=4 [ 0.000000] NR_IRQS:64 nr_irqs:64 0 [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] rockchip_mmc_get_phase: invalid clk rate [ 0.000000] rockchip_mmc_get_phase: invalid clk rate [ 0.000000] rockchip_mmc_get_phase: invalid clk rate [ 0.000000] rockchip_mmc_get_phase: invalid clk rate [ 0.000000] rockchip_mmc_get_phase: invalid clk rate [ 0.000000] rockchip_mmc_get_phase: invalid clk rate [ 0.000000] rockchip_mmc_get_phase: invalid clk rate [ 0.000000] rockchip_mmc_get_phase: invalid clk rate [ 0.000000] Architected 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.000008] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns [ 0.001222] Console: colour dummy device 80x25 [ 0.001481] console [tty1] enabled [ 0.001514] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [ 0.001531] pid_max: default: 32768 minimum: 301 [ 0.001701] Security Framework initialized [ 0.001717] Yama: becoming mindful. [ 0.001749] AppArmor: AppArmor disabled by boot time parameter [ 0.001826] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes) [ 0.001843] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes) [ 0.002915] Initializing cgroup subsys io [ 0.002943] Initializing cgroup subsys memory [ 0.002988] Initializing cgroup subsys devices [ 0.003007] Initializing cgroup subsys freezer [ 0.003026] Initializing cgroup subsys net_cls [ 0.003049] Initializing cgroup subsys perf_event [ 0.003069] Initializing cgroup subsys net_prio [ 0.003092] Initializing cgroup subsys hugetlb [ 0.003110] Initializing cgroup subsys pids [ 0.003170] ftrace: allocating 46463 entries in 182 pages [ 0.143702] sched-energy: CPU device node has no sched-energy-costs [ 0.143729] Invalid sched_group_energy for CPU0 [ 0.143740] CPU0: update cpu_capacity 1024 [ 0.143820] ASID allocator initialised with 32768 entries [ 0.147166] Detected VIPT I-cache on CPU1 [ 0.147242] Invalid sched_group_energy for CPU1 [ 0.147249] CPU1: update cpu_capacity 1024 [ 0.147254] CPU1: Booted secondary processor [410fd034] [ 0.148047] Detected VIPT I-cache on CPU2 [ 0.148099] Invalid sched_group_energy for CPU2 [ 0.148105] CPU2: update cpu_capacity 1024 [ 0.148110] CPU2: Booted secondary processor [410fd034] [ 0.148860] Detected VIPT I-cache on CPU3 [ 0.148915] Invalid sched_group_energy for CPU3 [ 0.148922] CPU3: update cpu_capacity 1024 [ 0.148927] CPU3: Booted secondary processor [410fd034] [ 0.149039] Brought up 4 CPUs [ 0.149106] SMP: Total of 4 processors activated. [ 0.149121] CPU features: detected feature: 32-bit EL0 Support [ 0.149140] CPU: All CPU(s) started at EL2 [ 0.149186] alternatives: patching kernel code [ 0.149457] Invalid sched_group_energy for CPU3 [ 0.149472] Invalid sched_group_energy for Cluster3 [ 0.149482] Invalid sched_group_energy for CPU2 [ 0.149492] Invalid sched_group_energy for Cluster2 [ 0.149501] Invalid sched_group_energy for CPU1 [ 0.149511] Invalid sched_group_energy for Cluster1 [ 0.149522] Invalid sched_group_energy for CPU0 [ 0.149533] Invalid sched_group_energy for Cluster0 [ 0.150458] devtmpfs: initialized [ 0.178914] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.178957] futex hash table entries: 1024 (order: 4, 65536 bytes) [ 0.179683] xor: measuring software checksum speed [ 0.219570] 8regs : 1079.000 MB/sec [ 0.259662] 8regs_prefetch: 968.000 MB/sec [ 0.299749] 32regs : 1403.000 MB/sec [ 0.339839] 32regs_prefetch: 1222.000 MB/sec [ 0.339852] xor: using function: 32regs (1403.000 MB/sec) [ 0.339896] pinctrl core: initialized pinctrl subsystem [ 0.340345] regulator-dummy: no parameters [ 0.343128] Failed to find legacy iommu devices [ 0.344052] NET: Registered protocol family 16 [ 0.355995] cpuidle: using governor ladder [ 0.367622] cpuidle: using governor menu [ 0.367671] Registered FIQ tty driver [ 0.368458] vdso: 2 pages (1 code @ ffffff8008c96000, 1 data @ ffffff8009464000) [ 0.368504] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.369789] DMA: preallocated 2048 KiB pool for atomic allocations [ 0.390749] gpiochip_add_data: registered GPIOs 0 to 31 on device: gpio0 [ 0.390916] gpiochip_add_data: registered GPIOs 32 to 63 on device: gpio1 [ 0.391089] gpiochip_add_data: registered GPIOs 64 to 95 on device: gpio2 [ 0.391249] gpiochip_add_data: registered GPIOs 96 to 127 on device: gpio3 [ 0.504596] raid6: int64x1 gen() 202 MB/s [ 0.572492] raid6: int64x1 xor() 191 MB/s [ 0.640579] raid6: int64x2 gen() 324 MB/s [ 0.708697] raid6: int64x2 xor() 250 MB/s [ 0.776754] raid6: int64x4 gen() 445 MB/s [ 0.844874] raid6: int64x4 xor() 330 MB/s [ 0.913103] raid6: int64x8 gen() 369 MB/s [ 0.981173] raid6: int64x8 xor() 304 MB/s [ 1.049394] raid6: neonx1 gen() 363 MB/s [ 1.117365] raid6: neonx1 xor() 368 MB/s [ 1.185537] raid6: neonx2 gen() 550 MB/s [ 1.253618] raid6: neonx2 xor() 450 MB/s [ 1.321750] raid6: neonx4 gen() 744 MB/s [ 1.389870] raid6: neonx4 xor() 550 MB/s [ 1.457976] raid6: neonx8 gen() 746 MB/s [ 1.526102] raid6: neonx8 xor() 575 MB/s [ 1.526112] raid6: using algorithm neonx8 gen() 746 MB/s [ 1.526124] raid6: .... xor() 575 MB/s, rmw enabled [ 1.526135] raid6: using intx1 recovery algorithm [ 1.526795] mpp venc_srv: mpp_probe enter [ 1.526836] mpp venc_srv: init success [ 1.527270] rockchip-pm rockchip-suspend: not set wakeup-config [ 1.527288] rockchip-pm rockchip-suspend: not set pwm-regulator-config [ 1.528200] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/regulators/regulator@0[0]' [ 1.528243] vccio_1v8: 1800 mV [ 1.528596] reg-fixed-voltage regulators:regulator@0: vccio_1v8 supplying 1800000uV [ 1.528696] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/regulators/regulator@1[0]' [ 1.528724] vccio_3v3: 3300 mV [ 1.529091] reg-fixed-voltage regulators:regulator@1: vccio_3v3 supplying 3300000uV [ 1.529189] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc-phy-regulator[0]' [ 1.529217] vcc_phy: 1800 mV [ 1.529534] reg-fixed-voltage vcc-phy-regulator: vcc_phy supplying 1800000uV [ 1.529634] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vcc-sys[0]' [ 1.529664] vcc_sys: 5000 mV [ 1.529992] reg-fixed-voltage vcc-sys: vcc_sys supplying 5000000uV [ 1.530363] of_get_named_gpiod_flags: parsed 'gpio' property of node '/sdmmc-regulator[0]' - status (0) [ 1.530440] reg-fixed-voltage sdmmc-regulator: Looking up vin-supply from device tree [ 1.530536] vcc_sd: supplied by vccio_3v3 [ 1.530553] vccio_3v3: could not add device link regulator.5 err -2 [ 1.530663] vcc_sd: 3300 mV [ 1.531075] reg-fixed-voltage sdmmc-regulator: vcc_sd supplying 3300000uV [ 1.531366] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc-host-vbus[0]' - status (0) [ 1.531435] reg-fixed-voltage vcc-host-vbus: Looking up vin-supply from device tree [ 1.531496] vcc_host_vbus: supplied by vcc_sys [ 1.531513] vcc_sys: could not add device link regulator.6 err -2 [ 1.531585] vcc_host_vbus: 5000 mV [ 1.531967] reg-fixed-voltage vcc-host-vbus: vcc_host_vbus supplying 5000000uV [ 1.532217] of_get_named_gpiod_flags: parsed 'gpio' property of node '/vcc-otg-vbus[0]' - status (0) [ 1.532282] reg-fixed-voltage vcc-otg-vbus: Looking up vin-supply from device tree [ 1.532339] vcc_otg_vbus: supplied by vcc_sys [ 1.532355] vcc_sys: could not add device link regulator.7 err -2 [ 1.532426] vcc_otg_vbus: 5000 mV [ 1.532802] reg-fixed-voltage vcc-otg-vbus: vcc_otg_vbus supplying 5000000uV [ 1.533778] iommu: Adding device ff350000.vpu_service to group 0 [ 1.533867] iommu: Adding device ff351000.avsd to group 1 [ 1.533963] iommu: Adding device ff360000.rkvdec to group 2 [ 1.534058] iommu: Adding device ff330000.h265e to group 3 [ 1.534170] iommu: Adding device ff340000.vepu to group 4 [ 1.534279] iommu: Adding device ff370000.vop to group 5 [ 1.535035] rk_iommu ff350800.iommu: can't get sclk [ 1.535528] rk_iommu ff360480.iommu: can't get aclk [ 1.535550] rk_iommu ff360480.iommu: can't get hclk [ 1.535565] rk_iommu ff360480.iommu: can't get sclk [ 1.535881] rk_iommu ff330200.iommu: can't get sclk [ 1.536161] rk_iommu ff340800.iommu: can't get sclk [ 1.536368] rk_iommu ff373f00.iommu: can't get sclk [ 1.536635] rk_iommu ff3a0800.iommu: can't get sclk [ 1.537477] SCSI subsystem initialized [ 1.537806] libata version 3.00 loaded. [ 1.538211] usbcore: registered new interface driver usbfs [ 1.538302] usbcore: registered new interface driver hub [ 1.538409] usbcore: registered new device driver usb [ 1.538637] media: Linux media interface: v0.10 [ 1.538710] Linux video capture interface: v2.00 [ 1.538957] pps_core: LinuxPPS API ver. 1 registered [ 1.538969] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 1.539010] PTP clock support registered [ 1.541789] Advanced Linux Sound Architecture Driver Initialized. [ 1.542865] Bluetooth: Core ver 2.21 [ 1.542927] NET: Registered protocol family 31 [ 1.542939] Bluetooth: HCI device and connection manager initialized [ 1.542958] Bluetooth: HCI socket layer initialized [ 1.542977] Bluetooth: L2CAP socket layer initialized [ 1.543022] Bluetooth: SCO socket layer initialized [ 1.543873] NetLabel: Initializing [ 1.543887] NetLabel: domain hash size = 128 [ 1.543897] NetLabel: protocols = UNLABELED CIPSOv4 [ 1.543985] NetLabel: unlabeled traffic allowed by default [ 1.544540] rockchip-cpuinfo cpuinfo: Serial : 81f0c15b8fd24656 [ 1.545891] clocksource: Switched to clocksource arch_sys_counter [ 1.694102] NET: Registered protocol family 2 [ 1.694974] TCP established hash table entries: 32768 (order: 6, 262144 bytes) [ 1.695402] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes) [ 1.696827] TCP: Hash tables configured (established 32768 bind 32768) [ 1.696997] UDP hash table entries: 2048 (order: 5, 196608 bytes) [ 1.697265] UDP-Lite hash table entries: 2048 (order: 5, 196608 bytes) [ 1.698001] NET: Registered protocol family 1 [ 1.698663] RPC: Registered named UNIX socket transport module. [ 1.698680] RPC: Registered udp transport module. [ 1.698689] RPC: Registered tcp transport module. [ 1.698702] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 1.698984] PCI: CLS 0 bytes, default 64 [ 1.699914] Trying to unpack rootfs image as initramfs... [ 2.204549] Freeing initrd memory: 5664K [ 2.205817] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available [ 2.207964] kvm [1]: 8-bit VMID [ 2.207976] kvm [1]: Hyp mode initialized successfully [ 2.208474] kvm [1]: interrupt-controller@ff814000 IRQ48 [ 2.208871] kvm [1]: timer IRQ3 [ 2.213818] audit: initializing netlink subsys (disabled) [ 2.213997] audit: type=2000 audit(2.132:1): initialized [ 2.214744] Initialise system trusted keyring [ 2.215425] HugeTLB registered 2 MB page size, pre-allocated 0 pages [ 2.232831] VFS: Disk quotas dquot_6.6.0 [ 2.233166] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 2.236796] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 2.239389] NFS: Registering the id_resolver key type [ 2.239462] Key type id_resolver registered [ 2.239472] Key type id_legacy registered [ 2.239504] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 2.240772] fuse init (API version 7.23) [ 2.242259] JFS: nTxBlock = 8192, nTxLock = 65536 [ 2.251534] SGI XFS with ACLs, security attributes, realtime, no debug enabled [ 2.256588] Key type big_key registered [ 2.256703] TEE Core Framework initialization (ver 1:0.1) [ 2.256738] TEE armv7 Driver initialization [ 2.257388] tz_tee_probe: name="armv7sec", id=0, pdev_name="armv7sec.0" [ 2.257414] TEE core: Alloc the misc device "opteearmtz00" (id=0) [ 2.257825] TEE Core: Register the misc device "opteearmtz00" (id=0,minor=62) [ 2.264068] NET: Registered protocol family 38 [ 2.264127] Key type asymmetric registered [ 2.264147] Asymmetric key parser 'x509' registered [ 2.264564] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 244) [ 2.264827] io scheduler noop registered [ 2.264853] io scheduler deadline registered (default) [ 2.264940] io scheduler cfq registered [ 2.266793] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply from device tree [ 2.266817] phy phy-ff450000.syscon:usb2-phy@100.0: Looking up phy-supply property in node /syscon@ff450000/usb2-phy@100/host-port failed [ 2.267400] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply from device tree [ 2.267423] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up phy-supply property in node /syscon@ff450000/usb2-phy@100/otg-port failed [ 2.267847] phy phy-ff450000.syscon:usb2-phy@100.1: Looking up vbus-supply from device tree [ 2.269345] rockchip-u3phy ff470000.usb3-phy: Looking up vbus-supply from device tree [ 2.269370] rockchip-u3phy ff470000.usb3-phy: Looking up vbus-supply property in node /usb3-phy@ff470000 failed [ 2.269400] rockchip-u3phy ff470000.usb3-phy: Failed to get VBUS supply regulator [ 2.269839] phy phy-ff470000.usb3-phy.2: Looking up phy-supply from device tree [ 2.269857] phy phy-ff470000.usb3-phy.2: Looking up phy-supply property in node /usb3-phy@ff470000/utmi@ff470000 failed [ 2.270405] phy phy-ff470000.usb3-phy.3: Looking up phy-supply from device tree [ 2.270429] phy phy-ff470000.usb3-phy.3: Looking up phy-supply property in node /usb3-phy@ff470000/pipe@ff478000 failed [ 2.272241] rockchip-u3phy ff470000.usb3-phy: Rockchip u3phy initialized successfully [ 2.273225] phy phy-ff430000.hdmiphy.4: Looking up phy-supply from device tree [ 2.273247] phy phy-ff430000.hdmiphy.4: Looking up phy-supply property in node /hdmiphy@ff430000 failed [ 2.279412] Module initialized. [ 2.279812] rk-vcodec vpu_combo: Looking up vcodec-supply from device tree [ 2.279937] rk-vcodec vpu_combo: vcodec regulator not ready, retry [ 2.280305] rk-vcodec ff360000.rkvdec: Looking up vcodec-supply from device tree [ 2.280387] rk-vcodec ff360000.rkvdec: vcodec regulator not ready, retry [ 2.281387] probe device ff330000.h265e [ 2.281867] mpp_dev ff330000.h265e: try to get iommu dev ffffffc0f4057010 [ 2.282442] mpp_dev ff330000.h265e: resource ready, register device [ 2.283005] probe device ff340000.vepu [ 2.283449] mpp_dev ff340000.vepu: try to get iommu dev ffffffc0f4057810 [ 2.283868] mpp_dev ff340000.vepu: resource ready, register device [ 2.287912] dma-pl330 ff1f0000.dmac: Loaded driver for PL330 DMAC-241330 [ 2.287936] dma-pl330 ff1f0000.dmac: DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16 [ 2.288790] pwm-regulator vdd-arm: GPIO lookup for consumer enable [ 2.288808] pwm-regulator vdd-arm: using device tree for GPIO lookup [ 2.288826] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/vdd-arm[0]' [ 2.288840] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/vdd-arm[0]' [ 2.288854] pwm-regulator vdd-arm: using lookup tables for GPIO lookup [ 2.288874] pwm-regulator vdd-arm: lookup for GPIO enable failed [ 2.288961] pwm-regulator vdd-arm: Looking up pwm-supply from device tree [ 2.288982] pwm-regulator vdd-arm: Looking up pwm-supply property in node /vdd-arm failed [ 2.289027] vdd_arm: 950 <--> 1400 mV at 1197 mV [ 2.289377] pwm-regulator vdd-arm: Looking up pwm-supply from device tree [ 2.289396] pwm-regulator vdd-arm: Looking up pwm-supply property in node /vdd-arm failed [ 2.289511] pwm-regulator vdd-arm: Looking up pwm-supply from device tree [ 2.289528] pwm-regulator vdd-arm: Looking up pwm-supply property in node /vdd-arm failed [ 2.289692] pwm-regulator vdd-log: GPIO lookup for consumer enable [ 2.289707] pwm-regulator vdd-log: using device tree for GPIO lookup [ 2.289725] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/vdd-log[0]' [ 2.289741] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/vdd-log[0]' [ 2.289757] pwm-regulator vdd-log: using lookup tables for GPIO lookup [ 2.289774] pwm-regulator vdd-log: lookup for GPIO enable failed [ 2.289809] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 2.289827] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 2.289946] vdd_log: 900 <--> 1300 mV at 900 mV [ 2.290238] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 2.290258] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 2.290353] pwm-regulator vdd-arm: Looking up pwm-supply from device tree [ 2.290374] pwm-regulator vdd-arm: Looking up pwm-supply property in node /vdd-arm failed [ 2.290395] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 2.290413] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 2.291250] Serial: 8250/16550 driver, 5 ports, IRQ sharing disabled [ 2.292276] ff110000.serial: ttyS0 at MMIO 0xff110000 (irq = 13, base_baud = 1500000) is a 16550A [ 2.293209] ff130000.serial: ttyS2 at MMIO 0xff130000 (irq = 14, base_baud = 1500000) is a 16550A [ 2.294607] console [ttyS2] enabled [ 2.296700] [drm] Initialized drm 1.1.0 20060810 [ 2.302579] [drm] Rockchip DRM driver version: v1.0.1 [ 2.302913] rockchip-drm display-subsystem: devfreq is not set [ 2.303730] rockchip-drm display-subsystem: bound ff370000.vop (ops 0xffffff8008d67390) [ 2.304183] i2c i2c-4: of_i2c: modalias failure on /hdmi@ff3c0000/ports [ 2.304213] dwhdmi-rockchip ff3c0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.304351] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2) [ 2.305719] rockchip-drm display-subsystem: bound ff3c0000.hdmi (ops 0xffffff8008d5bcc0) [ 2.305741] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 2.305751] [drm] No driver support for vblank timestamp query. [ 2.306244] rockchip-drm display-subsystem: failed to parse loader memory [ 2.937077] rockchip-vop ff370000.vop: [drm:vop_crtc_enable] Update mode to 1920x1080p60, type: 11 [ 3.026781] Console: switching to colour frame buffer device 240x67 [ 3.093514] rockchip-drm display-subsystem: fb0: frame buffer device [ 3.104397] usbcore: registered new interface driver udl [ 3.108145] Registered IR keymap rc-cec [ 3.108454] rc rc0: RC for dw_hdmi as /devices/platform/ff3c0000.hdmi/rc/rc0 [ 3.109240] input: RC for dw_hdmi as /devices/platform/ff3c0000.hdmi/rc/rc0/input0 [ 3.110128] Unable to detect cache hierarchy for CPU 0 [ 3.111899] brd: module loaded [ 3.124938] loop: module loaded [ 3.125012] lkdtm: No crash points registered, enable through debugfs [ 3.130368] rk_gmac-dwmac ff550000.ethernet: Looking up phy-supply from device tree [ 3.130575] rk_gmac-dwmac ff550000.ethernet: clock input or output? (output). [ 3.130596] rk_gmac-dwmac ff550000.ethernet: TX delay(0x30). [ 3.130616] rk_gmac-dwmac ff550000.ethernet: RX delay(0x10). [ 3.130684] rk_gmac-dwmac ff550000.ethernet: integrated PHY? (yes). [ 3.130934] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_refout [ 3.130956] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_speed [ 3.136097] rk_gmac-dwmac ff550000.ethernet: init for RMII [ 3.170090] stmmac - user ID: 0x10, Synopsys ID: 0x35 [ 3.170102] Ring mode enabled [ 3.170112] DMA HW capability register supported [ 3.170122] Normal descriptors [ 3.170132] RX Checksum Offload Engine supported (type 2) [ 3.170142] TX Checksum insertion supported [ 3.170152] Wake-Up On Lan supported [ 3.170259] Enable RX Mitigation via HW Watchdog Timer [ 3.170491] of_get_named_gpiod_flags: can't parse 'snps,reset-gpio' property of node '/ethernet@ff550000[0]' [ 3.644437] libphy: stmmac: probed [ 3.644464] eth%d: PHY ID 1234d400 at 0 IRQ POLL (stmmac-1:00) active [ 3.644483] eth%d: PHY ID 00000000 at 1 IRQ POLL (stmmac-1:01) [ 3.644500] eth%d: PHY ID 00000000 at 2 IRQ POLL (stmmac-1:02) [ 3.644514] eth%d: PHY ID 00000000 at 3 IRQ POLL (stmmac-1:03) [ 3.644529] eth%d: PHY ID 00000000 at 4 IRQ POLL (stmmac-1:04) [ 3.644544] eth%d: PHY ID 00000000 at 5 IRQ POLL (stmmac-1:05) [ 3.644558] eth%d: PHY ID 00000000 at 6 IRQ POLL (stmmac-1:06) [ 3.644574] eth%d: PHY ID 00000000 at 7 IRQ POLL (stmmac-1:07) [ 3.644588] eth%d: PHY ID 00000000 at 8 IRQ POLL (stmmac-1:08) [ 3.644603] eth%d: PHY ID 00000000 at 9 IRQ POLL (stmmac-1:09) [ 3.644617] eth%d: PHY ID 00000000 at 10 IRQ POLL (stmmac-1:0a) [ 3.644633] eth%d: PHY ID 00000000 at 11 IRQ POLL (stmmac-1:0b) [ 3.644646] eth%d: PHY ID 00000000 at 12 IRQ POLL (stmmac-1:0c) [ 3.644662] eth%d: PHY ID 00000000 at 13 IRQ POLL (stmmac-1:0d) [ 3.644676] eth%d: PHY ID 00000000 at 14 IRQ POLL (stmmac-1:0e) [ 3.644692] eth%d: PHY ID 00000000 at 15 IRQ POLL (stmmac-1:0f) [ 3.644706] eth%d: PHY ID 00000000 at 16 IRQ POLL (stmmac-1:10) [ 3.644722] eth%d: PHY ID 00000000 at 17 IRQ POLL (stmmac-1:11) [ 3.644736] eth%d: PHY ID 00000000 at 18 IRQ POLL (stmmac-1:12) [ 3.644751] eth%d: PHY ID 00000000 at 19 IRQ POLL (stmmac-1:13) [ 3.644765] eth%d: PHY ID 00000000 at 20 IRQ POLL (stmmac-1:14) [ 3.644781] eth%d: PHY ID 00000000 at 21 IRQ POLL (stmmac-1:15) [ 3.644795] eth%d: PHY ID 00000000 at 22 IRQ POLL (stmmac-1:16) [ 3.644811] eth%d: PHY ID 00000000 at 23 IRQ POLL (stmmac-1:17) [ 3.644825] eth%d: PHY ID 00000000 at 24 IRQ POLL (stmmac-1:18) [ 3.644839] eth%d: PHY ID 00000000 at 25 IRQ POLL (stmmac-1:19) [ 3.644855] eth%d: PHY ID 00000000 at 26 IRQ POLL (stmmac-1:1a) [ 3.644869] eth%d: PHY ID 00000000 at 27 IRQ POLL (stmmac-1:1b) [ 3.644885] eth%d: PHY ID 00000000 at 28 IRQ POLL (stmmac-1:1c) [ 3.644896] eth%d: PHY ID 00000000 at 29 IRQ POLL (stmmac-1:1d) [ 3.644910] eth%d: PHY ID 00000000 at 30 IRQ POLL (stmmac-1:1e) [ 3.644923] eth%d: PHY ID 00000000 at 31 IRQ POLL (stmmac-1:1f) [ 3.647292] Rockchip WiFi SYS interface (V1.00) ... [ 3.647501] usbcore: registered new interface driver cdc_ether [ 3.647600] usbcore: registered new interface driver rndis_host [ 3.650581] phy phy-ff470000.usb3-phy.2: u3phy u2 power on [ 3.650635] phy phy-ff470000.usb3-phy.3: u3phy u3 power on [ 3.652245] dwc2 ff580000.usb: Looking up vusb_d-supply from device tree [ 3.652502] dwc2 ff580000.usb: Looking up vusb_a-supply from device tree [ 3.735309] dwc2 ff580000.usb: DWC OTG Controller [ 3.735369] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1 [ 3.735441] dwc2 ff580000.usb: irq 45, io mem 0xff580000 [ 3.735804] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.735825] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.735842] usb usb1: Product: DWC OTG Controller [ 3.735857] usb usb1: Manufacturer: Linux 4.4.213-rockchip64 dwc2_hsotg [ 3.735870] usb usb1: SerialNumber: ff580000.usb [ 3.737073] hub 1-0:1.0: USB hub found [ 3.737131] hub 1-0:1.0: 1 port detected [ 3.738957] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 3.738984] ehci-pci: EHCI PCI platform driver [ 3.739132] ehci-platform: EHCI generic platform driver [ 3.742028] ehci-platform ff5c0000.usb: EHCI Host Controller [ 3.742431] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 2 [ 3.742644] ehci-platform ff5c0000.usb: irq 46, io mem 0xff5c0000 [ 3.753923] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00 [ 3.754235] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.754253] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.754271] usb usb2: Product: EHCI Host Controller [ 3.754286] usb usb2: Manufacturer: Linux 4.4.213-rockchip64 ehci_hcd [ 3.754300] usb usb2: SerialNumber: ff5c0000.usb [ 3.755367] hub 2-0:1.0: USB hub found [ 3.755452] hub 2-0:1.0: 1 port detected [ 3.756423] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver [ 3.756479] ohci-platform: OHCI generic platform driver [ 3.757212] ohci-platform ff5d0000.usb: Generic Platform OHCI controller [ 3.757651] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3 [ 3.757928] ohci-platform ff5d0000.usb: irq 47, io mem 0xff5d0000 [ 3.818213] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [ 3.818233] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.818251] usb usb3: Product: Generic Platform OHCI controller [ 3.818269] usb usb3: Manufacturer: Linux 4.4.213-rockchip64 ohci_hcd [ 3.818282] usb usb3: SerialNumber: ff5d0000.usb [ 3.819426] hub 3-0:1.0: USB hub found [ 3.819487] hub 3-0:1.0: 1 port detected [ 3.821400] xhci-hcd xhci-hcd.7.auto: xHCI Host Controller [ 3.821768] xhci-hcd xhci-hcd.7.auto: new USB bus registered, assigned bus number 4 [ 3.822111] xhci-hcd xhci-hcd.7.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x04210010 [ 3.822212] xhci-hcd xhci-hcd.7.auto: irq 183, io mem 0xff600000 [ 3.822732] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002 [ 3.822749] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.822767] usb usb4: Product: xHCI Host Controller [ 3.822782] usb usb4: Manufacturer: Linux 4.4.213-rockchip64 xhci-hcd [ 3.822795] usb usb4: SerialNumber: xhci-hcd.7.auto [ 3.823946] hub 4-0:1.0: USB hub found [ 3.824011] hub 4-0:1.0: 1 port detected [ 3.824699] xhci-hcd xhci-hcd.7.auto: xHCI Host Controller [ 3.825056] xhci-hcd xhci-hcd.7.auto: new USB bus registered, assigned bus number 5 [ 3.825203] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM. [ 3.825411] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003 [ 3.825429] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 3.825445] usb usb5: Product: xHCI Host Controller [ 3.825458] usb usb5: Manufacturer: Linux 4.4.213-rockchip64 xhci-hcd [ 3.825471] usb usb5: SerialNumber: xhci-hcd.7.auto [ 3.826629] hub 5-0:1.0: USB hub found [ 3.826687] hub 5-0:1.0: 1 port detected [ 3.827681] usbcore: registered new interface driver usbserial [ 3.827769] usbcore: registered new interface driver usbserial_generic [ 3.827823] usbserial: USB Serial support registered for generic [ 3.830054] usbcore: registered new interface driver iforce [ 3.830233] usbcore: registered new interface driver xpad [ 3.830940] usbcore: registered new interface driver usbtouchscreen [ 3.833060] i2c /dev entries driver [ 3.835020] rk3x-i2c ff170000.i2c: Initialized RK3xxx I2C bus at ffffff800a85a000 [ 3.837443] IR NEC protocol handler initialized [ 3.837469] IR RC5(x/sz) protocol handler initialized [ 3.837487] IR RC6 protocol handler initialized [ 3.837503] IR JVC protocol handler initialized [ 3.837522] IR Sony protocol handler initialized [ 3.837543] IR SANYO protocol handler initialized [ 3.837561] IR Sharp protocol handler initialized [ 3.837578] IR MCE Keyboard/mouse protocol handler initialized [ 3.837596] IR XMP protocol handler initialized [ 3.839666] usbcore: registered new interface driver uvcvideo [ 3.839680] USB Video Class driver (1.1.1) [ 3.840422] rockchip-iodomain ff100000.syscon:io-domains: Looking up vccio1-supply from device tree [ 3.840745] rockchip-iodomain ff100000.syscon:io-domains: Looking up vccio2-supply from device tree [ 3.840959] rockchip-iodomain ff100000.syscon:io-domains: Looking up vccio3-supply from device tree [ 3.841091] rockchip-iodomain ff100000.syscon:io-domains: Looking up vccio4-supply from device tree [ 3.841205] rockchip-iodomain ff100000.syscon:io-domains: Looking up vccio5-supply from device tree [ 3.841327] rockchip-iodomain ff100000.syscon:io-domains: Looking up vccio6-supply from device tree [ 3.841450] rockchip-iodomain ff100000.syscon:io-domains: Looking up pmuio-supply from device tree [ 3.845460] rockchip-thermal ff250000.tsadc: tsadc is probed successfully! [ 3.847682] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com [ 3.847725] Bluetooth: Virtual HCI driver ver 1.5 [ 3.847961] Bluetooth: HCI UART driver ver 2.3 [ 3.847980] Bluetooth: HCI UART protocol H4 registered [ 3.847992] Bluetooth: HCI UART protocol LL registered [ 3.848004] Bluetooth: HCI UART protocol ATH3K registered [ 3.848179] usbcore: registered new interface driver bfusb [ 3.848298] usbcore: registered new interface driver btusb [ 3.848887] cpu cpu0: leakage=14 [ 3.848920] cpu cpu0: leakage-volt-sel=1 [ 3.848988] cpu cpu0: Looking up cpu-supply from device tree [ 3.849173] pwm-regulator vdd-arm: Looking up pwm-supply from device tree [ 3.849195] pwm-regulator vdd-arm: Looking up pwm-supply property in node /vdd-arm failed [ 3.849331] cpu cpu0: Failed to get pvtm [ 3.850143] cpu cpu0: Looking up cpu-supply from device tree [ 3.850317] pwm-regulator vdd-arm: Looking up pwm-supply from device tree [ 3.850338] pwm-regulator vdd-arm: Looking up pwm-supply property in node /vdd-arm failed [ 3.850596] cpu cpu0: Looking up cpu-supply from device tree [ 3.850678] pwm-regulator vdd-arm: Looking up pwm-supply from device tree [ 3.850695] pwm-regulator vdd-arm: Looking up pwm-supply property in node /vdd-arm failed [ 3.852675] sdhci: Secure Digital Host Controller Interface driver [ 3.852689] sdhci: Copyright(c) Pierre Ossman [ 3.852709] Synopsys Designware Multimedia Card Interface Driver [ 3.854790] dwmmc_rockchip ff520000.dwmmc: IDMAC supports 32-bit address mode. [ 3.854854] dwmmc_rockchip ff520000.dwmmc: Using internal DMA controller. [ 3.854878] dwmmc_rockchip ff520000.dwmmc: Version ID is 270a [ 3.854968] dwmmc_rockchip ff520000.dwmmc: DW MMC controller at irq 41,32 bit host data width,256 deep fifo [ 3.855013] dwmmc_rockchip ff520000.dwmmc: Looking up vmmc-supply from device tree [ 3.855030] dwmmc_rockchip ff520000.dwmmc: Looking up vmmc-supply property in node /dwmmc@ff520000 failed [ 3.855069] dwmmc_rockchip ff520000.dwmmc: Looking up vqmmc-supply from device tree [ 3.855086] dwmmc_rockchip ff520000.dwmmc: Looking up vqmmc-supply property in node /dwmmc@ff520000 failed [ 3.855111] dwmmc_rockchip ff520000.dwmmc: No vmmc regulator found [ 3.855126] dwmmc_rockchip ff520000.dwmmc: No vqmmc regulator found [ 3.855155] dwmmc_rockchip ff520000.dwmmc: GPIO lookup for consumer wp [ 3.855172] dwmmc_rockchip ff520000.dwmmc: using device tree for GPIO lookup [ 3.855196] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff520000[0]' [ 3.855213] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff520000[0]' [ 3.855226] dwmmc_rockchip ff520000.dwmmc: using lookup tables for GPIO lookup [ 3.855246] dwmmc_rockchip ff520000.dwmmc: lookup for GPIO wp failed [ 3.870016] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 3.887063] dwmmc_rockchip ff520000.dwmmc: 1 slots initialized [ 3.890986] dwmmc_rockchip ff500000.dwmmc: num-slots property not found, assuming 1 slot is available [ 3.893236] dwmmc_rockchip ff500000.dwmmc: IDMAC supports 32-bit address mode. [ 3.893299] dwmmc_rockchip ff500000.dwmmc: Using internal DMA controller. [ 3.893323] dwmmc_rockchip ff500000.dwmmc: Version ID is 270a [ 3.893490] dwmmc_rockchip ff500000.dwmmc: DW MMC controller at irq 42,32 bit host data width,256 deep fifo [ 3.893544] dwmmc_rockchip ff500000.dwmmc: Looking up vmmc-supply from device tree [ 3.893778] dwmmc_rockchip ff500000.dwmmc: Looking up vqmmc-supply from device tree [ 3.893800] dwmmc_rockchip ff500000.dwmmc: Looking up vqmmc-supply property in node /dwmmc@ff500000 failed [ 3.893841] dwmmc_rockchip ff500000.dwmmc: No vqmmc regulator found [ 3.894016] dwmmc_rockchip ff500000.dwmmc: GPIO lookup for consumer cd [ 3.894033] dwmmc_rockchip ff500000.dwmmc: using device tree for GPIO lookup [ 3.894056] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/dwmmc@ff500000[0]' [ 3.894073] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/dwmmc@ff500000[0]' [ 3.894085] dwmmc_rockchip ff500000.dwmmc: using lookup tables for GPIO lookup [ 3.894102] dwmmc_rockchip ff500000.dwmmc: lookup for GPIO cd failed [ 3.894123] dwmmc_rockchip ff500000.dwmmc: GPIO lookup for consumer wp [ 3.894135] dwmmc_rockchip ff500000.dwmmc: using device tree for GPIO lookup [ 3.894150] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff500000[0]' [ 3.894164] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff500000[0]' [ 3.894181] dwmmc_rockchip ff500000.dwmmc: using lookup tables for GPIO lookup [ 3.894194] dwmmc_rockchip ff500000.dwmmc: lookup for GPIO wp failed [ 3.905927] mmc0: MAN_BKOPS_EN bit is not set [ 3.906988] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 52000000Hz, actual 50000000HZ div = 0) [ 3.907193] mmc_host mmc0: Bus speed (slot 0) = 100000000Hz (slot req 52000000Hz, actual 50000000HZ div = 1) [ 3.907299] mmc0: new DDR MMC card at address 0001 [ 3.908381] mmcblk0: mmc0:0001 S0J58X 59.3 GiB [ 3.908819] mmcblk0boot0: mmc0:0001 S0J58X partition 1 31.5 MiB [ 3.909262] mmcblk0boot1: mmc0:0001 S0J58X partition 2 31.5 MiB [ 3.909720] mmcblk0rpmb: mmc0:0001 S0J58X partition 3 4.00 MiB [ 3.910109] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 3.911326] mmcblk0: p1 [ 3.927094] dwmmc_rockchip ff500000.dwmmc: 1 slots initialized [ 3.928128] dwmmc_rockchip ff510000.dwmmc: IDMAC supports 32-bit address mode. [ 3.928181] dwmmc_rockchip ff510000.dwmmc: Using internal DMA controller. [ 3.928209] dwmmc_rockchip ff510000.dwmmc: Version ID is 270a [ 3.928304] dwmmc_rockchip ff510000.dwmmc: DW MMC controller at irq 43,32 bit host data width,256 deep fifo [ 3.928370] dwmmc_rockchip ff510000.dwmmc: Looking up vmmc-supply from device tree [ 3.928389] dwmmc_rockchip ff510000.dwmmc: Looking up vmmc-supply property in node /dwmmc@ff510000 failed [ 3.928433] dwmmc_rockchip ff510000.dwmmc: Looking up vqmmc-supply from device tree [ 3.928449] dwmmc_rockchip ff510000.dwmmc: Looking up vqmmc-supply property in node /dwmmc@ff510000 failed [ 3.928471] dwmmc_rockchip ff510000.dwmmc: No vmmc regulator found [ 3.928486] dwmmc_rockchip ff510000.dwmmc: No vqmmc regulator found [ 3.928516] dwmmc_rockchip ff510000.dwmmc: GPIO lookup for consumer wp [ 3.928530] dwmmc_rockchip ff510000.dwmmc: using device tree for GPIO lookup [ 3.928549] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff510000[0]' [ 3.928566] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff510000[0]' [ 3.928578] dwmmc_rockchip ff510000.dwmmc: using lookup tables for GPIO lookup [ 3.928596] dwmmc_rockchip ff510000.dwmmc: lookup for GPIO wp failed [ 3.928884] platform sdio-pwrseq: GPIO lookup for consumer reset [ 3.928899] platform sdio-pwrseq: using device tree for GPIO lookup [ 3.928929] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/sdio-pwrseq[0]' - status (0) [ 3.928997] dwmmc_rockchip ff510000.dwmmc: allocated mmc-pwrseq [ 3.942051] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 3.958064] dwmmc_rockchip ff510000.dwmmc: 1 slots initialized [ 3.958385] sdhci-pltfm: SDHCI platform and OF driver helper [ 3.959509] of_get_named_gpiod_flags: parsed 'gpios' property of node '/leds/working[0]' - status (0) [ 3.963404] hidraw: raw HID events driver (C) Jiri Kosina [ 3.971662] usbcore: registered new interface driver usbhid [ 3.971679] usbhid: USB HID core driver [ 3.978232] usbcore: registered new interface driver snd-usb-audio [ 3.981084] rk3328-codec ff410000.codec: spk_depop_time use default value. [ 3.981505] mmc2: queuing unknown CIS tuple 0x80 (7 bytes) [ 3.985006] mmc2: queuing unknown CIS tuple 0x80 (6 bytes) [ 3.988854] mmc2: queuing unknown CIS tuple 0x80 (7 bytes) [ 3.992522] u32 classifier [ 3.992554] Netfilter messages via NETLINK v0.30. [ 3.992678] ip_set: protocol 6 [ 3.992862] Initializing XFRM netlink socket [ 3.993796] NET: Registered protocol family 10 [ 3.995337] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 3.995402] Bridge firewalling registered [ 3.995641] Bluetooth: RFCOMM socket layer initialized [ 3.995694] Bluetooth: RFCOMM ver 1.11 [ 3.995721] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 3.995738] Bluetooth: HIDP socket layer initialized [ 3.995881] 8021q: 802.1Q VLAN Support v1.8 [ 3.995929] [WLAN_RFKILL]: Enter rfkill_wlan_init [ 3.996502] [WLAN_RFKILL]: Enter rfkill_wlan_probe [ 3.996540] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi_chip_type = ap6330 [ 3.996547] [WLAN_RFKILL]: wlan_platdata_parse_dt: enable wifi power control. [ 3.996556] [WLAN_RFKILL]: wlan_platdata_parse_dt: wifi power controled by gpio. [ 3.996567] of_get_named_gpiod_flags: can't parse 'WIFI,poweren_gpio' property of node '/wireless-wlan[0]' [ 3.996576] of_get_named_gpiod_flags: can't parse 'WIFI,vbat_gpio' property of node '/wireless-wlan[0]' [ 3.996583] of_get_named_gpiod_flags: can't parse 'WIFI,reset_gpio' property of node '/wireless-wlan[0]' [ 3.996661] of_get_named_gpiod_flags: parsed 'WIFI,host_wake_irq' property of node '/wireless-wlan[0]' - status (0) [ 3.996672] [WLAN_RFKILL]: wlan_platdata_parse_dt: get property: WIFI,host_wake_irq = 51, flags = 0. [ 3.996686] [WLAN_RFKILL]: wlan_platdata_parse_dt: The ref_wifi_clk not found ! [ 3.996693] [WLAN_RFKILL]: rfkill_wlan_probe: init gpio [ 3.996708] [WLAN_RFKILL]: Exit rfkill_wlan_probe [ 3.996846] [BT_RFKILL]: Enter rfkill_rk_init [ 3.997251] mmc2: queuing unknown CIS tuple 0x80 (19 bytes) [ 3.997691] of_get_named_gpiod_flags: parsed 'uart_rts_gpios' property of node '/wireless-bluetooth[0]' - status (0) [ 3.997707] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: uart_rts_gpios = 42. [ 3.997731] of_get_named_gpiod_flags: parsed 'BT,power_gpio' property of node '/wireless-bluetooth[0]' - status (0) [ 3.997738] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,power_gpio = 53. [ 3.997746] of_get_named_gpiod_flags: can't parse 'BT,reset_gpio' property of node '/wireless-bluetooth[0]' [ 3.997754] of_get_named_gpiod_flags: can't parse 'BT,wake_gpio' property of node '/wireless-bluetooth[0]' [ 3.997770] of_get_named_gpiod_flags: parsed 'BT,wake_host_irq' property of node '/wireless-bluetooth[0]' - status (0) [ 3.997779] [BT_RFKILL]: bluetooth_platdata_parse_dt: get property: BT,wake_host_irq = 58. [ 3.997792] [BT_RFKILL]: bluetooth_platdata_parse_dt: clk_get failed!!!. [ 3.998049] [BT_RFKILL]: Request irq for bt wakeup host [ 3.998150] [BT_RFKILL]: ** disable irq [ 3.998428] [BT_RFKILL]: bt shut off power [ 3.998467] [BT_RFKILL]: bt_default device registered. [ 3.998647] Key type dns_resolver registered [ 3.998679] Error: Driver 'ov4689' is already registered, aborting... [ 3.998725] Error: Driver 'ov7750' is already registered, aborting... [ 3.998745] Error: Driver 'ov13850' is already registered, aborting... [ 3.998759] Error: Driver 'sc031gs' is already registered, aborting... [ 3.999991] Registered cp15_barrier emulation handler [ 4.000039] Registered setend emulation handler [ 4.001358] registered taskstats version 1 [ 4.001391] Loading compiled-in X.509 certificates [ 4.004244] Btrfs loaded, integrity-checker=on [ 4.004383] BTRFS: selftest: Running btrfs free space cache tests [ 4.004421] BTRFS: selftest: Running extent only tests [ 4.004446] BTRFS: selftest: Running bitmap only tests [ 4.004477] BTRFS: selftest: Running bitmap and extent tests [ 4.004511] BTRFS: selftest: Running space stealing from bitmap to extent [ 4.005612] BTRFS: selftest: Free space cache tests finished [ 4.005618] BTRFS: selftest: Running extent buffer operation tests [ 4.005622] BTRFS: selftest: Running btrfs_split_item tests [ 4.005708] BTRFS: selftest: Running find delalloc tests [ 4.054949] mmc_host mmc2: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0) [ 4.056733] mmc2: new high speed SDIO card at address 0001 [ 4.277426] BTRFS: selftest: Running btrfs_get_extent tests [ 4.277735] BTRFS: selftest: Running hole first btrfs_get_extent test [ 4.277780] BTRFS: selftest: Running outstanding_extents tests [ 4.277960] BTRFS: selftest: Running qgroup tests [ 4.277966] BTRFS: selftest: Qgroup basic add [ 4.278070] BTRFS: selftest: Qgroup multiple refs test [ 4.356377] Key type encrypted registered [ 4.357335] rockchip ion idev is NULL [ 4.357356] rga2 ff390000.rga: rga ion client create success! [ 4.357662] rga: Driver loaded successfully ver:4.00 [ 4.358051] rga2: Module initialized. [ 4.358735] rk-vcodec vpu_combo: Looking up vcodec-supply from device tree [ 4.358901] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 4.358915] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 4.359268] rk-vcodec vpu_combo: failed on clk_get clk_cabac [ 4.359280] rk-vcodec vpu_combo: failed on clk_get clk_core [ 4.359331] rk-vcodec vpu_combo: Failed to init_opp_table (-2) [ 4.359457] rk-vcodec: probe of vpu_combo failed with error -2 [ 4.360419] rk-vcodec ff360000.rkvdec: Looking up vcodec-supply from device tree [ 4.360574] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 4.360589] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 4.360763] rk-vcodec ff360000.rkvdec: parent devfreq is disabled [ 4.361268] rk-vcodec ff360000.rkvdec: Failed to get leakage [ 4.361291] rk-vcodec ff360000.rkvdec: Looking up vcodec-supply from device tree [ 4.361412] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 4.361423] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 4.361459] vdd_log: could not add device link ff360000.rkvdec err -17 [ 4.361479] vdd_log: Failed to create debugfs directory [ 4.361493] rk-vcodec ff360000.rkvdec: Failed to get pvtm [ 4.362212] rk-vcodec ff360000.rkvdec: probe device [ 4.362892] rk-vcodec ff360000.rkvdec: drm allocator with mmu enabled [ 4.364071] rk-vcodec ff360000.rkvdec: init success [ 4.364883] of_get_named_gpiod_flags: can't parse 'simple-audio-card,hp-det-gpio' property of node '/hdmi-sound[0]' [ 4.364898] of_get_named_gpiod_flags: can't parse 'simple-audio-card,mic-det-gpio' property of node '/hdmi-sound[0]' [ 4.365870] asoc-simple-card hdmi-sound: i2s-hifi <-> ff000000.i2s mapping ok [ 4.368403] of_get_named_gpiod_flags: can't parse 'simple-audio-card,hp-det-gpio' property of node '/spdif-sound[0]' [ 4.368421] of_get_named_gpiod_flags: can't parse 'simple-audio-card,mic-det-gpio' property of node '/spdif-sound[0]' [ 4.369211] asoc-simple-card spdif-sound: dit-hifi <-> ff030000.spdif mapping ok [ 4.371488] hctosys: unable to open rtc device (rtc0) [ 4.371507] of_cfs_init [ 4.371596] of_cfs_init: OK [ 4.389651] ALSA device list: [ 4.389667] #0: HDMI [ 4.389672] #1: SPDIF [ 4.391034] Freeing unused kernel memory: 1216K [ 5.547818] EXT4-fs (mmcblk0p1): mounted filesystem with writeback data mode. Opts: (null) [ 5.979399] systemd[1]: System time before build time, advancing clock. [ 5.990284] systemd[1]: Inserted module 'autofs4' [ 6.001464] ip_tables: (C) 2000-2006 Netfilter Core Team [ 6.009502] cgroup: cgroup2: unknown option "nsdelegate" [ 6.022183] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 6.023922] systemd[1]: Detected architecture arm64. [ 6.037833] systemd[1]: Set hostname to <rk3318-box>. [ 6.318567] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling. [ 6.318594] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.) [ 6.568256] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.577223] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.580669] systemd[1]: Created slice system-getty.slice. [ 6.581489] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.582971] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 6.583712] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.584433] systemd[1]: Listening on udev Control Socket. [ 6.585059] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.585754] systemd[1]: Listening on fsck to fsckd communication Socket. [ 6.586568] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.587336] systemd[1]: Listening on Journal Socket (/dev/log). [ 6.587946] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.589138] systemd[1]: Created slice User and Session Slice. [ 6.589773] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.589936] systemd[1]: Reached target Slices. [ 6.590406] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.590823] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 6.591826] random: systemd: uninitialized urandom read (16 bytes read, 103 bits of entropy available) [ 6.592263] systemd[1]: Listening on Journal Audit Socket. [ 6.592928] systemd[1]: Reached target System Time Synchronized. [ 6.594257] systemd[1]: Listening on Journal Socket. [ 6.600181] systemd[1]: Starting Set the console keyboard layout... [ 6.609357] systemd[1]: Starting Restore / save the current clock... [ 6.617702] systemd[1]: Mounting Huge Pages File System... [ 6.627211] systemd[1]: Mounting Kernel Debug File System... [ 6.636364] systemd[1]: Mounting POSIX Message Queue File System... [ 6.637715] systemd[1]: Condition check resulted in File System Check on Root Device being skipped. [ 6.638862] systemd[1]: Listening on Syslog Socket. [ 6.639891] systemd[1]: Reached target Swap. [ 6.641478] systemd[1]: Listening on udev Kernel Socket. [ 6.651449] systemd[1]: Starting udev Coldplug all Devices... [ 6.660990] systemd[1]: Starting Create list of required static device nodes for the current kernel... [ 6.663113] systemd[1]: Condition check resulted in Dispatch Password Requests to Console Directory Watch when bootsplash is active being skipped. [ 6.666812] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point. [ 6.678703] systemd[1]: Starting Load Kernel Modules... [ 6.690412] systemd[1]: Starting Remount Root and Kernel File Systems... [ 6.698419] systemd[1]: Starting Nameserver information manager... [ 6.699665] systemd[1]: Reached target Remote File Systems. [ 6.703092] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. [ 6.703953] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 6.708199] systemd[1]: Reached target Local Encrypted Volumes. [ 6.710126] systemd[1]: Reached target Paths. [ 6.721740] systemd[1]: Started Restore / save the current clock. [ 6.724679] systemd[1]: Mounted Huge Pages File System. [ 6.726374] systemd[1]: Mounted Kernel Debug File System. [ 6.728056] systemd[1]: Mounted POSIX Message Queue File System. [ 6.732275] systemd[1]: Started Create list of required static device nodes for the current kernel. [ 6.754569] systemd[1]: Started Load Kernel Modules. [ 6.760448] systemd[1]: Started Nameserver information manager. [ 6.770674] systemd[1]: Mounting Kernel Configuration File System... [ 6.779455] systemd[1]: Starting Apply Kernel Variables... [ 6.785009] EXT4-fs (mmcblk0p1): re-mounted. Opts: commit=600,errors=remount-ro [ 6.792470] systemd[1]: Mounting FUSE Control File System... [ 6.805595] systemd[1]: Started Remount Root and Kernel File Systems. [ 6.815679] systemd[1]: Mounted Kernel Configuration File System. [ 6.826591] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. [ 6.835092] systemd[1]: Starting Load/Save Random Seed... [ 6.842761] systemd[1]: Starting Create System Users... [ 6.856643] systemd[1]: Mounted FUSE Control File System. [ 6.893003] systemd[1]: Started Apply Kernel Variables. [ 6.924276] systemd[1]: Started Load/Save Random Seed. [ 6.959399] systemd[1]: Started Create System Users. [ 6.967264] systemd[1]: Starting Create Static Device Nodes in /dev... [ 7.039143] systemd[1]: Started Create Static Device Nodes in /dev. [ 7.052243] systemd[1]: Starting udev Kernel Device Manager... [ 7.080923] systemd[1]: Started Set the console keyboard layout. [ 7.089522] systemd[1]: Reached target Local File Systems (Pre). [ 7.103004] systemd[1]: Mounting /tmp... [ 7.123041] systemd[1]: Mounted /tmp. [ 7.131515] systemd[1]: Reached target Local File Systems. [ 7.143641] systemd[1]: Starting Armbian ZRAM config... [ 7.157684] systemd[1]: Starting Set console font and keymap... [ 7.165826] systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped. [ 7.189671] systemd[1]: Started udev Kernel Device Manager. [ 7.202458] systemd[1]: Started Set console font and keymap. [ 7.214885] systemd[1]: Started udev Coldplug all Devices. [ 7.235209] systemd[1]: Starting Helper to synchronize boot up for ifupdown... [ 7.270188] systemd[1]: Started Helper to synchronize boot up for ifupdown. [ 7.285410] systemd[1]: Starting Raise network interfaces... [ 7.450448] zram: Added device: zram0 [ 7.452085] zram: Added device: zram1 [ 7.455067] zram: Added device: zram2 [ 7.646953] zram0: detected capacity change from 0 to 2047062016 [ 7.745218] rockchip-saradc ff280000.saradc: Looking up vref-supply from device tree [ 7.760313] systemd[1]: Found device /dev/ttyS2. [ 7.761182] I : [File] : drivers/gpu/arm/mali400/mali/linux/mali_kernel_linux.c; [Line] : 417; [Func] : mali_module_init(); svn_rev_string_from_arm of this mali_ko is '', rk_ko_ver is '5', built at '17:13:36', on 'Apr 16 2021'. [ 7.761608] mali-utgard ff300000.gpu: mali_platform_device->num_resources = 9 [ 7.761613] mali-utgard ff300000.gpu: resource[0].start = 0x0x00000000ff300000 [ 7.761617] mali-utgard ff300000.gpu: resource[1].start = 0x0x00000000ff300000 [ 7.761621] mali-utgard ff300000.gpu: resource[2].start = 0x0x0000000000000013 [ 7.761626] mali-utgard ff300000.gpu: resource[3].start = 0x0x0000000000000014 [ 7.761631] mali-utgard ff300000.gpu: resource[4].start = 0x0x0000000000000015 [ 7.761635] mali-utgard ff300000.gpu: resource[5].start = 0x0x0000000000000016 [ 7.761639] mali-utgard ff300000.gpu: resource[6].start = 0x0x0000000000000017 [ 7.761644] mali-utgard ff300000.gpu: resource[7].start = 0x0x0000000000000018 [ 7.761648] mali-utgard ff300000.gpu: resource[8].start = 0x0x0000000000000019 [ 7.761654] D : [File] : drivers/gpu/arm/mali400/mali/platform/rk/rk.c; [Line] : 623; [Func] : mali_platform_device_init(); to add platform_specific_data to platform_device_of_mali. [ 7.761716] mali-utgard ff300000.gpu: Looking up mali-supply from device tree [ 7.762038] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 7.762052] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 7.763012] mali-utgard ff300000.gpu: leakage=12 [ 7.763029] mali-utgard ff300000.gpu: leakage-volt-sel=1 [ 7.763098] mali-utgard ff300000.gpu: Looking up mali-supply from device tree [ 7.763326] pwm-regulator vdd-log: Looking up pwm-supply from device tree [ 7.763337] pwm-regulator vdd-log: Looking up pwm-supply property in node /vdd-log failed [ 7.763389] vdd_log: could not add device link ff300000.gpu err -17 [ 7.765535] vdd_log: Failed to create debugfs directory [ 7.765574] mali-utgard ff300000.gpu: Failed to get pvtm [ 7.775753] Mali: Mali device driver loaded [ 7.842197] random: nonblocking pool is initialized [ 7.866244] devfreq ff300000.gpu: Couldn't update frequency transition information. [ 7.902236] gpio_ir_recv ir-receiver: GPIO lookup for consumer (null) [ 7.902264] gpio_ir_recv ir-receiver: using device tree for GPIO lookup [ 7.902406] of_get_named_gpiod_flags: parsed 'gpios' property of node '/ir-receiver[0]' - status (0) [ 7.902567] Registered IR keymap rc-empty [ 7.902820] rc rc1: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc1 [ 7.903341] input: gpio_ir_recv as /devices/platform/ir-receiver/rc/rc1/input1 [ 7.905530] rc rc1: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter [ 7.976647] systemd[1]: Started Raise network interfaces. [ 7.992849] Adding 1999080k swap on /dev/zram0. Priority:5 extents:1 across:1999080k SS [ 8.206469] brcmfmac: brcmf_c_preinit_dcmds: Firmware version = wl0: Apr 16 2014 16:43:15 version 6.10.58 (TOB) (r470760) FWID 01-4b84a3c8 [ 8.247207] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 8.356531] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 8.356553] cfg80211: World regulatory domain updated: [ 8.356560] cfg80211: DFS Master region: unset [ 8.356560] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 8.356574] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 8.356581] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 8.356585] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 8.356589] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 8.356593] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 8.356597] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 8.356600] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 8.356604] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) [ 8.397716] zram1: detected capacity change from 0 to 52428800 [ 8.474289] systemd[1]: Started Armbian ZRAM config. [ 8.515257] systemd[1]: Starting Armbian memory supported logging... [ 8.522010] rc rc1: two consecutive events of type space [ 8.523894] systemd[1]: Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch. [ 8.531891] systemd[1]: Reached target Sound Card. [ 8.548408] systemd[1]: Starting Load/Save RF Kill Switch Status... [ 8.612321] [BT_RFKILL]: bt shut off power [ 8.616464] systemd[1]: Started Load/Save RF Kill Switch Status. [ 8.641084] EXT4-fs (zram1): mounted filesystem without journal. Opts: discard [ 11.122219] systemd[1]: Started Armbian memory supported logging. [ 11.134836] systemd[1]: Starting Journal Service... [ 11.467377] systemd[1]: Started Journal Service. [ 11.532107] systemd-journald[596]: Received request to flush runtime journal from PID 1 [ 14.098642] nr_pdflush_threads exported in /proc is scheduled for removal [ 14.642007] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 14.778997] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 14.843773] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 15.277413] NET: Registered protocol family 17 [ 15.533342] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 18.609487] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 21.783800] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code [ 21.783832] cfg80211: World regulatory domain updated: [ 21.783842] cfg80211: DFS Master region: unset [ 21.783847] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) [ 21.783858] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A) [ 21.783868] cfg80211: (2457000 KHz - 2482000 KHz @ 20000 KHz, 92000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 21.783874] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A) [ 21.783881] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A) [ 21.783888] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s) [ 21.783896] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s) [ 21.783905] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A) [ 21.783911] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A) All modules worked right out of the box; Wi-Fi, HDMI (video and sound), Ethernet and IR. Thank you so much, @jock for all the hard work you've put in to this. 0 Quote Link to comment Share on other sites More sharing options...
jock Posted September 20, 2021 Author Share Posted September 20, 2021 @AlwinLub Running weston on legacy kernel could not be a good idea since closed binary blobs probably miss some needed functionality. I suggest you to try the mainline images in the first page or also the mainline image I posted for @Wester_Minskright above The screen tearing can be due to the video being not synchronized to refresh rate: that's normal and hardly we can do anything. If tearing is very heavy with pieces of display moving up and down during redraw, it could be caused by the very same issue @Wester_Minskis having, so I suggest trying also the experimental image I did for him (which has no X11, it has to be installed manually) Soon I will refresh images on first page. 0 Quote Link to comment Share on other sites More sharing options...
AlwinLub Posted September 20, 2021 Share Posted September 20, 2021 I've downloaded the mainline image you've built for Wester_Minsk. I will try it tonight. I've seen people getting rid of screen tearing using weston since some say it's more optimized than X11 ever was (i can't confirm this, but it's worth a try). For a little context on the screen tearing: I'm developing a Kivy app for advanced multimedia features (like Spotify Connect, IPTV playback, remote playback from the box via other devices) all built in a single app. It already is a very complex interface, but it's running great at 60-120 fps, but the tearing throws me off when quickly animating objects. It's using gl4es and it seems hardware accelerated because without gl4es it runs at about 5-20fps. Thanks again for your quick reply and help. I'll keep you posted! 0 Quote Link to comment Share on other sites More sharing options...
jock Posted September 20, 2021 Author Share Posted September 20, 2021 Mainline image contains Lima driver which already has support for opengl. It is good enough to run Kodi, so I don't know how much good will run for your app. 3d games are still quite slow on mali 400/450 and Lima. 0 Quote Link to comment Share on other sites More sharing options...
Ben N Voutour Posted September 21, 2021 Share Posted September 21, 2021 what about recompiling the overclocked dtb file i sent? can it be used in a armbian build? i am trying the most recent build and it is fairly stable still testing ... Cheers 0 Quote Link to comment Share on other sites More sharing options...
AlwinLub Posted September 21, 2021 Share Posted September 21, 2021 I've tested your build on the little HK1 Max, and it works like a charm. I've left it running for about 10 hours without any hiccups. There is however one problem, my Kivy app recognizes the Mali and Mesa libraries, but it will only show a black screen under X, Wayland and headless (sdl2) mode. Weston works like a charm and i can move windows smoothly, and they will fade smoothly upon opening and closing. I've noticed that while using weston, there was no (noticeable) screen tearing. When i try to open the Kivy-app in headless mode (running from the command line directly) it only shows a black screen with a cursor. The app will open without Open GL ES under X11, but i'll only get 2-10 fps because it uses llvm instead of Mali450 as renderer. As i suspect this is an issue with Kivy, i've already posted a topic via the Kivy Discord-channel, and i'm now waiting for a reply. Kivy log: Spoiler user@rk3318-box:~/projecttv/kivy$ python3 ../hw.py [INFO ] [Logger ] Record log in /home/user/.kivy/logs/kivy_21-09-21_44.txt [INFO ] [Kivy ] v2.1.0.dev0 [INFO ] [Kivy ] Installed at "/home/user/projecttv/kivy/kivy/__init__.py" [INFO ] [Python ] v3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110] [INFO ] [Python ] Interpreter at "/usr/bin/python3" [INFO ] [Logger ] Purge log fired. Processing... [INFO ] [Logger ] Purge finished! [INFO ] [Factory ] 189 symbols loaded [DEBUG ] [Cache ] register <kv.resourcefind> with limit=None, timeout=60 [DEBUG ] [Cache ] register <kv.lang> with limit=None, timeout=None [DEBUG ] [Cache ] register <kv.image> with limit=None, timeout=60 [DEBUG ] [Cache ] register <kv.atlas> with limit=None, timeout=None [INFO ] [Image ] Providers: img_tex, img_dds, img_sdl2, img_pil (img_ffpyplayer ignored) [DEBUG ] [Cache ] register <kv.texture> with limit=1000, timeout=60 [DEBUG ] [Cache ] register <kv.shader> with limit=1000, timeout=3600 [INFO ] [Text ] Provider: sdl2 [DEBUG ] [App ] Loading kv </home/user/projecttv/kivy/../my.kv> [DEBUG ] [App ] kv </home/user/projecttv/kivy/../my.kv> not found [INFO ] [Window ] Provider: sdl2 [INFO ] [GL ] Using the "OpenGL ES 2" graphics system [INFO ] [GL ] Backend used <sdl2> [INFO ] [GL ] OpenGL version <b'2.1 Mesa 20.3.5'> [INFO ] [GL ] OpenGL vendor <b'lima'> [INFO ] [GL ] OpenGL renderer <b'Mali450'> [INFO ] [GL ] OpenGL parsed version: 2, 1 [INFO ] [GL ] Shading version <b'1.20'> [INFO ] [GL ] Texture max size <4096> [INFO ] [GL ] Texture max units <16> [DEBUG ] [Shader ] Fragment compiled successfully [DEBUG ] [Shader ] Vertex compiled successfully [DEBUG ] [ImageSDL2 ] Load </home/user/projecttv/kivy/kivy/data/glsl/default.png> [INFO ] [Window ] auto add sdl2 input provider [INFO ] [Window ] virtual keyboard not allowed, single mode, not docked [DEBUG ] [Resource ] add </usr/share/fonts> in path list [DEBUG ] [Resource ] add </usr/share/fonts/truetype> in path list [DEBUG ] [Resource ] add </usr/share/fonts/truetype/dejavu> in path list [DEBUG ] [Resource ] add </usr/share/fonts/X11> in path list [DEBUG ] [Resource ] add </usr/share/fonts/X11/100dpi> in path list [DEBUG ] [Resource ] add </usr/share/fonts/X11/75dpi> in path list [DEBUG ] [Resource ] add </usr/share/fonts/X11/misc> in path list [DEBUG ] [Resource ] add </usr/share/fonts/X11/Type1> in path list [DEBUG ] [Resource ] add </usr/share/fonts/X11/util> in path list [DEBUG ] [Resource ] add </usr/share/fonts/X11/encodings> in path list [DEBUG ] [Resource ] add </usr/share/fonts/X11/encodings/large> in path list [DEBUG ] [Resource ] add </usr/local/share/fonts> in path list [DEBUG ] [Resource ] add </home/user/projecttv/kivy/kivy/data/fonts> in path list [DEBUG ] [Base ] Create provider from mouse [DEBUG ] [Base ] Create provider from probesysfs [DEBUG ] [ProbeSysfs ] using probesysfs! [INFO ] [Base ] Start application main loop [INFO ] [GL ] NPOT texture support is available I've also noticed that while running setup.py, kivy will search for the following files when it detects Mesa: mali_paths = ( '/usr/lib/arm-linux-gnueabihf/libMali.so', '/usr/lib/arm-linux-gnueabihf/mali-egl/libmali.so', '/usr/local/mali-egl/libmali.so') None of these files exist and i don't know if this could be the possible issue. Thanks again for taking your time with me. 0 Quote Link to comment Share on other sites More sharing options...
jock Posted September 21, 2021 Author Share Posted September 21, 2021 @AlwinLub I guess that's a Kivy issue. Actually the opensource driver for mali 400/450 is called lima. It's not up to the performance of the closed source driver, but feature-wise it should be much more standard compliant than the proprietary ARM Mali driver. In fact I can run many opengl/opengles games with Lima that just don't work or work bad with Mali proprietary driver. Performance is not stellar, but they indeed render correctly. The mali_paths python tuple is specifically for the mali proprietary driver, that's why those files are not present in the mainline kernel. You can even manually install the mali driver (and disable the lima driver), but it is something I would not suggest, much better stick to opensource! I'm sorting out some USB3 issue right now for rk3318, once there I would like to update the images with something more recent, like kernel 5.14 and debian bullseye/ubuntu hirsute, so you can also get a much more recent Mesa library with latest fixes and features. In the meantime let's wait for Kivy forum people, I wonder if they already had some experience with Lima driver; in case they are not, it is nice to do some pioneering work 0 Quote Link to comment Share on other sites More sharing options...
jock Posted September 21, 2021 Author Share Posted September 21, 2021 7 hours ago, RetroFan90 said: what about recompiling the overclocked dtb file i sent? can it be used in a armbian build? i am trying the most recent build and it is fairly stable still testing ... Cheers I didn't see any overclocked dtb file here around... however I'm not really fond of overclocking for these chips: they already are scrap parts that somehow reach the nominal frequencies. Some of the rk3318 boxes are also downclocked by manufacturers to 1.1 Ghz to be stable, overclocking is not something I would really love about. It's already hard to get the things together and make the board working stable enough. Adding another big source of instability... hmm I don't think it is a wise idea. 1 Quote Link to comment Share on other sites More sharing options...
AlwinLub Posted September 21, 2021 Share Posted September 21, 2021 1 hour ago, jock said: I didn't see any overclocked dtb file here around... however I'm not really fond of overclocking for these chips: they already are scrap parts that somehow reach the nominal frequencies. Some of the rk3318 boxes are also downclocked by manufacturers to 1.1 Ghz to be stable, overclocking is not something I would really love about. It's already hard to get the things together and make the board working stable enough. Adding another big source of instability... hmm I don't think it is a wise idea. I've got my board running at 1.3 Ghz with the legacy kernel. When pushing the hardware (by compiling or letting the CPU sit at 100%) the temperatures would regularly hit 80-90 degrees celsius, which i'm not very comfy with. With the new image, it's sitting at 1Ghz (via armbian-config) with max 70-75 degrees under heavy load. I could install a bigger heatsink, but as you said, the RK3318 is a sketchy chip. 0 Quote Link to comment Share on other sites More sharing options...
AlwinLub Posted September 21, 2021 Share Posted September 21, 2021 3 hours ago, jock said: @AlwinLub I guess that's a Kivy issue. Actually the opensource driver for mali 400/450 is called lima. It's not up to the performance of the closed source driver, but feature-wise it should be much more standard compliant than the proprietary ARM Mali driver. In fact I can run many opengl/opengles games with Lima that just don't work or work bad with Mali proprietary driver. Performance is not stellar, but they indeed render correctly. The mali_paths python tuple is specifically for the mali proprietary driver, that's why those files are not present in the mainline kernel. You can even manually install the mali driver (and disable the lima driver), but it is something I would not suggest, much better stick to opensource! I'm sorting out some USB3 issue right now for rk3318, once there I would like to update the images with something more recent, like kernel 5.14 and debian bullseye/ubuntu hirsute, so you can also get a much more recent Mesa library with latest fixes and features. In the meantime let's wait for Kivy forum people, I wonder if they already had some experience with Lima driver; in case they are not, it is nice to do some pioneering work I did some research on how to install the proprietary drivers, but it's quite hard to get in to for developers like me who are more used to the high-level stuff (python, lamp stack). There is info out there but it's too complicated for my simple brain. I've also tried running the kivy build script with and without OpenGL ES, Wayland and X11 without any improvement. I've even tried using OpenGL Kivy with GL4ES without any result (it doesn't get recognized by Kivy). I would like to help out wherever i can because i feel projects like Armbian are simply quite amazing. Thanks again for your help and your awesome builds, i'm really looking forward to using the updated images with the newer Mesa library and crossing my fingers somebody smarter than me comes up with a solution, or that the updated images will 'just work' with Kivy. Quote Mainline image contains Lima driver which already has support for opengl. It is good enough to run Kodi, so I don't know how much good will run for your app. 3d games are still quite slow on mali 400/450 and Lima. On the Legacy kernel images with GL4ES, it runs at 60-80 fps without any (noticeable) dips. Kivy exclusively uses OpenGL/OpenGL ES to render the interface. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.