jock
-
Posts
2075 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by jock
-
-
8 hours ago, suryob said:
hello everyone,
happy new year,
hope everyone are in good conditions,I own MXQ 4K box with RK3228a chip, on the board written R29_MXQ_221_V1.0_0926, I want to install armbian on it,
I already download multitool from the first page and burn it into MMC card using balena, when I try to boot the yellow LED is blinking but there is no display,here is the UART log
U-Boot 2020.10-armbian+ (Mar 12 2021 - 13:38:05 +0000)
Model: Generic Rockchip rk322x TV Box board
DRAM: 1010 MiB
MMC: dwmmc@30000000: 1, dwmmc@30020000: 0
Loading Environment from EXT4...
** Unable to use mmc 0:auto for loading the env **
In: serial@11030000
Out: serial@11030000
Err: serial@11030000
Model: Generic Rockchip rk322x TV Box board
Net: eth0: ethernet@30200000
starting USB...
Bus usb@30040000: USB DWC2
Bus usb@30080000: USB EHCI 1.00
Bus usb@300c0000: USB EHCI 1.00
Bus usb@30100000: USB EHCI 1.00
scanning bus usb@30040000 for devices... 1 USB Device(s) found
scanning bus usb@30080000 for devices... 1 USB Device(s) found
scanning bus usb@300c0000 for devices... 1 USB Device(s) found
scanning bus usb@30100000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
175 bytes read in 10 ms (16.6 KiB/s)
1: Multitool
Retrieving file: /kernel.img
8719272 bytes read in 386 ms (21.5 MiB/s)
append: boot=PARTUUID=21fcd12b-01 root=PARTUUID=21fcd12b-02 rootwait console=ttyS2,115200 verbose=1 consoleblank=0
Retrieving file: /rk322x-box.dtb
46636 bytes read in 9 ms (4.9 MiB/s)
## Flattened Device Tree blob at 61f00000
Booting using the fdt blob at 0x61f00000
EHCI failed to shut down host controller.
EHCI failed to shut down host controller.
Loading Device Tree to 683f1000, end 683ff62b ... OKStarting kernel ...
[ 0.000000] Booting Linux on physical CPU 0xf00
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Initializing cgroup subsys cpuacct
[ 0.000000] Linux version 4.4.194-rk322x (root@armbianbuild) (gcc version 8.3.0 (GNU Toolchain for the A-profile Architecture 8.3-2019.03 (arm-rel-8.36)) ) #47 SMP Thu Apr 9 17:37:46 UTC 2020
[ 0.000000] CPU: ARMv7 Processor [410fc075] revision 5 (ARMv7), cr=10c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Generic RK322x TV Box board
[ 0.000000] cma: Reserved 128 MiB at 0x98000000
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] psci: probing for conduit method from DT.
[ 0.000000] psci: PSCIv65535.65535 detected in firmware.
[ 0.000000] psci: Using standard PSCI v0.2 function IDs
[ 0.000000] psci: MIGRATE_INFO_TYPE not supported.
[ 0.000000] PERCPU: Embedded 14 pages/cpu @e7659000 s24856 r8192 d24296 u57344
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 256256
[ 0.000000] Kernel command line: boot=PARTUUID=21fcd12b-01 root=PARTUUID=21fcd12b-02 rootwait console=ttyS2,115200 verbose=1 consoleblank=0
[ 0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 871700K/1034240K available (12820K kernel code, 875K rwdata, 3224K rodata, 796K init, 1219K bss, 31468K reserved, 131072K cma-reserved, 0K highmem)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
[ 0.000000] lowmem : 0xb0000000 - 0xf0000000 (1024 MB)
[ 0.000000] pkmap : 0xafe00000 - 0xb0000000 ( 2 MB)
[ 0.000000] modules : 0xaf000000 - 0xafe00000 ( 14 MB)
[ 0.000000] .text : 0xb0008000 - 0xb0c8d53c (12822 kB)
[ 0.000000] .init : 0xb10a1000 - 0xb1168000 ( 796 kB)
[ 0.000000] .data : 0xb1168000 - 0xb1242e94 ( 876 kB)
[ 0.000000] .bss : 0xb1244000 - 0xb1374ee4 (1220 kB)
[ 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 32.
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 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.000009] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[ 0.000025] Switching to timer-based delay loop, resolution 41ns
[ 0.001749] Console: colour dummy device 80x30
[ 0.001788] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[ 0.001808] pid_max: default: 32768 minimum: 301
[ 0.001959] Security Framework initialized
[ 0.001975] Yama: becoming mindful.
[ 0.002065] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.002081] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.003098] Initializing cgroup subsys io
[ 0.003141] Initializing cgroup subsys memory
[ 0.003189] Initializing cgroup subsys devices
[ 0.003211] Initializing cgroup subsys freezer
[ 0.003230] Initializing cgroup subsys net_cls
[ 0.003247] Initializing cgroup subsys perf_event
[ 0.003266] Initializing cgroup subsys net_prio
[ 0.003301] Initializing cgroup subsys pids
[ 0.003380] CPU: Testing write buffer coherency: ok
[ 0.003440] ftrace: allocating 41720 entries in 123 pages
[ 0.086760] /cpus/cpu@f00 missing clock-frequency property
[ 0.086802] /cpus/cpu@f01 missing clock-frequency property
[ 0.086821] /cpus/cpu@f02 missing clock-frequency property
[ 0.086843] /cpus/cpu@f03 missing clock-frequency property
[ 0.086855] CPU0: update cpu_capacity 430
[ 0.086867] CPU0: thread -1, cpu 0, socket 15, mpidr 80000f00
[ 0.086968] Setting up static identity map for 0x60008280 - 0x600082d8
[ 0.090355] CPU1: update cpu_capacity 430
[ 0.090366] CPU1: thread -1, cpu 1, socket 15, mpidr 80000f01
[ 0.091635] CPU2: update cpu_capacity 430
[ 0.091644] CPU2: thread -1, cpu 2, socket 15, mpidr 80000f02
[ 0.092903] CPU3: update cpu_capacity 430
[ 0.092913] CPU3: thread -1, cpu 3, socket 15, mpidr 80000f03
[ 0.093066] Brought up 4 CPUs
[ 0.093109] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[ 0.093118] CPU: All CPU(s) started in SVC mode.
[ 0.094909] devtmpfs: initialized
[ 0.113102] VFP support v0.3: implementor 41 architecture 2 part 30 variant 7 rev 5
[ 0.113701] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[ 0.113746] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.120441] xor: measuring software checksum speed
[ 0.158752] arm4regs : 1011.000 MB/sec
[ 0.198860] 8regs : 705.000 MB/sec
[ 0.238961] 32regs : 684.000 MB/sec
[ 0.279066] neon : 1018.000 MB/sec
[ 0.279077] xor: using function: neon (1018.000 MB/sec)
[ 0.279122] pinctrl core: initialized pinctrl subsystem
[ 0.280941] NET: Registered protocol family 16
[ 0.283358] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[ 0.295265] cpuidle: using governor ladder
[ 0.307265] cpuidle: using governor menu
[ 0.330563] console [pstore-1] enabled
[ 0.330576] pstore: Registered ramoops as persistent store backend
[ 0.330588] ramoops: attached 0xf0000@0x62e00000, ecc: 0/0
[ 0.333605] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.333629] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.432436] raid6: int32x1 gen() 133 MB/s
[ 0.500379] raid6: int32x1 xor() 131 MB/s
[ 0.568642] raid6: int32x2 gen() 166 MB/s
[ 0.636913] raid6: int32x2 xor() 137 MB/s
[ 0.705070] raid6: int32x4 gen() 163 MB/s
[ 0.773329] raid6: int32x4 xor() 137 MB/s
[ 0.841482] raid6: int32x8 gen() 166 MB/s
[ 0.909745] raid6: int32x8 xor() 113 MB/s
[ 0.977738] raid6: neonx1 gen() 381 MB/s
[ 1.045995] raid6: neonx1 xor() 290 MB/s
[ 1.114242] raid6: neonx2 gen() 519 MB/s
[ 1.182376] raid6: neonx2 xor() 376 MB/s
[ 1.250671] raid6: neonx4 gen() 581 MB/s
[ 1.318829] raid6: neonx4 xor() 400 MB/s
[ 1.387105] raid6: neonx8 gen() 559 MB/s
[ 1.455315] raid6: neonx8 xor() 391 MB/s
[ 1.455329] raid6: using algorithm neonx4 gen() 581 MB/s
[ 1.455339] raid6: .... xor() 400 MB/s, rmw enabled
[ 1.455350] raid6: using intx1 recovery algorithm
[ 1.456471] rockchip-pm rockchip-suspend: not set wakeup-config
[ 1.456500] rockchip-pm rockchip-suspend: not set pwm-regulator-config
[ 1.460417] iommu: Adding device 20020000.vpu-service to group 0
[ 1.460533] iommu: Adding device 20030000.rkvdec to group 1
[ 1.460633] iommu: Adding device 20050000.vop to group 2
[ 1.460724] iommu: Adding device 20070000.iep to group 3
[ 1.461347] rk_iommu 20020800.iommu: can't get sclk
[ 1.462085] rk_iommu 20030480.iommu: can't get sclk
[ 1.462357] rk_iommu 20053f00.iommu: can't get sclk
[ 1.462508] rk_iommu 20070800.iommu: can't get aclk
[ 1.462527] rk_iommu 20070800.iommu: can't get hclk
[ 1.462544] rk_iommu 20070800.iommu: can't get sclk
[ 1.463520] SCSI subsystem initialized
[ 1.463966] usbcore: registered new interface driver usbfs
[ 1.464070] usbcore: registered new interface driver hub
[ 1.464206] usbcore: registered new device driver usb
[ 1.464447] media: Linux media interface: v0.10
[ 1.464531] Linux video capture interface: v2.00
[ 1.464754] pps_core: LinuxPPS API ver. 1 registered
[ 1.464770] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 1.464812] PTP clock support registered
[ 1.466926] Advanced Linux Sound Architecture Driver Initialized.
[ 1.468188] Bluetooth: Core ver 2.21
[ 1.468272] NET: Registered protocol family 31
[ 1.468285] Bluetooth: HCI device and connection manager initialized
[ 1.468308] Bluetooth: HCI socket layer initialized
[ 1.468327] Bluetooth: L2CAP socket layer initialized
[ 1.468390] Bluetooth: SCO socket layer initialized
[ 1.469386] NetLabel: Initializing
[ 1.469412] NetLabel: domain hash size = 128
[ 1.469422] NetLabel: protocols = UNLABELED CIPSOv4
[ 1.469508] NetLabel: unlabeled traffic allowed by default
[ 1.470685] clocksource: Switched to clocksource arch_sys_counter
[ 1.573562] NET: Registered protocol family 2
[ 1.574563] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 1.574798] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[ 1.575159] TCP: Hash tables configured (established 8192 bind 8192)
[ 1.575282] UDP hash table entries: 512 (order: 2, 24576 bytes)
[ 1.575354] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[ 1.575779] NET: Registered protocol family 1
[ 1.576637] RPC: Registered named UNIX socket transport module.
[ 1.576663] RPC: Registered udp transport module.
[ 1.576674] RPC: Registered tcp transport module.
[ 1.576685] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.577727] hw perfevents: enabled with armv7_cortex_a7 PMU driver, 5 counters available
[ 1.580996] Initialise system trusted keyring
[ 1.595906] VFS: Disk quotas dquot_6.6.0
[ 1.596244] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.599212] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 1.602982] NFS: Registering the id_resolver key type
[ 1.603073] Key type id_resolver registered
[ 1.603085] Key type id_legacy registered
[ 1.603122] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.603226] ntfs: driver 2.1.32 [Flags: R/W].
[ 1.604197] JFS: nTxBlock = 7834, nTxLock = 62673
[ 1.616668] SGI XFS with security attributes, no debug enabled
[ 1.626374] NET: Registered protocol family 38
[ 1.626441] Key type asymmetric registered
[ 1.626464] Asymmetric key parser 'x509' registered
[ 1.627051] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 1.627386] io scheduler noop registered
[ 1.627423] io scheduler deadline registered
[ 1.627522] io scheduler cfq registered (default)
[ 1.631209] phy phy-11000000.syscon:usb2-phy@800.2: Failed to get VBUS supply regulator
[ 1.636796] rk-vcodec 20020000.vpu-service: no regulator for vcodec
[ 1.637373] rk-vcodec 20020000.vpu-service: probe device
[ 1.637885] rk-vcodec 20020000.vpu-service: drm allocator with mmu enabled
[ 1.639451] rk-vcodec 20020000.vpu-service: could not find power_model node
[ 1.639482] rk-vcodec 20020000.vpu-service: init success
[ 1.639875] rk-vcodec 20030000.rkvdec: vcodec regulator not ready, retry
[ 1.644402] dma-pl330 110f0000.pdma: Loaded driver for PL330 DMAC-241330
[ 1.644437] dma-pl330 110f0000.pdma: DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16
[ 1.645611] rockchip-system-monitor rockchip-system-monitor: system monitor probe
[ 1.648401] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 1.649359] 11030000.serial: ttyS2 at MMIO 0x11030000 (irq = 30, base_baud = 1500000) is a 16550A
[ 2.681245] console [ttyS2] enabled
[ 2.686818] [drm] Initialized drm 1.1.0 20060810
[ 2.693983] [drm] Rockchip DRM driver version: v1.0.1
[ 2.699414] rockchip-drm display-subsystem: devfreq is not set
[ 2.706176] rockchip-drm display-subsystem: bound 20050000.vop (ops 0xb0d111b0)
[ 2.714007] i2c i2c-0: of_i2c: modalias failure on /hdmi@200a0000/ports
[ 2.720693] dwhdmi-rockchip 200a0000.hdmi: registered DesignWare HDMI I2C bus driver
[ 2.728568] dwhdmi-rockchip 200a0000.hdmi: Detected HDMI TX controller v2.01a with HDCP (inno_dw_hdmi_phy)
[ 2.739901] rockchip-drm display-subsystem: bound 200a0000.hdmi (ops 0xb0d09708)
[ 2.747413] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 2.754059] [drm] No driver support for vblank timestamp query.
[ 2.760141] rockchip-drm display-subsystem: failed to parse display resources
[ 3.389493] rockchip-vop 20050000.vop: [drm:vop_crtc_enable] Update mode to 1366x768p60, type: 11
[ 3.390269] dwhdmi-rockchip 200a0000.hdmi: Rate 85750000 missing; compute N dynamically
[ 3.390337] dwhdmi-rockchip 200a0000.hdmi: HDMI infoframe: Auxiliary Video Information (AVI), version 2, length 13
[ 3.390345] dwhdmi-rockchip 200a0000.hdmi: colorspace: RGB
[ 3.390352] dwhdmi-rockchip 200a0000.hdmi: scan mode: Underscan
[ 3.390358] dwhdmi-rockchip 200a0000.hdmi: colorimetry: No Data
[ 3.390365] dwhdmi-rockchip 200a0000.hdmi: picture aspect: No Data
[ 3.390372] dwhdmi-rockchip 200a0000.hdmi: active aspect: Same as Picture
[ 3.390379] dwhdmi-rockchip 200a0000.hdmi: itc: IT Content
[ 3.390386] dwhdmi-rockchip 200a0000.hdmi: extended colorimetry: xvYCC 601
[ 3.390393] dwhdmi-rockchip 200a0000.hdmi: quantization range: Full
[ 3.390400] dwhdmi-rockchip 200a0000.hdmi: nups: Unknown Non-uniform Scaling
[ 3.390406] dwhdmi-rockchip 200a0000.hdmi: video code: 0
[ 3.390412] dwhdmi-rockchip 200a0000.hdmi: ycc quantization range: Full
[ 3.390419] dwhdmi-rockchip 200a0000.hdmi: hdmi content type: Graphics
[ 3.390426] dwhdmi-rockchip 200a0000.hdmi: pixel repeat: 0
[ 3.390433] dwhdmi-rockchip 200a0000.hdmi: bar top 0, bottom 0, left 0, right 0
[ 3.390627] rockchip-vop 20050000.vop: mode_update:1, need wait blk:1
[ 3.390634] rockchip-vop 20050000.vop: [drm:vop_isr] *ERROR* BUS_ERROR irq err
[ 3.423937] rockchip-vop 20050000.vop: [drm:vop_isr] *ERROR* POST_BUF_EMPTY irq err
[ 3.478930] Console: switching to colour frame buffer device 170x48
[ 3.659392] rockchip-drm display-subsystem: fb0: frame buffer device
[ 3.683176] brd: module loaded
[ 3.699705] loop: module loaded
[ 3.703002] lkdtm: No crash points registered, enable through debugfs
[ 3.712652] libphy: Fixed MDIO Bus: probed
[ 3.716882] tun: Universal TUN/TAP device driver, 1.6
[ 3.721971] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[ 3.728671] CAN device driver interface
[ 3.734306] rk_gmac-dwmac 30200000.ethernet: clock input or output? (output).
[ 3.741521] rk_gmac-dwmac 30200000.ethernet: TX delay(0x30).
[ 3.747214] rk_gmac-dwmac 30200000.ethernet: RX delay(0x10).
[ 3.752942] rk_gmac-dwmac 30200000.ethernet: integrated PHY? (yes).
[ 3.759436] rk_gmac-dwmac 30200000.ethernet: cannot get clock clk_mac_speed
[ 3.771506] rk_gmac-dwmac 30200000.ethernet: init for RMII
[ 3.810826] stmmac - user ID: 0x10, Synopsys ID: 0x35
[ 3.815932] Ring mode enabled
[ 3.819022] DMA HW capability register supported
[ 3.823573] Normal descriptors
[ 3.826923] RX Checksum Offload Engine supported (type 2)
[ 3.832422] TX Checksum insertion supported
[ 3.836709] Wake-Up On Lan supported
[ 3.840522] rk_gmac-dwmac 30200000.ethernet: rk_get_eth_addr: mac address: 8a:dc:a9:9d:75:5d
[ 3.848992] eth%d: device MAC address 8a:dc:a9:9d:75:5d
[ 3.854239] Enable RX Mitigation via HW Watchdog Timer
[ 3.878835] libphy: stmmac: probed
[ 3.882276] eth%d: PHY ID 1234d400 at 0 IRQ POLL (stmmac-0:00) active
[ 3.888765] eth%d: PHY ID 00000000 at 1 IRQ POLL (stmmac-0:01)
[ 3.894624] eth%d: PHY ID 00000000 at 2 IRQ POLL (stmmac-0:02)
[ 3.900481] eth%d: PHY ID 00000000 at 3 IRQ POLL (stmmac-0:03)
[ 3.906334] eth%d: PHY ID 00000000 at 4 IRQ POLL (stmmac-0:04)
[ 3.912185] eth%d: PHY ID 00000000 at 5 IRQ POLL (stmmac-0:05)
[ 3.918035] eth%d: PHY ID 00000000 at 6 IRQ POLL (stmmac-0:06)
[ 3.923884] eth%d: PHY ID 00000000 at 7 IRQ POLL (stmmac-0:07)
[ 3.929734] eth%d: PHY ID 00000000 at 8 IRQ POLL (stmmac-0:08)
[ 3.935585] eth%d: PHY ID 00000000 at 9 IRQ POLL (stmmac-0:09)
[ 3.941444] eth%d: PHY ID 00000000 at 10 IRQ POLL (stmmac-0:0a)
[ 3.947383] eth%d: PHY ID 00000000 at 11 IRQ POLL (stmmac-0:0b)
[ 3.953319] eth%d: PHY ID 00000000 at 12 IRQ POLL (stmmac-0:0c)
[ 3.959254] eth%d: PHY ID 00000000 at 13 IRQ POLL (stmmac-0:0d)
[ 3.965189] eth%d: PHY ID 00000000 at 14 IRQ POLL (stmmac-0:0e)
[ 3.971124] eth%d: PHY ID 00000000 at 15 IRQ POLL (stmmac-0:0f)
[ 3.977059] eth%d: PHY ID 00000000 at 16 IRQ POLL (stmmac-0:10)
[ 3.982994] eth%d: PHY ID 00000000 at 17 IRQ POLL (stmmac-0:11)
[ 3.988929] eth%d: PHY ID 00000000 at 18 IRQ POLL (stmmac-0:12)
[ 3.994893] eth%d: PHY ID 00000000 at 19 IRQ POLL (stmmac-0:13)
[ 4.000843] eth%d: PHY ID 00000000 at 20 IRQ POLL (stmmac-0:14)
[ 4.006786] eth%d: PHY ID 00000000 at 21 IRQ POLL (stmmac-0:15)
[ 4.012729] eth%d: PHY ID 00000000 at 22 IRQ POLL (stmmac-0:16)
[ 4.018668] eth%d: PHY ID 00000000 at 23 IRQ POLL (stmmac-0:17)
[ 4.024606] eth%d: PHY ID 00000000 at 24 IRQ POLL (stmmac-0:18)
[ 4.030545] eth%d: PHY ID 00000000 at 25 IRQ POLL (stmmac-0:19)
[ 4.036486] eth%d: PHY ID 00000000 at 26 IRQ POLL (stmmac-0:1a)
[ 4.042429] eth%d: PHY ID 00000000 at 27 IRQ POLL (stmmac-0:1b)
[ 4.048369] eth%d: PHY ID 00000000 at 28 IRQ POLL (stmmac-0:1c)
[ 4.054309] eth%d: PHY ID 00000000 at 29 IRQ POLL (stmmac-0:1d)
[ 4.060253] eth%d: PHY ID 00000000 at 30 IRQ POLL (stmmac-0:1e)
[ 4.066192] eth%d: PHY ID 00000000 at 31 IRQ POLL (stmmac-0:1f)
[ 4.073990] PPP generic driver version 2.4.2
[ 4.079018] Atmel at76x USB Wireless LAN Driver 0.17 loading
[ 4.084914] usbcore: registered new interface driver at76c50x-usb
[ 4.091221] usbcore: registered new interface driver rtl8187
[ 4.097058] usbcore: registered new interface driver rndis_wlan
[ 4.103185] usbcore: registered new interface driver zd1201
[ 4.109339] usbcore: registered new interface driver rt2800usb
[ 4.115455] Rockchip WiFi SYS interface (V1.00) ...
[ 4.120565] pegasus: v0.9.3 (2013/04/25), Pegasus/Pegasus II USB Ethernet driver
[ 4.128111] usbcore: registered new interface driver pegasus
[ 4.133903] usbcore: registered new interface driver rtl8150
[ 4.139684] usbcore: registered new interface driver r8152
[ 4.145309] usbcore: registered new interface driver asix
[ 4.150824] usbcore: registered new interface driver ax88179_178a
[ 4.157036] usbcore: registered new interface driver cdc_ether
[ 4.162998] usbcore: registered new interface driver dm9601
[ 4.168737] usbcore: registered new interface driver smsc75xx
[ 4.174619] usbcore: registered new interface driver smsc95xx
[ 4.180480] usbcore: registered new interface driver net1080
[ 4.186250] usbcore: registered new interface driver rndis_host
[ 4.192287] usbcore: registered new interface driver MOSCHIP usb-ethernet driver
[ 4.199897] usbcore: registered new interface driver cdc_ncm
[ 4.205677] usbcore: registered new interface driver cdc_mbim
[ 4.212109] 30040000.usb supply vusb_d not found, using dummy regulator
[ 4.218938] 30040000.usb supply vusb_a not found, using dummy regulator
[ 4.239246] dwc2 30040000.usb: DWC OTG Controller
[ 4.244094] dwc2 30040000.usb: new USB bus registered, assigned bus number 1
[ 4.251240] dwc2 30040000.usb: irq 49, io mem 0x30040000
[ 4.257024] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 4.263871] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.271126] usb usb1: Product: DWC OTG Controller
[ 4.275859] usb usb1: Manufacturer: Linux 4.4.194-rk322x dwc2_hsotg
[ 4.282149] usb usb1: SerialNumber: 30040000.usb
[ 4.288094] hub 1-0:1.0: USB hub found
[ 4.291989] hub 1-0:1.0: 1 port detected
[ 4.298074] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 4.304686] ehci-platform: EHCI generic platform driver
[ 4.312649] ehci-platform 30080000.usb: EHCI Host Controller
[ 4.318861] ehci-platform 30080000.usb: new USB bus registered, assigned bus number 2
[ 4.327145] ehci-platform 30080000.usb: irq 50, io mem 0x30080000
[ 4.342760] ehci-platform 30080000.usb: USB 2.0 started, EHCI 1.00
[ 4.349365] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 4.356217] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.363473] usb usb2: Product: EHCI Host Controller
[ 4.368377] usb usb2: Manufacturer: Linux 4.4.194-rk322x ehci_hcd
[ 4.374488] usb usb2: SerialNumber: 30080000.usb
[ 4.380310] hub 2-0:1.0: USB hub found
[ 4.384200] hub 2-0:1.0: 1 port detected
[ 4.391293] ehci-platform 300c0000.usb: EHCI Host Controller
[ 4.397821] ehci-platform 300c0000.usb: new USB bus registered, assigned bus number 3
[ 4.406125] ehci-platform 300c0000.usb: irq 52, io mem 0x300c0000
[ 4.422766] ehci-platform 300c0000.usb: USB 2.0 started, EHCI 1.00
[ 4.429340] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 4.436187] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.443437] usb usb3: Product: EHCI Host Controller
[ 4.448339] usb usb3: Manufacturer: Linux 4.4.194-rk322x ehci_hcd
[ 4.454453] usb usb3: SerialNumber: 300c0000.usb
[ 4.460271] hub 3-0:1.0: USB hub found
[ 4.464159] hub 3-0:1.0: 1 port detected
[ 4.471239] ehci-platform 30100000.usb: EHCI Host Controller
[ 4.477448] ehci-platform 30100000.usb: new USB bus registered, assigned bus number 4
[ 4.485754] ehci-platform 30100000.usb: irq 54, io mem 0x30100000
[ 4.502764] ehci-platform 30100000.usb: USB 2.0 started, EHCI 1.00
[ 4.509332] usb usb4: New USB device found, idVendor=1d6b, idProduct=0002
[ 4.516177] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.523430] usb usb4: Product: EHCI Host Controller
[ 4.528332] usb usb4: Manufacturer: Linux 4.4.194-rk322x ehci_hcd
[ 4.534445] usb usb4: SerialNumber: 30100000.usb
[ 4.540256] hub 4-0:1.0: USB hub found
[ 4.544150] hub 4-0:1.0: 1 port detected
[ 4.549036] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 4.555314] ohci-platform: OHCI generic platform driver
[ 4.561126] ohci-platform 300a0000.usb: Generic Platform OHCI controller
[ 4.568848] ohci-platform 300a0000.usb: new USB bus registered, assigned bus number 5
[ 4.577126] ohci-platform 300a0000.usb: irq 51, io mem 0x300a0000
[ 4.643076] usb usb5: New USB device found, idVendor=1d6b, idProduct=0001
[ 4.649950] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.657211] usb usb5: Product: Generic Platform OHCI controller
[ 4.663166] usb usb5: Manufacturer: Linux 4.4.194-rk322x ohci_hcd
[ 4.669288] usb usb5: SerialNumber: 300a0000.usb
[ 4.676156] hub 5-0:1.0: USB hub found
[ 4.680054] hub 5-0:1.0: 1 port detected
[ 4.685098] ohci-platform 300e0000.usb: Generic Platform OHCI controller
[ 4.692336] ohci-platform 300e0000.usb: new USB bus registered, assigned bus number 6
[ 4.700570] ohci-platform 300e0000.usb: irq 53, io mem 0x300e0000
[ 4.767096] usb usb6: New USB device found, idVendor=1d6b, idProduct=0001
[ 4.773949] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.781204] usb usb6: Product: Generic Platform OHCI controller
[ 4.787175] usb usb6: Manufacturer: Linux 4.4.194-rk322x ohci_hcd
[ 4.793301] usb usb6: SerialNumber: 300e0000.usb
[ 4.799437] hub 6-0:1.0: USB hub found
[ 4.803330] hub 6-0:1.0: 1 port detected
[ 4.808328] ohci-platform 30120000.usb: Generic Platform OHCI controller
[ 4.815566] ohci-platform 30120000.usb: new USB bus registered, assigned bus number 7
[ 4.823818] ohci-platform 30120000.usb: irq 55, io mem 0x30120000
[ 4.887062] usb usb7: New USB device found, idVendor=1d6b, idProduct=0001
[ 4.893903] usb usb7: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 4.901160] usb usb7: Product: Generic Platform OHCI controller
[ 4.907121] usb usb7: Manufacturer: Linux 4.4.194-rk322x ohci_hcd
[ 4.913245] usb usb7: SerialNumber: 30120000.usb
[ 4.919389] hub 7-0:1.0: USB hub found
[ 4.923283] hub 7-0:1.0: 1 port detected
[ 4.928378] usbcore: registered new interface driver cdc_acm
[ 4.934099] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 4.942261] usbcore: registered new interface driver cdc_wdm
[ 4.948292] usbcore: registered new interface driver usb-storage
[ 4.954560] usbcore: registered new interface driver usbserial
[ 4.960523] usbcore: registered new interface driver usbserial_generic
[ 4.967139] usbserial: USB Serial support registered for generic
[ 4.973296] usbcore: registered new interface driver keyspan
[ 4.979049] usbserial: USB Serial support registered for Keyspan - (without firmware)
[ 4.986968] usbserial: USB Serial support registered for Keyspan 1 port adapter
[ 4.994340] usbserial: USB Serial support registered for Keyspan 2 port adapter
[ 5.001742] usbserial: USB Serial support registered for Keyspan 4 port adapter
[ 5.009193] usbcore: registered new interface driver option
[ 5.014859] usbserial: USB Serial support registered for GSM modem (1-port)
[ 5.022548] usbcore: registered new interface driver oti6858
[ 5.028604] usbserial: USB Serial support registered for oti6858
[ 5.034816] usbcore: registered new interface driver qcserial
[ 5.040664] usbserial: USB Serial support registered for Qualcomm USB modem
[ 5.047849] usbcore: registered new interface driver sierra
[ 5.053522] usbserial: USB Serial support registered for Sierra USB modem
[ 5.061497] usbcore: registered new interface driver iforce
[ 5.067336] usbcore: registered new interface driver xpad
[ 5.073080] usbcore: registered new interface driver usbtouchscreen
[ 5.080761] i2c /dev entries driver
[ 5.087574] usbcore: registered new interface driver uvcvideo
[ 5.093374] USB Video Class driver (1.1.1)
[ 5.099746] Boot mode: normal
[ 5.104339] rockchip-thermal 11150000.tsadc: tsadc is probed successfully!
[ 5.113294] device-mapper: ioctl: 4.34.0-ioctl (2015-10-28) initialised: dm-devel@redhat.com
[ 5.122249] Bluetooth: Virtual HCI driver ver 1.5
[ 5.127365] Bluetooth: HCI UART driver ver 2.3
[ 5.131862] Bluetooth: HCI UART protocol H4 registered
[ 5.137030] Bluetooth: HCI UART protocol LL registered
[ 5.142200] Bluetooth: HCI UART protocol ATH3K registered
[ 5.147622] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 5.154131] Bluetooth: HCI UART protocol BCM registered
[ 5.159585] usbcore: registered new interface driver bfusb
[ 5.165280] usbcore: registered new interface driver btusb
[ 5.170819] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[ 5.177310] cpu cpu0: leakage=4
[ 5.180574] cpu cpu0: leakage-volt-sel=0
[ 5.184804] cpu cpu0: Failed to get pvtm
[ 5.190519] cpu cpu0: avs=0
[ 5.193528] cpu cpu0: l=-2147483648 h=2147483647 hyst=0 l_limit=0 h_limit=0
[ 5.200569] cpu cpu0: failed to read out thermal zone (-22)
[ 5.207065] cpu cpu0: failed to find power_model node
[ 5.213149] Synopsys Designware Multimedia Card Interface Driver
[ 5.220163] dwmmc_rockchip 30000000.dwmmc: IDMAC supports 32-bit address mode.
[ 5.227658] dwmmc_rockchip 30000000.dwmmc: Using internal DMA controller.
[ 5.234501] dwmmc_rockchip 30000000.dwmmc: Version ID is 270a
[ 5.240378] dwmmc_rockchip 30000000.dwmmc: DW MMC controller at irq 45,32 bit host data width,256 deep fifo
[ 5.250219] dwmmc_rockchip 30000000.dwmmc: No vmmc regulator found
[ 5.256426] dwmmc_rockchip 30000000.dwmmc: No vqmmc regulator found
[ 5.262872] dwmmc_rockchip 30000000.dwmmc: Got CD GPIO
[ 5.281038] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[ 5.303461] dwmmc_rockchip 30000000.dwmmc: 1 slots initialized
[ 5.310018] dwmmc_rockchip 30010000.dwmmc: num-slots property not found, assuming 1 slot is available
[ 5.319497] dwmmc_rockchip 30010000.dwmmc: IDMAC supports 32-bit address mode.
[ 5.326963] dwmmc_rockchip 30010000.dwmmc: Using internal DMA controller.
[ 5.333834] dwmmc_rockchip 30010000.dwmmc: Version ID is 270a
[ 5.339746] dwmmc_rockchip 30010000.dwmmc: DW MMC controller at irq 46,32 bit host data width,256 deep fifo
[ 5.349644] dwmmc_rockchip 30010000.dwmmc: No vmmc regulator found
[ 5.355875] dwmmc_rockchip 30010000.dwmmc: No vqmmc regulator found
[ 5.375215] mmc_host mmc1: Bus speed (slot 0) = 976562Hz (slot req 400000Hz, actual 244140HZ div = 2)
[ 5.397221] dwmmc_rockchip 30010000.dwmmc: 1 slots initialized
[ 5.403625] dwmmc_rockchip 30020000.dwmmc: IDMAC supports 32-bit address mode.
[ 5.411193] dwmmc_rockchip 30020000.dwmmc: Using internal DMA controller.
[ 5.418086] dwmmc_rockchip 30020000.dwmmc: Version ID is 270a
[ 5.424038] dwmmc_rockchip 30020000.dwmmc: DW MMC controller at irq 47,32 bit host data width,256 deep fifo
[ 5.433862] dwmmc_rockchip 30020000.dwmmc: 'clock-freq-min-max' property was deprecated.
[ 5.435417] mmc_host mmc0: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 5.435527] mmc0: new high speed SDHC card at address b020
[ 5.436823] mmcblk0: mmc0:b020 SB32G 29.7 GiB
[ 5.439587] mmcblk0: p1 p2
[ 5.445946] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[ 5.447477] mmc1: new high speed SDIO card at address 0001
[ 5.479963] dwmmc_rockchip 30020000.dwmmc: No vmmc regulator found
[ 5.486202] dwmmc_rockchip 30020000.dwmmc: No vqmmc regulator found
[ 5.505582] mmc_host mmc2: Bus speed (slot 0) = 2343750Hz (slot req 400000Hz, actual 390625HZ div = 3)
[ 5.527673] dwmmc_rockchip 30020000.dwmmc: 1 slots initialized
[ 5.535112] ledtrig-cpu: registered to indicate activity on CPUs
[ 5.541456] hidraw: raw HID events driver (C) Jiri Kosina
[ 5.547702] usbcore: registered new interface driver usbhid
[ 5.553387] usbhid: USB HID core driver
[ 5.557969] ashmem: initialized
[ 5.563840] rknandbase v1.2 2018-05-08
[ 5.568190] rknand 30030000.nandc: rknand_probe clk rate = 150000000
[ 5.575014] ftl_init fffffffe
[ 5.578020] rk_ftl_init fail
[ 5.582236] usbcore: registered new interface driver snd-usb-audio
[ 5.588734] usbcore: registered new interface driver snd-ua101
[ 5.594931] usbcore: registered new interface driver snd-usb-caiaq
[ 5.601495] usbcore: registered new interface driver snd-usb-6fire
[ 5.607931] usbcore: registered new interface driver snd-usb-hiface
[ 5.614429] usbcore: registered new interface driver snd-bcd2000
[ 5.620667] usbcore: registered new interface driver snd_usb_pod
[ 5.626837] usbcore: registered new interface driver snd_usb_podhd
[ 5.633143] usbcore: registered new interface driver snd_usb_toneport
[ 5.638469] mmc_host mmc2: Bus speed (slot 0) = 37500000Hz (slot req 37500000Hz, actual 37500000HZ div = 0)
[ 5.644087] mmc2: new high speed MMC card at address 0001
[ 5.645350] mmcblk2: mmc2:0001 EMC08G 7.20 GiB
[ 5.645985] mmcblk2boot0: mmc2:0001 EMC08G partition 1 4.00 MiB
[ 5.646580] mmcblk2boot1: mmc2:0001 EMC08G partition 2 4.00 MiB
[ 5.647305] mmcblk2rpmb: mmc2:0001 EMC08G partition 3 4.00 MiB
[ 5.651447] Alternate GPT is invalid, using primary GPT.
[ 5.651568] mmcblk2: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10 p11 p12 p13 p14 p15 p16 p17 p18 p19 p20 p21
[ 5.691606] usbcore: registered new interface driver snd_usb_variax
[ 5.704085] u32 classifier
[ 5.706875] input device check on
[ 5.710541] Actions configured
[ 5.713987] Netfilter messages via NETLINK v0.30.
[ 5.718752] nfnl_acct: registering with nfnetlink.
[ 5.723668] nf_conntrack version 0.5.0 (15668 buckets, 62672 max)
[ 5.730877] Initializing XFRM netlink socket
[ 5.736228] NET: Registered protocol family 10
[ 5.742383] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 5.748390] sit: IPv6 over IPv4 tunneling driver
[ 5.754346] NET: Registered protocol family 17
[ 5.758916] NET: Registered protocol family 15
[ 5.763501] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 5.776182] Bridge firewalling registered
[ 5.780237] can: controller area network core (rev 20120528 abi 9)
[ 5.786565] NET: Registered protocol family 29
[ 5.791061] can: raw protocol (rev 20120528)
[ 5.795376] can: broadcast manager protocol (rev 20120528 t)
[ 5.801092] can: netlink gateway (rev 20130117) max_hops=1
[ 5.807331] Bluetooth: RFCOMM TTY layer initialized
[ 5.812328] Bluetooth: RFCOMM socket layer initialized
[ 5.817591] Bluetooth: RFCOMM ver 1.11
[ 5.821414] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 5.827385] Bluetooth: HIDP socket layer initialized
[ 5.832464] 8021q: 802.1Q VLAN Support v1.8
[ 5.836723] lib80211: common routines for IEEE802.11 drivers
[ 5.842461] [WLAN_RFKILL]: Enter rfkill_wlan_init
[ 5.847623] [BT_RFKILL]: Enter rfkill_rk_init
[ 5.852303] Key type dns_resolver registered
[ 5.857082] flash vendor_init_thread!
[ 5.857186] Error: Driver 'sc031gs' is already registered, aborting...
[ 5.857755] Registering SWP/SWPB emulation handler
[ 5.859070] registered taskstats version 1
[ 5.859087] Loading compiled-in X.509 certificates
[ 5.862368] Btrfs loaded
[ 5.863953] rga2: Driver loaded successfully ver:4.01
[ 5.864193] rga2: Module initialized.
[ 5.864231] pvtm list NULL
[ 5.865922] rk-vcodec 20030000.rkvdec: leakage=4
[ 5.865942] rk-vcodec 20030000.rkvdec: leakage-volt-sel=0
[ 5.866122] rk-vcodec 20030000.rkvdec: Failed to get pvtm
[ 5.866642] rk-vcodec 20030000.rkvdec: avs=0
[ 5.867158] rk-vcodec 20030000.rkvdec: probe device
[ 5.867831] rk-vcodec 20030000.rkvdec: drm allocator with mmu enabled
[ 5.869750] rk-vcodec 20030000.rkvdec: init success
[ 5.877046] asoc-simple-card hdmi-sound: i2s-hifi <-> 100c0000.i2s0 mapping ok
[ 5.881089] asoc-simple-card spdif-sound: dit-hifi <-> 100d0000.spdif mapping ok
[ 5.883963] hctosys: unable to open rtc device (rtc0)
[ 5.895852] vendor storage:20190527 ret = 0
[ 5.899509] ALSA device list:
[ 5.899522] #0: DW-I2S-HDMI
[ 5.899525] #1: SPDIF
[ 5.963824] flash vendor storage:20170308 ret = -1
[ 5.968979] ttyS2 - failed to request DMA, use interrupt mode
[ 5.984984] VFS: Mounted root (squashfs filesystem) readonly on device 179:2.
[ 5.997043] devtmpfs: mounted
[ 6.001224] Freeing unused kernel memory: 796K
[ 6.005760] This architecture does not have kernel memory protection.Debian GNU/Linux 10 localhost ttyS2
localhost login: root (automatic login)
sh: 1: cannot create /run/motd.dynamic.new: Read-only file system
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
-bash: cannot set terminal process group (-1): Inappropriate ioctl for device
-bash: no job control in this shell
root@localhost:~# [ 8.558106] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.I hope this log can be helpful on investigation,
thank you,
Hello, happy new year to you too!
Yes, you're the unlucky owner of these R29 boards which have this HDMI issue for which we don't have any solution yet, mostly because we don't have a board to study closely and the issue does not show any clue in logs and in device tree.
The issue is so difficult to track down that even LibreELEC images behaves the same.
Some people on the forum did some tests to help, but at the moment none succedeed.
Unitl we get an R29 board in our hands (and despite the forum leech above says, no people offered anything) we are still clueless.
-
On 12/29/2021 at 9:23 AM, ASD2003ru said:
I install armbian to eMMC, SDCard and External SSD on USB3.
After power on - os loaded from SDCard, if I reboot, loaded from SSD USB3.
If disable power, os loaded from sdcard.
How make sdcard for load from SSD USB3?
Thanks.
Don't put a bootable device in sdcard.
Why you need three armbian installations puzzles me, yet a cold reboot should not let USB3 boot since order is fixed and is sdcard -> USB -> eMMC
-
21 minutes ago, paradigman said:
You're right, the driver IC isn't that, it's the FD6551. I don't see this type in the linked repo among the supported ICs. Is it a hopeless thing or should I try the source of the FD650?
It is supported by openvfd driver
-
3 minutes ago, johnyp said:
No, in order to be able to install armbian again in must flash the android firmware back, after this emmc appears again in multitool. The emmc doesn't disappear after every reboot, it is random. If i understood correctly the bootloader doesn't initiate the nand. From bash shell did an fdisk - l and blkid and no drives shown. Can't figure out what hangs.
Me neither, but still if you don't provide more details I have no answers.
- Which board do you have?
- Logs (ie: the output of sudo armbianmonitor -u)
- Photos of the board
- DId you run rk322x-config or you didn't? Why you didn't? DId you follow the instructions or are you going the "lone wolf" way?
-
1 hour ago, johnyp said:
It seems that after reboot cpu doesn't see the emmc. If i try to use multiboot utility to restore an image it does not see the emmc either. Don't know how to explain better. The boot process drops to bash shell with an alert msg device uid not found.
So your eMMC appears back only when you do a cold reboot?
-
On 12/14/2021 at 12:41 PM, vkkindia said:
Does the fat partition of sdcard limits the file size to 4gb?!
Any idea how to uncompress it.
will it be safe to restore in tvbox using this backup in multitool.
Yes, the FAT partition is limiting the size of the backup to 4gb. Probably your box has some content in it that is not easily compressible and this results in a very large backup.
The problem is not of easy solution: except splitting the gzipped file every 4gb (which I don't know how it could be done automatically via gzip command), the other proper solution would be another partition type.
Other options are NTFS, ext4 or exFAT.
NTFS is cumbersome on some linux systems, especially with some very old distros which may not have the write capability.
ext4 is not available on windows
exFAT cuts away Windows XP, but there should be a separate MS driver for it. This could be the way to go, but in this case the same drill as ntfs applies, with the malus that exfat is much more recent, there are less tools and older distributions may not work as well.
-
On 12/16/2021 at 6:54 PM, callegar said:
@jock Sorry for getting back to the thread with a lot of delay, my laptop broke down... So it should be possible to use your tree as a basis to patch the current mainline and compile it (provided that the patches still apply cleanly?) I'll look into the armbian documentation to see if this can be done in an automatized way when a new stable release for the kernel series comes out... Just in case there is a quick recipe, please let me have a pointer to it ;-)
My branch is already kept aligned with mainline armbian often. It should be already possible to merge with mainline with no hassle at all.
It requires some minor tidy up though, since had to make some "shortcuts" to let rk3318 be seen as rk3328 in armbian scripts, and that needs to be fixed properly first before trying to merge: I'm sure that the trick works for rk3318, but I'm not sure that the trick does not break some other board.
-
On 12/12/2021 at 9:49 PM, karkow said:
No. It is possible without the GUI. You can enable it in the kernel settings.
I run libreelec with ssh enabled on this box.
I upload dmesg.log from libreelec in an earlier post.
Then you could transfer the uncompressed image via scp (or put in on the sdcard) and then use dd to burn it on the internal eMMC.
The command would be:
dd if=armbian.img of=/dev/mmcblk2 bs=512k oflag=direct status=progress
Indeed change armbian.img with the name of your image (or rename the image as well).
-
-
17 hours ago, karkow said:
Is there any other way to install armbian than multitool?
Yes, but you need to follow the same instructions as "restore backup" in first page.
17 hours ago, karkow said:Can multitool work without graphical mode for example via ssh?
Not yet: the multitool is based upon a very stripped down debian. Putting ssh into requires many other packages that would make way too bigger and mostly other packages require proper configuration (login, dhcp, etc...)
17 hours ago, karkow said:Is it possible to run armbian from SD card like on AMLogic?
It is not a "plug and play", you still require to erase the internal eMMC or install Armbian to run another installation from sdcard.
17 hours ago, karkow said:Is it possible to use libreelec with ssh to install armbian?
I guess in some convoluted way you could do it, but actually you need to enable SSH first in libreelec and you can do that only using the GUI, which is not available for you as long as HDMI does not work on your board
-
5 minutes ago, paradigman said:
Let me remind you that my main problem is that the HDMI output doesn't work and I still don't have a solution. If I read correctly, it is also a board with rk3228A like mine. Replacing the cable / monitor does not help.I know, but yet I don't have any such board to investigate the issue.
Some people solved changing HDMI cable, clearly it was not the same issue you have.
Feel free to donate such boards if you want to contribute and expect issues solved.
-
11 hours ago, karkow said:
Yes. Red lights and yellow blinking but no video on hdmi.
You get one of those boards which have no working HDMI output.
It is an unsolved problem right now, mostly because this never happened to any developer and the cause is unknown.
The usual suggestions are related to change the HDMI cable and change the TV/monitor to see if it is a problem of the board or not.
-
10 hours ago, RetroFan90 said:
is it possible to boot android from usb?
when i flashed the image with sdboot tool 1.69 it boots up partially and fails in short of no eMMC...
if i flash android to my 16gb usb thumbdrive and leave the micro sd card inserted so it can boot from usb....
android 9 is the first one i wanna try
You should ask Android people then.
AFAIK Android images have some hardwired settings that make it work only on internal eMMC.
These settings should be changed to make it work, but don't ask me: never dig into.
-
On 12/6/2021 at 3:40 PM, karkow said:
Multitool - not sure if it starts - no picture.
I tried with other .dtb files pulled from Amrbian Buster - no image.
Any suggestions please?
If the led is blinking, multitool booted. If led is steady, multitool didn't boot.
Can't say anything more about without logs (serial log would be ideal) or other infos.
Surely changing dtb won't help.
-
1 hour ago, MX10.AC2N said:
I was wondering if this could not be the infra-red receive led on the remote ?
No, it is led: Light Emitting Diode. The infrared receiver is not emitting anything, hence it is not a led.
Probably there are other variants of your board which have a led that must be react on remote controller activity.
Your board hasn't this led, but the chinese guy that wrote the dtb thought that the ir node may be left there.
1 hour ago, MX10.AC2N said:This is where I got it wrong, the user has to make these changes in a folder that does not exist with the rk3318 image you built ??
Do I need to create this folder /sys/class/leds and paste the triggers into it ?Does the value set in the linux trigger, default-trigger predominate over the others ? Cannot change this trigger value even if I am logged in as root.
That's not possible: /sys is a virtual filesystem exported by kernel itself.
Files in that directory does not really exist on partition but are generated by kernel.
This is what I get on my board (with a keyboard attached):
root@rk3318-box:~# cd /sys/class/leds/ root@rk3318-box:/sys/class/leds# ls input0::capslock input0::numlock input0::scrolllock working
And this is the content of working directory:
root@rk3318-box:/sys/class/leds# cd working root@rk3318-box:/sys/class/leds/working# ls brightness device max_brightness power subsystem trigger uevent root@rk3318-box:/sys/class/leds/working# cat trigger none usb-gadget usb-host kbd-scrolllock kbd-numlock kbd-capslock kbd-kanalock kbd-shiftlock kbd-altgrlock kbd-ctrllock kbd-altlock kbd-shiftllock kbd-shiftrlock kbd-ctrlllock kbd-ctrlrlock usbport disk-activity disk-read disk-write ide-disk mtd nand-disk heartbeat cpu cpu0 cpu1 cpu2 cpu3 [mmc2] mmc1 activity default-on panic mmc0 mmc3 rfkill-any rfkill-none rc-feedback bluetooth-power hci0-power rfkill0 rfkill1 stmmac-1:00:link stmmac-1:00:100Mbps stmmac-1:00:10Mbps
-
7 hours ago, RetroFan90 said:
how do i get this to boot off a usb external hdd or thumbdrive ? do i just flash it to the usb hdd and plug it into the usb 2.0 port ? or the usb 3.0 Port?
my emmc is cooked due to an error i made with the emmc clock ground button mod i did (i learned from that mistake and will improve the basic part of it.)but now the thing won't boot without a bootable sd card either in multitool
(no eMMC = No Good...)
but in armbian raw flashed to sd card, it boots up and begins the initial setup like username/etc...
i tried before 5.15.2 to boot exclusively from a usb hdd and i had no luck even when the eMMC is empty or inaccessible
(yet again boiling down to clock/gnd pcb track damage
the pad separated from the pcb due to too much heat caused from a crappy soldering iron and a loose wire pulled the track and dot and now the eMMC is kaput unless there is a way to get it working again...Grrr...!)
i've tried to get it to boot from the 2.0 port and nothing...
i tried the 3.0 port and still nothing with the card or the hdd...
i'm at a loss here.
USB boot is a peculiarity of the u-boot shipped with armbian.
Normally you need to install armbian on eMMC and you get both SD and USB boot.
Since your eMMC in not functional, the only way to do USB boot on your board is to keep an sdcard with u-boot only in the slot (ie: delete the armbian partition from sdcard) and the hdd in the USB 2.0 plug.
USB 3.0 is not supported yet in u-boot.
-
15 hours ago, markst said:
Any ideas?
No logs = no ideas. armbian-monitor -u and post here the link
Also you must stay stick to led-conf2, the one for your very specific board.
Other led-conf are not for your board and may prevent the system from boot.
SP6330 is a sort-of clone of AP6330, at least it should be. It happened in the past that the cover plate told something and the chip inside was another. Happens with chinese crap.
-
@markst I understand there is no blame, but the phrase"Technically, rockchip devices cannot be bricked" is followed by a detailed explanation about why this is true.
The whole paragraph is important to read, not just the first few words, in particular you can note:
QuoteIn most of the rk3318/28 boards, shorting the clock pin is difficult or impossible because eMMC are BGA chips with no exposed pins.
Pay double attention when burning something on the internal flash memory and always test first the image booting from the sdcard to be sure it works before burning anything in internal flash.
Don't know, but it looks to me there are enough warnings
-
22 hours ago, markst said:
I bricked the board using Armbian_21.05.1_Rk322x-box_buster_current_5.10.34_minimal.img I just uploaded it to emmc with the Multitool and did not first test by booting it off an sd card. The screen is now Black and I can no longer boot form SD. I even tried a usba-usba cable and nothing. The PC will not recognize the board connected. I do get a red led when powering the board.
My first flash of the emmc was using Armbian 21.11 - Debian Bullseye minimal - mainline kernel 5.15.2 Build date: 2021-11-12 and that worked no problem (except choppy video)
Well, putting the image for rk322x on rk3318/28 is definitely not a smart move. Never tried myself, now we know it definitely bricks the board
I bet your only chance is to go with maskrom mode, you have to find the eMMC clock pad on your board and put it to ground.
edit: ah, about videos in chromium, they will be choppy until a lot things required for multimedia are squared out. Can be next year or can be never, surely accelerated video in browsers is a complex task.
-
4 hours ago, ilmich said:
Hi all,
I've a box with rk3228b, nand, ddr2 etc etc and I'm using it as mediacenter with Libreelec 9.2 installed on sdcard.
The box recognize the nand, but I had never been able to install the operating system in it (tried with rkdeveloptool, dd and others but without succes).
Until today, when I've discovered this beautiful tool called multitool
I had to make a few small changes (basically removed offset and gpt creation in the nand flash code), but it works great.
So my question is, it's possible to add an option to write a generic image, in order to make this tool more useful!?
Last question, I think that the libreelec bootloader has some trouble when boot from NAND, but it's strange, because I've readed that the multitool one shoud be the same. It's true, or there are some changes that I can apply and retry?!
Thanks for your hard work.
Michele
Ciao Michele,
Multitool already burns generic images on flash, whatever flash it is.
stepnand procedure is for armbian only, because it carries u-boot SPL in place of rockchip miniloader.
Also the rockchip nand driver prevents the access to very first sectors of the flash, hence there is the need for offset and gpt with stepnand procedure.
Libreelec (legacy 4.4 kernel) carries the rockchip proprietary miniloader and thus can be burned on NAND using the regular "burn image to flash" menu option and it should work: multitool should suggest you to ignore to burn the bootloader sectors and you should answer yes.
Beware that you need the image with legacy 4.4 kernel: mainline kernel images have no nand driver and will never boot from nand.
-
1 hour ago, markst said:
Looks like I bricked my X88 pro 10. I flashed the wrong file to the eMMc now it will not boot at all. Even will not boot off the sdcard. Any idea how to unbrick? I read about unbricking but I do not have a clock pin exposed on the board
Don't know, you didn't even said what you did to brick the board. "Wrong file" is way too generic.
In the previous post you said you successfully installed armbian, now the board is bricked?
General unbrick instructions are in the first page, but you may need something specific for your board (see @Huafu posts)
-
@Huafu I saw the same labels on the top side on your board but could not find the pads/holes. Looking better at @markst's board, they are probably the four vertically aligned pads just a bit on the left.
I don't know which group is the right one, it may be those on the top side or those on the bottom side as well, so the only way to know is experimenting
Note also that you are not forced to connect the GND pin of the adapter to the GND pin on the board: you can connect it anywhere to the ground plane of the board. The shield of the ethernet/HDMI/USB connectors, for example, share the same ground plane. If you have a multimeter, you can easily discover that the GND pad and all the shields are just connected together.
Having those small pads is a bit of a hassle because soldering is not easy with them.
-
@calipzone That's cool you patched the kernel by yourself
Well, I don't really know how to proceed here... the old driver probably is for kernel 3.10.
It is possible that the rtl8723as is just a bit different than 8723bs, so inspecting the old driver may turn out to show what differences are there and try to patch the mainline kernel driver, but it is a work that require some knowledge, patience and time.
Surely I would suggest you to find the binary firmware of your rtl8723as and let the driver take it overwriting rtl8723bs.bin, so you are sure that the WiSoC gets the proper binary and all the missing pieces are in the kernel driver itself.
-
On 11/26/2021 at 7:58 PM, calipzone said:
Tried all *8723* but no effect.
Hmm I see no references to 024c:8723 in 8723bs mainline kernel driver and actually there are no references to 8723AS anywhere.
It should be nice to tweak the 8723bs driver to accept 8723as chip and see what happens
If you agree, I can do a minimal test image just to try and see what happens. Do you wish to conduct such test?
CSC Armbian for RK3318/RK3328 TV box boards
in Rockchip CPU Boxes
Posted
Well it should not be this way, maybe there is an issue with u-boot that needs to be investigated.
U-boot is programmed to have the fixed boot order which is always sdcard -> USB -> eMMC, so if it skips sdcard it behaves in the wrong way.
This could be an issue of your particular board, an issue from armbian or an issue from u-boot, thus needs to be investigated.
Just guessing, but it could also be that you have installed the same armbian image on sdcard and USB stick: boot happens telling the kernel the filesystem UUID and, if you installed the same armbian image on both media, rootfs on both sdcard and USB have the same UUID. The kernel takes one of them "at random", so it may boot from one or the other on every reboot.