SuperMaximus

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.

@Werner Yes, squashfs is listed in lsmod, but it does not seem to be mounted.

I try to install chromium and get this: 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?

@SteeMan Could you be more specific, please? How do I specify the bmp in the patch?

Is it possible to install Multimedia Framework for Armbian CLI images? I have to run Chromium with Web GL 2.0 support and don't need Desktop things.... In my case under latest Armbian Debian CLI image I have packages not found. root@tinkerboard:~# sudo apt install media-buster-legacy-tinkerboard --install-recommends Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package media-buster-legacy-tinkerboard root@tinkerboard:~# sudo apt install media-buster-legacy-rk3328 --install-recommends Reading package lists... Done Building dependency tree... Done Reading state information... Done E: Unable to locate package media-buster-legacy-rk3328

@jock Once again, thanks for your profound advices & help! Now that I understood that completely black screen replacing all u-boot console messages might lead user astray and I decided just to change only the logo with the submarine and leave console messages: Is there a way to replace this with my own BMP? Actually I tried to change all related BMPs from cloned data on my hard drive, but compilation of u-boot results again in the same submarine logo. It seems that cache is pulled anew during compilation. /root/armbian/cache/sources/u-boot-worktree/u-boot/v2022.04/drivers/video/u_boot_logo.bmp /root/armbian/cache/sources/u-boot-worktree/u-boot/v2022.04/tools/logos/u_boot_logo.bmp /root/armbian/cache/sources/u-boot-worktree/u-boot/v2022.04/tools/logos/u_boot_logo.svg

@jock Thanks again for the patch! Now it's tested & working. Will try to compile with wlan0 drivers and let you know the result.

@jock Thanks! I've tried to compile u-boot separately with the attached patch and it succeeded without errors! Regarding your advice concerning driver - is there any special condition when I can see kernel config details during running ./compile.sh? The point is that when I first time cloned the repo, I saw that menu with detailed drivers selection, but now when I choose "Show a kernel configuration menu before compilation" I see nothing but a board selection menu and it follows by kernel selection (I normally opt for Jammy) and image type, after I press OK it starts compiling. Struggling to see that detailed compilation menu again.

@jock I wonder if I can just compile U-boot and then update it in my working Armbian 22.11 image? (with kernel 5.15.80) First I need to compile it with the .patch you provided, but once I put it in patches dir, it says during compilation: o.k. ] Looking for user patches in [ userpatches/u-boot/v2022.07 ] [ o.k. ] * [l][c] 0001-HACK-configs-meson64-prevent-stdout-stderr-on-videoconsole.patch [ o.k. ] * [l][b] 0001-tinkerboard-defconfig-fix.patch [ o.k. ] * [l][b] 0002-tinkerboard-add-emmc.patch [ o.k. ] * [l][b] 0003-UMS-mode-on-otg-port.patch [ o.k. ] * [l][c] 0003-mmc-meson-gx-change-clock-phase-value-on-axg-SoCs.patch [ o.k. ] * [l][b] 0004-make-emmc-bootable.patch [ o.k. ] * [l][b] add-overlay-support.patch [ warn ] * [l][b] disable-u-boot-hdmi.patch [ failed ] [ o.k. ] * [l][c] enable-DT-overlays-support.patch [ o.k. ] * [l][c] u-boot-meson64-support-old-bootscripts.patch [ o.k. ] * [l][b] zzz-usb-otg-fix.patch Something might be wrong with the last line of patch...

@jock Just checked! It's rtl8723ds

@jock, I have 2 boards (rev 2.02), nothing works in 6.1, whereas 5.15 is OK. I couldn't succeed with script, probably because of missed "-" before ""stdin=serial,usbkbd\0" \" Now that I've put "-" the compiler doesn't like #include <configs/rk3288_common.h> So I'm struggling with two problems now - attempt to compile an older Armbian with older kernel and fighting with patch...

@jock Yes, it seems that 6.1 has missing wlan0 drivers (tried all possible precompiled images). It just doesn't mount at all. I am on current main branch. By the way, it seems I should've put patch in /userpatches//u-boot/v2022.04 I did, but again it failed to compile. I attach the log and here's the error excerpt: [🔨] -> 09/12: disable-u-boot-hdmi(:1) [🔨] Problem with ->disable-u-boot-hdmi(:1) <-: Failed to apply patch /home/max/build/userpatches/u-boot/v2022.07/disable-u-boot-hdmi.patch: [🔨] STDOUT: patching file "include/configs/tinker_rk3288.h" [🔨] STDOUT: Hunk #1 FAILED at 8. [🔨] STDOUT: 1 out of 1 hunk FAILED -- saving rejects to file "/tmp/tmpzjcowxqx" [🔨] -> 10/12: enable-DT-overlays-support(:1) (+2/-0)[1M] {Kconfig} [🔨] -> 11/12: u-boot-meson64-support-old-bootscripts(:1) (+4/-0)[1M] {meson64.h} [🔨] -> 12/12: zzz-usb-otg-fix(:1) (+2/-0)[1M] {dwc2.c} Build.log

@jock Thank you! I have created a "disable-u-boot-hdmi.patch" file under /build/userpatches Then compiled ./compile.sh CREATE_PATCHES="yes" LIB_TAG="v22.11.1" but finally nothing changed, I still see u-boot console & u-boot logo, thus HDMI patch is either wrong or not applied... Did I miss something? Besides, I have [[ $LINUXFAMILY == rockchip && $BRANCH == current ]] && BOOTBRANCH='tag:v2022.07' #conditionally change u-boot git branch/tag #KERNELBRANCH="tag:v5.15.80" #always change to this kernel tag in my "lib.config" under /build/userpatches Somehow BOOTBRANCH parameter wirjed out, whereas KERNELBRANCH (when I uncomment it) does not compile the appointed version. Also I can't make LIB_TAG working. I am mentioning this, because I need to compile exact version of Armbian (22.11.1) with Kernel ver (5.15.80) but it does not seem to work, it picks up 6.1 anyhow. Tinkerboard S has no wlan0 in 6.1 and latest Armbian v.23, thus I wanted to compile an older version under older current branch. I understand it may be offtopic, but if you know how to solve both issues, I will be immensely grateful! I attach my compile log here too. log-build-4355e230-ddb8-45a2-ae2c-8242e8ab404d.log

@c0rnelius How do I up my build to v2022.07?

@c0rnelius Tried to compile excluding `CONFIG_DM_RESET=y` from /build/cache/sources/u-boot-worktree/u-boot/v2022.04/configs/tinker-rk3288_defconfig Result - device boots with all u-boot messages & logo as if there were no changes.