Search the Community

Hi, I have an Rock64 v2.0 and after update to trunk 24.8.0-trunk.369 to 24.8.0-trunk.399 the OS stop to starting process with this kernel error: U-Boot 2022.07-armbian (Mar 14 2024 - 00:34:55 +0000) Model: Pine64 Rock64 DRAM: 4 GiB PMIC: RK8050 (on=0x40, off=0x00) Core: 229 devices, 25 uclasses, devicetree: separate MMC: mmc@ff500000: 1, mmc@ff520000: 0 Loading Environment from MMC... Card did not respond to voltage select! : -110 *** Warning - No block device, using default environment In: serial@ff130000 Out: serial@ff130000 Err: serial@ff130000 Model: Pine64 Rock64 Net: eth0: ethernet@ff540000 Hit any key to stop autoboot: 0 Card did not respond to voltage select! : -110 switch to partitions #0, OK mmc0(part 0) is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3920 bytes read in 4 ms (957 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 0:1 166 bytes read in 4 ms (40 KiB/s) 18182239 bytes read in 408 ms (42.5 MiB/s) 30030336 bytes read in 671 ms (42.7 MiB/s) 53582 bytes read in 13 ms (3.9 MiB/s) 2825 bytes read in 13 ms (211.9 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Trying kaslrseed command... Info: Unknown command can be safely ignored since kaslrseed does not apply to all boards. Unknown command 'kaslrseed' - try 'help' Moving Image from 0x2080000 to 0x2200000, end=3f40000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 18182175 Bytes = 17.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to fbdca000, end fcf2101f ... OK Loading Device Tree to 00000000fbd54000, end 00000000fbdc9fff ... OK Starting kernel ... efi_free_pool: illegal free 0x00000000fbf23040 efi_free_pool: illegal free 0x00000000fbf20040 [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] Linux version 6.6.39-current-rockchip64 (armbian@next) (aarch64-linux-gnu-gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #1 SMP PR EEMPT Thu Jul 11 10:49:22 UTC 2024 [ 0.000000] Machine model: Pine64 Rock64 [ 0.000000] efi: UEFI not found. [ 0.000000] NUMA: No NUMA configuration found [ 0.000000] NUMA: Faking a node at [mem 0x0000000000200000-0x00000000feffffff] [ 0.000000] NUMA: NODE_DATA [mem 0xfe7b9980-0xfe7bbfff] [ 0.000000] Zone ranges: [ 0.000000] DMA [mem 0x0000000000200000-0x00000000feffffff] [ 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-0x00000000feffffff] [ 0.000000] Initmem setup node 0 [mem 0x0000000000200000-0x00000000feffffff] [ 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] cma: Reserved 128 MiB at 0x00000000efc00000 on node -1 [ 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.2 [ 0.000000] percpu: Embedded 31 pages/cpu s88296 r8192 d30488 u126976 [ 0.000000] Detected VIPT I-cache on CPU0 [ 0.000000] CPU features: detected: ARM erratum 845719 [ 0.000000] alternatives: applying boot alternatives [ 0.000000] Kernel command line: root=UUID=b7daa1a9-9cd9-4cf7-8de6-79f3a229a5cb rootwait rootfstype=ext4 splash=verbose console=ttyS2,1500000 console=tty1 consoleblank=0 logleve l=7 ubootpart=a08d4006-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1 [ 0.000000] Unknown kernel command line parameters "splash=verbose ubootpart=a08d4006-01 cgroup_enable=memory cgroup_memory=1", will be passed to user space. [ 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] Fallback order for Node 0: 0 [ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1027656 [ 0.000000] Policy zone: DMA [ 0.000000] mem auto-init: stack:off, heap alloc:on, heap free:off [ 0.000000] software IO TLB: SWIOTLB bounce buffer size adjusted to 3MB [ 0.000000] software IO TLB: area num 4. [ 0.000000] software IO TLB: mapped [mem 0x00000000fdd27000-0x00000000fe127000] (4MB) [ 0.000000] Memory: 3912228K/4175872K available (16960K kernel code, 2318K rwdata, 5244K rodata, 4672K init, 604K bss, 132572K reserved, 131072K 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] Root IRQ handler: gic_handle_irq [ 0.000000] GIC: Using split EOI/Deactivate mode [ 0.000000] rcu: srcu_init: Setting srcu_struct sizes based on contention. [ 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.000835] Console: colour dummy device 80x25 [ 0.000854] printk: console [tty1] enabled [ 0.001936] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000) [ 0.001984] pid_max: default: 32768 minimum: 301 [ 0.002127] LSM: initializing lsm=capability,yama,apparmor,integrity [ 0.002199] Yama: becoming mindful. [ 0.002350] AppArmor: AppArmor initialized [ 0.002523] Mount-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.002580] Mountpoint-cache hash table entries: 8192 (order: 4, 65536 bytes, linear) [ 0.005755] RCU Tasks: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1. [ 0.005952] RCU Tasks Trace: Setting shift to 2 and lim to 1 rcu_task_cb_adjust=1. [ 0.006364] rcu: Hierarchical SRCU implementation. [ 0.006392] rcu: Max phase no-delay instances is 1000. [ 0.009573] EFI services will not be available. [ 0.010200] smp: Bringing up secondary CPUs ... [ 0.011185] Detected VIPT I-cache on CPU1 [ 0.011327] CPU1: Booted secondary processor 0x0000000001 [0x410fd034] [ 0.012534] Detected VIPT I-cache on CPU2 [ 0.012677] CPU2: Booted secondary processor 0x0000000002 [0x410fd034] [ 0.013799] Detected VIPT I-cache on CPU3 [ 0.013940] CPU3: Booted secondary processor 0x0000000003 [0x410fd034] [ 0.014103] smp: Brought up 1 node, 4 CPUs [ 0.014234] SMP: Total of 4 processors activated. [ 0.014258] CPU features: detected: 32-bit EL0 Support [ 0.014279] CPU features: detected: 32-bit EL1 Support [ 0.014304] CPU features: detected: CRC32 instructions [ 0.014447] CPU: All CPU(s) started at EL2 [ 0.014480] alternatives: applying system-wide alternatives [ 0.017940] devtmpfs: initialized [ 0.033786] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns [ 0.033874] futex hash table entries: 1024 (order: 4, 65536 bytes, linear) [ 0.039538] pinctrl core: initialized pinctrl subsystem [ 0.040410] DMI not present or invalid. [ 0.041528] NET: Registered PF_NETLINK/PF_ROUTE protocol family [ 0.043945] DMA: preallocated 2048 KiB GFP_KERNEL pool for atomic allocations [ 0.045140] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations [ 0.046206] DMA: preallocated 2048 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations [ 0.046352] audit: initializing netlink subsys (disabled) [ 0.046725] audit: type=2000 audit(0.044:1): state=initialized audit_enabled=0 res=1 [ 0.047916] thermal_sys: Registered thermal governor 'fair_share' [ 0.047929] thermal_sys: Registered thermal governor 'bang_bang' [ 0.047960] thermal_sys: Registered thermal governor 'step_wise' [ 0.047984] thermal_sys: Registered thermal governor 'user_space' [ 0.048133] cpuidle: using governor menu [ 0.048709] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers. [ 0.048904] ASID allocator initialised with 65536 entries [ 0.050414] Serial: AMBA PL011 UART driver [ 0.061914] platform ff370000.vop: Fixed dependency cycle(s) with /hdmi@ff3c0000 [ 0.062087] platform ff3c0000.hdmi: Fixed dependency cycle(s) with /vop@ff370000 [ 0.074197] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.074734] rockchip-gpio ff210000.gpio: probed /pinctrl/gpio@ff210000 [ 0.075392] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.075851] rockchip-gpio ff220000.gpio: probed /pinctrl/gpio@ff220000 [ 0.076551] gpio gpiochip2: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.077014] rockchip-gpio ff230000.gpio: probed /pinctrl/gpio@ff230000 [ 0.077543] gpio gpiochip3: Static allocation of GPIO base is deprecated, use dynamic allocation. [ 0.077970] rockchip-gpio ff240000.gpio: probed /pinctrl/gpio@ff240000 [ 0.082525] Modules: 25280 pages in range for non-PLT usage [ 0.082543] Modules: 516800 pages in range for PLT usage [ 0.083824] HugeTLB: registered 1.00 GiB page size, pre-allocated 0 pages [ 0.083887] HugeTLB: 0 KiB vmemmap can be freed for a 1.00 GiB page [ 0.083915] HugeTLB: registered 32.0 MiB page size, pre-allocated 0 pages [ 0.083941] HugeTLB: 0 KiB vmemmap can be freed for a 32.0 MiB page [ 0.083967] HugeTLB: registered 2.00 MiB page size, pre-allocated 0 pages [ 0.083994] HugeTLB: 0 KiB vmemmap can be freed for a 2.00 MiB page [ 0.084020] HugeTLB: registered 64.0 KiB page size, pre-allocated 0 pages [ 0.084045] HugeTLB: 0 KiB vmemmap can be freed for a 64.0 KiB page [ 0.085808] cryptd: max_cpu_qlen set to 1000 [ 0.152413] raid6: neonx8 gen() 1067 MB/s [ 0.220525] raid6: neonx4 gen() 1099 MB/s [ 0.288629] raid6: neonx2 gen() 1039 MB/s [ 0.356741] raid6: neonx1 gen() 888 MB/s [ 0.424859] raid6: int64x8 gen() 683 MB/s [ 0.492957] raid6: int64x4 gen() 800 MB/s [ 0.561054] raid6: int64x2 gen() 698 MB/s [ 0.629157] raid6: int64x1 gen() 516 MB/s [ 0.629182] raid6: using algorithm neonx4 gen() 1099 MB/s [ 0.697248] raid6: .... xor() 781 MB/s, rmw enabled [ 0.697275] raid6: using neon recovery algorithm [ 0.698389] iommu: Default domain type: Translated [ 0.698433] iommu: DMA domain TLB invalidation policy: strict mode [ 0.699184] SCSI subsystem initialized [ 0.699916] usbcore: registered new interface driver usbfs [ 0.699999] usbcore: registered new interface driver hub [ 0.700079] usbcore: registered new device driver usb [ 0.700685] pps_core: LinuxPPS API ver. 1 registered [ 0.700713] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it> [ 0.700770] PTP clock support registered [ 0.701024] EDAC MC: Ver: 3.0.0 [ 0.701981] scmi_core: SCMI protocol bus registered [ 0.703830] NetLabel: Initializing [ 0.703869] NetLabel: domain hash size = 128 [ 0.703890] NetLabel: protocols = UNLABELED CIPSOv4 CALIPSO [ 0.704022] NetLabel: unlabeled traffic allowed by default [ 0.704310] vgaarb: loaded [ 0.705173] clocksource: Switched to clocksource arch_sys_counter [ 0.708499] VFS: Disk quotas dquot_6.6.0 [ 0.708601] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [ 0.709626] AppArmor: AppArmor Filesystem Enabled [ 0.722601] NET: Registered PF_INET protocol family [ 0.722971] IP idents hash table entries: 65536 (order: 7, 524288 bytes, linear) [ 0.729115] tcp_listen_portaddr_hash hash table entries: 2048 (order: 3, 32768 bytes, linear) [ 0.729395] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear) [ 0.729521] TCP established hash table entries: 32768 (order: 6, 262144 bytes, linear) [ 0.730191] TCP bind hash table entries: 32768 (order: 8, 1048576 bytes, linear) [ 0.731571] TCP: Hash tables configured (established 32768 bind 32768) [ 0.731809] UDP hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.732010] UDP-Lite hash table entries: 2048 (order: 4, 65536 bytes, linear) [ 0.732467] NET: Registered PF_UNIX/PF_LOCAL protocol family [ 0.732550] NET: Registered PF_XDP protocol family [ 0.732590] PCI: CLS 0 bytes, default 64 [ 0.732960] Trying to unpack rootfs image as initramfs... [ 0.737530] kvm [1]: IPA Size Limit: 40 bits [ 0.739707] kvm [1]: vgic interrupt IRQ9 [ 0.739788] kvm [1]: Hyp mode initialized successfully [ 0.743045] Initialise system trusted keyrings [ 0.743155] Key type blacklist registered [ 0.743544] workingset: timestamp_bits=44 max_order=20 bucket_order=0 [ 0.743657] zbud: loaded [ 0.744577] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.745289] fuse: init (API version 7.39) [ 0.747697] integrity: Platform Keyring initialized [ 0.805623] jitterentropy: Initialization failed with host not compliant with requirements: 9 [ 0.805691] xor: measuring software checksum speed [ 0.813564] 8regs : 1261 MB/sec [ 0.821435] 32regs : 1261 MB/sec [ 0.829961] arm64_neon : 1162 MB/sec [ 0.829996] xor: using function: 32regs (1261 MB/sec) [ 0.830031] Key type asymmetric registered [ 0.830054] Asymmetric key parser 'x509' registered [ 0.830218] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [ 0.830553] io scheduler mq-deadline registered [ 0.830586] io scheduler kyber registered [ 0.830672] io scheduler bfq registered [ 0.840782] dma-pl330 ff1f0000.dma-controller: Loaded driver for PL330 DMAC-241330 [ 0.840842] dma-pl330 ff1f0000.dma-controller: DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16 [ 0.843541] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled [ 0.850416] printk: console [ttyS2] disabled [ 0.851142] ff130000.serial: ttyS2 at MMIO 0xff130000 (irq = 21, base_baud = 1500000) is a 16550A [ 0.851281] printk: console [ttyS2] enabled [ 0.953465] Serial: AMBA driver [ 0.957675] rockchip-vop ff370000.vop: Adding to iommu group 2 [ 0.975135] loop: module loaded [ 0.981356] spi-nor spi0.0: unrecognized JEDEC id bytes: 00 00 00 00 00 00 [ 0.984299] tun: Universal TUN/TAP device driver, 1.6 [ 0.985984] thunder_xcv, ver 1.0 [ 0.986374] thunder_bgx, ver 1.0 [ 0.986723] nicpf, ver 1.0 [ 0.987631] e1000e: Intel(R) PRO/1000 Network Driver [ 0.988097] e1000e: Copyright(c) 1999 - 2015 Intel Corporation. [ 0.988689] igb: Intel(R) Gigabit Ethernet Network Driver [ 0.989218] igb: Copyright (c) 2007-2014 Intel Corporation. [ 0.989789] igbvf: Intel(R) Gigabit Virtual Function Network Driver [ 0.990364] igbvf: Copyright (c) 2009 - 2012 Intel Corporation. [ 0.991141] sky2: driver version 1.30 [ 0.994041] dwc2 ff580000.usb: supply vusb_d not found, using dummy regulator [ 0.994949] dwc2 ff580000.usb: supply vusb_a not found, using dummy regulator [ 1.008604] dwc2 ff580000.usb: DWC OTG Controller [ 1.009105] dwc2 ff580000.usb: new USB bus registered, assigned bus number 1 [ 1.009836] dwc2 ff580000.usb: irq 28, io mem 0xff580000 [ 1.010633] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [ 1.011401] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.012065] usb usb1: Product: DWC OTG Controller [ 1.012503] usb usb1: Manufacturer: Linux 6.6.39-current-rockchip64 dwc2_hsotg [ 1.013218] usb usb1: SerialNumber: ff580000.usb [ 1.014622] hub 1-0:1.0: USB hub found [ 1.015048] hub 1-0:1.0: 1 port detected [ 1.017892] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 1.018453] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2 [ 1.019347] xhci-hcd xhci-hcd.0.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000008002000010 [ 1.019797] ehci-platform ff5c0000.usb: EHCI Host Controller [ 1.019824] ohci-platform ff5d0000.usb: Generic Platform OHCI controller [ 1.019874] ohci-platform ff5d0000.usb: new USB bus registered, assigned bus number 3 [ 1.020051] ohci-platform ff5d0000.usb: irq 30, io mem 0xff5d0000 [ 1.020253] xhci-hcd xhci-hcd.0.auto: irq 27, io mem 0xff600000 [ 1.020771] ehci-platform ff5c0000.usb: new USB bus registered, assigned bus number 4 [ 1.021659] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller [ 1.022275] ehci-platform ff5c0000.usb: irq 29, io mem 0xff5c0000 [ 1.022662] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 5 [ 1.025873] xhci-hcd xhci-hcd.0.auto: Host supports USB 3.0 SuperSpeed [ 1.026738] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [ 1.027505] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.028170] usb usb2: Product: xHCI Host Controller [ 1.028621] usb usb2: Manufacturer: Linux 6.6.39-current-rockchip64 xhci-hcd [ 1.029302] usb usb2: SerialNumber: xhci-hcd.0.auto [ 1.030685] hub 2-0:1.0: USB hub found [ 1.031115] hub 2-0:1.0: 1 port detected [ 1.032120] usb usb5: We don't know the algorithms for LPM for this host, disabling LPM. [ 1.033063] usb usb5: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.06 [ 1.033861] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.034530] usb usb5: Product: xHCI Host Controller [ 1.034983] usb usb5: Manufacturer: Linux 6.6.39-current-rockchip64 xhci-hcd [ 1.035627] usb usb5: SerialNumber: xhci-hcd.0.auto [ 1.037038] hub 5-0:1.0: USB hub found [ 1.037495] hub 5-0:1.0: 1 port detected [ 1.038649] usbcore: registered new interface driver usb-storage [ 1.041203] ehci-platform ff5c0000.usb: USB 2.0 started, EHCI 1.00 [ 1.041308] mousedev: PS/2 mouse device common for all mice [ 1.042168] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.06 [ 1.043060] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.043337] i2c_dev: i2c /dev entries driver [ 1.043729] usb usb4: Product: EHCI Host Controller [ 1.044571] usb usb4: Manufacturer: Linux 6.6.39-current-rockchip64 ehci_hcd [ 1.045263] usb usb4: SerialNumber: ff5c0000.usb [ 1.046748] i2c 1-0018: Fixed dependency cycle(s) with /i2c@ff160000/pmic@18/regulators/DCDC_REG4 [ 1.047847] hub 4-0:1.0: USB hub found [ 1.048304] hub 4-0:1.0: 1 port detected [ 1.055997] rk808-regulator rk808-regulator.2.auto: there is no dvs0 gpio [ 1.056671] rk808-regulator rk808-regulator.2.auto: there is no dvs1 gpio [ 1.057327] rk808-regulator rk808-regulator.2.auto: max buck steps per change: 8 [ 1.081519] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 6.06 [ 1.082306] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.082973] usb usb3: Product: Generic Platform OHCI controller [ 1.083518] usb usb3: Manufacturer: Linux 6.6.39-current-rockchip64 ohci_hcd [ 1.084162] usb usb3: SerialNumber: ff5d0000.usb [ 1.085746] hub 3-0:1.0: USB hub found [ 1.086125] rk808-rtc rk808-rtc.4.auto: registered as rtc0 [ 1.086209] hub 3-0:1.0: 1 port detected [ 1.088464] rk808-rtc rk808-rtc.4.auto: setting system clock to 2016-01-21T08:50:08 UTC (1453366208) [ 1.091461] input: rk805 pwrkey as /devices/platform/ff160000.i2c/i2c-1/1-0018/rk805-pwrkey.6.auto/input/input0 [ 1.097547] dw_wdt ff1a0000.watchdog: No valid TOPs array specified [ 1.101755] sdhci: Secure Digital Host Controller Interface driver [ 1.102345] sdhci: Copyright(c) Pierre Ossman [ 1.102804] Synopsys Designware Multimedia Card Interface Driver [ 1.104203] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.105241] dwmmc_rockchip ff520000.mmc: IDMAC supports 32-bit address mode. [ 1.105955] dwmmc_rockchip ff520000.mmc: Using internal DMA controller. [ 1.106578] dwmmc_rockchip ff520000.mmc: Version ID is 270a [ 1.107167] dwmmc_rockchip ff520000.mmc: DW MMC controller at irq 43,32 bit host data width,256 deep fifo [ 1.109379] mmc_host mmc1: card is non-removable. [ 1.110231] ledtrig-cpu: registered to indicate activity on CPUs [ 1.111561] SMCCC: SOC_ID: ARCH_SOC_ID not implemented, skipping .... [ 1.112394] hid: raw HID events driver (C) Jiri Kosina [ 1.113029] usbcore: registered new interface driver usbhid [ 1.113587] usbhid: USB HID core driver [ 1.117672] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available [ 1.120844] drop_monitor: Initializing network drop monitor service [ 1.121412] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 1.122110] NET: Registered PF_INET6 protocol family [ 2.085361] mmc1: switch to bus width 8 failed [ 2.093072] mmc1: mmc_select_hs200 failed, error -110 [ 2.093656] mmc1: error -110 whilst initialising MMC card [ 2.117348] mmc_host mmc1: Bus speed (slot 0) = 300000Hz (slot req 300000Hz, actual 300000HZ div = 0) [ 2.344406] Freeing initrd memory: 17756K [ 2.412003] Segment Routing with IPv6 [ 2.412489] In-situ OAM (IOAM) with IPv6 [ 2.412998] NET: Registered PF_PACKET protocol family [ 2.413862] 8021q: 802.1Q VLAN Support v1.8 [ 2.414357] Key type dns_resolver registered [ 2.432128] registered taskstats version 1 [ 2.432767] Loading compiled-in X.509 certificates [ 2.450926] zswap: loaded using pool zstd/z3fold [ 2.472299] Key type .fscrypt registered [ 2.472691] Key type fscrypt-provisioning registered [ 2.476799] Btrfs loaded, zoned=yes, fsverity=yes [ 2.477509] Key type encrypted registered [ 2.477901] AppArmor: AppArmor sha1 policy hashing enabled [ 2.511378] rockchip-drm display-subsystem: bound ff370000.vop (ops 0xffff8000811d64a0) [ 2.512225] dwhdmi-rockchip ff3c0000.hdmi: supply avdd-0v9 not found, using dummy regulator [ 2.513259] dwhdmi-rockchip ff3c0000.hdmi: supply avdd-1v8 not found, using dummy regulator [ 2.514437] dwhdmi-rockchip ff3c0000.hdmi: Detected HDMI TX controller v2.11a with HDCP (inno_dw_hdmi_phy2) [ 2.516473] dwhdmi-rockchip ff3c0000.hdmi: registered DesignWare HDMI I2C bus driver [ 2.517758] rockchip-drm display-subsystem: bound ff3c0000.hdmi (ops 0xffff8000811da6a8) [ 2.519710] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0 [ 2.520588] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 2.521437] rockchip-drm display-subsystem: [drm] Cannot find any crtc or sizes [ 2.523570] WCN: marlin_init entry! [ 2.524419] of_cfs_init [ 2.524419] dwmmc_rockchip ff500000.mmc: IDMAC supports 32-bit address mode. [ 2.524462] dwmmc_rockchip ff500000.mmc: Using internal DMA controller. [ 2.524703] of_cfs_init: OK [ 2.525350] dwmmc_rockchip ff500000.mmc: Version ID is 270a [ 2.525438] dwmmc_rockchip ff500000.mmc: DW MMC controller at irq 50,32 bit host data width,256 deep fifo [ 2.526169] clk: Disabling unused clocks [ 2.537224] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0) [ 2.551678] Freeing unused kernel memory: 4672K [ 2.552307] Run /init as init process [ 3.081702] mmc1: switch to bus width 8 failed [ 3.091425] mmc1: mmc_select_hs200 failed, error -110 [ 3.091934] mmc1: error -110 whilst initialising MMC card [ 3.117307] mmc_host mmc1: Bus speed (slot 0) = 200000Hz (slot req 200000Hz, actual 200000HZ div = 0) [ 3.336405] gpio-syscon ff100000.syscon:gpio: can't read the data register offset! [ 3.409089] rk_gmac-dwmac ff540000.ethernet: IRQ eth_wake_irq not found [ 3.409793] rk_gmac-dwmac ff540000.ethernet: IRQ eth_lpi not found [ 3.410514] rk_gmac-dwmac ff540000.ethernet: PTP uses main clock [ 3.411385] rk_gmac-dwmac ff540000.ethernet: clock input or output? (input). [ 3.412040] rk_gmac-dwmac ff540000.ethernet: TX delay(0x24). [ 3.412564] rk_gmac-dwmac ff540000.ethernet: RX delay(0x18). [ 3.413098] rk_gmac-dwmac ff540000.ethernet: integrated PHY? (no). [ 3.413766] rk_gmac-dwmac ff540000.ethernet: clock input from PHY [ 3.419358] rk_gmac-dwmac ff540000.ethernet: init for RGMII [ 3.420317] rk_gmac-dwmac ff540000.ethernet: User ID: 0x10, Synopsys ID: 0x35 [ 3.421011] rk_gmac-dwmac ff540000.ethernet: DWMAC1000 [ 3.421556] rk_gmac-dwmac ff540000.ethernet: DMA HW capability register supported [ 3.422260] rk_gmac-dwmac ff540000.ethernet: RX Checksum Offload Engine supported [ 3.422951] rk_gmac-dwmac ff540000.ethernet: COE Type 2 [ 3.423440] rk_gmac-dwmac ff540000.ethernet: Wake-Up On Lan supported [ 3.424165] rk_gmac-dwmac ff540000.ethernet: Normal descriptors [ 3.424729] rk_gmac-dwmac ff540000.ethernet: Ring mode enabled [ 3.425354] rk_gmac-dwmac ff540000.ethernet: Enable RX Mitigation via HW Watchdog Timer [ 3.637295] RTL8211F Gigabit Ethernet stmmac-0:00: attached PHY driver (mii_bus:phy_addr=stmmac-0:00, irq=POLL) [ 3.638258] RTL8211F Gigabit Ethernet stmmac-0:01: attached PHY driver (mii_bus:phy_addr=stmmac-0:01, irq=POLL) [ 3.725500] rk_gmac-dwmac ff540000.ethernet end0: renamed from eth0 [ 3.887873] async_tx: api initialized (async) [ 4.101386] mmc1: switch to bus width 8 failed [ 4.115376] mmc1: mmc_select_hs200 failed, error -110 [ 4.115867] mmc1: error -110 whilst initialising MMC card [ 4.141358] mmc_host mmc1: Bus speed (slot 0) = 100000Hz (slot req 100000Hz, actual 100000HZ div = 0) [ 5.189315] mmc1: switch to bus width 8 failed [ 5.216118] mmc1: mmc_select_hs200 failed, error -110 [ 5.216625] mmc1: error -110 whilst initialising MMC card [ 5.230517] mmc1: Failed to initialize a non-removable card [ 8.574559] rockchip-pm-domain ff100000.syscon:power-controller: failed to get ack on domain 'hevc', val=0x88220 I try to searchr on web similar problem and I found this 2 threads that try to fix problem: https://forum.pine64.org/showthread.php?tid=19356 https://archlinuxarm.org/forum/viewtopic.php?f=65&t=16981 The problem is an correction to emmc device driver for Rock64. This is the solution: pinctrl: rockchip: correct RK3328 iomux width flag for GPIO2-B pins @clee Can you add this fix for Rock64? Thanks

