SuperMaximus

Hi! I'm using Tinkerboard S R2.0 in headless mode, but with LightDM (kiosk mode). It's connected to HDMI display, and I soldered display's backlight on/off contact to a relay that can turn on/off the backlight. 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.

Thanks for your recommendation. I followed it and added pwm1, pwm2, pwm3 to my armbianEnv verbosity=0 bootlogo=true console=serial overlay_prefix=rockchip overlays=i2c1 i2c4 spi2 spidev2 uart1 uart2 pwm1 pwm2 pwm3 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 And now my Tinkerboard can't boot at all. I can't even connect via SSH. Is there any way out of it? Thanks!

@jock I would be grateful for your help! I want to control the Waveshare 7" HDMI LCD screen brightness via this PWM.

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 & 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

Hi! 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!

@CryBaby Could you please advise how to make a separate partition on Armbian for "/boot"? I was tinkering with attempts to make /boot read-only via u-boot CLI, but had no luck. I mean not only making a partition as such, but also telling Armbian that /boot is on another mmcblk. I am using Tinkerboards EMMC. Thanks!

@JMCC Would you please share the Chromium-browser that comes with Buster? Maybe you've got .deb package so that I could try it on Bullseye?

@JMCC It's rather hard to give up the latest kernel and already configured SBC and roll back to Buster Is there any chance to install Chromium that supports Web GL 2 on newer distros?

Are these repos sudo add-apt-repository ppa:liujianfeng1994/panfork-mesa sudo add-apt-repository ppa:liujianfeng1994/rockchip-multimedia suitable for all RK chipsets? I have RK3288 (Tinkerboard S R2.0) and would like to install Chromium with Web GL 2 support. Can't find the proper repo with this browser for RK3288.

I'm struggling to find the proper PPA with "chromium-browser" that would work with WebGL2 on Tinkerboard S (RK3288). Snap version does not support Web GL2. Does anybody know the good PPA with Chromium for RK3288?

@Igor Not yet:) I am using Tinkerboard to automate a house boiler room so far. But, nevertheless I just joined the donators as I consider this forum helpful! I am OK to be Tinkerboard S R2.0 tester to make it fully supported by Armbian.

@CryBaby Thanks! Is this action enough to prevent corruption of bootloader during unexpected power outage?

@jock I do appreciate your valuable hint regarding 8723ds driver adding in manual kernel compilation, but everytime I do sudo apt full-upgrade eventually I get my driver wiped out from the system. Could you please advise what should I do in this case to avoid it? Should I manually patch kernel manually again?

How can I make sure my /boot is protected against power failure making eMMC of Tinkerboard corrupted? 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!

I reinstalled snapd, rebooted and the problem vanished. Don't understand why it appeared though.