martinayotte

Ok ! I've found the recipe :
chmod 4775 /usr/bin/python If you wish to restrict the security, you should probably copy /usr/bin/python into /usr/bin/python-as-root and doing "chmod 4775 /usr/bin/python-as-root" and running your GPIO python code with this one.

No, there is no problem about using the whole space.
The issue will be present when cloning, except if the image is first backed-up on external disk bigger than the sdcard and then shrinked.
 

Don't try to enable internal GPIO pullups, it is waste of time since internal ones are too weak for I2C, which need something like 3K while internals are usually around 30K.
Simply add some external ones on one of your peripherals ...
 

Ok ! I've found the recipe :
chmod 4775 /usr/bin/python If you wish to restrict the security, you should probably copy /usr/bin/python into /usr/bin/python-as-root and doing "chmod 4775 /usr/bin/python-as-root" and running your GPIO python code with this one.

I will try, but daily job take most of my time these days ...

With the help of @megi / @megous , I've now my Pinebook-A64 LCD working.
Here is the patch : https://github.com/armbian/build/commit/d49be78b702d7779f78d2655126a56e7f2ea7426
 

With the help of @megi / @megous , I've now my Pinebook-A64 LCD working.
Here is the patch : https://github.com/armbian/build/commit/d49be78b702d7779f78d2655126a56e7f2ea7426
 

I've tried for months to clarify the reason of such issue ...
My last working kernel was 5.7.6, and the issue appeared as soon as 5.8.0, I've done "diff" between both branches and I still didn't figured out the glitches ...

If you look at the resulting image, maybe the rtl8189fs.ko is still present and broken ...
 
Anyway, I've done builds+tests on all my OPi which using this rtl8189, and results are successful, I've done this commit :
https://github.com/armbian/build/commit/bba53d4644e83cd46b80820b5835ad7c2e7691e5

It seems that NanoPi K1 Plus is using rtl8189 WiFi ... Right ?
Driver is broken in 5.11, I'm working on it with other guys, I'm using OPiPC+/OPiLite/OPiPlus2E.
In the mean time, if you don't need WiFi, disable the module :
mv /lib/modules/5.11.1-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko /lib/modules/5.11.1-sunxi/kernel/drivers/net/wireless/rtl8189fs/8189fs.ko-disabled  

Yes, and No ... it prevent all networking if WiFi is present, such as running "ifconfig" will hang forever.
Simply move or delete the 8189fs.ko module will prevent that.

As I said months ago, you need to execute the backup using SSH ...
 
ssh root@<ip_board_to_be_backup> "dd if=/dev/mmcblk1" | dd of=backup_image.img bs=100M  

Ok ! I've found the recipe :
chmod 4775 /usr/bin/python If you wish to restrict the security, you should probably copy /usr/bin/python into /usr/bin/python-as-root and doing "chmod 4775 /usr/bin/python-as-root" and running your GPIO python code with this one.

The PCF8523 chip is a good one since it can trigger an alarm interrupt ...

IT'S FINALLY HERE...

THE OFFICIAL ROCKCHIP-LEGACY MULTIMEDIA INTEGRATION
 
After two years of using a separate script to enable the multimedia features in RK3399 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
Download a Armbian Buster Legacy Desktop image for your board, and install it with the standard Armbian method. Install the complete multimedia solution with sudo apt update && sudo apt upgrade sudo apt install media-buster-legacy-rk3399 --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
Accelerated GLES/EGL X desktop: No action needed. Accelerated Chromium, with WebGL and video display acceleration: No action needed 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". 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.
ISP Camera with real-time h.264/1080p HW encoding: 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. OpenCL 1.2 support: It will be fully functional, no further action needed. You can download some tests and examples from this link. Kodi 18.9 Leia with full RKMPP+GBM acceleration, 4K-HDR capable: You can start it from LightDM 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 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. 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.

It is here : https://www.armbian.com/orange-pi-zero/

After hours of investigation, and after having figured out that SPI for H6 wasn't working since 5.7.x, I've found why : missing SPI pins in DT ...
 
https://github.com/armbian/build/commit/e3ade9e9f4292c6b257ad10f676edc4055106d2a
 

I've checked on my second OPi0 where I didn't upgrade firmware, so still previous version, and the issue is also present :
[ 14.824376] xradio: XR819 device discovered [ 15.056442] xradio: hardware vers. 7.9 [ 15.056457] xradio: firmware vers. 8 (WSM), build 43, api 1060, cap 0x0003 [ 15.056460] xradio: Config USE_EXTENSIONS [ 40.809788] xradio TXRX-WRN: received frame has no key status [ 40.809802] xradio TXRX-WRN: dropped received frame [ 3653.654011] xradio WRN: BH: missed 4 consecutive interrupts! [ 5423.670767] xradio WRN: BH: missed 5 consecutive interrupts! [ 7584.760350] xradio WRN: BH: missed 6 consecutive interrupts! [ 9724.478792] xradio WRN: BH: missed 7 consecutive interrupts! [10080.291066] xradio WRN: BH: missed 8 consecutive interrupts! [10777.751448] xradio WRN: BH: missed 9 consecutive interrupts! [13480.647858] xradio WRN: BH: missed 10 consecutive interrupts! [18367.827745] xradio WRN: BH: missed 11 consecutive interrupts! [19237.530227] xradio WRN: BH: missed 12 consecutive interrupts! [20461.024844] xradio WRN: BH: missed 13 consecutive interrupts!  

After hours of investigation, and after having figured out that SPI for H6 wasn't working since 5.7.x, I've found why : missing SPI pins in DT ...
 
https://github.com/armbian/build/commit/e3ade9e9f4292c6b257ad10f676edc4055106d2a
 

After hours of investigation, and after having figured out that SPI for H6 wasn't working since 5.7.x, I've found why : missing SPI pins in DT ...
 
https://github.com/armbian/build/commit/e3ade9e9f4292c6b257ad10f676edc4055106d2a
 

I will try my best, but "time is the missing ingredient" as usual ...
(I'm currently chasing why SPI0 doesn't work properly on OPiOne+ while it was with few earlier kernel versions)

I will try my best, but "time is the missing ingredient" as usual ...
(I'm currently chasing why SPI0 doesn't work properly on OPiOne+ while it was with few earlier kernel versions)

I will try my best, but "time is the missing ingredient" as usual ...
(I'm currently chasing why SPI0 doesn't work properly on OPiOne+ while it was with few earlier kernel versions)

Upgrade done ! No side effect seen until now ...

You can try a workaround by doing "cp /usr/bin/python /usr/bin/python-sudo ; chmod a+s /usr/bin/python-sudo" so that execution will be done as root.