Hi all, I try to use a SATA/SSD connected via USB instead of a SD Card or eMMC, but it doesnt boot at all. I tried to use U-Boot for Rock64 on SPI: Release 2017.09-rockchip-ayufan-1065-g95f6152134 · ayufan-rock64/linux-u-boot · GitHub (flashed to SD Card and successfully booted on Rock64), but without success. I flashed the same Image to SD Card, eMMC and SSD. Booting from SD Card and eMMC works without problems, SSD is visible from Rock64, correct UUID is written in "armbianEnv.txt" on SSD. But nevertheless - it doesn´t boot. I use the Rock64 for my Home Automation and want to use the SSD because it should be more stable long term as a eMMC or SD Card. Kind Regards Martin

Hi, First of all I am posting in Rockpro64 section because I am not seeing one for Rock64 What I need is like the title says: use OTG USB port as regular USB 2.0 port (so I can connect another device). Currently I need the 2 USB 2.0 ports (USB 3.0 is already being used with a external disk). Is this possible? OS version: Armbian 24.2.1 Jammy - Linux 6.6.16-current-rockchip64 Thanks in advance.

Hi team, This is not exactly Armbian related, however I hope to find some help here, also it can be useful for someone else in custom board development (my case). For testing I have Olimex RK3328-SOM-EVB and RK3318 TV box boards. They both behave the same way. As summary I'm trying to boot Linux using the Bootrom and USB OTG only, in other words without any external boot NVM attached. To archive this I build U-Boot SPL (u-boot-spl.bin), which support SDP protocol via USB OTG. For SDP file transfer I'm using imx_usb tool. The binaries used in the process are: rk3328_uboot_v1.19.250.bin - consists of u-boot-tpl.bin and u-boot-spl.bin created with boot_merger tool. u-boot.itb - FIT image (ATF, u-boot.bin and dtb), mainline U-Boot v2023.10 kernel.itb - FIT image (Image.gz and dtb), mainline kernel v6.1 I also prepared a proper sdcard image, from above binaries and wrote it to an SD card. My test setup consists of two booting paths, note the binaries in both are the same: With boot path 1, u-boot-tpl, u-boot-spl loaded via USB OTG: RK3328 in Mask ROM mode, SD card removed rkdeveloptool db rk3328_uboot_v1.19.250.bin insert SD card imx_usb - u-boot.itb boot kernel from U-boot prompt: setenv bootargs root=/dev/mmcblk1p2 console=ttyS2,1500000 earlycon ro rootwait; mmc dev 1; load mmc 1 0x800800 kernel.itb; bootm 0x800800 With boot path 2, u-boot-tpl, u-boot-spl loaded from SD card: insert SD card, power on (or reset) the board imx_usb - u-boot.itb boot kernel from U-boot prompt: setenv bootargs root=/dev/mmcblk1p2 console=ttyS2,1500000 earlycon ro rootwait; mmc dev 1; load mmc 1 0x800800 kernel.itb; bootm 0x800800 The overall description of two boot paths is as follow: boot path 1: rk3328_uboot_v1.19.250.bin (bootrom via OTG)-+ +- -> uboot.itb (imx_usb) -> kernel.itb (from SD card) boot path 2: rk3328_uboot_v1.19.250.bin (bootrom via SD) -+ The issues I have: When the SoC is booted through boot path 1 the kernel hangs soon after starting ... [ 0.016620] smp: Bringing up secondary CPUs ... If boot path 2 is used - The kernel boots and everything works as expected. The Bootrom in RK3318/28 first tries eMMC, SPI NOR, SPI NAND and SD card, if those boot devices failed then USB OTG is used for booting. Since the only difference between two boot paths is the way the TPL/SPL is loaded from the Bootrom - USB OTG or SD card, the only logical explanation I can think of is that there is some "leftover" in SoC state after OTG boot, which causes the kernel to hang. Does anyone have any idea how I can narrow down and eventually find the cause for this issue?

