apt update
apt upgrade
apt install linux-headers-current-rockchip
apt install zfs-dkms zfsutils-linux

This gets me linux-image-current-rockchip 25.8.1 (kernel 6.12.44-current-rockchip) and a module built from zfs-dkms 2.3.2-2~bpo12+2.  So far so good.  And then I ran

modprobe zfs.ko

and was rewarded with the following panic in the kernel's module loader:

[ 1128.728803] spl: loading out-of-tree module taints kernel.
[ 1128.859152] zfs: module license 'CDDL' taints kernel.
[ 1128.859178] Disabling lock debugging due to kernel taint
[ 1128.859401] zfs: module license taints kernel.
[ 1128.860612] 8<--- cut here ---
[ 1128.860624] Unable to handle kernel paging request at virtual address 5e4f51d0 when read
[ 1128.860641] [5e4f51d0] *pgd=00000000
[ 1128.860663] Internal error: Oops: 5 [#1] SMP ARM
[ 1128.865857] Modules linked in: spl(O) zram zsmalloc snd_soc_hdmi_codec snd_usb_audio snd_soc_simple_card binfmt_misc snd_soc_rockchip_i2s snd_soc_simple_card_utils snd_hwdep hantro_vpu snd_usbmidi_lib rockchip_vdec(C) snd_ump snd_soc_core r8723bs(C) rockchip_rga rockchip_iep snd_rawmidi v4l2_vp9 panfrost snd_pcm_dmaengine v4l2_jpeg rk_crypto snd_seq_device v4l2_h264 dw_hdmi_i2s_audio snd_pcm videobuf2_dma_contig gpu_sched dw_hdmi_cec v4l2_mem2mem snd_timer syscon_reboot_mode crypto_engine reboot_mode snd dw_wdt rk3288_gpiomem soundcore rockchip_thermal cpufreq_dt fuse gpio_keys realtek
[ 1128.924379] CPU: 3 UID: 0 PID: 20465 Comm: modprobe Tainted: P         C O       6.12.44-current-rockchip #1
[ 1128.935373] Tainted: [P]=PROPRIETARY_MODULE, [C]=CRAP, [O]=OOT_MODULE
[ 1128.942570] Hardware name: Rockchip (Device Tree)
[ 1128.947822] PC is at resolve_symbol+0xf8/0x368
[ 1128.952795] LR is at cmp_name+0x14/0x18
[ 1128.957081] pc : [<b01ac790>]    lr : [<b01ab960>]    psr: 90010013
[ 1128.964083] sp : f1f1dd68  ip : f1f1dca8  fp : f1f1ddbc
[ 1128.969919] r10: f1f1ded0  r9 : af1f81dc  r8 : af1f62ac
[ 1128.975755] r7 : af2489c0  r6 : af248c48  r5 : f1f1de48  r4 : af52c300
[ 1128.983049] r3 : 00000000  r2 : 5e4f51c0  r1 : 00000000  r0 : 00000001
[ 1128.990342] Flags: NzcV  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[ 1128.998318] Control: 10c5387d  Table: 0364c06a  DAC: 00000051
[ 1129.004737] Register r0 information: non-paged memory
[ 1129.010383] Register r1 information: NULL pointer
[ 1129.015639] Register r2 information: non-paged memory
[ 1129.021283] Register r3 information: NULL pointer
[ 1129.026538] Register r4 information: 201-page vmalloc region starting at 0xaf514000 allocated at load_module+0x744/0x1b34
[ 1129.038795] Register r5 information: 2-page vmalloc region starting at 0xf1f1c000 allocated at kernel_clone+0xac/0x340
[ 1129.050759] Register r6 information: 5-page vmalloc region starting at 0xaf247000 allocated at load_module+0x744/0x1b34
[ 1129.062820] Register r7 information: 5-page vmalloc region starting at 0xaf247000 allocated at load_module+0x744/0x1b34
[ 1129.074881] Register r8 information: 3-page vmalloc region starting at 0xaf1f6000 allocated at load_module+0x744/0x1b34
[ 1129.086942] Register r9 information: 3-page vmalloc region starting at 0xaf1f6000 allocated at load_module+0x744/0x1b34
[ 1129.099003] Register r10 information: 2-page vmalloc region starting at 0xf1f1c000 allocated at kernel_clone+0xac/0x340
[ 1129.111062] Register r11 information: 2-page vmalloc region starting at 0xf1f1c000 allocated at kernel_clone+0xac/0x340
[ 1129.123120] Register r12 information: 2-page vmalloc region starting at 0xf1f1c000 allocated at kernel_clone+0xac/0x340
[ 1129.135179] Process modprobe (pid: 20465, stack limit = 0xf191b45c)
[ 1129.142183] Stack: (0xf1f1dd68 to 0xf1f1e000)
[ 1129.147050] dd60:                   b01abd14 af52c3fc 00000000 f26174f8 00000100 af2489c0
[ 1129.156193] dd80: 00000000 af1f62ac 00000000 e7df2e2d b4795600 00005a2b f26174f8 f26bcb48
[ 1129.165334] dda0: af6dc2b4 00000000 0006a3d0 f1f1ded0 f1f1deb4 f1f1ddc0 b01ae384 b01ac6a4
[ 1129.174476] ddc0: b02f81d4 b02f2340 f26bcbc0 00000000 00000003 004d6d38 00000000 00000001
[ 1129.183618] dde0: 00000000 b4795600 f26bc508 00000000 af52c3fc 0000001e 00000000 b132bdb0
[ 1129.192759] de00: 00000000 af52c300 af52c300 b1bd8b84 af52c30c b1c8a1a4 00000000 00000001
[ 1129.201901] de20: b5b7e600 f26bcbc0 00459bc0 00459bc0 f1f1de5c f1f1de40 00459bc0 00000000
[ 1129.211041] de40: 7fffffff b5b7e600 00000000 00000000 00000000 00000000 00000000 00000000
[ 1129.220182] de60: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[ 1129.229324] de80: 00000000 e7df2e2d 00000002 00000000 b5b7e600 004d6d38 b5b7e600 b1c8a5b4
[ 1129.238465] dea0: bbba0708 b5b7e600 f1f1df3c f1f1deb8 b01aeedc b01ad31c f1f1decc 7fffffff
[ 1129.247607] dec0: 00000000 00000002 00000000 f2263000 f2576523 f24d6640 f2263000 00459bc0
[ 1129.256749] dee0: f26bc508 f26bc388 f25e9c54 0008272c 000a7eac 000a5a90 000c5d78 00000000
[ 1129.265890] df00: 000a5a80 00000028 00000029 00000016 00000000 0000001e 00000000 e7df2e2d
[ 1129.275031] df20: 00000001 000000f6 b1c8a1a4 00000001 f1f1dfa4 f1f1df40 b01af2ac b01aee50
[ 1129.284172] df40: 00000000 00000000 004d6d38 b1c8a58c bbba0708 00000000 b1c8a58c 00000000
[ 1129.293314] df60: 00000000 f1f1df64 f1f1df64 fffffffc 00000000 e7df2e2d 000000c0 004d8ad8
[ 1129.302456] df80: 00fa74bc 22b57200 0000017b b01002c8 b4795600 0000017b 00000000 f1f1dfa8
[ 1129.311598] dfa0: b0100060 b01af108 004d8ad8 00fa74bc 00000004 004d6d38 00000000 004d86bc
[ 1129.320738] dfc0: 004d8ad8 00fa74bc 22b57200 0000017b 00fa7520 00000000 00000000 004d50bc
[ 1129.329879] dfe0: aeb5c0e8 aeb5c0d8 004cf149 a6bc3002 40070030 00000004 00000000 00000000
[ 1129.339018] Call trace: 
[ 1129.341845]  resolve_symbol from load_module+0x1074/0x1b34
[ 1129.347983]  r10:f1f1ded0 r9:0006a3d0 r8:00000000 r7:af6dc2b4 r6:f26bcb48 r5:f26174f8
[ 1129.356735]  r4:00005a2b
[ 1129.359559]  load_module from init_module_from_file+0x98/0xd4
[ 1129.365987]  r10:b5b7e600 r9:bbba0708 r8:b1c8a5b4 r7:b5b7e600 r6:004d6d38 r5:b5b7e600
[ 1129.374738]  r4:00000000
[ 1129.377562]  init_module_from_file from sys_finit_module+0x1b0/0x310
[ 1129.384670]  r6:00000001 r5:b1c8a1a4 r4:000000f6
[ 1129.389826]  sys_finit_module from ret_fast_syscall+0x0/0x54
[ 1129.396154] Exception stack(0xf1f1dfa8 to 0xf1f1dff0)
[ 1129.401798] dfa0:                   004d8ad8 00fa74bc 00000004 004d6d38 00000000 004d86bc
[ 1129.410939] dfc0: 004d8ad8 00fa74bc 22b57200 0000017b 00fa7520 00000000 00000000 004d50bc
[ 1129.420079] dfe0: aeb5c0e8 aeb5c0d8 004cf149 a6bc3002
[ 1129.425724]  r10:0000017b r9:b4795600 r8:b01002c8 r7:0000017b r6:22b57200 r5:00fa74bc
[ 1129.434475]  r4:004d8ad8
[ 1129.437302] Code: ea00004a e5922000 e1520006 0a000047 (e5923010) 
[ 1129.444162] ---[ end trace 0000000000000000 ]---

I have been unable to find debug symbols or a way to get an objdump of the loaded kernel (probably I am just missing something).  Please advise what more I can tell you to be useful.

I am unable to run armbianmonitor; after the above, lsmod hangs, and upon boot, the machine attempts to load zfs.ko which again crashes as above and userspace is pretty direly stuck.

FWIW, I am happily running ZFS on a Tinkerboard with an older system, specifically linux-image-current-rockchip 24.11.1 (which is kernel 6.6.63-current-rockchip) and zfs-dkms 2.2.2-0ubuntu9.1.

IT'S FINALLY HERE...

THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION

After two years of using a separate script to enable the multimedia features in RK3288/3328 Legacy Kernel, the whole framework has been incorporated to the official Armbian packaging system. The choice distro for this integration is Debian Buster (see FAQ at the end of this post about the reasons).

I. Installation

1. Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method.
2. Install the complete multimedia solution with

   sudo apt update && sudo apt upgrade
   
   sudo apt install media-buster-legacy-tinkerboard --install-recommends
   ## Or ##
   sudo apt install media-buster-legacy-rk3328 --install-recommends

   The switch "--install-recommends" will add the whole Kodi binary addons collection (retro-gaming cores, music visualizations, screensavers, additional media decoders/encoders, vfs, etc.), plus the GLES-to-OpenGL wrapper "gl4es".

II. Features

1. Accelerated GLES/EGL X desktop: No action needed.
2. Accelerated Chromium, with WebGL and video display acceleration: No action needed
3. Desktop video player capable of smooth 4K HEVC-HDR: Use the "Rockchip Gst Player" from the Multimedia menu, or choose it with right-click on the media file. Command-line 4K playing is also possible with "gst-play-1.0 --videosink=kmssink".
4. RKMPP-accelerated MPV: Use normally for standard operation (windowed with mouse-operated GUI). For fullscreen, keyboard-operated mode, use the command line switch "--gpu-context=drm" (this will allow you to play smooth 4K).
           - See instructions below, in the next post, for playing Youtube videos up to 4k with this MPV.
5. ISP Camera with real-time h.264/1080p HW encoding (RK3288 only): Using the Gstreamer Plugin. Check this wiki for instructions on how to use it. Most of it applies to Armbian, except for the selection of ov5647/imx219 camera, which must be done using DT overlays.
6. OpenCL 1.2 support (RK3288 only): It will be fully functional, no further action needed. You can download some tests and examples from this link.
7. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from Light DM menu as your user account: 
    
   Alternatively, you can also run it as a system service with these command lines:

   sudo systemctl disable lightdm
   sudo systemctl enable kodi-gbm
   sudo reboot

    

8. Full collection of Kodi binary add-ons: Includes retrogaming cores, media encoders and decoders, PVR, screensavers, vfs and audio visualizations. They are all installed with the package "kodi-addons-full", but are disabled by default. They need to be enabled individually within the Kodi GUI.
9. OpenGL 2.1 support through the gl4es wrapper: It is installed with the package "gl4es", with no further action needed.

III. Sources

This is the list of the sources used for the packages:

IV. FAQ

• ¿Why did you use Debian Buster as a base for this implementation?
  It was the most appropriate for several reasons. Upstream Rockchip-Linux developers use Debian buster, so the software could be ported with less modifications than if we chose a different distro. Besides, it is a completely stable distro, unlike Bullseye, which is a moving target as of today. It also has Chromium as a package, unlike Focal that uses snap instead. For last, it has a good backports repo, with several libs that would otherwise need to be compiled and maintained if we chose, for example, Focal.
   
• ¿Why Legacy instead of Mainline?
  This is an implementation based on the vendor's BSP kernel. It has been tested and is reliable, which many people will prefer rather than having a bleeding-edge, less stable implementation. In addition to that, Mainline upstream multimedia support is still a WIP, and lacks many features that are only present on Legacy kernels.
   
• ¿Will you add new features to this implementation?
  No, this implementation will only receive bug fixes if necessary. From now on, all multimedia work will be focused on Mainline and recent distros (like Focal or Bullseye). All new features will go there.

I’m using an ASUS Tinker Board (RK3288, 2 GB, released in 2017). Since this board is quite old and we are now in 2025

I want to run the latest stable Armbian and develop a Python application using I²C, UART, PWM, and GPIO pins.

Which Armbian image and kernel branch (current or edge) is the most stable for this board?

Are there any specific steps or adjustments needed due to its older hardware?

Thanks!

Can anyone point me in the right direction for an Armbian image that would allow audio recording over the 3.5mm jack? I'm trying to record audio over the 3.5mm jack. This works on a previous installation, but I'm trying to update to a curreent Armbian.

Running Tinkerboard S R2.0 and this image:
Armbian_25.2.1_Tinkerboard_noble_current_6.12.13_xfce_desktop.img

Playback works record does not. 

Works:

aplay /usr/share/sounds/alsa/Side_Right.wav -D hw:CARD=Audio,DEV=2

None of the following arecord commands work:

arecord --vumeter=mono -D hw:CARD=Audio,DEV=0 -f S16_LE -c 2 -d 5 /tmp/t.wav
arecord --vumeter=mono -D hw:CARD=Audio,DEV=1 -f S16_LE -c 2 -d 5 /tmp/t.wav
arecord --vumeter=mono -D plughw:CARD=Audio,DEV=0 -f S16_LE -c 2 -d 5 /tmp/t.wav
arecord --vumeter=mono -D plughw:CARD=Audio,DEV=1 -f S16_LE -c 2 -d 5 /tmp/t.wav
arecord --vumeter=mono -D default:CARD=Audio -f S16_LE -c 2 -d 5 /tmp/t.wav
arecord --vumeter=mono -D sysdefault:CARD=Audio -f S16_LE -c 2 -d 5 /tmp/t.wav
arecord --vumeter=mono -D front:CARD=Audio,DEV=0 -f S16_LE -c 2 -d 5 /tmp/t.wav

I advise that I'm a noob.

I have a MKS TS35 v2.0, that uses ST7796/ILI9341 (or ILI9486, I think) for LCD and ADS7843E for touch, and now I want to use it in my Asus Tinker Board for Klipper. I know that it's possible because exists one HOW-TO of this for Raspberry Pi 3b+. I wanna that someone, with knowledge in Armbian and Tinker Board, build (adapt) this DTS on GITHUB https://github.com/fbeltrao-br/mksts35/blob/main/mksts35v2.dts. I want this especially because the pinout https://github.com/fbeltrao-br/mksts35/blob/main/pinout.png, that is more easy for me understand what pins I need connect. 

sorry just switched my box for the first time in a long time. i was wondering if i can seamlessly upgrade to the latest Armbian without losing hardware acceleration included in RK3288/RK3328 Legacy Multimedia Framework or is it only for Debian Buster? is kodi-gbm (RKMPP) still viable? is there a compatible version much higher than 18.9 "Leia"? thanks!

I tried to activate the SPI interface on a Tinkerboard2S. I used the last Armbian version (Armbian_community_25.2.0-trunk.110_Tinkerboard-2_bookworm_current_6.6.63_minimal).

I edited the /boot/armbianEnv.txt and add the overlays, I found different parameters and all doesn't work, I tried:

• overlays=spi0 spi2
• overlays=spi-spidev
  param_spidev_spi_bus=0
• and via armbian-config:
  fdt_overlays=rockchip-rk3399-spi-spidev

But with all approaches I didn't get a /dev/spi* device.

Any ideas?

TIA

Hello,

the latest armbian image (Bookworm_current_xfce) with kernel 6.6 has issues with the winstar tftp 5 inch hdmi display that I am using.

Bootloader (u-boot) is showing but after loading the  kernel message, screen goes blank.

The screen resolution is 800x480, in attach the pdf specs.

Info: the official asus image with kernel 4.4 works, but it is not an option for me as I don't want to use debian buster.

Please help.

Thank you very much.

Bogdan

WF50FSYFGDHNV.pdf

I see that Amrbian turns off image output (launches screensaver as a black screen) after 10-15 min, but I could not find out where those settings are stored. Please help to find out.

Hi! 
When I try to access PWM via procedure described here

https://tinker-board.asus.com/forum/index.php?/topic/15132-direct-gpio-access/

I see that

Quote

pwmchip2

&

Quote

pwmchip3

are not present (although they should be)

I can see pwmchip0, but I don't understand what GPIO it is.
Following ASUS docs from GitHub

https://github.com/TinkerBoard/TinkerBoard/wiki/User-Guide#gpio-config-table-for-tinker-board-s--tinker-board-s-r20

GPIO32 and GPIO33 should be here:

PWM:/sys/class/pwm/pwmchip3

and PWM:/sys/class/pwm/pwmchip2

But those directories are not present.

root@tinkerboard:~# ls -la /sys/class/pwm/
total 0
drwxr-xr-x  2 root root 0 Oct  7 11:47 .
drwxr-xr-x 65 root root 0 Jan  1  1970 ..
lrwxrwxrwx  1 root root 0 Oct  7 11:47 pwmchip0 -> ../../devices/platform/ff680000.pwm/pwm/pwmchip0

My Armbian Env is:

verbosity=0
bootlogo=true
console=serial
overlay_prefix=rockchip
overlays=i2c1 i2c4 spi2 spidev2 uart1 uart2
rootdev=UUID=7a71009a-a5f6-439f-a2d3-38574c1ea09b
rootfstype=ext4
extraargs=vt.global_cursor_default=0 quiet splash plymouth.ignore-serial-consoles systemd.unified_cgroup_hierarchy=0
stdout=serial
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

The desktop does not respond to 2 different keyboards I have tried. If I use a mouse to open Terminal, the keyboards do work in the Terminal.

If I try to open Web Browser in the applications menu, I get a window saying "Failed to execute Web Browser. Input/output error."

apt update and apt upgrade do not fix the problem.

Here is a log: https://paste.armbian.com/onikesixam

It continued to reboot from some kernel panic, which I forgot to take note; but since it hadn't been upgraded to jammy, I took the opportunity to do it. Pluging in the uSD card (with the newly released jammy version, just downloaded here), power, and all (including the ethernet cord!!), first boot I have to create my user (which, for some reasons refuses to let me put my usual fr3d tag, obliging me to go with the common "fred", but OK ), then all the trivial steps to set my locale settings. Then  the beautiful armbian desktop penguin greats me. 

Nice now some more little custumisations and I'm ready to go, or so I thought; the wireless connection doesn't work, it fails to connect (and it is only 2m away from my router), it continues to ask me for the password, which has was not changed in the meantime.

I tried 

nmtui

But nothing change, well I only got the funny message 

Quote

Secrets were not given.......

I also tried to fix it by looking into 

armbian-config

but nothing, after the third time, I get the same message about "secrets" not being given.

I also tried installing "non-free" package, hoping it would find missing piece of software/firmware/driver to solve my issue, but as you can immagine it doesn't.
And I also found out the "browser" can't be opened, as it gives me some kind of Input/output errors, yet if I scroll down to the internet program section, I can open firefox, and it seems (only used it for 1h, more or less) to be working properly.
Would some good soul help me find a solution??

As soon as I'm able to send some screenshots i'll do it.

Thanks in advance,

fr3d

I installed Armbian 23.11 Bookworm Kernel 6.1, Size: 482Mb, Release date: Nov 30, 2023. After installation, a CH340 based board was connected to my original Tinkerboard and recognized. Subsequently, I used armbian-config to provide the default desktop (Cinnamon flavor). Thereafter, the CH340 board is incompletely recognized. Specifically, no device is presented as /dev/ttyUSB?. The device appears in the list from lsusb, the kernel module ch341.ko loads, but no device in /dev. The forum search shows a previous instance of a similar issue many years back. I attempted to build the driver from wch.cn, but the kernel sources pulled from armbian-config were for the Linux tinkerboard 6.1.63-current-rockchip kernel and,so, a mismatch for the running kernel.

uname -a
Linux tinkerboard 6.1.68-current-rockchip #1 SMP PREEMPT Wed Dec 13 17:39:30 UTC 2023 armv7l GNU/Linux

lsusb |grep -i ch34
Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics CH340 serial converter

lsmod | grep -i ch34
ch341                  20480  0
usbserial              28672  1 ch341

• Tinkerboard (rev 1?) has 2 USB devices (from RK3288's internal ports), one for the Realtek HD audio, and one for the 4 USB ports (Genesys 4-port USB hub). 
  • while i have no info for the HD audio, the hub is powered via the 5V lines (noted as V5 pin in the datasheet). my mistake would be not checking if all the 5V power lines are shorted, or it's just connected to the hub. there's an option to NC the pin if using an external regulator (say, the RK808 power management chip?)
• The LAN is separated to the hub and instead directly connected to the RK3288
  • At least the datasheet for RK3288 says. no pinouts whatsoever so i think this is all inside the chip

I noticed this strange behavior across unique setups (LAN connected, 1x keyboard-usb combo, and even 1x-3x USB SATA devices (power separated since these are 3.5 inch drives))

• Sometimes the USB hub disconnects for no particular reason while turned on
  • "disconnects", i mean, when SSH over the device the `lsusb` appears nothing but the Realtek devices. the Genesys hub isnt listed.
  • i wouldnt associate it with power considering that the whole board only consumes 0.7A Max (on all those setups) when connected to an ammeter
  • this carries over across reboots and wont reset until power was disconnected off the wall.
    • i need to rest the board for a while (like several minutes) without power and peripherals. probably a polyfuse triggering and resetting?
  • this also happens on occasions when i plugged failing drives. 
    • i was thinking if it has to do with `usb 1-1 disconnected` where the kernel restarts the USB devices on General Failure on the SATA commands. but it's a weird behavior that it restarts the whole hub rather than the device itself. 
• Sometimes the LAN disconnects as well simultaneously
  • cant SSH over the LAN, only via WiFi.
  • this can be resetted via a reboot, unlike the USB hub.

any help would be appreciated, or tips to recreate this. i was thinking of using USB load testers as a stress test. a limitation of mine is also me not providing /var/log/syslogs on these events considering i cant access the device when this happened.

I need to make sure that my GPIOs remember the last state when my Tinkerboard reboots. Is it possible to modify the bootloader and avoid GPIO.cleanup?

If yes, then how?

Thanks!

I am using an HDMI switch. I have noticed that TinkerBoard Armbian, displays fine the UBOOT text/logo but after that, the HDMI shows no signal/image

If I connect the HDMI cable directly from the board to the monitor all is ok.

What would be the reason or setting to be changed so TinkerBoard HDMI port can output display either case (hdmi direct to over a hdmi switch)

tx in advance

Is it possible to mount read-only /boot while leaving the rest of FS writeable? I know about Overlay root FS, it's OK, but I need to protect only boot.

Please help to mount it properly.

Thanks!

And where the patch should be placed?

There are many folders in /home/max/build/patch/u-boot/

Thanks!

root@tinkerboard:~# sudo apt install chromium-browser
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
  chromium-browser
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 0 B/49.2 kB of archives.
After this operation, 165 kB of additional disk space will be used.
Preconfiguring packages ...
(Reading database ... 41567 files and directories currently installed.)
Preparing to unpack .../chromium-browser_1%3a85.0.4183.83-0ubuntu2.22.04.1_armhf.deb ...
=> Installing the chromium snap
==> Checking connectivity with the snap store
==> Installing the chromium snap
error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount:
       /tmp/syscheck-mountpoint-3456514169: unknown filesystem type 'squashfs'.
dpkg: error processing archive /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu2.22.04.1_armhf.deb (--unpack):
 new chromium-browser package pre-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 /var/cache/apt/archives/chromium-browser_1%3a85.0.4183.83-0ubuntu2.22.04.1_armhf.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

This only happens in Armbian 23, in Armbian 22 both Ubuntu/Debian images everything worked well.

Any way to solve without rebuilding image?

Hi,

I'll install OpenMediaVault and Nextcloud on a tinkerboard and I would like to know if there is any advantage on run system on SATA / USB in this case and if it is possible to do this on tinkerboard since it was not clear for me on the docs.

Thank you

So I want to follow the recommended method and power it through the GPIO pins. I am considering using this or this powersupply. (I realize 10A on the second one is overkill for the tinkerboard, but the price difference from the 3A rated one is minimal and I could find some other use for it in the future). Is any of this a reasonable choice? TonyMac32 warns not to exceed 5.5v but both list a voltage protection range higher than that.

TonyMac32 also mentions using a zener diode and a capacitor to filter power and protect the board from overvoltage. While I have a basic understanding of electronics, I don't know how to make that circuit or the exact values of the components that I would need. Could someone elaborate on how to make this circuit and the difference it would make over plugging straight to the GPIO pins?

Thank you

1. ok from the get go the board powers (not load tested, just power through and run kodi-gbm UI) from 3.4V to 6.2V. undervolting or overvolting it doesnt shuts itself down (no red light), then bringing back to operating voltages boots the board up
   
   also take not that operating voltages for RK808 was 2.7V to 5.5V. the missing 0.7V was probably the diode drop people are talking about. maybe? without a multimeter (only using the power supply's voltmeter-ammeter) i can't check it that much. but i'm fine that it has wide range of operating voltages.
2. on all observed voltages, 3A seems to be the max current. it needs to be sustained though. also full load without peripherals (and HDMI, HDMI seems to be active than passive) is observed 2.3-2.5A. booting up the board needs about 0.7A to keep on going
   
   this would probably contradict as well the "increase voltage to 5.25 or smthing" given that no matter how many volts you put into it, it would only use 3A.
3. weirdly (since this contradicts the block schematics from tinkerboard), #1 and #2 are observed in both USB and GPIO with no difference (significant or not) under load.
   
   it's weird since
   3.1. if USB lines were protected, there should be a diode drop *only* on USB lines. but this was seen on GPIO as well.
   3.2. some claims microUSB only has max 2.5A but this is not seen in this case: the setup sustained 2.7A going 2.9A.
   
   also, powering both GPIO and USB with the same power block doesnt seem to affect stability at all (still hard limits at 3A.)

so with that, there are few suggestions for powering the board as well (and minor observations. opinionated parts ahead)

• people talking about overvolting or undervolting the power rails doesnt really help at all at slightest. it'll still top at 3A. what overvolting could help were powering via USB peripherals, but i wouldnt recommend it plugging straight given the fact that 2.5A on full load? you only have 0.5A to spare on heavy load.
  
  get a usb y splitter (tape over the USB power lines to the board. idk why but i have usb resets whenever i dont have them. then again plugging a hard drive in there shouldnt be happening in the first place)
• the raspberry pi 3B+ adaptor (5.25V, 2.5A)? good enough actually! as long as it can deliver 5V across the device, AND as long as you dont have power heavy devices on it. it doesnt matter that much so long as your USB cable can handle phone-charger level of amps. rk3288 was designed with mobile phones in mind. it'll always power at 3.7V. i always having issues when im using a cable that can only do 0.5A across it. no can do.
  
  probably for me, but this is why you dont need to be hung with the minor details. starting from this, im wracking my brain around if tinkerboard was sensitive to power drops (like 5.1v or 5.2v would show stability improvements) but nope! just chuck it right in, it'll be fine. just check your connections and stuff.
• powering through the GPIO pins is recommended of course, but it's an overkill. probably the reason for it was most USB chargers only go 2A max and that would underpower the tinkerboard, doing  boot loops instead of starting correctly. then again YMMV: my place has 3A or 5A chargers everywhere. and with the introduction and interests of fast chargers, you'll find chargers (and cables) that can deliver more than you expect.
• on sidenote on powering through the GPIO: PLEASE GET YOUR GAUGES RIGHT. i powered it via the ATX FDD (remember those?) connector, with 12V pin removed. it turns out for some reason its max current is 1A and its just thin flimsy as hell. get a thicker wire.
  
  it didnt drop the current (thankfully) but the wire became so warm to touch, it's weird. i wouldnt wanna run this on full load. at least i didnt get burned wires. cooling fan helps a lot
• also you cant bypass that 3A limit. that's 3A total, both GPIO and USB inputs. even powering both USB and GPIO (like that one person suggested) doesnt really do anything. you wouldnt get that much power in, but at least you can protect your wires?
  
  which is weird since block schematics shows GPIO and USB has different lines? so it should have different protections and stuff. a multimeter can help see if those inputs are shorted (GPIO vs microUSB vs peripherals) but i dont have one at the moment
  
  i would also like to measure the voltage across the peripherals if any load situations will lead to undervolting the outputs, but i dont have a USB tester at the moment.
• RK808 seems to be programmable but interfacing with it is outside of my skill set. any help would do

i hope this post helps everyone well. no one uses these boards anymore except for niche use cases but i still enjoy it. i hope in the future i can get myself a huge NAS server with an RK3588S on it. kinda lonely to be honest

stress testing the board with stress -c 4 doesn't bring the board into shutdown, but logging in to kodi-gbm or using graphical interface? it brings instability all of a sudden. there's no inherent pattern from the shudowns except when i launch kodi or access some files (emby transcoding doesn't cause any instability). anything outside the text mode should cause it to shutdown. weirdly enough, when i removed the USB peripherals (2xUSB HDD, own power supply for both cases) the instability worsens and doesn't boot or sometimes reboot cycle after fsck.ext4 on startup.

this board was powered by an ATX PSU (using the FDD connector). measured 5.1V across it. is there a possibility i tripped some overcurrent protection or something?

any suggestions how to fix it? can i actually power it using a separate usb 5v/3a connector as stated here? https://github.com/berinc/Asus-Tinker-Board

i don't have any troubleshooting tools at the moment. i don't have a usb tester or a multimeter (leads broke.)

thanks for your help.

i installed Armbian 22.11 Jammy minimal image for headless console only usage. 

 uname -a
Linux tinkerboard 5.15.80-rockchip #22.11.1 SMP PREEMPT Wed Nov 30 11:05:19 UTC 2022 armv7l armv7l armv7l GNU/Linux

i installed teamviewer and if device rebooted with hdmi connected, i am able to use  teamviewer and teamviewer shows shell output

but when rebooted without hdmi cable connected, teamviewer seems working on device , but cant connect it.. 

here is teamviewer info 

 TeamViewer                           15.37.3  (DEB)

 TeamViewer ID:                        1374960804

 teamviewerd status                   ● teamviewerd.service - TeamViewer remote control daemon
     Loaded: loaded (/etc/systemd/system/teamviewerd.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2022-12-23 13:40:52 +03; 6min ago
    Process: 1659 ExecStart=/opt/teamviewer/tv_bin/teamviewerd -d (code=exited, status=0/SUCCESS)
   Main PID: 1758 (teamviewerd)
      Tasks: 18 (limit: 4734)
     Memory: 13.3M
        CPU: 6.351s
     CGroup: /system.slice/teamviewerd.service
             └─1758 /opt/teamviewer/tv_bin/teamviewerd -d

Dec 23 13:40:47 tinkerboard systemd[1]: Starting TeamViewer remote control daemon...
Dec 23 13:40:52 tinkerboard systemd[1]: teamviewerd.service: Can't open PID file /run/teamviewerd.pid (yet?) after start: Operation not permitted
Dec 23 13:40:52 tinkerboard systemd[1]: Started TeamViewer remote control daemon.

so what i tried on armbianEnv.txt with several combinations (even one by one and with different combinations)

setenv video-mode sunxi:640x480-24@60,monitor=dvi,hpd=0,edid=0

setenv videoconfig "drm_kms_helper.edid_firmware=edid/1024x768.bin"
setenv HPD "false"
setenv vout "dvi"
saveenv

and recompiled boot.cmd with: 

sudo mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr

still cant connect teamviewer without hdmi cable.. 

so what am i missing? or how to do it properly on tinkerboard with armbian?

ps: it was easy on raspberrypi , just change resolution in raspi-config and save.. teamviewer started to work.. 

thanks.. 

sudo docker run -d --name hello hello-world

b22653867370a24ab900fc077f50fc6b05bb6eb986906caee88250fc9e9f5433 docker: Error response from daemon:
failed to create shim task: OCI runtime create failed: runc create failed: unable to start container
process: error during container init: error setting cgroup config for procHooks process:
bpf_prog_query(BPF_CGROUP_DEVICE) failed: function not implemented: unknown.

docker --version
Docker version 20.10.21, build baeda1f

uname -a
Linux tinkerboard 5.15.74-rockchip #22.08.6 SMP PREEMPT Tue Oct 18 06:40:37 UTC 2022 armv7l armv7l armv7l GNU/Linux

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.1 LTS
Release:	22.04
Codename:	jammy

Following the procedure from

https://docs.armbian.com/User-Guide_Advanced-Features/

at the point where it requires:

2. Copy /etc/network/interfaces.hostapd to /etc/network/interfaces

i realize the file interfaces.hostapd is missing, even though hostapd is installed

hostapd is already the newest version (3:2.10-6~armbian22.02.3+1)

I manually created the file with the following content even though I'm not sure if that's correct (as referred in one post on the forum):

auto lo br0
iface lo inet loopback

allow-hotplug eth0
iface eth0 inet manual

allow-hotplug wlan0
iface wlan0 inet manual

iface br0 inet dhcp
bridge_ports eth0 wlan0

/etc/network/interfaces.hostapd remains in there without issues, but at the moment of copying its info to /etc/network/interfaces and rebooting, the SBC won't let me log in through ssh.  In order to do so i have to comment the added lines to gain back access.

Any pointers on how can i finish the process to create the hotspot?

Thanks.

I have installed "Armbian_22.08.7_Tinkerboard_bullseye_current_5.15.74_minimal.img.xz" on a Tinkerboard (no S, with RK3288).

I have tried to set the output of some header pins without success. I used both "sysfs" and "gpiod" (which uses char-devices).

Test procedure, e.g. for pin 36 (gpio223):

# echo "223" > /sys/class/gpio/export
# cat /sys/class/gpio/gpio223/direction 
in
# cat /sys/class/gpio/gpio223/value 
0

# echo "out" > /sys/class/gpio/gpio223/direction
# cat /sys/class/gpio/gpio223/direction
out
# echo "1" > /sys/class/gpio/gpio223/value
# cat /sys/class/gpio/gpio223/value 
0
# echo "0" > /sys/class/gpio/gpio223/value
# cat /sys/class/gpio/gpio223/value 
0

The example is for the pin36 is grounded by an resistor with 1kOhm. If the resistor is switched to 3.3V all read values are go to "1".
The read values match the measured voltage (~0V for "0", ~3.3.V for "1").

The same behaviour for "gpioset 7 7=0". After this, the "gpioinfo 7" lists the line as output, like expected. Only the voltage remain unchanged (gpioget will change the line to input).

With TinkerOS the same test is working (with sysfs only, because old Kernel 4.4.).

Afterwards I have also tested some (or all) different options, like "sudo gpioset -m wait -D push-pull -B pull-down gpiochip7 7=0". But no success.

Have I something missed to set up in the device tree? I have enabled i2c1 & i2c4 and disabled all other features (uart, spi and w1-gpio etc.) by usage of armbian-config.

Thanks for your help in advance

Hello

I cannot enable the Bluetooth on Tinkerboard device. Tried latest image, fresh install.

I've opened the question on StackOverflow: https://superuser.com/questions/1698728/cannot-enable-bluetooth-on-tinkerboard-armbian

It contains technical details.

The latest what I've found so far is it could be related to Kernel compilation flags:

# Extract from the /boot/config-5.10.60-rockchip

CONFIG_SERIAL_DEV_BUS=y
CONFIG_BT_HCIUART_3WIRE=y
CONFIG_BT_HCIUART_SERDEV=y
# CONFIG_BT_HCIUART_RTL - is not set
# CONFIG_SERIAL_DEV_CTRL_TTYPORT - is not set

I tried to download and compile the kernel and stuck. Basically I do not know where to find the kernel used to build the image.

And most of all I'm not 100% sure I have to recompile the kernel. I do not believe nobody tested the Bluetooth before. Most probably it is configuration issue.

Please assist

I have Armbian 22.08.6 Jammy with Linux 5.15.74-rockchip with Desktop running on an "Asus Tinker Board Rev. 1.2".

My Problem is that I get no stable HDMI Connection. Picture is appearing and disappearing every few seconds. Changing Cable, Monitors, Resolution and Refreshrate doesn’t change the problem. 

After Research in the forum I saw that I should provide „armbianmonitor -u“ here:

https://paste.armbian.com/oriqiwilah

I would be able to compile a custom

image, but I don‘t know where to start bugfixing because I am no HDMI Expert.

Maybe it has something to do with a Sync-Problem like described here:

https://forum.armbian.com/topic/7342-terminal-video-corruptionsync-problem-tinker-board/?do=findComment&comment=56099

Thank you for help!

PS:

I posted this question accidentally in the wrong language before and tried to contact the moderators, but I am not allowed to post new question or reach them with the private message feature. So I post this here as a new user! Thanks!

Habe Armbian 22.08.6 Jammy with Linux 5.15.74-rockchip mit Desktop auf "Asus Tinker Board Rev. 1.2" laufen, aber leider bekomme ich per HDMI keine stabile Verbindung.

HDMI Kabel bereits getauscht (geht mit anderen Geräten einwandfrei) auch Montor getauscht (geht mit anderen Geräten auch einwandfrei).

Auflösungen und Framerates habe ich durchprobiert - fehlerbild aber immer das gleiche; Bild bleibt bestenfalls ein paar sekunden ein, dann geht es wieder aus für ein paar Sekunden und das setzt sich fort.

Hab ein bisschen hier im Forum recheriert und sehe das man ein "armbianmonitor -u" ausführen soll und im Forum posten:

https://paste.armbian.com/oriqiwilah

Ich bin grundsätzlich in der Lage ein neues Image zu kompilieren aber ich bin noch unsicher wo ich anfangen soll den Fehler zu suchen.

Hier ein Forumbeitrag über ein Sync Problem -  weiß nicht ob das mit dem zu tun hat.

Vielen Dank!

I have set

kernel.panic=180

in /etc/sysctl.conf to reboot on a kernel panic. 

Before, the system would keep running/hanging and I could read the errors if I turned on a attached display.  Now the result is that the tinkerboard switches off.  My expected result would be a reboot.

Do I have to set something else?  Or do I need to use watchdog? 

I am using the original tinkerboard with debian bullseye, kernel 5.15.48-rockchip.  

1.Where to connect outside diode to thinkerboard .

2.How to turn off/on it from command line.

I've been (trying) to move the Tinker and MiQi u-boots to 2020.07, however if I use any of the following:

A MiQi,

A Tinker S

an image for a Tinker S

an image for a Tinker on a Tinker S

I get stuck in the initramfs busybox with it telling me the filesystem is toast.  The only 2020.07 combo I've gotten to boot is the Tinker with the non-eMMC supporting u-boot.  As for clues, I haven't found any, the u-boot source code is of course very well organized for debugging purposes  :lol:.

If anyone has an idea about what could be going on with this let me know, I'm shelving the effort to think about other stuff.

I have enabled the SPI0 (and UART1) directly from armbian-config, I have disabled all the other peripherals.

The connections are these:

INT   -------------> pin 32

CLK -------------> pin 11

SI ----------------> pin 13

SO --------------> pin 15

CS --------------> pin 29

in : /boot/armbianEnv.txt

i add this:

user_overlays=spi-mcp251x

but it don't work and i can't find a guide for this board

thanks a lot for your help

I've got a problem getting USB devices to work with Armbian 22.02.1 (Tinkerboard_bullseye_current_5.15.25) - fresh install, bare image without any modifications.

While a simple usb keyboard would more or less work, plugging some devices seems to crash the built-in USB hub.

This happens in "cold"-plug as in "hot"-plug, whereas there are slight differences.

Booting up without any USB device attached:

lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:49f6 Realtek Semiconductor Corp. USB Audio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

After hot-plugging in any USB device the Genesis USB Hub has disappeared:

lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 0bda:49f6 Realtek Semiconductor Corp. USB Audio
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

dmesg has these two entries:

[  131.740593] usb 1-1: USB disconnect, device number 2
[  134.624629] usb usb1-port1: connect-debounce failed

So far what I tried to find out a little more:

• USB Card Readers and Datasticks work if "cold" plugged (=before power on), but crash on hotplug.
• USB Card Readers crash if hotplugged or "cold" plugged, removed and re-attached.
• USB stays crashed if the system reboots without a power off in between. Always!
• Huawei Surfsticks that do a modeswitch (e.g. USB_MODESWITCH etc. to get from  storage- to network-mode) crash the system. Maybe modeswitch triggers the same problem as hotplug?
• I tried Tinkerboard R2.0 and S R2.0 - and serveral of each from my collection. Same problem with every board.

Does anyone have more information on or suggestions how to analyse these issues?
I read hotplug was in issue in 2018, does this remain?

I've used the Tinkerboard S (Rockchip RK3288) with the Armbian images available for download (https://www.armbian.com/tinkerboard/).  Currently, the /dev/ttyS4 serial port is not available unless CONFIG_SERIAL_8250_NR_UARTS=5 when the Linux kernel is built since the serial ports are populated in /dev starting with /dev/ttyS0 and the last serial port to be populated is /dev/ttyS4.  By default,  CONFIG_SERIAL_8250_NR_UARTS=4.  Some additional kernel settings are required to ensure that all of the available serial ports can be utilized.  Moreover,  I had to activate I2C4 in the device tree overlay using the Armbian configuration utility (https://docs.armbian.com/User-Guide_Armbian-Config/) since I2C4 is required for my application.  I also built the kernel and the BSP using the excellent instructions posted on the Ambian website.

Would a patch be good to contribute?  I can contribute this myself if required.  I am wondering if there is a reason (design philosophy) for not supporting all of the serial ports and some of the devices listed in the device pinout.  Perhaps it would be good to ensure that all or most of the features listed in the pinout work out of the box on the supported images?

Hi!
I have installed Armbian buster 21.08.3 and can`t discover any externally connected i2c devices, such as rtc or ssd1306
Any ideas?
i2cdetect -l
i2c-2   i2c             rk3x-i2c                                I2C adapter
i2c-0   i2c             rk3x-i2c                                I2C adapter
i2c-5   i2c             rk3x-i2c                                I2C adapter

sudo i2cdetect -y 0                                                                            
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:         -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

sudo i2cdetect -y 2
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: 50 51 52 53 -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

sudo i2cdetect -y 5
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- 49 -- -- -- -- -- --
50: 50 -- -- -- -- -- -- -- -- 59 -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

https://justpaste.it/5jszu

I tried with I2C connected and disconnected between screen and tinkerboard.  No change. (See below, looks like i2c-3/3-0045/tinker_mcu_bl is missing ).   I checked around that area and tinker_mcu_bl is missing, but folder 3-0045 exists with lots of files in there. (bottom of the post)

From dmesg I also see that i2c had a failure (ret = -6). (see next paste)

Looking forward I see that -6 is no device found on i2c bus (assuming that's correct?). Does anyone know if brightness control works?

[    2.446829] tinker-mcu: tinker_mcu_probe: address = 0x45   
[    2.446843] tinker-mcu: send_cmds: 80  
[    2.493126] tinker-mcu: init_cmd_check: recv_cmds: 0xC3    
[    3.161121] tinker_mcu_screen_power_up 
[    3.161122] tinker-mcu: tinker_mcu_screen_power_up:   
[    3.161127] tinker-mcu: send_cmds: 8500     
[    4.545081] tinker-mcu: send_cmds: 8501     
[    4.569108] tinker-mcu: send_cmds: 8104     
[    4.572138] tinker-mcu: send_cmds: send command failed, ret = -6     
[    4.574293] tinker-mcu: tinker_mcu_set_bright: bright = 0xff 

shadowpho@tinkerboard:~$ sudo rpi-backlight -Btinker-board -p toggle    
Traceback (most recent call last):    
File "/usr/local/bin/rpi-backlight", line 10, in <module>  sys.exit(main())     
File "/usr/local/lib/python3.7/dist-packages/rpi_backlight/cli.py", line 103, in main   if backlight.power:  
File "/usr/local/lib/python3.7/dist-packages/rpi_backlight/__init__.py", line 213, in power     return bool(self._get_value("tinker_mcu_bl"))     
File "/usr/local/lib/python3.7/dist-packages/rpi_backlight/__init__.py", line 85, in _get_value raise e     
File "/usr/local/lib/python3.7/dist-packages/rpi_backlight/__init__.py", line 77, in _get_value return int((self._backlight_sysfs_path / name).read_text())    
File "/usr/lib/python3.7/pathlib.py", line 1199, in read_text with self.open(mode='r', encoding=encoding, errors=errors) as f: 
File "/usr/lib/python3.7/pathlib.py", line 1186, in open   opener=self._opener) 
File "/usr/lib/python3.7/pathlib.py", line 1039, in _opener   return self._accessor.open(self, flags, mode)   FileNotFoundError: [Errno 2] No such file or directory: '/sys/devices/platform/ff150000.i2c/i2c-3/3-0045/tinker_mcu_bl'   

yesterday i got a powerloss , and my Asus tinkerboard got shutdown. i think i had some updates installed but not yet rebooted

the Tinkerboard never restarted again.

i first suspected a crashed Emmc disk but i did the following tests and got to the conclusion that Armbian for Tinkerboard is currently broken

- restored a past complete image to either SD or Emmc : boots ok.

- shutdown then unplug/replug power : OK

- update with apt-get update + apt-get upgrade => reboot OK, but shutdown, and then never restart, bricked. shutdown down either with desktop or command line

tested also with a second Tinkerboard with no Emmc, SD re-image from working backup, boot on SD : OK. apt-get upgrade. reboot : OK. shutdown => bricked.

what can i check on my SD card ( i installed a Windows ext2/ext4 explorer) to correct the issue ?

I have a brand new Tinker Board S with the latest Armbian buster installed. I have hostapd set up for the board to be a WiFi access point. I can see the SSID on my Windows and mobile devices but when I connect, hostapd tells me an error code 8 and that the device is disassociated. I don't think this is the issue as the kernel panics at exactly the same time.  Here is the output from dmesg:

[  101.279674] ------------[ cut here ]------------
[  101.284852] kernel BUG at mm/slub.c:4117!
[  101.289337] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[  101.295860] Modules linked in: fuse rtc_ds1307 xt_state xt_conntrack nft_counter nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_compat nf_tables nfnetlink snd_soc_simple_card snd_soc_simple_card_utils snd_usb_audio snd_hwdep snd_usbmidi_lib snd_rawmidi snd_seq_device hantro_vpu(C) snd_soc_rockchip_i2s snd_soc_hdmi_codec snd_soc_rockchip_pcm rockchip_rga snd_soc_core v4l2_h264 snd_pcm_dmaengine videobuf2_dma_contig videobuf2_dma_sg snd_pcm videobuf2_vmalloc v4l2_mem2mem videobuf2_memops videobuf2_v4l2 snd_timer videobuf2_common snd soundcore dw_wdt rk_crypto syscon_reboot_mode reboot_mode rk3288_gpiomem r8723bs(C) rockchip_thermal cpufreq_dt zram ip_tables gpio_keys panfrost gpu_sched dw_hdmi_i2s_audio dw_hdmi_cec realtek
[  101.371009] CPU: 0 PID: 2294 Comm: RTW_CMD_THREAD Tainted: G         C        5.10.21-rockchip #21.02.3
[  101.381513] Hardware name: Rockchip (Device Tree)
[  101.386781] PC is at kfree+0x49c/0x524
[  101.390971] LR is at nl80211_send_station+0x964/0x100c
[  101.396717] pc : [<c02c9ebc>]    lr : [<c0ec8430>]    psr: 40070013
[  101.403723] sp : c404fd10  ip : c404fd50  fp : c404fd4c
[  101.409565] r10: c1506808  r9 : 00023454  r8 : c1772340
[  101.415406] r7 : eee1d454  r6 : c0ec8430  r5 : c0fad7a8  r4 : 00000000
[  101.422705] r3 : eee1d458  r2 : 00000000  r1 : c793df78  r0 : c0fad7a8
[  101.430006] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[  101.437985] Control: 10c5387d  Table: 07ca406a  DAC: 00000051
[  101.444411] Process RTW_CMD_THREAD (pid: 2294, stack limit = 0xabe5bfbc)
[  101.451905] Stack: (0xc404fd10 to 0xc4050000)
[  101.456770] fd00:                                     00000011 00000000 c0fad7a8 c6124190
[  101.465921] fd20: c793df1c c404fdf8 c4cc4780 00000011 00000000 c0fad7a8 c612418c c1506808
[  101.475071] fd40: c404fdac c404fd50 c0ec8430 c02c9a2c 00000005 00000013 c404fd74 00000000
[  101.484221] fd60: c1506808 c6124030 c612418c c6124014 e3500000 ba00005c 0008d8ec d3fcf9d2
[  101.493371] fd80: f08db550 c342c9e0 00000000 c342c000 00000a20 c793df0a c404fdf8 c4cc4780
[  101.502521] fda0: c404fdf4 c404fdb0 c0ec910c c0ec7ad8 00000000 c342c800 c342c000 c793df0a
[  101.511671] fdc0: c404fdf8 c1506808 00000008 c1506808 0000001c 00000000 00000000 bf0ac050
[  101.520821] fde0: c793e980 ffff3def c404feec c404fdf8 bf0a1ffc c0ec9088 00000000 00000000
[  101.529971] fe00: c010d19c 00060040 00000fff d3fcf9d2 c010c214 c1506808 d3fcf9d2 00000006
[  101.539120] fe20: 00000000 00000000 00000000 ffff3def c404fe64 c404fe40 bf084e68 bf084b5c
[  101.548270] fe40: c404fe74 c404fe50 c010c214 c010d11c c1506808 00000000 c0fb4d9c c1504900
[  101.557420] fe60: bf0ac050 c793e980 c793df1c 0000005c c404fec4 c404fe80 c02cba38 c028872c
[  101.566570] fe80: bf05ceb4 c02c9b18 c2001d80 c793df80 00ffff00 ffffe000 00000078 c793df00
[  101.575720] fea0: c404febc c012af1c c0fad8e8 c0fad7a8 c404fed4 c404fec0 c012af1c c01526f4
[  101.584870] fec0: bf05cf10 f11dff84 c404feec d3fcf9d2 f08da000 f11dff84 00000078 c793df00
[  101.594020] fee0: c404ff0c c404fef0 bf05cf28 bf0a1f88 f08db000 00000000 f08db4b8 c1504900
[  101.603170] ff00: c404ff24 c404ff10 bf067dd8 bf05cd6c f08db000 f08dd000 c404ff74 c404ff28
[  101.612320] ff20: bf055930 bf067d58 60000013 c60ad600 f08db49c f08da000 bf0b4000 c342da00
[  101.621470] ff40: c404e000 f08db480 c404ff74 c60ad600 c543f640 c404e000 bf05579c f08da000
[  101.630620] ff60: 00000000 c61037c8 c404ffac c404ff78 c0149700 bf0557a8 c60ad630 c60ad630
[  101.639769] ff80: 00000000 c543f640 c0149564 00000000 00000000 00000000 00000000 00000000
[  101.648919] ffa0: 00000000 c404ffb0 c0100148 c0149570 00000000 00000000 00000000 00000000
[  101.658068] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  101.667217] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[  101.676360] Backtrace:
[  101.679110] [<c02c9a20>] (kfree) from [<c0ec8430>] (nl80211_send_station+0x964/0x100c)
[  101.687970]  r10:c1506808 r9:c612418c r8:c0fad7a8 r7:00000000 r6:00000011 r5:c4cc4780
[  101.696726]  r4:c404fdf8
[  101.699566] [<c0ec7acc>] (nl80211_send_station) from [<c0ec910c>] (cfg80211_new_sta+0x90/0x1bc)
[  101.709290]  r10:c4cc4780 r9:c404fdf8 r8:c793df0a r7:00000a20 r6:c342c000 r5:00000000
[  101.718045]  r4:c342c9e0
[  101.720945] [<c0ec907c>] (cfg80211_new_sta) from [<bf0a1ffc>] (rtw_cfg80211_indicate_sta_assoc+0x80/0x9c [r8723bs])
[  101.732614]  r10:ffff3def r9:c793e980 r8:bf0ac050 r7:00000000 r6:00000000 r5:0000001c
[  101.741369]  r4:c1506808
[  101.744319] [<bf0a1f7c>] (rtw_cfg80211_indicate_sta_assoc [r8723bs]) from [<bf05cf28>] (rtw_stassoc_event_callback+0x1c8/0x1d4 [r8723bs])
[  101.758130]  r7:c793df00 r6:00000078 r5:f11dff84 r4:f08da000
[  101.764572] [<bf05cd60>] (rtw_stassoc_event_callback [r8723bs]) from [<bf067dd8>] (mlme_evt_hdl+0x8c/0xb4 [r8723bs])
[  101.776345]  r7:c1504900 r6:f08db4b8 r5:00000000 r4:f08db000
[  101.782788] [<bf067d4c>] (mlme_evt_hdl [r8723bs]) from [<bf055930>] (rtw_cmd_thread+0x194/0x3d4 [r8723bs])
[  101.793585]  r5:f08dd000 r4:f08db000
[  101.797647] [<bf05579c>] (rtw_cmd_thread [r8723bs]) from [<c0149700>] (kthread+0x19c/0x1b4)
[  101.806992]  r10:c61037c8 r9:00000000 r8:f08da000 r7:bf05579c r6:c404e000 r5:c543f640
[  101.815747]  r4:c60ad600
[  101.818586] [<c0149564>] (kthread) from [<c0100148>] (ret_from_fork+0x14/0x2c)
[  101.826662] Exception stack(0xc404ffb0 to 0xc404fff8)
[  101.832305] ffa0:                                     00000000 00000000 00000000 00000000
[  101.841455] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  101.850603] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000
[  101.858003]  r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c0149564
[  101.866758]  r4:c543f640
[  101.869594] Code: eaffff17 e5973004 e3130001 1affff83 (e7f001f2)
[  101.876416] ---[ end trace 8e72c51e24431188 ]---
[  106.311591] RTL8723BS: ap recv disassoc reason code(8) sta:b8:ee:65:33:39:bf

I found potential similar posts on this forum but they were marked as addressed/patched/resolved. Do I somehow have an older nl80211 driver?

Hi,

New build, Armbian_21.05.0-trunk_Tinkerboard_focal_current_5.10.22_xfce_desktop.img.

The build finished ok and the image after flashing is working just fine, but..

unfortunately there is no /boot/dtb/overlay folder and of course none and its .dtbo entries are found anywere.

Am I missing something ?

Is the latest build system broken for Tinkerboard ?

Do I need to specify something during the build process menu ?

/PS

Just checked with the Armbian ready-made provided image for Tinkerboard, the

Armbian_21.02.1_Tinkerboard_focal_current_5.10.12_desktop.img.xz

and

Armbian_21.02.3_Tinkerboard_buster_current_5.10.21_xfce_desktop.img.xz

they also lack the /boot/dtb/overlay folder..

On a fresh Buster Minimal install, what is required to get armbian-config fully functional?

apt install armbian-config 'works' but some functions don't, for instance it fails setting the locale as dpkg-reconfigure errors as 

usr/lib/armbian-config/jobs.sh line 839 dpkg-reconfigure : command not found

EDIT:

In armbian-config I selected 'full firmware package' and rebooted, time zone settings now work.

Was odd that the welcome page said run armbian-config (beta) but it had to be installed manually via apt.

Hey guys, i want help to install anydesk in tinker board with armbian focal

I just download Armbian_20.11.6_Tinkerboard_bionic_legacy_4.4.213_desktop.img.xz flased it on sd card with balenaEtcher, tried to boot and got error:

So. I can't do my first login.

Hi all,

I'm using for the Tinkerboard the mem freeze and resume methods; in particular using by the pins near the video connector (and a button) to resume the board.

Is it possible to use other pins to achieve that?

Thanks!

THE MEDIA SCRIPT IS DEPRECATED, IN FAVOR OF THE OFFICIAL LEGACY MULTIMEDIA FRAMEWORK. PLEASE REFER TO THIS TOPIC:

The UN-official, UN-supported, UN-necessary, UN-popular, UN-precedented...

RK3288 MEDIA TESTING SCRIPT [2.0: Bionic update]

So here is the final release of the RK3288 media testing script. Basically, the script provides the following functionality:

• Installing all the libraries and system configurations necessary for GPU accelerated X desktop, Chromium WebGL, full VPU video play acceleration up to 4k@30 HEVC (the maximum supported by the SoC), and GLES 3.1 / OpenCL 1.2 support.
• Three video players supporting full VPU acceleration (RKMPP) and KMS display (GBM or a X11 DRM "hack", as described by the authors), namely: MPV, Gstreamer and Kodi 18.0 alpha preview.
• Two example programs using the OpenCL functionality: Examples form the Arm Compute Library, and a GPU crypto miner (an old version, but small and simple).
• A library that will act as an OpenGL to OpenGL-ES wrapper, allowing you to run programs that use OpenGL 1.5-2.0.
• Two additional small packages, that have no big interest from the developer prospective, but I find them interesting to play with: Support libraries for commercial web video streaming (tested with Netflix), and a simple Pulseaudio GTK equalizer using LADSPA.

Here is a more thorough documentation:

Version 2.0 (Bionic):

ARMBIAN UNOFFICIAL RK3288 MEDIA TESTING SCRIPT
----------------------------------------------
v2.0 Bionic - 2018/10/22


This script will install several multimedia-related software pieces in a
RK3288 Ubuntu Bionic Armbian desktop default image (kernel 4.4.y).
Currently it only supports the installation of the features, while
uninstall must be performed manually.

The script must be run in a command line from the same directory it was
unpacked (./media-rk3288.sh), and will ask for superuser privileges if
not launched with "sudo". Each subfolder contains, in addition to the
packages needed for installation, a text file with information about the
sources for those packages.

The script will present the user with a menu where they can select the
features to be installed. Here is a brief description of each option:

- System: This option will install the base libraries, X server packages
          and system files configuration. It must be run at least once
          before installing any of the other features, or after any
          system upgrade that modified X or Chromium configuration.
          Enabling system config will also present the user with the
          choice of two different versions of the Rockchip X server:
            · Stable: The standard version that you can download from 
              Rockchip repos.
            . Experimental: This version is taken from some PR that 
              didn't make it into the release version, and is supposed
              to give better performance. More info here:
              https://github.com/rockchip-linux/xserver/pull/10
           
- Devel: When this option is enabled, the script will install the 
         development libraries for every other option that is selected.
         So, for example, if in your first run of the script you keep 
         this option disabled and enable the rest, it will install all 
         the features but without any devel lib. If eventually you need,
         e.g., to compile some app requiring Gstreamer development libs,
         then you can run again the script, and select only "Devel" and
         "Gstreamer", so in that run it will only install Gstreamer with
         the development libraries, without touching the rest.
         
- MPV: This is a RKMPP accelerated version of MPV. In order to use the 
       hardware acceleration, it needs to make use of KMS for display,
       which means that it will ignore the X server if it is running,
       and play video in a full-screen overlay, using keyboard or LIRC
       to control the player. Type "man mpv" for a list of keyboard
       controls (tip: shift+Q will save position and exit).
       Alternatively, you can also use software decoding, and output to
       a X window with mouse support. It will still have some display
       acceleration through X11/EGL, though not as efficient as GBM/KMS.
         · To use the X, non-RKMPP version, just type "mpv <file>" in
           the console, or use the launcher labeled simply "MPV".
         . To use the GBM+RKMPP version, type "mpv-gbm <file>", or use
           the "MPV (GBM)" launcher.
         · You can use the player even in a console-only session.

- Gstreamer: These are the Rockchip Gstreamer plugins for media playback
             and capture.
             Notice that the Gstreamer plugin is the only method that
             allows full RKMMP+KMS acceleration associated to a X 
             window.
               · To play a video in a X session, use the launcher "Rock-
                 chip Gst Player".
               . From the command line, in a X session, type:
                 "gst-play-1.0 --videosink=rkximagesink <file>"
               . From a console-only session, type:
                 "gst-play-1.0 --videosink=kmssink <file>"

- CLSamples: A couple of simple programs to test OpenCL capabilities:
	     · Compiled examples from the Arm Compute Library
	     . An old GPU crypto miner (cgminer) with support for
	       extra algorythms like Skein.
	     They are installed under ~/clsamples, where you can find
	     a readme.txt file with instructions.

- GL4ES: An Opengl-ES wrapper library that will allow you to use OpenGL
         1.5-2.0 compatible programs with hardware acceleration. 
         More info: https://github.com/ptitSeb/gl4es.
         · In order to make it easier to use the library, we have
           included a script called "glrun", that will set the proper
           environment variables. Launch your OpenGL program like this:
           "glrun <command>"
         
- Streaming: This will install the Widevine and Pepper-Flash libraries
             for Chrome, enabling you to stream videos from sites such
             as Netflix (tested) or Hulu (untested).
             It will also install the h264ify addon, which will force
             all Youtube videos to use the H.264 codec.

- Equalizer: A GTK-based equalizer for PulseAudio, using LADSPA. You
             need to enable it through the menu entry, and select the
             desired preset or tweak your own settings. The "Boosted"
             preset is recommended for everyday use.
             This package is old and unmaintained, but I still find it
             useful.

- Kodi: Kodi 18.0 Leia beta 3. This version is supposed to be stable
        enough for normal use. But the main purpose of including Kodi in
        the script is to test the new RKMPP+KMS implementation. We don't
        intend to offer a full-fledged distribution of Kodi. For that, I
        recommend using LibreELEC.
        It cannot be launched from an active X session, you need to
        switch to a virtual terminal first.
        · The "Kodi" desktop launcher will switch you to VT1, launch
          Kodi and then bring you back to VT7.
        · From the command line, in a X session, type:
          "kodi-gbm-wrapper" for the same effect.
        · If you are already in a console-only session, you can just 
          type "kodi".

All the RKMPP accelerated players can handle up to 4K@30 HEVC with
perfect smoothness.


Please report bugs and suggestions in the thread dedicated to this
script at the Armbian Forum. Enjoy!

JMCC.

Version 1.0 (Xenial):

ARMBIAN UNOFFICIAL RK3288 MEDIA TESTING SCRIPT
----------------------------------------------
v1.0 Xenial - 2018/05/16

This script will install several multimedia-related software pieces in a
RK3288 Ubuntu Xenial Armbian desktop default image (kernel 4.4.y).
Currently it only supports the installation of the features, while
uninstall must be performed manually.

The script must be run in a command line from the same directory it was
unpacked (./media-rk3288.sh), and will ask for superuser privileges if
not launched with "sudo". Each subfolder contains, in addition to the
packages needed for installation, a text file with information about the
sources for those packages.

The script will present the user with a menu where they can select the
features to be installed. Here is a brief description of each option:

- System: This option will install the base libraries, X server packages
          and system files configuration. It must be run at least once
          before installing any of the other features, or after any
          system upgrade that modified X or Chromium configuration.
          Enabling system config will also present the user with the
          choice of two different versions of the Rockchip X server:
            · An older version that replaces the standard 1.18.y server
              bundled with Xenial, and therefore doesn't need to install
              a backported version of the X server.
            . The most recent version from the Rockchip Git. It is based
              on X server versiojn 1.19.y, so it requires the
              installation of a backported X server.
           The older version does not have proper video Vsync, so it is
           not too recommended for multimedia use. It might also be less
           stable, more testing is needed to tell. On the other hand, it
           offers the possibility of enabling window manager compositing
           and gives a snappier desktop experience.
           
- Devel: When this option is enabled, the script will install the 
         development libraries for every other option that is enabled.
         So, for example, if in your first run of the script you keep 
         this option disabled and enable the rest, it will install all 
         the features but without any devel lib. If eventually you need,
         e.g., to compile some app requiring Gstreamer development libs,
         then you can run again the script, and select only "Devel" and
         "Gstreamer", so in that run it will only install Gstreamer with
         the development libraries, without touching the rest.
         
- MPV: This is a RKMPP accelerated version of MPV. In order to use the 
       hardware acceleration, it needs to make use of KMS for display,
       which means that it will ignore the X server if it is running,
       and play video in a full-screen overlay, using keyboard or LIRC
       to control the player. Type "man mpv" for a list of keyboard
       controls (tip: shift+Q will save position and exit).
       Alternatively, you can also use software decoding, and output to
       a X window with mouse support. It will still have some display
       acceleration through X11/EGL, though not as efficient as GBM/KMS.
         · To use the X, non-RKMPP version, just type "mpv <file>" in
           the console, or use the launcher labeled simply "MPV".
         . To use the GBM+RKMPP version, type "mpv-gbm <file>", or use
           the "MPV (GBM)" launcher.
         · You can use the player even in a console-only session.
- Gstreamer: These are the Rockchip Gstreamer plugins for media playback
             and capture. The plugins themselves are just a few small
             libs, but since the version shipped with Xenial is so old,
             we need to install also a full Gstreamer 1.12 backport.
             It will also install a demo Qt5 player.
             Notice that the Gstreamer plugin is the only method that
             allows full RKMMP+KMS acceleration associated to a X 
             window.
               · To play a video in a X session, use the launcher "Rock-
                 chip Gst Player".
               . From the command line, in a X session, type:
                 "gst-play-1.0 --videosink=rkximagesink <file>"
               . From a console-only session, type:
                 "gst-play-1.0 --videosink=kmssink <file>"
- CLSamples: A couple of simple programs to test OpenCL capabilities:
         · Compiled examples from the Arm Compute Library
         . An old GPU crypto miner (cgminer) with support for
           extra algorythms like Skein.
         They are installed under ~/clsamples, where you can find
         a readme.txt file with instructions.
- Streaming: This will install the Widevine and Pepper-Flash libraries
             for Chrome, enabling you to stream videos from sites such
             as Netflix (tested) or Hulu (untested).
             It will also install the h264ify addon, which will force
             all Youtube videos to use the H.264 codec.
- Equalizer: A GTK-based equalizer for PulseAudio, using LADSPA. You
             need to enable it through the menu entry, and select the
             desired preset or tweak your own settings. The "Boosted"
             preset is recommended for everyday use.
             This package is old and unmaintained, but I still find it
             useful.
- Kodi: A preview of Kodi 18.0 Leia. Since it is still in alpha state,
        it is not recommended for regular use, but you can test the
        quality of the new RKMPP+KMS implementation that is being
        added to this version. It will crash when trying to open a file
        from USB sticks or Samba share, so please copy them to the
        SD card before testing.
        It cannot be launched from an active X session, you need to
        switch to a virtual terminal first.
        · The "Kodi" desktop launcher will switch you to VT1, launch
          Kodi and then bring you back to VT7.
        · From the command line, in a X session, type:
          "kodi-gbm-wrapper" for the same effect.
        · If you are already in a console-only session, you can just 
          type "kodi".
All the RKMPP accelerated players can handle up to 4K@30 HEVC with
perfect smoothness.

Please report bugs and suggestions in the thread dedicated to this
script at the Armbian Forum. Enjoy!
JMCC.

>>> DOWNLOAD LINK (2.0, FOR BIONIC DESKTOP) <<<

> Older Download link (1.0, for Xenial) <

Instructions:

1. Download the file above
2. Untar it: tar xvf media-rk3288_*.tar.xz
3. cd media-script
4. ./media-rk3288.sh

Notes:

• This script is not officially supported by the Armbian project. It is just a community effort to help the development of the main build, by experimenting with a possible implementation of the media capabilities of this particular SoC.
• Therefore, questions about the script should not be laid out as support requests, but as commentaries or community peer-to-peer assistance.
• That being said, all commentaries/suggestions/corrections are very welcome. In the same way, I will do my best to help solve any difficulty that may arise regarding the script.

Enjoy!

I got wierd screen blinking after update kernel from 5.8.18-rockchip to 5.9.14-rockchip.

Here is blurry video with screen blinking.

My screen resolution is 1600x900 and i'm using HDMI-to-VGA adapter. All was working fine with kernel 5.8.18-rockchip.

I still can connect to sbc via ssh, so I checked kernel version, install old one and blinking gone:

q@tinkerboard:/var/cache/apt/archives$ uname -a
Linux tinkerboard 5.9.14-rockchip #20.11.3 SMP PREEMPT Fri Dec 11 22:00:29 CET 2020 armv7l armv7l armv7l GNU/Linux
q@tinkerboard:/var/cache/apt/archives$ dpkg-deb -I linux-image-current-rockchip_20.11_armhf.deb
 new Debian package, version 2.0.
 size 27169880 bytes: control archive=50048 bytes.
     403 bytes,    12 lines      control
  194536 bytes,  1942 lines      md5sums
     428 bytes,    15 lines   *  postinst             #!/bin/bash
     299 bytes,    12 lines   *  postrm               #!/bin/bash
     932 bytes,    34 lines   *  preinst              #!/bin/bash
     297 bytes,    12 lines   *  prerm                #!/bin/bash
 Package: linux-image-current-rockchip
 Source: linux-5.8.18-rockchip
 Version: 20.11
 Architecture: armhf
 Maintainer: Igor Pecovnik <igor.pecovnik@****l.com>
 Installed-Size: 80090
 Section: kernel
 Priority: optional
 Homepage: http://www.kernel.org/
 Description: Linux kernel, version 5.8.18-rockchip
  This package contains the Linux kernel, modules and corresponding other
  files, version: 5.8.18-rockchip.
q@tinkerboard:/var/cache/apt/archives$ sudo dpkg -i linux-image-current-rockchip_20.11_armhf.deb
dpkg: warning: downgrading linux-image-current-rockchip from 20.11.3 to 20.11
(Reading database ... 112356 files and directories currently installed.)
Preparing to unpack linux-image-current-rockchip_20.11_armhf.deb ...
update-initramfs: Deleting /boot/initrd.img-5.9.14-rockchip
Removing obsolete file uInitrd-5.9.14-rockchip
Unpacking linux-image-current-rockchip (20.11) over (20.11.3) ...
Setting up linux-image-current-rockchip (20.11) ...
update-initramfs: Generating /boot/initrd.img-5.8.18-rockchip
update-initramfs: Converting to u-boot format
q@tinkerboard:/var/cache/apt/archives$ sudo reboot

Please, fix blinking bug in 5.9.14-rockchip.

Looks like problem raised when hdmi patches was disabled: https://github.com/armbian/build/commit/62c27823a637698e88284bc0c0f0d31342ed9641

The hardware video encoding/decoding facilities are the real meat of the RK3288, and recent Rockchip boards.

The VPU driver aims to use these facilities in order to provide the smooth video playback experience that every Netflix/Hulu addict expects when buying such boards.

Which mean, once this part dealt with, you might be able to enjoy your Multimedia oriented distributions/softwares on your Rockchip boards (MiQi, Tinkerboard and maybe Pine64 too !)

So the driver is already available in Rockchip 4.4 kernels, and started to be ported in an Out-Of-Tree fashion by phhusson on Github, and then got the attention of wzyy2, one of the Rockchip guy, which updated it and took care of multiple bugs that were present in this version.

I'm now reassembling the code, include files and all in my rockchip-vcodec repository, patching the code to use it with the latest 4.13 kernels.

Now, the problems are : I don't get the big picture from the user side. So it's kinda hard to test this quickly.

Rockchip seems to rely on their library, MPP, and patched gstreamer packages if I understand correctly. Last time I tried the "test-suite" of the MPP library, things were "clunky". Since it's mostly maintained by one person, ayaka, I'm pretty sure that it's the kind of test-suite that only the owner clearly understands. I know that problem, as I did the same thing with some of my libraries.

So, basically, the main goals are :

• ! Compile the VPU driver without issues. I took care of that for now. The driver compiles, loads AND unloads correctly, without issues.
• ? Understand clearly what packages, patches and software are needed to use the VPU services provided by the VPU driver.
• ? Enjoy 1080p movies without a hitch on RK3288 boards (and others Rockchip boards if possible) !

I'll add these goals on the Github pages so that everyone gets how things are going, from the GH page.

If you have any issue with the driver and/or it's use, file it on my repository and I'll see what I can do.

Hello,

I have been experimenting with the bluetooth audio on my tinkerboard.  The issue is both present on the last rockchip-next (4.1x I think) and the rockchip-current 5.8.18 kernel. I am using bluez and bluealsa.

The problem is specific to the onboard bluetooth, using an external bluetooth dongle (a cheap and old CSR Bluetooth 3.0 dongle from China)  works as expected, I can even send audio to multiple devices simultaneously (quality is very bad, but thats a bandwidth problem).

As long as I just connect one bluetooth audio device everything is fine.  I can have multiple paired, but disconnected, devices and as long as I connect and play and diconnect, things keep working.  But as soon as I try to connect a second device, while another one is already connected (not even playing), the second device shortly shows up as connected in `bluetoothctl` (while the LED on the speaker itself stil shows not-connected) and about 10-20 seconds later the device shows up as disconnected and would not even reconnect unless switched on or off.  

The error logged by bluetoothd / bluez (5.55-1) is

bluetoothd[15142]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 74:A3:xx:xx:xx:xx: Connection refused (111)

The connection process does not reach the bluealsa layer, I had similar problems when quickly testing with pulseaudio's bluetooth module.

My question:

Is there anywhere in the armbian tinkerboard configuration some hardcoded option to only connect to one device at a time?  I cannot imagine this to be alimit of the on-board chip, Are there any config options for the HCI UART kernel driver?

Hi. I would like to download last armbian image for my Asus tinkerboard, but all download links broken:
https://www.armbian.com/tinkerboard/
Can you fix that?

I found Armbian_20.08.1_Tinkerboard_focal_current_5.8.6_desktop.img.xz here: https://armbian.tnahosting.net/archive/tinkerboard/archive/

Is that latest one?

Wifi AP access point broken in Linux tinkerboard 5.4.44-rockchip #20.05.2 SMP PREEMPT Wed Jun 3 10:43:15 CEST 2020 armv7l armv7l armv7l GNU/Linux

[  456.873025] ------------[ cut here ]------------
[  456.878198] kernel BUG at mm/slub.c:3968!
[  456.882680] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM
[  456.889200] Modules linked in: xt_MASQUERADE xt_conntrack ipt_REJECT iptable_filter nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 fuse zstd snd_soc_hdmi_codec zram snd_soc_simple_card snd_soc_simple_card_utils gpio_keys panfrost dw_hdmi_i2s_audio gpu_sched snd_usb_audio snd_soc_rockchip_i2s snd_soc_rockchip_pcm snd_hwdep snd_usbmidi_lib rockchip_rga snd_rawmidi snd_soc_core snd_seq_device snd_pcm_dmaengine videobuf2_dma_sg v4l2_mem2mem snd_pcm videobuf2_memops videobuf2_v4l2 snd_timer rk_crypto snd videobuf2_common soundcore syscon_reboot_mode dw_wdt reboot_mode rk3288_gpiomem r8723bs(C) rockchip_thermal cpufreq_dt sch_fq_codel ip_tables hid_logitech_hidpp hid_logitech_dj realtek
[  456.975109] CPU: 1 PID: 1564 Comm: RTW_CMD_THREAD Tainted: G         C        5.4.44-rockchip #20.05.2
[  456.985512] Hardware name: Rockchip (Device Tree)
[  456.990779] PC is at kfree+0x2dc/0x308
[  456.994974] LR is at nl80211_send_station+0x954/0xfc4
[  457.000621] pc : [<c02b81c0>]    lr : [<c0e2a470>]    psr: 400b0013
[  457.007625] sp : e8edfd28  ip : e8edfd58  fp : e8edfd54
[  457.013464] r10: c1606788  r9 : eccca0c0  r8 : e8edfec0
[  457.019304] r7 : e8edfec0  r6 : c0e2a470  r5 : ef3bb75c  r4 : 00000000
[  457.026601] r3 : 00000100  r2 : 00000024  r1 : ea678d61  r0 : e8edfec0
[  457.033901] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment none
[  457.041878] Control: 10c5387d  Table: 2965806a  DAC: 00000051
[  457.048303] Process RTW_CMD_THREAD (pid: 1564, stack limit = 0x081ec079)
[  457.055796] Stack: (0xe8edfd28 to 0xe8ee0000)
[  457.060669] fd20:                   ea678cdc c07996bc e8edfe00 e80a9480 00000011 00000000
[  457.069818] fd40: e8edfec0 eccca0c0 e8edfdb4 e8edfd58 c0e2a470 c02b7ef0 00000005 00000013
[  457.078967] fd60: c0276534 00000000 c1606788 eccca030 eccca0c0 eccca014 00000000 00000000
[  457.088115] fd80: 0086c550 e9c85a1a 000101dc ec46d9e0 ec46d000 00000000 00000a20 ea678cca
[  457.097263] fda0: e8edfe00 e80a9480 e8edfdfc e8edfdb8 c0e2b18c c0e29b28 00000000 ec46d800
[  457.106411] fdc0: ec46d000 ea678cca e8edfe00 00000001 e8edfdec c1606788 0000001c 00000000
[  457.115560] fde0: 00000000 bf091050 e85b9d80 00009930 e8edfeec e8edfe00 bf086684 c0e2b108
[  457.124708] fe00: 00000000 00000000 000fffff c02b72e4 c010d6a0 c1606788 e9c85a1a c02b73bc
[  457.133856] fe20: 0000000a 00000000 e8edfebc e8edfe38 c02b73bc c0151ec8 bf069230 bf068f24
[  457.143004] fe40: e816fc00 c1606788 c010d6a0 00210d00 8015000a 00000001 00000001 e816fc00
[  457.152153] fe60: ffffe000 600b0013 e8edfeac e8edfe78 ea678cdc 00000085 e8edfec4 8015000a
[  457.161301] fe80: c02b5990 c0277ffc e8edfef0 e9c85a1a 000000a1 ee401c00 ef39d39c bf03df0c
[  457.170450] fea0: e816fc00 c012bf24 ffffe000 000000a1 e8edfed4 e8edfec0 c012bf24 c0151ec8
[  457.179598] fec0: bf03df20 f1225f84 e8edfeec e9c85a1a f086b000 f1225f84 000000a1 ea678cc0
[  457.188746] fee0: e8edff0c e8edfef0 bf03df38 bf086610 f086c000 00000000 f086c4b8 c1604900
[  457.197894] ff00: e8edff24 e8edff10 bf048e4c bf03dd7c f086c000 f086e000 e8edff74 e8edff28
[  457.207042] ff20: bf03693c bf048dcc e8edff4c e8edff38 f086c49c f086b000 bf099000 ec46f200
[  457.216190] ff40: e8ede000 f086c480 c014902c e8369900 e9975200 00000000 e8ede000 f086b000
[  457.225339] ff60: bf0367a4 ed7a57e8 e8edffac e8edff78 c014a214 bf0367b0 e8369928 e8369928
[  457.234486] ff80: 00000000 e9975200 c014a0a4 00000000 00000000 00000000 00000000 00000000
[  457.243626] ffa0: 00000000 e8edffb0 c01010e8 c014a0b0 00000000 00000000 00000000 00000000
[  457.252752] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  457.261879] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000 00000000 00000000
[  457.271004] Backtrace: 
[  457.273733] [<c02b7ee4>] (kfree) from [<c0e2a470>] (nl80211_send_station+0x954/0xfc4)
[  457.282481]  r9:eccca0c0 r8:e8edfec0 r7:00000000 r6:00000011 r5:e80a9480 r4:e8edfe00
[  457.291132] [<c0e29b1c>] (nl80211_send_station) from [<c0e2b18c>] (cfg80211_new_sta+0x90/0x1cc)
[  457.300850]  r10:e80a9480 r9:e8edfe00 r8:ea678cca r7:00000a20 r6:00000000 r5:ec46d000
[  457.309586]  r4:ec46d9e0
[  457.312433] [<c0e2b0fc>] (cfg80211_new_sta) from [<bf086684>] (rtw_cfg80211_indicate_sta_assoc+0x80/0x9c [r8723bs])
[  457.324095]  r10:00009930 r9:e85b9d80 r8:bf091050 r7:00000000 r6:00000000 r5:0000001c
[  457.332831]  r4:c1606788
[  457.335692] [<bf086604>] (rtw_cfg80211_indicate_sta_assoc [r8723bs]) from [<bf03df38>] (rtw_stassoc_event_callback+0x1c8/0x1d4 [r8723bs])
[  457.349489]  r7:ea678cc0 r6:000000a1 r5:f1225f84 r4:f086b000
[  457.355845] [<bf03dd70>] (rtw_stassoc_event_callback [r8723bs]) from [<bf048e4c>] (mlme_evt_hdl+0x8c/0xb4 [r8723bs])
[  457.367601]  r7:c1604900 r6:f086c4b8 r5:00000000 r4:f086c000
[  457.373959] [<bf048dc0>] (mlme_evt_hdl [r8723bs]) from [<bf03693c>] (rtw_cmd_thread+0x198/0x3d8 [r8723bs])
[  457.384744]  r5:f086e000 r4:f086c000
[  457.388754] [<bf0367a4>] (rtw_cmd_thread [r8723bs]) from [<c014a214>] (kthread+0x170/0x174)
[  457.398083]  r10:ed7a57e8 r9:bf0367a4 r8:f086b000 r7:e8ede000 r6:00000000 r5:e9975200
[  457.406828]  r4:e8369900
[  457.409653] [<c014a0a4>] (kthread) from [<c01010e8>] (ret_from_fork+0x14/0x2c)
[  457.417718] Exception stack(0xe8edffb0 to 0xe8edfff8)
[  457.423356] ffa0:                                     00000000 00000000 00000000 00000000
[  457.432492] ffc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[  457.441618] ffe0: 00000000 00000000 00000000 00000000 00000013 00000000
[  457.449006]  r10:00000000 r9:00000000 r8:00000000 r7:00000000 r6:00000000 r5:c014a0a4
[  457.457750]  r4:e9975200
[  457.460574] Code: 1a000003 e5953004 e3130001 1a000000 (e7f001f2) 
[  457.467381] ---[ end trace 4acbc8c15e9e6aa7 ]---
 

since i have a Asus tinkerboard incoming i was wondering if anyone knows if the "generic" arm64 distro will work this board. Its based of the rockchip RK3288 SoC

The support pages states that the board supports debian, but since i dont need a UI ect (im going to use it headless) i dont need the board to load a ui into memory and wanted to use a normal build instead of the TinkerOS

Please note, my knowledge of the inner workings of *nix is quite limited, so if my question is to generic or imprecise i apologize.

HI all,

first of all, I found thi sissue adopting a new board to the CSC tree, done by @balbes150. As it seems to be a problem of RK3288 in general, I post here, in case please move the topic to the approriate place.

I have a JLD076 board, and started adjusting the DTS to the schematic. According to the schematic, and the TRM of RK3289, there is a maximum number of 160 GPIOs.

This is also the number I get from my schematics.

So I expected th get suitable number of pins from gpioinfo (bank:number 0:19, 1:4, 2:18, 3:28, 4:26, 5:12, 6:19, 7:24, 8:10).

Instead, I get listed (0:24, 1...7:32, 8:16).

I tried now to set ngpios for the &gpioX entries in the DTS, both in the rk3288.dtsi and the rk3288-ev-act8846.dts, and verified by dtc that the ngpios entry is in the DTB file, but gpioinfo still shows the wrong number of pins.

This seems to be hardcoded somewhere... any ideas on what I do wrong here?

Best regards, any help is appreciated. Michael

Just as a notice the Raspberrry PI 7" DSI Touchscreen was working fine on Armbian with the 4.4 Kernel. Using the current Armbian for Tinkerboard and the 4.19 Kernel it does not work any longer,

nor does it with the current development Kernel 5.1. Does there have to be any special things to be set to get it working again? On the 4.4 Kernel it was working out of the box.

Thanx

I am testing RK3288 with ubuntu 20.04 (gnome) btw NICE

And I have some problems with panfrost and I am looking for anybody with RK3288 device that can confirm or not same behavior.

Problem is that when I switch GPU to 600MHz

sudo bash -c 'echo "userspace" > /sys/class/drm/card1/device/devfreq/ffa30000.gpu/governor'

sudo bash -c 'echo "600000000" > /sys/class/drm/card1/device/devfreq/ffa30000.gpu/userspace/set_freq'

and when I run glmark2-es2 or glmark2-es2-wayland

I start to see https://pastebin.com/NuYqHdxH  in kernel.log

So I made bugreport(https://gitlab.freedesktop.org/mesa/mesa/-/issues/2693) for panfrost and they think that problem is in low voltage on gpu

as everything is fine on 400MHz

So anybody can try?

just build ubuntu 20.04 for your RK3288 device

sudo BETA=yes EXPERT=yes ./compile.sh

server build should be fine

and then apt install ubuntu-desktop

ubuntu 20.04 has almost latest mesa so everything work just fine

In order to review the Tinker Board boot logs via serial console, I set up armbianEnv.txt to get the logs.

But Armbian didn't output anything. Can anyone tell me what is wrong?

As long as I reviewed boot.cmd, the serial port was assigned to /dev/ttyS2. So I used UART2 GPIO pins (GP7C7 for TX, GP7C6 for RX) to interact.

(snip)
if test "${console}" = "serial" || test "${console}" = "both"; then setenv consoleargs "console=ttyS2,115200n8 ${consoleargs}"; fi
(snip)

The barudrate is 115200.

Of course, I re-checked my connection between USB-UART serial cable and UART2 GPIO pins (USB-UART RX to GP7C7TX, USB-UART TX to GP7C6 RX).

Any information is helpful and appreciated.

Thanks.

----

Referenced Doc:

https://docs.armbian.com/User-Guide_Allwinner_overlays/#example-bootarmbianenvtxt-contents

my armbianEnv.txt:

I added console=serial.

verbosity=1
console=serial
overlay_prefix=rockchip
overlays=i2c1 i2c4 spi2 spidev2 uart1 uart2
rootdev=UUID=(stripped)
rootfstype=ext4
usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u

USB UART Cable:
FTDI TTL-232R-3V3

Board Product:

ASUS Tinker Board (Power supply via GPIO, 5V4A)

Armbian Image File:
Armbian_20.05.2_Tinkerboard_buster_current_5.4.44_minimal.img.xz

OS Info:

root@tinkerboard:/boot# cat /etc/armbian-release 
# PLEASE DO NOT EDIT THIS FILE
BOARD=tinkerboard
BOARD_NAME="Tinkerboard"
BOARDFAMILY=rockchip
BUILD_REPOSITORY_URL=https://github.com/armbian/build
BUILD_REPOSITORY_COMMIT=2efd215a
DISTRIBUTION_CODENAME=buster
DISTRIBUTION_STATUS=supported
VERSION=20.05.2
LINUXFAMILY=rockchip
BRANCH=current
ARCH=arm
IMAGE_TYPE=stable
BOARD_TYPE=conf
INITRD_ARCH=arm
KERNEL_IMAGE_TYPE=Image

root@tinkerboard:/boot# uname -a
Linux tinkerboard 5.4.44-rockchip #20.05.2 SMP PREEMPT Wed Jun 3 10:43:15 CEST 2020 armv7l GNU/Linux

Hello people, I use a Tinker Board as a low power desktop computer for browsing, office documents and general tinkering, and after all this time it got personalized enough to worry about loosing all this setup and it is a hassle to just overwrite everything every time a new image comes around.

Was wondering if it is possible to use apt dist-upgrade as means to get from Bionic Desktop 5.4 to Focal Desktop 5.4 as can be done on x86 platforms without breaking everything?

I logged an issue a little while ago with Armbian running on the Tinkerboard that the screen when rotated 90 degrees couldn't draw the screen at any speed.

I have been playing with a few alternatives incl going back to the original tinkeros. All have issues so I was delighted to see the FOCAL port.

I am using the recommended Waveshare 7" touchscreen that you advertise on the home page as tested 3rd party hardware.

Both the desktop and the server versions of Focal come up with the error Configure crtc 0 failed setting mode when I manually set the supported resolution of 1024 x 600 at 60Hz using xrandr

Exactly the same settings on TinkerOS works perfectly., but has many other issues!

In the /var/log/Xorg.0.log file there is an message

Allocate new frame buffer 1024 x 600 stride

failed to set mode : Invalid argument.

I used cvt to generate the modeline using settings 1024 600 60

then I used xrandr --newmode and added the modeline

xrandr --addmode HDMI-1 1024x600_60.00

When I set the output to use this setting

xrandr --output HDMI-1 --mode "1024x600_60.00" 

I get the error crtc 0 failed.

As mentioned this works on TinkerOS and is the device that is included in the tested 3rd party hardware. 

What I am doing wrong? 

Thanks in advance.

Hello people, I have an Asus Tinker Board S and decided to use the Mainline Armbian for this board, love the new panfrost driver but seems it is glitching all over the place, icons in the menu disappear and reappear when mouse hovers over them, tick boxes do not show if they are ticked and only flicker when mouse is over them and applications menu keep redrawing all over when trying to use among the most prominent problems. Other operating systems work well in this matter.

Anyone else is having these problems with the mainline 5.4.28 kernel build?

So recently I decided to use my (quite old) tinker board, I downloaded the last armbian (desktop, 4.4.213) OS, managed to install a vncserver (x11vnc) and also to use it without a screen plugged in it. And now I would like to turn it into a urbackup server, but I got some error with mdadm, "Module md_mod not found in directory /lib/modules/4.4.213-rockchip".
I tried to use this forum to find a solution (https://github.com/armbian/build), but I couldn't make it work. When i tipe ´´git clone https://github.com/armbian/build´´ it stop around 7% at resolving deltas, and it just freeze.

Someone could have any idea how to solve this issue??

And i can't get my armbianmonitor link to paste......

Thanks guys.

If anyone has troubles with HDMI when using 5.x kernels, and has enough skills to recompile an armbian, give this a try : https://github.com/Miouyouyou/build

And then either answer here, or in the bug report : https://github.com/armbian/build/pull/1887

So I have armbian installed on a tinkerboard and have had absolutely no issues with it until I bought a new Samsung 7000 series TV (2019).  For some reason this TV does not recognize the signal coming from the tinkerboard. 

For the life of me I cannot figure out how to get this to work.  I notice a few references online about being able to force a resolution but nothing related to the rockchip boards. 

Is there an equivalent way to force a display resolution as in this article?

https://docs.armbian.com/Hardware_Allwinner/#how-to-reconfigure-video-output

I'm running 4.19.21-rockchip 5.76

I've also tried kernel 5.4.28 as well and it's the same issue.  Just for kicks I loaded Lakka on there and it works just fine so I know the board itself is working properly. 

I don't even know where to begin.  I was hoping someone could chime in and point me in the right direction. 

Hi,

I installed "Armbian_20.02.7_Tinkerboard_buster_current_5.4.28_minimal" at my tinkerboard and, in order to enable uart 4, I had to rebuild the kernel onboard (from linux-source-current-rockchip_20.02.7_all.deb).

The uart 4 came alive but the processor serial number now is missing from cpuinfo (printing 0000000000). How can I bring  it up again?

Kernel 4.19 will be the pilot for this, the discussion now that it seems to be working thanks to @martinayotte and @zador.blood.stained's feedback and examples is what to overlay.

For testing/debugging I started with some ASUS overlays for RTC and 1wire.

Easy ones:

• spidev out of the default tree but as default overlays.  instead of making 1 overlay and messing with parameters, just make 2 overlays
• DAC's:  I don't have a lot of hardware to play with, but @gkkpch has contributed to the existing ASUS overlays, if we ask super nicely maybe we'll get some help.  I2S on mainline is a question

Harder ones:

       RPI display:   I almost got this working on Mainline, I need to return to it, make it work, and make it an overlay.

       Cameras:      I honestly don't know if this is actually possible, I need to look at the drivers a bit more closely.

Original Content from Split:
 

Quote

@martinayotte I am trying to get overlays working on Rockchip, so far I have them compiling, and the boot script is loading them and such, I am having an issue with the fdt apply command, debugging tonight, something needs enabled in U-boot I assume.

I have a TinkerBoard S.

In Bionic Desktop (kernel 4.4), the wireless icon menu lists two devices: wlan0 (which is the expected interface) and p2p0: I don't know this one, but it is always chosen for auto-connecting to the local wireless lan, receiving a random IP and not the one I configured on the router.

I can then manually connect to the network with the wlan0 interface the IP is correct.

How do I disable / remove / anyway stop that p2p0 interface to "steal" the network connection?

I used

sudo swapoff -a

as suggested in this thread:

but the setting isn't persisted, and upon reboot

sudo swapon --summary

shows a partition

There's no "swap" text in my /etc/fstab

I'm trying to install Kubernetes, so I need to disable swap.

Hello, I own a Tinker Board S (bought one or two years ago) attached to a Sony Bravia KDL 22EX320 TV by HDMI, which has a native resolution of 1388x768 pixels.

Bionic desktop with kernel 5.4 (got from https://dl.armbian.com/tinkerboard/Bionic_current_desktop) didn't properly recognize the TV resolution, but set it to 1920x1024.

If I run

xrandr --props

the resolution is not listed.

I'm posting because I'm almost sure that the old TinkerOS 2.0.8 (that I installed with the board) recognized the TV resolution correctly - it anyway boots to desktop without requiring interaction, so not being able to read the text at the edges of the console is not a big issue - and I just tested that the current 2.1.11 does too: they both start in 1920x1024, but the Monitor settings windows lists 1360x768.

Back to Armbian, I however managed to create the default user and to get to the Bionic desktop; I'd like to add that the display settings window should have a "Test" function that reverts to the previous settings if the new aren't confirmed, because if the chosen resolution isn't supported, the screen stays black.

I have Tinker Board S. I have been using both Tinker OS and Armbian for a while. Recently I upgraded to 5.4.28-rockchip. I noticed that randomly and frequently when I watch cnn.com or other media, my video would freeze. Initially I thought the firefox or chromium crashes. However, later, I realized it was the network issue. Other devices were still able to connect to the internet. When I checked the ifconfig, the network devices still showed proper connection. However, there is no way to ping any URLs. Disconnecting/reconnecting network does not fix the issue. The only fix was reboot.

How can I troubleshoot this issue? I was trying to do armbianmonitor but at that time, there was no network at all.

http://ix.io/2fVR This is armbianmonitor after reboot and no problem at all.  for baseline reference. 

i had 2 ASUS TinkerBoard S and I want to work with your software...

The Software was via Etcher installed on several MC - Cards (16, 32 and 64 GB), but it still not working.

The POWER - LED is red and the both LEDs on GBIC - Interface are blinking green and yellow :-(

So, what kind of problems that  I have here.

I tried out several IMAGE from your WebSite - but no one won't to work with me :-(

Best regards

Matthias 

Using Linux tinkerboard 4.19.69-rockchip #5.95 SMP PREEMPT Mon Sep 2 07:34:36 CEST 2019 armv7l armv7l armv7l GNU/Linux

Using glxgears as a test case.. I get 60fps without the screen rotated.  If I rotate the screen right or left the frame rate drops to 4fps.  That's on a fresh boot with nothing else running.  I tested TinkerOS on the same board and it works fine rotated.  My Raspberry PI 4 works fine rotated as well.  What could be the problem with Armbian?

Anyone have an issue where on a fresh install with apt update and upgrade I create a hotspot then have openvpn connect on boot. It works fine as a hotspot with 200mbps up and down but when the traffic is routes through a vpn by connecting openvpn the board will crash/become unresponsive if the upload is used heavily. Works great until I run a speedtest and on the upload the board will crash. Normal use is fine even pegging download causes no issue. Le potato s905x works amazing in this regard and never crashes period. Is this a known bug?

Hi!

I seem to have the same problem described here:

I have an Asus Tinkerboard, not the S version.

Today I upgraded from the latest Asus TinkerOS image:

20190821-tinker-board-linaro-stretch-alip-v2.0.11.img

to:

Armbian_19.11.3.346_Tinkerboard_buster_current_5.3.15_minimal.img

I notice that my maximum CPU frequency has dropped from 1.80GHz to 1.61GHz.

cpufreq-info now reports:

$ cpufreq-info
cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 115 us.
  hardware limits: 126 MHz - 1.61 GHz

...

and my cpufrequtils config is unmodified:

$ cat /etc/default/cpufrequtils
ENABLE=true
MIN_SPEED=600000
MAX_SPEED=1900000
GOVERNOR=ondemand

Whereas on TinkerOS, cpufreq-info reported:

$ cpufreq-info

cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
Report errors and bugs to cpufreq@vger.kernel.org, please.
analyzing CPU 0:
  driver: cpufreq-dt
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 115 us.
  hardware limits: 126 MHz - 1.80 GHz

...

Is this something I can change locally, or does something need to change in the Armbian image?

Hi guys

i am new on forum so i am sorry if this topic is in wrong place or if i badly look for answer in existing topics.

I already using bionic legacy 4.4.199 destkop for few weeks and i am happy ( only problem which i have is with bluetooth-device manager not working aftar i connect keyboard or mouse and handsfree doesnt work too)

but i see on web that there is new version so i download bionic 5.4.8 desktop to give a try. boot look normal until i get to tinkerboard login. there i use default root/1234 - it ask for changing root pass so i make it - then Retype pass and after enter it doesnt do anything. i can type anythong but enter only move to another line but nothing else.

i even try to flash twice but same result.

I have same problem on buster_current_5.4.8_minimal

is it normal (on develop) or there is problem on my TB?

thanks for answers.

(sorry for my bad english)

Hi there,

can anyone give me an URL that i can download an Armbian Stretch Release for the Tinkerboard S?

I´ve Problems with my RPI-RF-MOD and i´m thinking it is something with the new Releases.

Thx.

Hi all,

I'm trying a Tinkerboard running armbian (minimal) and DietPi.

My goal is to handle suspend and wake up.

To enter in suspend mode i run 'echo mem > /sys/power/state'.

I'm looking other ways to suspend .. by C application or by a signal on GPIO

To wakes up I notes different modes on different OSes:

- linaro pressing power button, pressing a key on usb+bt keyboard, pressing usb+bt mouse button

- dietpi - pressing power button

- armbian minimal - nothing ? my guess is that the board shuts down

Please con you confirm?

Where does reside this different behaviors?

Thanks, regards.

PS: is it possible to handle hibernation?

Hello,

I'm unable to make the RTL8723BS chip on my Tinker Board to work on AP mode with the 5.4 kernel (same configuration works on legacy kernel).  When I try to connect I get this error on dmesg:

RTL8723BS: ap recv deauth reason code(3) sta:40:4e:36:cf:8a:18

On the console I also get a bunch of kernel errors similar to this:

Message from syslogd@localhost at Dec 27 14:26:11 ...
 kernel:[  799.239910] ff60: bf0377a4 dd8057e8 dd07ffac dd07ff78 c014a17c bf0377b0 de2d9128 de2d9128
 

Is this a known problem?

Thanks

Hello,

I'm trying to show a startup logo a Tinker Board without success. I tried to add a parameter logo=/boot/boot.bmp to /boot/armbianEnv.txt but it doesn't work.

Is the boot logo implemented on the Tinker Board? Does it require a patch?

Thanks for your feedback.

+ How to resize for ramdisk, and how to using sd card as ramdisk and swap file, so emmc size will be have more space, because I want install kali into

+ If using bionic desktop, and only install kali tool for pentest, will bionic running ok ? or I must build and install kali as root ?

Hope someone can help me know it.

Thank you so much

Dear all,

I'm looking for help on having  RFCOMM TTY working on a Tinker Board S. Any help will be welcome !!

Using : Ubuntu Bionic with Armbian Linux 4.19.69-rockchip

# uname -a
Linux astrotinker 4.19.69-rockchip #5.95 SMP PREEMPT Mon Sep 2 07:34:36 CEST 2019 armv7l armv7l armv7l GNU/Linux

I'm trying to have rfcomm tty working with a bt HC-05 dongle, but RFCOMM TTY seems not to be available. The BT HC-05 is well reconized and connected:

 # bluetoothctl
[NEW] Controller 80:C5:F2:46:E2:C2 astrotinker [default]
[NEW] Device 00:14:03:06:04:ED HC-05_TIC
Agent registered

# systemctl restart bluetooth.service

# systemctl status bluetooth.service
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2019-11-25 22:23:51 CET; 3min 30s ago
     Docs: man:bluetoothd(8)
  Process: 5198 ExecStartPost=/usr/bin/rfcomm bind rfcomm1 00:14:03:06:04:ED (code=exited, status=0/SUCCESS)
 Main PID: 5196 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4784)
   CGroup: /system.slice/bluetooth.service
           └─5196 /usr/lib/bluetooth/bluetoothd -E

Nov 25 22:23:51 astrotinker bluetoothd[5196]: System does not support network plugin
Nov 25 22:23:51 astrotinker bluetoothd[5196]: Bluetooth management interface 1.14 initialized
Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSource
Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.129 path=/MediaEndpoint/A2DPSink
Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.73 path=/MediaEndpoint/A2DPSource
Nov 25 22:23:51 astrotinker bluetoothd[5196]: Endpoint registered: sender=:1.73 path=/MediaEndpoint/A2DPSink
Nov 25 22:23:51 astrotinker bluetoothd[5196]: RFCOMM server failed for Headset Voice gateway: rfcomm_bind: Address already in use (98)
Nov 25 22:23:51 astrotinker bluetoothd[5196]: RFCOMM server failed for :1.73/Profile/HSPHSProfile/00001108-0000-1000-8000-00805f9b34fb:
Nov 25 22:23:51 astrotinker rfcomm[5198]: RFCOMM TTY support not available
Nov 25 22:23:51 astrotinker systemd[1]: Started Bluetooth service.
 

# journalctl -u bluetooth.service
-- Logs begin at Mon 2019-11-25 00:30:28 CET, end at Mon 2019-11-25 22:23:52 CET. --
Nov 25 00:30:35 astrotinker systemd[1]: Starting Bluetooth service...
Nov 25 00:30:35 astrotinker bluetoothd[1466]: Bluetooth daemon 5.48
Nov 25 00:30:35 astrotinker bluetoothd[1466]: Starting SDP server
Nov 25 00:30:35 astrotinker bluetoothd[1466]: kernel lacks bnep-protocol support
Nov 25 00:30:35 astrotinker bluetoothd[1466]: System does not support network plugin
Nov 25 00:30:35 astrotinker bluetoothd[1466]: Bluetooth management interface 1.14 initialized
Nov 25 00:30:35 astrotinker rfcomm[1467]: RFCOMM TTY support not available

Regards

Franck

Hi all,

I just bought TinkerBoard S and I downloaded 

Armbian Stretch 4.19 (tried both with and without desktop ) and I tried to boot.

But no luck I was waiting for few mins but nothing.

I also tried Armbian Strech 4.4 but also nothing.

Am I missing something here?

Original TinkerOS work without any issue

Thank you for any advice/help

Hello people, I am trying to set CPU Governors but all the cores change to the same clock and cpufreq-info reports "CPUs which run at the same hardware frequency: 0 1 2 3", with that even one thread working is making the CPU scale up all clocks and heat more than it should, is there a way to unlink them and each one have their own clocks according to each core processing load?

Hello all,

I downloaded the Armbian Buster OS desktop version.

I need to run it with a vertical display - portrait mode.

The OS starts correctly and I see the desktop in landscape mode but when I try to rotate left the display, it does not rotate and return to landscape mode.

The display is a large NBT monitor 1920x1080 that I need to rotate to 1080x1920.

Any idea?

Regards

Looking for a current realtime RTOS real time deb package or SD card image for the tinkerboard. I have been trying to compile a current real time build.  All of my attempts have failed so far.  free offer described below

Hello!

I would like to know if it is possible to use the microUSB-Connector for connecting a USB device (a 7-port USB hub in my case)?

My Tinkerboard is powered through the GPIO pins, so i don't use the microUSB for power input.

Is it even possible from the hardware architecture of the board?

Do i need some extra kernel packages and/or USB OTG to make it work?

Thanks in advance,

aElmecker

Greetings,

After setting my tinkerboard pins 22 and 24 as an Inputs, they reverts to being an output pin on HIgh after around 30 seconds. What is the cause of this? Is this some kind of feature. I don't have this happen on any other pin other than these 2.

iomari

Greetings,

On the tinkerBoard, I'm using python.

I having difficulty understanding why the functions don't return the values that is expected according tho the library help.

I'm using python3 and the ASUS GPIO library.

import ASUS.GPIO as GPIO 

GPIO.setmode(GPIO.BOARD)

This is the output from ipython:

In [18]: help(GPIO.gpio_function)                                                                                                                                                                                    
Help on built-in function gpio_function in module ASUS.GPIO:

gpio_function(...)
    Return the current GPIO function (IN, OUT, PWM, SERIAL, I2C, SPI)
    channel - either board pin number ,RK number or ASUS number depending on which mode is set.

But when I try for instance:

In [19]: GPIO.gpio_function(29)                                                                                                                                                                                      
Out[19]: 1

AS you can see, the return value is '1' not  (IN, OUT, PWM, SERIAL, I2C, SPI)

Also if I run:

In [20]: help(GPIO.getmode)                                                                                                                                                                                         
Help on built-in function getmode in module ASUS.GPIO:

getmode(...)
    Get numbering mode used for channel numbers.
    Returns BOARD, RK, ASUS or UNKNOWN

Then I run:

In [21]: GPIO.getmode()                                                                                                                                                                                              
Out[21]: 10
 

As you can see, I'm not getting a return of 'BOARD, RK, ASUS or UNKNOWN'

but instead I'm getting 10.

IS it me or are the outputs to these functions wrong?

iomari

Hi 

I have a problem with change desktop language from en to polish. I tryed all solutions armbian-config , dpkg-reconfigure locales, export LANG. 

After reboot I got english desktop and locale info 

http://ecocut.pl/wp-content/uploads/2019/03/locale-1.jpg

Hi, 

I am looking for a solution to have the JustBoom and HifiBerry Audio Hat with dtoverlays working like in the TinkerOS 2.0.8 Image from ASUS.

Does someone known and has a procedure how to compile those and integrate in the Image or Compile a new kernel with its integration or a way to get those two hat's working?

Many Thanks for your help

Roman

Hi,

I spent several days trying to figure this out, which is a bit confusing given all the information that is available and posts and wikis saying that "Waveshare" LCDs are supposed to work, but something is still not right, hope you guys can help.

What I have:

ASUS Tinker Board S, flashed with Armbian_5.90_Tinkerboard_Debian_buster_default_4.4.182_desktop.img

Updated to 4.19.57-rockchip via armbian-config (in order to get the fbtft* modules that were missing in 4.4).

The LCD is a 3.5" original Waveshare 32a panel.

I started by adding the overlay for this screen (i.e. my armbianEnv.txt has these overlays: overlays=i2c1 i2c4 spi2 waveshare35a-tinker uart1 uart2):

https://github.com/TinkerBoard/debian_kernel/blob/develop/arch/arm/boot/dts/overlays/waveshare35a-tinker-overlay.dts

I have a serial console connection and I could see that the overlay is getting loaded upon boot:

Applying kernel provided DT overlay rockchip-i2c1.dtbo
286 bytes read in 1 ms (279.3 KiB/s)
Applying kernel provided DT overlay rockchip-i2c4.dtbo
311 bytes read in 1 ms (303.7 KiB/s)
Applying kernel provided DT overlay rockchip-spi2.dtbo
2224 bytes read in 2 ms (1.1 MiB/s)
Applying kernel provided DT overlay rockchip-waveshare35a-tinker.dtbo
287 bytes read in 2 ms (139.6 KiB/s)
Applying kernel provided DT overlay rockchip-uart1.dtbo
287 bytes read in 1 ms (280.3 KiB/s)
Applying kernel provided DT overlay rockchip-uart2.dtbo
232 bytes read in 1 ms (226.6 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)

Adding the above overlay made the touchscreen work out of the box, however the framebuffer device didn't. In dmesg I could see the following:

[   15.706674] fbtft: module is from the staging directory, the quality is unknown, you have been warned.
[   15.712403] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned.
[   15.712696] rockchip-pinctrl pinctrl: unable to find group for node waveshare35a_pins
[   15.712708] fb_ili9486: probe of spi2.0 failed with error -22

I read the driver sources, pinctrl documentation, overlay documentation, but being a userspace coder I did not really know what to make of all this and the above pinctrl error message.

The waveshare nodes were available in the live device tree, so I am not sure why this line triggers and where this "group" is supposed to be coming from:

https://github.com/armbian/linux/blob/rockchip/drivers/pinctrl/pinctrl-rockchip.c#L566

I then tried to configure the fbtft_device driver manually using the following parameters (tried to use the values from the waveshare dts):

modprobe fbtft_device custom name=fb_ili9486 gpios=dc:163,reet:171 speed=15000000 busnum=2 rotate=270 fps=30 txbuflen=32768 bgr=0 width=480 height=320

The above made half of the screen to react, settig the rotation to 0 allowed to access the whole screen (tried catting /dev/random into /dev/fb0 which fills the screen with random colored pixels).

I added xorg settings as suggested in the tinkerboard wiki and started xorg:

Section "Device"
    Identifier  "Rockchip Graphics"
    Driver      "fbdev"
    Option      "fbdev"          "/dev/fb0"
    Option      "DRI"            "2"
EndSection

However the image looked totally distorted (I had the feeling that its drawing every other line), it was however vaguely recognizable as some text / X login screen.

Just out of curiosity I removed the overlay, rebooted and again loaded the driver as above with the same result (only that touchscreen did not work anymore as expected).

I am adding a full dmesg output with the overlay applied, the first fbtft load attempt is the "automatic" one and shows the rockchip pinctrl error, the second fbtft loading comes from my manual modprobe line which I pasted earlier.

I have no idea where to go from here, I thought those Waveshare screens are well supported, and from what I read they seem to work for others. What am I missing?

Kind regards,

Jin

P.S. ...couple of hours later...

Turned out that the results are a lot better if width and height parameters are left out. While the dts suggests to use bgr=0, bgr=1 gives correct colors, but it seems that the gamma is totally off. I also tried taking the init sequence from the dts and passing it to fbtft_device, but I could not see any difference.

So right now I ended up with the following line and results:

modprobe fbtft_device custom name=fb_ili9486 bgr=1 gpios=dc:163,reset:171 speed=15000000 busnum=2 fps=30 txbuflen=32768

Original image for comparison:

So, some progress at last, I'd however be still interested in fixing the pinctrl problem and understanding why the dts would not work...
Next question of course - how to come up with proper gamma values?

[    0.000000] Booting Linux on physical CPU 0x500
[    0.000000] Linux version 4.19.57-rockchip (root@nightly) (gcc version 7.4.1 20181213 [linaro-7.4-2019.02 revision 56ec6f6b99cc167ff0c2f8e1a2eed33b1edc85d4] (Linaro GCC 7.4-2019.02)) #5.90 SMP PREEMPT Sat Jul 6 11:15:03 CEST 2019
[    0.000000] CPU: ARMv7 Processor [410fc0d1] revision 1 (ARMv7), cr=10c5387d
[    0.000000] CPU: div instructions available: patching division code
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: Rockchip RK3288 Tinker Board
[    0.000000] Memory policy: Data cache writealloc
[    0.000000] On node 0 totalpages: 524288
[    0.000000]   Normal zone: 1728 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 196608 pages, LIFO batch:63
[    0.000000]   HighMem zone: 327680 pages, LIFO batch:63
[    0.000000] random: get_random_bytes called from start_kernel+0xa8/0x4c0 with crng_init=0
[    0.000000] percpu: Embedded 18 pages/cpu s43032 r8192 d22504 u73728
[    0.000000] pcpu-alloc: s43032 r8192 d22504 u73728 alloc=18*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3 
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 522560
[    0.000000] Kernel command line: earlyprintk root=UUID=a26ac16a-d702-4a37-b486-8fb5073e7627 rootwait rootfstype=ext4 console=ttyS2,115200n8  panic=10 consoleblank=0 loglevel=1 ubootpart=a11b0125-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   cgroup_enable=cpuset cgroup_memory=1 cgroup_enable=memory swapaccount=1
[    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] allocated 2097152 bytes of page_ext
[    0.000000] Memory: 2042376K/2097152K available (14336K kernel code, 972K rwdata, 2752K rodata, 2048K init, 4696K bss, 54776K reserved, 0K cma-reserved, 1310720K highmem)
[    0.000000] Virtual kernel memory layout:
                   vector  : 0xffff0000 - 0xffff1000   (   4 kB)
                   fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
                   vmalloc : 0xf0800000 - 0xff800000   ( 240 MB)
                   lowmem  : 0xc0000000 - 0xf0000000   ( 768 MB)
                   pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
                   modules : 0xbf000000 - 0xbfe00000   (  14 MB)
                     .text : 0x(ptrval) - 0x(ptrval)   (15328 kB)
                     .init : 0x(ptrval) - 0x(ptrval)   (2048 kB)
                     .data : 0x(ptrval) - 0x(ptrval)   ( 973 kB)
                      .bss : 0x(ptrval) - 0x(ptrval)   (4697 kB)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] ftrace: allocating 42774 entries in 126 pages
[    0.000000] rcu: Preemptible hierarchical RCU implementation.
[    0.000000] 	Tasks RCU enabled.
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] rockchip_mmc_get_phase: invalid clk rate
[    0.000000] 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.000008] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.000022] Switching to timer-based delay loop, resolution 41ns
[    0.001817] Console: colour dummy device 80x30
[    0.001860] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.001879] pid_max: default: 32768 minimum: 301
[    0.002046] Security Framework initialized
[    0.002056] Yama: becoming mindful.
[    0.002146] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.002164] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.003117] CPU: Testing write buffer coherency: ok
[    0.003163] CPU0: Spectre v2: using BPIALL workaround
[    0.003545] CPU0: thread -1, cpu 0, socket 5, mpidr 80000500
[    0.028039] Setting up static identity map for 0x100000 - 0x100060
[    0.036044] rcu: Hierarchical SRCU implementation.
[    0.052154] smp: Bringing up secondary CPUs ...
[    0.085663] CPU1: thread -1, cpu 1, socket 5, mpidr 80000501
[    0.085672] CPU1: Spectre v2: using BPIALL workaround
[    0.117863] CPU2: thread -1, cpu 2, socket 5, mpidr 80000502
[    0.117872] CPU2: Spectre v2: using BPIALL workaround
[    0.150080] CPU3: thread -1, cpu 3, socket 5, mpidr 80000503
[    0.150088] CPU3: Spectre v2: using BPIALL workaround
[    0.150304] smp: Brought up 1 node, 4 CPUs
[    0.150317] SMP: Total of 4 processors activated (192.00 BogoMIPS).
[    0.150324] CPU: All CPU(s) started in SVC mode.
[    0.152187] devtmpfs: initialized
[    0.168016] VFP support v0.3: implementor 41 architecture 3 part 30 variant d rev 0
[    0.168503] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.168525] futex hash table entries: 1024 (order: 4, 65536 bytes)
[    0.168969] xor: measuring software checksum speed
[    0.209042]    arm4regs  :  1042.000 MB/sec
[    0.249156]    8regs     :   803.000 MB/sec
[    0.289276]    32regs    :   801.000 MB/sec
[    0.329389]    neon      :  1330.000 MB/sec
[    0.329398] xor: using function: neon (1330.000 MB/sec)
[    0.329464] pinctrl core: initialized pinctrl subsystem
[    0.330668] NET: Registered protocol family 16
[    0.333551] DMA: preallocated 2048 KiB pool for atomic coherent allocations
[    0.334191] audit: initializing netlink subsys (disabled)
[    0.334417] audit: type=2000 audit(0.332:1): state=initialized audit_enabled=0 res=1
[    0.335944] cpuidle: using governor ladder
[    0.335999] cpuidle: using governor menu
[    0.337134] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[    0.337144] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.359598] gpio gpiochip0: (gpio0): added GPIO chardev (254:0)
[    0.359727] gpiochip_setup_dev: registered GPIOs 0 to 23 on device: gpiochip0 (gpio0)
[    0.359957] gpio gpiochip1: (gpio1): added GPIO chardev (254:1)
[    0.360067] gpiochip_setup_dev: registered GPIOs 24 to 55 on device: gpiochip1 (gpio1)
[    0.360292] gpio gpiochip2: (gpio2): added GPIO chardev (254:2)
[    0.360399] gpiochip_setup_dev: registered GPIOs 56 to 87 on device: gpiochip2 (gpio2)
[    0.360622] gpio gpiochip3: (gpio3): added GPIO chardev (254:3)
[    0.360731] gpiochip_setup_dev: registered GPIOs 88 to 119 on device: gpiochip3 (gpio3)
[    0.360962] gpio gpiochip4: (gpio4): added GPIO chardev (254:4)
[    0.361079] gpiochip_setup_dev: registered GPIOs 120 to 151 on device: gpiochip4 (gpio4)
[    0.361297] gpio gpiochip5: (gpio5): added GPIO chardev (254:5)
[    0.361416] gpiochip_setup_dev: registered GPIOs 152 to 183 on device: gpiochip5 (gpio5)
[    0.361624] gpio gpiochip6: (gpio6): added GPIO chardev (254:6)
[    0.361737] gpiochip_setup_dev: registered GPIOs 184 to 215 on device: gpiochip6 (gpio6)
[    0.361999] gpio gpiochip7: (gpio7): added GPIO chardev (254:7)
[    0.362110] gpiochip_setup_dev: registered GPIOs 216 to 247 on device: gpiochip7 (gpio7)
[    0.362337] gpio gpiochip8: (gpio8): added GPIO chardev (254:8)
[    0.362445] gpiochip_setup_dev: registered GPIOs 248 to 263 on device: gpiochip8 (gpio8)
[    0.463058] raid6: int32x1  gen()    89 MB/s
[    0.530840] raid6: int32x1  xor()   104 MB/s
[    0.599447] raid6: int32x2  gen()   101 MB/s
[    0.667234] raid6: int32x2  xor()   127 MB/s
[    0.735624] raid6: int32x4  gen()   163 MB/s
[    0.803879] raid6: int32x4  xor()   137 MB/s
[    0.872120] raid6: int32x8  gen()   201 MB/s
[    0.940330] raid6: int32x8  xor()   129 MB/s
[    1.008421] raid6: neonx1   gen()   345 MB/s
[    1.076565] raid6: neonx1   xor()   453 MB/s
[    1.144778] raid6: neonx2   gen()   426 MB/s
[    1.212946] raid6: neonx2   xor()   608 MB/s
[    1.281166] raid6: neonx4   gen()   741 MB/s
[    1.349343] raid6: neonx4   xor()   712 MB/s
[    1.417567] raid6: neonx8   gen()   650 MB/s
[    1.485736] raid6: neonx8   xor()   625 MB/s
[    1.485744] raid6: using algorithm neonx4 gen() 741 MB/s
[    1.485751] raid6: .... xor() 712 MB/s, rmw enabled
[    1.485758] raid6: using neon recovery algorithm
[    1.486410] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/vsys-regulator[0]'
[    1.486921] of_get_named_gpiod_flags: parsed 'gpio' property of node '/sdmmc-regulator[0]' - status (0)
[    1.490751] SCSI subsystem initialized
[    1.491041] usbcore: registered new interface driver usbfs
[    1.491110] usbcore: registered new interface driver hub
[    1.491194] usbcore: registered new device driver usb
[    1.491311] media: Linux media interface: v0.10
[    1.491356] videodev: Linux video capture interface: v2.00
[    1.491521] pps_core: LinuxPPS API ver. 1 registered
[    1.491530] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    1.491557] PTP clock support registered
[    1.492940] Bluetooth: Core ver 2.22
[    1.493004] NET: Registered protocol family 31
[    1.493013] Bluetooth: HCI device and connection manager initialized
[    1.493029] Bluetooth: HCI socket layer initialized
[    1.493041] Bluetooth: L2CAP socket layer initialized
[    1.493151] Bluetooth: SCO socket layer initialized
[    1.494166] clocksource: Switched to clocksource arch_sys_counter
[    1.682963] VFS: Disk quotas dquot_6.6.0
[    1.683056] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    1.683257] FS-Cache: Loaded
[    1.683504] CacheFiles: Loaded
[    1.698535] NET: Registered protocol family 2
[    1.699431] tcp_listen_portaddr_hash hash table entries: 512 (order: 1, 12288 bytes)
[    1.699484] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[    1.699591] TCP bind hash table entries: 8192 (order: 5, 163840 bytes)
[    1.699864] TCP: Hash tables configured (established 8192 bind 8192)
[    1.700020] UDP hash table entries: 512 (order: 2, 24576 bytes)
[    1.700090] UDP-Lite hash table entries: 512 (order: 2, 24576 bytes)
[    1.700400] NET: Registered protocol family 1
[    1.701175] RPC: Registered named UNIX socket transport module.
[    1.701184] RPC: Registered udp transport module.
[    1.701190] RPC: Registered tcp transport module.
[    1.701197] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.702037] Trying to unpack rootfs image as initramfs...
[    2.251983] Freeing initrd memory: 6380K
[    2.253233] hw perfevents: enabled with armv7_cortex_a12 PMU driver, 7 counters available
[    2.255705] Initialise system trusted keyrings
[    2.255970] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    2.264649] zbud: loaded
[    2.267012] FS-Cache: Netfs 'nfs' registered for caching
[    2.267788] NFS: Registering the id_resolver key type
[    2.267823] Key type id_resolver registered
[    2.267831] Key type id_legacy registered
[    2.267853] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    2.268124] SGI XFS with ACLs, security attributes, realtime, no debug enabled
[    2.283453] async_tx: api initialized (async)
[    2.283468] Key type asymmetric registered
[    2.283477] Asymmetric key parser 'x509' registered
[    2.283551] bounce: pool size: 64 pages
[    2.283607] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 243)
[    2.287850] io scheduler noop registered
[    2.287860] io scheduler deadline registered
[    2.288083] io scheduler cfq registered (default)
[    2.288094] io scheduler mq-deadline registered
[    2.288102] io scheduler kyber registered
[    2.295813] dma-pl330 ff250000.dma-controller: Loaded driver for PL330 DMAC-241330
[    2.295830] dma-pl330 ff250000.dma-controller: 	DBUFF-128x8bytes Num_Chans-8 Num_Peri-20 Num_Events-16
[    2.296768] dma-pl330 ffb20000.dma-controller: Loaded driver for PL330 DMAC-241330
[    2.296784] dma-pl330 ffb20000.dma-controller: 	DBUFF-64x8bytes Num_Chans-5 Num_Peri-6 Num_Events-10
[    2.297528] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[    2.299814] ff180000.serial: ttyS0 at MMIO 0xff180000 (irq = 39, base_baud = 1500000) is a 16550A
[    2.300820] ff190000.serial: ttyS1 at MMIO 0xff190000 (irq = 40, base_baud = 1500000) is a 16550A
[    2.301830] ff690000.serial: ttyS2 at MMIO 0xff690000 (irq = 41, base_baud = 1500000) is a 16550A
[    2.302049] console [ttyS2] enabled
[    2.304461] iommu: Adding device ff930000.vop to group 0
[    2.304728] rockchip-vop ff930000.vop: Linked as a consumer to ff930300.iommu
[    2.305133] iommu: Adding device ff940000.vop to group 1
[    2.305181] rockchip-vop ff940000.vop: Linked as a consumer to ff940300.iommu
[    2.306897] rockchip-drm display-subsystem: Linked as a consumer to ff930000.vop
[    2.306935] rockchip-drm display-subsystem: Linked as a consumer to ff940000.vop
[    2.307468] rockchip-drm display-subsystem: Linked as a consumer to ff980000.hdmi
[    2.308276] rockchip-drm display-subsystem: bound ff930000.vop (ops 0xc0f6d3fc)
[    2.308762] rockchip-drm display-subsystem: bound ff940000.vop (ops 0xc0f6d3fc)
[    2.308851] rockchip-drm display-subsystem: failed to bind ff980000.hdmi (ops 0xc0f6ea90): -517
[    2.309094] rockchip-drm display-subsystem: master bind failed: -517
[    2.309438] usbcore: registered new interface driver udl
[    2.314037] brd: module loaded
[    2.326677] loop: module loaded
[    2.330110] mdio_bus fixed-0: GPIO lookup for consumer reset
[    2.330123] mdio_bus fixed-0: using lookup tables for GPIO lookup
[    2.330135] mdio_bus fixed-0: No GPIO consumer reset found
[    2.330327] libphy: Fixed MDIO Bus: probed
[    2.331655] rk_gmac-dwmac ff290000.ethernet: PTP uses main clock
[    2.331697] rk_gmac-dwmac ff290000.ethernet: phy regulator is not available yet, deferred probing
[    2.333123] usbcore: registered new interface driver rt2500usb
[    2.333187] usbcore: registered new interface driver rt73usb
[    2.333252] usbcore: registered new interface driver rt2800usb
[    2.333321] usbcore: registered new interface driver rtl8xxxu
[    2.333396] usbcore: registered new interface driver rndis_wlan
[    2.333459] usbcore: registered new interface driver cdc_ether
[    2.333513] usbcore: registered new interface driver rndis_host
[    2.333900] dwc2 ff540000.usb: ff540000.usb supply vusb_d not found, using dummy regulator
[    2.333997] dwc2 ff540000.usb: Linked as a consumer to regulator.0
[    2.334019] dwc2 ff540000.usb: ff540000.usb supply vusb_a not found, using dummy regulator
[    2.394536] dwc2 ff540000.usb: DWC OTG Controller
[    2.394572] dwc2 ff540000.usb: new USB bus registered, assigned bus number 1
[    2.394618] dwc2 ff540000.usb: irq 46, io mem 0xff540000
[    2.395007] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    2.395022] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.395033] usb usb1: Product: DWC OTG Controller
[    2.395044] usb usb1: Manufacturer: Linux 4.19.57-rockchip dwc2_hsotg
[    2.395055] usb usb1: SerialNumber: ff540000.usb
[    2.395829] hub 1-0:1.0: USB hub found
[    2.395894] hub 1-0:1.0: 1 port detected
[    2.396786] dwc2 ff580000.usb: ff580000.usb supply vusb_d not found, using dummy regulator
[    2.396878] dwc2 ff580000.usb: Linked as a consumer to regulator.0
[    2.396900] dwc2 ff580000.usb: ff580000.usb supply vusb_a not found, using dummy regulator
[    2.522270] dwc2 ff580000.usb: EPs: 10, dedicated fifos, 972 entries in SPRAM
[    2.522744] dwc2 ff580000.usb: DWC OTG Controller
[    2.522788] dwc2 ff580000.usb: new USB bus registered, assigned bus number 2
[    2.522832] dwc2 ff580000.usb: irq 47, io mem 0xff580000
[    2.523125] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    2.523141] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.523152] usb usb2: Product: DWC OTG Controller
[    2.523163] usb usb2: Manufacturer: Linux 4.19.57-rockchip dwc2_hsotg
[    2.523174] usb usb2: SerialNumber: ff580000.usb
[    2.523933] hub 2-0:1.0: USB hub found
[    2.524001] hub 2-0:1.0: 1 port detected
[    2.526110] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    2.526119] ehci-platform: EHCI generic platform driver
[    2.526442] ehci-platform ff500000.usb: EHCI Host Controller
[    2.526741] ehci-platform ff500000.usb: new USB bus registered, assigned bus number 3
[    2.526908] ehci-platform ff500000.usb: irq 45, io mem 0xff500000
[    2.542228] ehci-platform ff500000.usb: USB 2.0 started, EHCI 1.00
[    2.542540] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[    2.542554] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.542566] usb usb3: Product: EHCI Host Controller
[    2.542577] usb usb3: Manufacturer: Linux 4.19.57-rockchip ehci_hcd
[    2.542587] usb usb3: SerialNumber: ff500000.usb
[    2.543318] hub 3-0:1.0: USB hub found
[    2.543383] hub 3-0:1.0: 1 port detected
[    2.544338] usbcore: registered new interface driver usb-storage
[    2.545057] usbcore: registered new interface driver iforce
[    2.545150] usbcore: registered new interface driver xpad
[    2.545322] usbcore: registered new interface driver usbtouchscreen
[    2.545944] i2c /dev entries driver
[    2.550755] rk808 0-001b: chip id: 0x0
[    2.555023] rk808 0-001b: GPIO lookup for consumer dvs
[    2.555035] rk808 0-001b: using device tree for GPIO lookup
[    2.555081] of_get_named_gpiod_flags: parsed 'dvs-gpios' property of node '/i2c@ff650000/pmic@1b[0]' - status (0)
[    2.555110] gpio gpiochip0: Persistence not supported for GPIO 11
[    2.555324] rk808 0-001b: GPIO lookup for consumer dvs
[    2.555335] rk808 0-001b: using device tree for GPIO lookup
[    2.555378] of_get_named_gpiod_flags: parsed 'dvs-gpios' property of node '/i2c@ff650000/pmic@1b[1]' - status (0)
[    2.555403] gpio gpiochip0: Persistence not supported for GPIO 12
[    2.555509] DCDC_REG1: supplied by vcc_sys
[    2.556690] DCDC_REG2: supplied by vcc_sys
[    2.557702] DCDC_REG3: supplied by vcc_sys
[    2.558070] DCDC_REG4: supplied by vcc_sys
[    2.559032] LDO_REG1: supplied by vcc_sys
[    2.560611] LDO_REG2: supplied by vcc_sys
[    2.561879] LDO_REG3: supplied by vcc_sys
[    2.563361] LDO_REG4: supplied by vcc_io
[    2.564798] LDO_REG5: supplied by vcc_io
[    2.566262] LDO_REG6: supplied by vcc_io
[    2.566536] vdd10_lcd: Bringing 800000uV into 1000000-1000000uV
[    2.567987] LDO_REG7: supplied by vcc_sys
[    2.569449] LDO_REG8: supplied by vcc_sys
[    2.570883] SWITCH_REG1: supplied by vcc_io
[    2.571317] SWITCH_REG2: supplied by vcc_io
[    2.575331] rk808-rtc rk808-rtc: registered as rtc0
[    2.577921] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consumer to regulator.13
[    2.578097] rockchip-iodomain ff770000.syscon:io-domains: Linked as a consumer to regulator.11
[    2.580472] device-mapper: ioctl: 4.39.0-ioctl (2018-04-03) initialised: dm-devel@redhat.com
[    2.580902] device-mapper: raid: Loading target version 1.14.0
[    2.581157] Bluetooth: HCI UART driver ver 2.3
[    2.581168] Bluetooth: HCI UART protocol H4 registered
[    2.581176] Bluetooth: HCI UART protocol ATH3K registered
[    2.581236] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    2.581322] usbcore: registered new interface driver bfusb
[    2.581403] usbcore: registered new interface driver btusb
[    2.581411] Bluetooth: Generic Bluetooth SDIO driver ver 0.1
[    2.582141] pwrseq_simple sdio-pwrseq: GPIO lookup for consumer reset
[    2.582204] pwrseq_simple sdio-pwrseq: using device tree for GPIO lookup
[    2.582249] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/sdio-pwrseq[0]' - status (0)
[    2.582283] gpio gpiochip4: Persistence not supported for GPIO 28
[    2.582316] pwrseq_simple sdio-pwrseq: GPIO lookup for consumer reset
[    2.582326] pwrseq_simple sdio-pwrseq: using device tree for GPIO lookup
[    2.582365] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/sdio-pwrseq[1]' - status (0)
[    2.582391] gpio gpiochip4: Persistence not supported for GPIO 27
[    2.582840] sdhci: Secure Digital Host Controller Interface driver
[    2.582847] sdhci: Copyright(c) Pierre Ossman
[    2.582853] Synopsys Designware Multimedia Card Interface Driver
[    2.583881] dwmmc_rockchip ff0c0000.dwmmc: IDMAC supports 32-bit address mode.
[    2.583926] dwmmc_rockchip ff0c0000.dwmmc: Using internal DMA controller.
[    2.583944] dwmmc_rockchip ff0c0000.dwmmc: Version ID is 270a
[    2.584019] dwmmc_rockchip ff0c0000.dwmmc: DW MMC controller at irq 30,32 bit host data width,256 deep fifo
[    2.584166] dwmmc_rockchip ff0c0000.dwmmc: Linked as a consumer to regulator.15
[    2.584285] dwmmc_rockchip ff0c0000.dwmmc: Linked as a consumer to regulator.11
[    2.584326] dwmmc_rockchip ff0c0000.dwmmc: GPIO lookup for consumer cd
[    2.584336] dwmmc_rockchip ff0c0000.dwmmc: using device tree for GPIO lookup
[    2.584364] of_get_named_gpiod_flags: can't parse 'cd-gpios' property of node '/dwmmc@ff0c0000[0]'
[    2.584387] of_get_named_gpiod_flags: can't parse 'cd-gpio' property of node '/dwmmc@ff0c0000[0]'
[    2.584400] dwmmc_rockchip ff0c0000.dwmmc: using lookup tables for GPIO lookup
[    2.584411] dwmmc_rockchip ff0c0000.dwmmc: No GPIO consumer cd found
[    2.584426] dwmmc_rockchip ff0c0000.dwmmc: GPIO lookup for consumer wp
[    2.584437] dwmmc_rockchip ff0c0000.dwmmc: using device tree for GPIO lookup
[    2.584458] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff0c0000[0]'
[    2.584477] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff0c0000[0]'
[    2.584489] dwmmc_rockchip ff0c0000.dwmmc: using lookup tables for GPIO lookup
[    2.584500] dwmmc_rockchip ff0c0000.dwmmc: No GPIO consumer wp found
[    2.597417] mmc_host mmc0: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    2.611063] dwmmc_rockchip ff0d0000.dwmmc: IDMAC supports 32-bit address mode.
[    2.611105] dwmmc_rockchip ff0d0000.dwmmc: Using internal DMA controller.
[    2.611123] dwmmc_rockchip ff0d0000.dwmmc: Version ID is 270a
[    2.611209] dwmmc_rockchip ff0d0000.dwmmc: DW MMC controller at irq 31,32 bit host data width,256 deep fifo
[    2.611296] dwmmc_rockchip ff0d0000.dwmmc: GPIO lookup for consumer wp
[    2.611307] dwmmc_rockchip ff0d0000.dwmmc: using device tree for GPIO lookup
[    2.611333] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff0d0000[0]'
[    2.611355] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff0d0000[0]'
[    2.611368] dwmmc_rockchip ff0d0000.dwmmc: using lookup tables for GPIO lookup
[    2.611380] dwmmc_rockchip ff0d0000.dwmmc: No GPIO consumer wp found
[    2.611446] dwmmc_rockchip ff0d0000.dwmmc: allocated mmc-pwrseq
[    2.611459] mmc_host mmc1: card is non-removable.
[    2.624591] mmc_host mmc1: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    2.638002] dwmmc_rockchip ff0f0000.dwmmc: IDMAC supports 32-bit address mode.
[    2.638054] dwmmc_rockchip ff0f0000.dwmmc: Using internal DMA controller.
[    2.638073] dwmmc_rockchip ff0f0000.dwmmc: Version ID is 270a
[    2.638192] dwmmc_rockchip ff0f0000.dwmmc: DW MMC controller at irq 32,32 bit host data width,256 deep fifo
[    2.638339] dwmmc_rockchip ff0f0000.dwmmc: GPIO lookup for consumer wp
[    2.638351] dwmmc_rockchip ff0f0000.dwmmc: using device tree for GPIO lookup
[    2.638378] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/dwmmc@ff0f0000[0]'
[    2.638400] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/dwmmc@ff0f0000[0]'
[    2.638414] dwmmc_rockchip ff0f0000.dwmmc: using lookup tables for GPIO lookup
[    2.638425] dwmmc_rockchip ff0f0000.dwmmc: No GPIO consumer wp found
[    2.638488] mmc_host mmc2: card is non-removable.
[    2.645429] random: fast init done
[    2.651329] mmc_host mmc2: Bus speed (slot 0) = 400000Hz (slot req 400000Hz, actual 400000HZ div = 0)
[    2.654693] mmc_host mmc1: Bus speed (slot 0) = 50000000Hz (slot req 50000000Hz, actual 50000000HZ div = 0)
[    2.657184] mmc1: new high speed SDIO card at address 0001
[    2.662762] sdhci-pltfm: SDHCI platform and OF driver helper
[    2.663040] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-leds/act-led[0]' - status (0)
[    2.663076] gpio gpiochip1: Persistence not supported for GPIO 24
[    2.663084] no flags found for gpios
[    2.663295] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-leds/heartbeat-led[0]' - status (0)
[    2.663325] gpio gpiochip1: Persistence not supported for GPIO 25
[    2.663332] no flags found for gpios
[    2.663569] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-leds/pwr-led[0]' - status (0)
[    2.663597] gpio gpiochip0: Persistence not supported for GPIO 3
[    2.663604] no flags found for gpios
[    2.664139] ledtrig-cpu: registered to indicate activity on CPUs
[    2.664329] hidraw: raw HID events driver (C) Jiri Kosina
[    2.664723] usbcore: registered new interface driver usbhid
[    2.664731] usbhid: USB HID core driver
[    2.665179] ashmem: initialized
[    2.665650] rockchip-saradc ff100000.saradc: Linked as a consumer to regulator.7
[    2.668954] NET: Registered protocol family 10
[    2.724388] mmc_host mmc2: Bus speed (slot 0) = 148500000Hz (slot req 150000000Hz, actual 148500000HZ div = 0)
[    2.727624] Segment Routing with IPv6
[    2.728620] NET: Registered protocol family 17
[    2.728694] bridge: filtering via arp/ip/ip6tables is no longer available by default. Update your scripts to load br_netfilter if you need this.
[    2.728879] Bluetooth: RFCOMM socket layer initialized
[    2.728917] Bluetooth: RFCOMM ver 1.11
[    2.728940] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[    2.728956] Bluetooth: HIDP socket layer initialized
[    2.729019] 8021q: 802.1Q VLAN Support v1.8
[    2.729052] lib80211: common routines for IEEE802.11 drivers
[    2.729061] lib80211_crypt: registered algorithm 'NULL'
[    2.729069] lib80211_crypt: registered algorithm 'WEP'
[    2.729077] lib80211_crypt: registered algorithm 'CCMP'
[    2.729085] lib80211_crypt: registered algorithm 'TKIP'
[    2.729120] Key type dns_resolver registered
[    2.729579] ThumbEE CPU extension supported.
[    2.729596] Registering SWP/SWPB emulation handler
[    2.730782] Loading compiled-in X.509 certificates
[    2.730889] zswap: loaded using pool lzo/zbud
[    2.732533] Btrfs loaded, crc32c=crc32c-generic
[    2.780009] rockchip-drm display-subsystem: bound ff930000.vop (ops 0xc0f6d3fc)
[    2.780435] rockchip-drm display-subsystem: bound ff940000.vop (ops 0xc0f6d3fc)
[    2.780703] dwhdmi-rockchip ff980000.hdmi: Detected HDMI TX controller v2.00a with HDCP (DWC MHL PHY)
[    2.781508] rockchip-drm display-subsystem: bound ff980000.hdmi (ops 0xc0f6ea90)
[    2.781520] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[    2.781526] [drm] No driver support for vblank timestamp query.
[    2.781575] [drm] Cannot find any crtc or sizes
[    2.782421] [drm] Initialized rockchip 1.0.0 20140818 for display-subsystem on minor 0
[    2.783432] rk_gmac-dwmac ff290000.ethernet: PTP uses main clock
[    2.783583] rk_gmac-dwmac ff290000.ethernet: Linked as a consumer to regulator.16
[    2.783601] rk_gmac-dwmac ff290000.ethernet: clock input or output? (input).
[    2.783616] rk_gmac-dwmac ff290000.ethernet: TX delay(0x30).
[    2.783629] rk_gmac-dwmac ff290000.ethernet: RX delay(0x10).
[    2.783645] rk_gmac-dwmac ff290000.ethernet: integrated PHY? (no).
[    2.783732] rk_gmac-dwmac ff290000.ethernet: cannot get clock clk_mac_speed
[    2.783743] rk_gmac-dwmac ff290000.ethernet: clock input from PHY
[    2.788769] rk_gmac-dwmac ff290000.ethernet: init for RGMII
[    2.789043] rk_gmac-dwmac ff290000.ethernet: User ID: 0x10, Synopsys ID: 0x35
[    2.789060] rk_gmac-dwmac ff290000.ethernet: 	DWMAC1000
[    2.789071] rk_gmac-dwmac ff290000.ethernet: DMA HW capability register supported
[    2.789081] rk_gmac-dwmac ff290000.ethernet: RX Checksum Offload Engine supported
[    2.789092] rk_gmac-dwmac ff290000.ethernet: COE Type 2
[    2.789103] rk_gmac-dwmac ff290000.ethernet: TX Checksum insertion supported
[    2.789112] rk_gmac-dwmac ff290000.ethernet: Wake-Up On Lan supported
[    2.789164] rk_gmac-dwmac ff290000.ethernet: Normal descriptors
[    2.789175] rk_gmac-dwmac ff290000.ethernet: Ring mode enabled
[    2.789184] rk_gmac-dwmac ff290000.ethernet: Enable RX Mitigation via HW Watchdog Timer
[    2.789315] mdio_bus stmmac-0: GPIO lookup for consumer reset
[    2.789327] mdio_bus stmmac-0: using lookup tables for GPIO lookup
[    2.789338] mdio_bus stmmac-0: No GPIO consumer reset found
[    2.789381] of_get_named_gpiod_flags: parsed 'snps,reset-gpio' property of node '/ethernet@ff290000[0]' - status (0)
[    2.790243] usb 1-1: new high-speed USB device number 2 using dwc2
[    2.878214] usb 3-1: new high-speed USB device number 2 using ehci-platform
[    2.999804] usb 1-1: New USB device found, idVendor=05e3, idProduct=0610, bcdDevice=32.98
[    2.999819] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    2.999830] usb 1-1: Product: USB2.0 Hub
[    3.000743] hub 1-1:1.0: USB hub found
[    3.001106] hub 1-1:1.0: 4 ports detected
[    3.083063] dwmmc_rockchip ff0f0000.dwmmc: Successfully tuned phase to 200
[    3.084725] mmc2: new HS200 MMC card at address 0001
[    3.086392] mmcblk2: mmc2:0001 HAG4a2 14.7 GiB 
[    3.087579] mmcblk2boot0: mmc2:0001 HAG4a2 partition 1 4.00 MiB
[    3.088769] mmcblk2boot1: mmc2:0001 HAG4a2 partition 2 4.00 MiB
[    3.089064] mmcblk2rpmb: mmc2:0001 HAG4a2 partition 3 4.00 MiB, chardev (241:0)
[    3.090484]  mmcblk2: p1
[    3.236257] usb 3-1: config 1 has an invalid interface number: 255 but max is 6
[    3.236273] usb 3-1: config 1 has no interface number 6
[    3.237730] usb 3-1: New USB device found, idVendor=0bda, idProduct=481a, bcdDevice= 0.00
[    3.237745] usb 3-1: New USB device strings: Mfr=3, Product=1, SerialNumber=2
[    3.237756] usb 3-1: Product: USB Audio
[    3.237767] usb 3-1: Manufacturer: Generic
[    3.237778] usb 3-1: SerialNumber: 201405280001
[    3.245849] input: Generic USB Audio Consumer Control as /devices/platform/ff500000.usb/usb3/3-1/3-1:1.255/0003:0BDA:481A.0001/input/input0
[    3.302738] input: Generic USB Audio as /devices/platform/ff500000.usb/usb3/3-1/3-1:1.255/0003:0BDA:481A.0001/input/input1
[    3.303451] hid-generic 0003:0BDA:481A.0001: input,hiddev96,hidraw0: USB HID v1.11 Device [Generic USB Audio] on usb-ff500000.usb-1/input255
[    3.810278] [drm] Cannot find any crtc or sizes
[    3.878294] libphy: stmmac: probed
[    3.878315] RTL8211E Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[    3.878329] RTL8211E Gigabit Ethernet stmmac-0:01: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:01, irq=POLL)
[    3.880431] rk808-rtc rk808-rtc: setting system clock to 2013-01-18 08:50:08 UTC (1358499008)
[    3.880778] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    3.909864] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    3.910483] vcc_sd: supplied by vcc_io
[    3.910600] vcc_sd: disabling
[    3.910901] ttyS2 - failed to request DMA
[    3.916060] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    3.916072] cfg80211: failed to load regulatory.db
[    3.919057] Freeing unused kernel memory: 2048K
[    3.919423] Run /init as init process
[   12.735934] EXT4-fs (mmcblk2p1): mounted filesystem with writeback data mode. Opts: (null)
[   13.141096] systemd[1]: System time before build time, advancing clock.
[   13.179610] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[   13.180855] systemd[1]: Detected architecture arm.
[   13.214872] systemd[1]: Set hostname to <tinkerboard>.
[   13.216978] systemd[1]: Failed to bump fs.file-max, ignoring: Invalid argument
[   13.573876] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP firewall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[   13.573903] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[   13.971581] random: systemd: uninitialized urandom read (16 bytes read)
[   13.986412] random: systemd: uninitialized urandom read (16 bytes read)
[   13.986854] systemd[1]: Listening on initctl Compatibility Named Pipe.
[   13.998465] random: systemd: uninitialized urandom read (16 bytes read)
[   13.998993] systemd[1]: Listening on udev Kernel Socket.
[   14.011153] systemd[1]: Listening on Journal Socket (/dev/log).
[   14.023294] systemd[1]: Listening on Journal Audit Socket.
[   14.393791] EXT4-fs (mmcblk2p1): re-mounted. Opts: commit=600,errors=remount-ro
[   15.166675] random: crng init done
[   15.166686] random: 7 urandom warning(s) missed due to ratelimiting
[   15.482786] systemd-journald[270]: Received request to flush runtime journal from PID 1
[   15.780425] cpu cpu0: Linked as a consumer to regulator.3
[   15.780529] cpu cpu0: Dropping the link to regulator.3
[   15.780824] cpu cpu0: Linked as a consumer to regulator.3
[   15.790262] cpufreq: cpufreq_online: CPU0: Running at unlisted freq: 500000 KHz
[   15.791978] cpufreq: cpufreq_online: CPU0: Unlisted initial frequency changed to: 600000 KHz
[   15.829654] of_get_named_gpiod_flags: parsed 'pendown-gpio' property of node '/spi@ff130000/waveshare35a-ts@1[0]' - status (0)
[   15.829769] ads7846 spi2.1: spi2.1 supply vcc not found, using dummy regulator
[   15.829815] ads7846 spi2.1: Linked as a consumer to regulator.0
[   15.832115] fbtft: module is from the staging directory, the quality is unknown, you have been warned.
[   15.838505] fb_ili9486: module is from the staging directory, the quality is unknown, you have been warned.
[   15.838869] rockchip-pinctrl pinctrl: unable to find group for node waveshare35a_pins
[   15.838884] fb_ili9486: probe of spi2.0 failed with error -22
[   15.838893] r8723bs: module is from the staging directory, the quality is unknown, you have been warned.
[   15.839866] ads7846 spi2.1: touchscreen, irq 246
[   15.840212] input: ADS7846 Touchscreen as /devices/platform/ff130000.spi/spi_master/spi2/spi2.1/input/input2
[   15.845273] RTL8723BS: module init start
[   15.845279] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40
[   15.845281] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40
[   15.845832] pnetdev = 81701a00
[   15.918220] zram: Added device: zram0
[   15.918684] zram: Added device: zram1
[   15.924573] zram: Added device: zram2
[   15.948357] mali ffa30000.gpu: Linked as a consumer to regulator.4
[   15.948943] mali ffa30000.gpu: GPU identified as 0x0750 r0p0 status 1
[   15.949120] mali ffa30000.gpu: Protected mode not available
[   15.949722] rk3288-crypto ff8a0000.cypto-controller: Crypto Accelerator successfully registered
[   15.954937] mali ffa30000.gpu: Probed as mali0
[   15.956764] of_get_named_gpiod_flags: parsed 'gpios' property of node '/gpio-keys/button@0[0]' - status (0)
[   15.956780] gpio gpiochip0: Persistence not supported for GPIO 5
[   15.956912] input: gpio-keys as /devices/platform/gpio-keys/input/input3
[   16.005718] zram1: detected capacity change from 0 to 1050013696
[   16.015553] RTL8723BS: rtw_ndev_init(wlan0)
[   16.016328] RTL8723BS: module init ret =0
[   16.145558] Adding 1025400k swap on /dev/zram1.  Priority:5 extents:1 across:1025400k SSFS
[   16.196627] of_get_named_gpiod_flags: can't parse 'simple-audio-card,hp-det-gpio' property of node '/sound[0]'
[   16.196637] of_get_named_gpiod_flags: can't parse 'simple-audio-card,mic-det-gpio' property of node '/sound[0]'
[   16.196975] asoc-simple-card sound: i2s-hifi <-> ff890000.i2s mapping ok
[   16.300344] zram0: detected capacity change from 0 to 52428800
[   16.429337] EXT4-fs (zram0): mounted filesystem without journal. Opts: discard
[   18.062115] usbcore: registered new interface driver snd-usb-audio
[   19.305218] gpio gpiochip4: Persistence not supported for GPIO 26
[   19.305406] gpio gpiochip4: Persistence not supported for GPIO 29
[   19.305549] gpio gpiochip4: Persistence not supported for GPIO 31
[   19.971322] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   19.972383] RTL8211E Gigabit Ethernet stmmac-0:00: attached PHY driver [RTL8211E Gigabit Ethernet] (mii_bus:phy_addr=stmmac-0:00, irq=POLL)
[   19.986166] rk_gmac-dwmac ff290000.ethernet eth0: No Safety Features support found
[   19.986177] rk_gmac-dwmac ff290000.ethernet eth0: PTP not supported by HW
[   19.986434] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   19.999831] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   20.013348] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin
[   20.994680] rk_gmac-dwmac ff290000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx
[   21.320389] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   21.320433] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   21.340142] ttyS0 - failed to request DMA
[   21.473675] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   91.334599] fbtft_device: module is from the staging directory, the quality is unknown, you have been warned.
[   91.335565] ads7846 spi2.1: ads7846 spi2.1 2000kHz 8 bits mode=0x00
[   91.335580] spi spi2.0: ili9486 spi2.0 15000kHz 8 bits mode=0x00
[   91.335670] rockchip-efuse ffb40000.efuse: ffb40000.efuse id=-1 pdata? no
[   91.336172] spi spi2.0: Deleting spi2.0
[   91.910870] Console: switching to colour frame buffer device 60x40
[   91.911340] graphics fb0: fb_ili9486 frame buffer, 480x320, 300 KiB video memory, 32 KiB buffer memory, fps=31, spi2.0 at 15 MHz
[   91.911402] fbtft_device: GPIOS used by 'fb_ili9486':
[   91.911405] fbtft_device: 'dc' = GPIO163
[   91.911407] fbtft_device: 'reset' = GPIO171
[   91.911414] ads7846 spi2.1: ads7846 spi2.1 2000kHz 8 bits mode=0x00
[   91.911418] fb_ili9486 spi2.0: fb_ili9486 spi2.0 15000kHz 8 bits mode=0x00

Update Feb-20-2018:  script update committed for out of the box audio support (both outputs and inputs) for ASUS Tinker Board. 

Available sinks:

• BT-VOIP
• SPDIF
• Headset (the jack)

Available sources:

• BT-VOIP
• Headset-input (the jack)

Tinkerboard sound is possible with Armbian, however I have not worked to get it set up "out of the box" because of a major bug in the sound itself, namely that it outputs pure high pitched garbage from certain applications and certain source materials.  I don't want anyone going deaf/destroying equipment, and I don't want to get backed into a corner on something I don't immediately know how to fix.  That said, I'm hoping @Kwiboo or @Da Alchemist or the like may have an idea of what's going on here, it's one of the more annoying issues holding this back from being a daily driver.  It's important to note I experienced the same sort of insanity using a simple I2S DAC with the Tinker Board.  If some PA settings can take care of it that's great, if it's a clock issue on the Tinker I'm not sure where to go from there.  I will be doing some testing on the new kernel 4.13, as there have been some clock reassignments/adjustments that, while seemingly unrelated, may be.  Also, has anyone found a specific driver for the Realtek chip, or is it still just "generic USB Audio?"