Hi all, I have a Rock64, running ioBroker, and want to update the npm/nodejs to update all the adapters - mainly MQTT with which I have some problems. Trying to run apt update or iob nodejs-update, I run into: The repository 'http://apt.armbian.com stretch Release' does no longer have a Release file. in several versions. Can you help me? Sources.list is (changed, this works now) deb-src [trusted=yes] http://archive.debian.org/debian stretch main non-free contrib deb [trusted=yes] http://archive.debian.org/debian-security stretch/updates main non-free contrib Armbian.list is: deb https://apt.armbian.com stretch main stretch-utils stretch-desktop With hopful regards Martin

Hey, I am working with Weston-7 alongside Lima driver with MESA v19 to render using MALI450 on the display but it isn't rendering it properly. I thought the issue is with MESA so I upgraded it to v20 and applied required patches for Weston-7, but still the result is same and there is no improvement. I have attached the video link below of Weston terminal on the display for reference. Weston render Any idea what I might be missing here?

I tried to update my odroidm1 to 23.11.2 (from 23.8.1) by fresh install using Armbian_23.11.2_Odroidm1_bookworm_current_6.1.68 flashed to sdcard but when booting the device (holding recovery button) I see "Gave up waiting for root file system device." The same issue when using the other CLI images flashed to sdcard. Any idea how to fix this? When mounting the sdcard from a ubuntu system the uuid seem to match and the sdcard is mountable.

I have owned numerous Raspberry Pi boards over the years, and I have always have ran Kodi on one of them. For years I have been wanting to upgrade my RPi 3 as it cannot play any of my H.265/HEVC videos. With all the shortages, and how old the Raspberry Pi 4 is getting, I made a rather spontaneous purchase for this Orange Pi 4 LTS board. Getting it all setup is easy enough, but of course, the video (even with H.264!) nearly maxes all 6 cores and the video is chunky as it's just doing everything without any video acceleration. Even navigating the menu seems slow and delayed. I have been scouring these forums and other sources for about 12 hours now, and I am still unsure which route to go. Just as a test, I ran Kodi as root and it was much smoother in the menu system and seemed to do H.264 (in software of course, so it was working really hard). But broke Pulseaudio, as Pulse is hardcoded to not accept connections from root when it's not setup as a system-wide service. Anyway, that's not an option. Kodi doesn't need to, and shouldn't run as root. I was very excited, then extremely let down when I found this post: A custom image with custom repositories? Plus, I don't want X11 or Wayland plus a window manager, I don't need it! Either way, it *seems* to be tied to a completely different chipset. I've been up all night working on this, and I am starting to go delirious, so any help would be appreciated.

Hi I had bought a NanoPi R4S with the goal of installing IPfire. Unfortunately that was too complicated for me https://wiki.ipfire.org/hardware/arm/friendlyelec/nanopi-r4s I had now installed Armbian and NextCloud and I am very satisfied. In about 10 hours I had "my own cloud". Therefore a very warm and big thank you to the Armbian developers. Only thanks to the Armbian, I can look over the Raspberry horizon. I wish you a very pleasant week Best regards

Hi, I've booted the board from SD card with the latest image and I'm trying to configure the board to boot from MTD and use USB drive as a system drive. When running armbian-config (or armbian-install, or nand-sata-install), it fails with error "SPI u-boot image not found!". It looks like the bootloader package is missing the /usr/lib/linux-u-boot-current-rock64_23.02.2_arm64/rkspi_loader.img. Can I find it anywhere? Dmitry

I get Kernel Panics when i do a reboot of the device with the reboot command. I don't get any Panics, when doing a normal boot of the System by powering it. The Panics don't occur on Manjaro. Updating the kernel to 6.1, did nothing for me and the Panic messages are always different and occur at different points of the Boot process. The System runs stable for days, when it boots. I don't have any clues what is going on hear, but i it seems that the device and sdcards aren't broken.

Hello community, I have just been successful building my own image of Ubuntu focal + preempt_rt (kernel 5.15.76-rt53) for my Rock64 board for the first time (a bit of additional background at the end of my post). Exciting! I had a few hiccups along the way, and I need to figure out a few more things. So far I'm happy and impressed with the project. However, given I want to share my work (and the resulting image(s)) I would like to ask for some pointers on what is the best way to go in regards of forking armbian/build and the changes I found myself doing. I have added my kernel compilation flags to config/kernel/linux-rockchip64-current.config but I feel like maybe I should create a new file, something like 'linux-rockchip64-current-rt.config' but I do not know if the compile.sh will find it (or how to make it find it) if I do so. What would be the best way to go about it? I added the PREEMPT_RT patches to patch/kernel/rockchip64-current , but again, there should probably be a folder for RT maybe? (I wonder how to make compile.sh find it). I created userpatches/lib.config with the content 'KERNELBRANCH='tag:v5.15.76'' to use the latest PREEMPT_RT compatible kernel, ideally this could be scripted to use the latest closest to 'current', which also would avoid needing to modify the patch/kernel/BOARD_NAME folder. I also needed to remove the box64 package cause it would stop building my image (GPG key outdated?) is this package necessary for a minimal installation? I don't think I found I needed it so far. I left a comment about it in this github issue: https://github.com/armbian/build/issues/3968#issuecomment-1310390875 I needed to add a couple of additional cmdline flags, I edited by hand (after booting the board) the resulting /boot/armbianEnv.txt with 'extraargs=nohz_full=3 isolcpus=3' and that worked, but I'd like to create the image with that already done. What would be the best place to do that? userpatches/customize-image.sh ? If I place anything in userpatches/customize-image.sh am I able to run the build just from there? Thank you very much for any pointers you can give me about best practices to go about it, anything I did wrong, or templates to follow. My first goal is to provide a reproducible build of ubuntu focal + preempt_rt for the rock64 board (which I'm very close!), but I'd be happy to extend the work to be able to apply the PREEMPT_RT patches to any board saving people a bit of the guess work I needed to do (at least for as long the patches are not part of the kernel by default!). Additional background: I need to use Ubuntu as my plan is to use ROS 2 on it, and the officially supported distro is Ubuntu (and focal happens to be the most useful for my use-case). I am aiming, in conjunction with some members of the ROS real-time working group, to ease the entry barrier of learning to make real-time apps for robotics. I am using a Rock64 board because it's similar to a Raspberry Pi 4, as I am unable to source a Raspi4 and I believe it is the same for everyone. Bonus: a quick test (running 10min) of cyclictest with stress on the system provided the following plot on latency (74us max, 15us min, about 20ish us average):

I have a Rock64, purchased in 2019, that has been running happily for 4 years. I was recently experimenting with hooking it up to a relay board and now I am unable to connect to the internet. I am unsure whether something is fried on the board itself or if this is a software problem I can fix, and unsure how to figure that out. Details I have learned more about relay boards now, so I'll do a few things differently and more carefully next attempt, but I had the 5v pin powering the relay board and the 3v pin, GPIO3_A4, and GPIO3_A5 connected to the control side to control two of the board's relays. When connected the Rock's power leds were still on, but either the OS or the internet was down, not sure which. When I then disconnected the relay board, everything worked as normal for a few iterations, but then it remained down even with the relay board disconnected. At this point I logged in over a serial console and found the OS working just fine, but no sign of the ethernet port. This is the current state and I'd like to figure out if it's a fixable one! I have ordered a wifi dongle, but I'd also like to get back ethernet if possible. I believe the only thing I've done intentionally that may have changed the state of the filesystem was that I ran `dpkg-reconfigure network-manager`. Not sure if that changed anything. The orange light on the ethernet port is lit constantly when the board is on. The green light is always off (now). `lspci` produces no output. `ip a` lists only the `lo` interface: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever `/etc/network/interfaces`: #source /etc/network/interfaces.d/* # Network is managed by Network manager auto eth0 iface eth0 inet dhcp # address 192.168.70.70 # netmask 255.255.255.0 # gateway 192.168.1.1 # dns-nameservers 8.8.8.8 8.8.4.4 USB, emmc, and sd still work Boot output The only thing I note here is the line `Net: No ethernet found.` and, at the bottom, several `EXT4-fs error`s. The first makes sense, that's what I'm seeing after bootup. Not sure what to do about the second, if anything.

The initial installation went fine from the flashed image on SD card, and still works fine. However, after using armbian-config to attempt to transfer the OS and bootloader to the eMMC card, nothing actually changes. It says it formats the card and then goes through the process of transferring the files, or at least it looks like it does. But when I reboot it it's still running on the SD card and no files appear to have been transferred to the eMMC. fstab lists the UUID of the SD card and not the eMMC at all; this is also true of the bootenv section of armbian-config. One thing I did notice is that there are some new directories under /mnt : '/mnt/nand-sata-install.Jkf7AG' and '/mnt/nand-sata-install.xo9PVr'. Both of these contain 'bootfs' and 'rootfs' directories, but these are all empty. Also, 'lsblk' shows some sort of boot partitions on the eMMC: mmcblk1 179:32 0 29.1G 0 disk └─mmcblk1p1 179:33 0 28.8G 0 part mmcblk1boot0 179:64 0 4M 1 disk mmcblk1boot1 179:96 0 4M 1 disk Previously, I used this board with ayufan, booting directly from the eMMC card. Before flashing the SD card I erased the boot files from the eMMC card, and as I said the initial installation seemed to go just fine

If I understand the custom-image script is run as a chroot after the image is built. So didn't see anything specifically in the docs but can I ONLY run (from compile script) the custom image script on an already already built image (in /output/images)? Along the same lines can I chroot at any time to the image via the compile script? I should mention that I am using the docker container build for arm on my amd machine. (i.e. ./compile.sh docker.... )

I wanted to build the cli version but didn't see an obvious way to do that with conf variables and the docs don't illuminate that choice. so I tried BUILD_MINIMAL=no BUILD_DESKTOP=no and that seems to do force the cli version. Just suggesting that this might be easier to grok if the variable was say BUILD_TYPE=(desktop|cli|minimal|custom) with maybe default cli where custom might be a rootfs that is custom (like one I put together) and thus doesn't need to be reconstructed from the custom-image script. Maybe setting custom then RELEASE could hold the path to the tarball? If that seems better maybe I can try making a pr? BTW this is not necessarily a beginner topic but didn't see a category for just generic building discussion.

I installed tvheadend on Armbian 22.08 Jammy and Bullseye using the 5.15 kernel. Tvheadend runs fine for a while and then freezes and disconnects filling the log file with the following message: rock64 kernel : au0828: recv_control_msg() Failed receiving control message, error -71. At first I thought it was a problem with Jammy, but I still had the same problem on Bullseye. So I switched to the legacy kernel 4.4.213-rockchip64 and I do not have the problem. I am using a Rock64 Ver. 2 with usb dvb tuner for tvheadend and it is stable running Bullseye with kernel 4.4.213. I am not sure what changed between these kernel versions, but it seems to cause this problem.

Hello, i am pretty new to arm embedded. I have a Rock64 V3.0 2019-0626 So I downloaded Armbian 22.08 Jammy XFCE from https://www.armbian.com/rock64/ and copied it on a 265GB SanDisk Extreme microsd XC 1 V30 A2 using Balena Etcher. Boot process did work, but startxfc4 did not work. The system just went on a blackscreen, but i could still switch to another terminal with alt+f1 ... Best regards, Bo

after several minutes, a 3 line error message is output on 2 old original rock64's. network works, I can log in from my local net, and dmesg says: [ 35.867400] Unbalanced IRQ 47 wake disable [ 35.867422] WARNING: CPU: 0 PID: 1580 at kernel/irq/manage.c:900 irq_set_irq_wake+0x108/0x148 [ 35.867447] Modules linked in: rfkill joydev snd_soc_spdif_tx gpio_ir_recv rc_core lz4hc cdc_acm lz4 hantro_vpu(C) rockchip_vdec(C) rockchip_iep snd_soc_simple_card v4l2_h264 snd_soc_rockchip_i2s rockchip_rga videobuf2_dma_contig snd_soc_rockchip_pcm snd_soc_hdmi_codec snd_soc_rk3328 snd_soc_simple_card_utils v4l2_mem2mem snd_soc_rockchip_spdif videobuf2_dma_sg videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_soc_core videobuf2_common videodev snd_pcm_dmaengine mc snd_pcm snd_timer snd soundcore cpufreq_dt zram binfmt_misc sch_fq_codel ramoops reed_solomon pstore_blk pstore_zone ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj realtek dwmac_rk stmmac_platform stmmac lima dw_hdmi_cec pcs_xpcs gpu_sched dw_hdmi_i2s_audio gpio_syscon [ 35.867680] CPU: 0 PID: 1580 Comm: NetworkManager Tainted: G C 5.15.74-rockchip64 #22.08.6 [ 35.867693] Hardware name: Pine64 Rock64 (DT) [ 35.867699] pstate: 800000c5 (Nzcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 35.867709] pc : irq_set_irq_wake+0x108/0x148 [ 35.867724] lr : irq_set_irq_wake+0x108/0x148 [ 35.867734] sp : ffff80000a7e3b30 [ 35.867739] x29: ffff80000a7e3b30 x28: ffff00000184d880 x27: 0000000000000000 [ 35.867757] x26: 0000000000000000 x25: 0000000000000000 x24: 0000ffffe172c0f8 [ 35.867774] x23: 000000000000002f x22: 0000000000000000 x21: 00000000ffffffea [ 35.867790] x20: ffff80000954c7c8 x19: ffff000000711200 x18: 0000000000000001 [ 35.867806] x17: 0000000000000000 x16: 0000000000000000 x15: 0000000000000280 [ 35.867822] x14: ffff80000a7e3840 x13: 00000000ffffffea x12: ffff800009b1fd10 [ 35.867838] x11: 0000000000000003 x10: ffff800009b07cd0 x9 : ffff800009b07d28 [ 35.867855] x8 : 0000000000017fe8 x7 : c0000000ffffefff x6 : 0000000000000001 [ 35.867870] x5 : ffff8000f501a000 x4 : 0000000000000000 x3 : 0000000000000002 [ 35.867886] x2 : 0000000000000001 x1 : 8cf7ed973ed99a00 x0 : 0000000000000000 [ 35.867903] Call trace: [ 35.867908] irq_set_irq_wake+0x108/0x148 [ 35.867920] stmmac_set_wol+0x74/0x128 [stmmac] [ 35.867985] dev_ethtool+0x1400/0x20b0 [ 35.867998] dev_ioctl+0x1fc/0x3f8 [ 35.868008] sock_do_ioctl+0xb4/0xf8 [ 35.868018] sock_ioctl+0x2d4/0x3b8 [ 35.868027] __arm64_sys_ioctl+0xa8/0xe8 [ 35.868038] invoke_syscall+0x44/0x108 [ 35.868050] el0_svc_common.constprop.3+0x94/0xf8 [ 35.868061] do_el0_svc+0x24/0x88 [ 35.868071] el0_svc+0x20/0x50 [ 35.868080] el0t_64_sync_handler+0x90/0xb8 [ 35.868089] el0t_64_sync+0x180/0x184 [ 35.868099] ---[ end trace b82369d81dab89d6 ]--- [ 147.094526] hdmi-audio-codec hdmi-audio-codec.4.auto: Only one simultaneous stream supported! [ 147.095731] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 147.096881] ff000000.i2s-i2s-hifi: soc_pcm_open() failed (-22) [ 147.250755] overlayfs: "xino" feature enabled using 2 upper inode bits. ================== on both machines. These have a primary assignment of running octoprint as part of my printer farm and hdmi video is required. Any clues as to what will restore their video?

Hello everyone, i was thinking about running a jellyfin server on the Rock64, is there any chance for hardware encoding? Thank you in advance Regards

On Armbian Buster, rockchip (rock64), kernel 5.16.69. This was also happening on the latest backported version of 5.10, I think 5.10.72? I tried upgrading to fix it to no avail. I have a couple 8TB HDDs that I use as backups. All I did was reformat one of them as btrfs and start copying the data back over from the other (still EXT4). I tried rsync and simple cp. Without fail, a few minutes into the operation, the copy operation will hang indefinitely, and all open terminals receive these kernel messages: Message from syslogd@localhost at Oct 1 16:59:57 ... kernel:[ 339.539365] Internal error: Oops: 96000004 [#1] PREEMPT SMP Message from syslogd@localhost at Oct 1 16:59:57 ... kernel:[ 339.560387] Code: cb0100a3 cb0d015c 7100019f 9b167c00 (9adb2400) After that, every subsequent copy operation from the EXT4 drive to this new btrfs partition will hang until I reboot the rock64. However, the drive otherwise continues to work fine. fsck and btrfs scrub find no problems. The super weird thing is I can still write files, and copy a small shell script from the home folder, all just fine--but copying from the other 8TB drive will immediately hang. I have had zero issues with either drive until trying btrfs now. I'm able to rsync between them just fine when they're both EXT4. journalctl.txt specific-error.txt

A month or two back, when I installed Armbian, I had to revert to an older kernel, 5.10.63-rockchip64, which has known vulnerabilities. I needed to be able to boot off of a USB 3 HDD, so I had to revert it and hold updates for the kernel/kernel headers. These are the commands I used to revert to the older kernel: sudo apt install linux-dtb-current-rockchip64=21.08.2 linux-image-current-rockchip64=21.08.2 sudo apt-mark hold linux-dtb-current-rockchip64 linux-image-current-rockchip64 Fast forward to today, where the issue with USB 3 has been apparently resolved in the latest kernel, I tried to unhold the kernel/kernel header updates, that seemed to work. But after running an update, nothing. It's still showing 5.10.63-rockchip64 when it should be 5.15.63rockchip64. I tried to run firmware updates and everything, still not updating the kernel. It still also says Armbian 22.05.3 Jammy. In Armbian Config, the latest kernel I can choose from seems to be one with borked USB3 support, linux-image-current-rockchip64=22.05.3 5.15.48-rockchip64. If I select this kernel, my OS will be bricked since I would not be able to boot off of the USB HDD. linux-image-current-rockchip64=22.08.1 5.15.63-rockchip64 should technically exist as it is the current Armbian release for this board, but it is nowhere to be found in Armbian Config and even after doing an unhold, the system will not update to the latest borked kernel either.

(Note: this is crossposted from an ATS issue, since I think it might be quicker to get answers here. Will post on one thread when I get answers that work in the other) Have installed ats on my Rock64, running Armbian 22.05 Jammy with kernel version 5.10.63, and am having trouble getting the fan to spin. The fan I'm using is the one that comes with this case, and it spins when I connect it to a battery. One possible issue is that I had to manually add an entry for PWM_CTL: running sudo find /sys -name pwm\*, I get: /sys/kernel/tracing/events/pwm /sys/kernel/tracing/events/pwm/pwm_apply /sys/kernel/tracing/events/pwm/pwm_get /sys/kernel/debug/tracing/events/pwm /sys/kernel/debug/tracing/events/pwm/pwm_apply /sys/kernel/debug/tracing/events/pwm/pwm_get /sys/kernel/debug/pwm /sys/class/pwm /sys/bus/platform/drivers/pwm-clock /sys/bus/platform/drivers/pwm-regulator /sys/firmware/devicetree/base/pinctrl/pwm1 /sys/firmware/devicetree/base/pinctrl/pwm1/pwm1-pin /sys/firmware/devicetree/base/pinctrl/pwmir /sys/firmware/devicetree/base/pinctrl/pwmir/pwmir-pin /sys/firmware/devicetree/base/pinctrl/pwm2 /sys/firmware/devicetree/base/pinctrl/pwm2/pwm2-pin /sys/firmware/devicetree/base/pinctrl/pwm0 /sys/firmware/devicetree/base/pinctrl/pwm0/pwm0-pin /sys/firmware/devicetree/base/__symbols__/pwm0_pin /sys/firmware/devicetree/base/__symbols__/pwm3 /sys/firmware/devicetree/base/__symbols__/pwm1 /sys/firmware/devicetree/base/__symbols__/pwm1_pin /sys/firmware/devicetree/base/__symbols__/pwmir_pin /sys/firmware/devicetree/base/__symbols__/pwm2_pin /sys/firmware/devicetree/base/__symbols__/pwm2 /sys/firmware/devicetree/base/__symbols__/pwm0 /sys/firmware/devicetree/base/pwm@ff1b0030 /sys/firmware/devicetree/base/pwm@ff1b0020 /sys/firmware/devicetree/base/pwm@ff1b0010 /sys/firmware/devicetree/base/pwm@ff1b0000 My guess was that I should use /sys/firmware/devicetree/base/pinctrl/pwm1. Putting that in my ats config, when I run ats -t, I get: info:'SYSTEM' Table info: 'BOARD' Table info: 'NAME' = ROCK64 info: 'CPU' = RK3328 info: 'THERMAL0_CTL' = /sys/class/thermal/thermal_zone0/temp info: 'THERMAL1_CTL' = ERROR info: 'PWM_CTL' = /sys/firmware/devicetree/base/pinctrl/pwm1 info: 'MAX_CONTINUOUS_THERMAL_TEMP' = 45 info: 'MIN_CONTINUOUS_THERMAL_TEMP' = 20 info: 'MAX_PWM' = 255 info: 'MIN_PWM' = 40 info: 'ALWAYS_ON' = false info: 'PROFILE_NAME' = profile0 info: 'PROFILE' = 0 info:'Pratio' timers info: 'Pratio[ -20 - 20 [' = 0 info: 'Pratio[ 20 ]' = 40 ... info: 'Pratio[ 45 ]' = 255 info: 'Pratio[ 45 - 70 [' = 255 (the temperature range is low so that the fan would definitely run if it was working) When I run this command, the fan doesn't spin. For what it's worth, here's the rest of the output of ats -t: Stopping for[ seconds ]............... 3 CPU Temperature[ max 70 °C ].......... 0 GPU Temperature[ max 70 °C ].......... 0 Fan PWM Duty Cycle value[ 0 - 255 ]... 190 -------------------- Running for[ seconds ]................ 10 CPU Temperature[ max 70 °C ].......... 39 GPU Temperature[ max 70 °C ].......... 0 Fan PWM Duty Cycle value[ 0 - 255 ]... 0 -------------------- Any idea what might be wrong?

Running latest Jammy image and trying to attach USB to SATA 3 SSD. I tried two different USB 3 to SATA adapters and they both show up in lsusb: Bus 005 Device 002: ID 2109:0711 VIA Labs, Inc. VL711 SATA 6Gb/s bridge sudo fdisk -l doesn't show drive, but I can plug into my desktop and it mounts disk. Could be related to https://github.com/MichaIng/DietPi/issues/5378

That's all, really. I appreciate the amount and quality of work that the leaders here generously share with the community. I donated an amount that would buy 6 bottles of my preferred local brew, hoping that the project's accountants will allow at least that tiny drop in the total donation pool to be used to celebrate a little. It's well-earned!