TRS-80

Essentialy, yes. VPU is identical in last generation SoC's RK3328 and RK3399, lacking VP9 capabilities in the older RK3288.
 
GPU, on the other hand, is very similar in the high-end SoC's (RK3288 and RK3399), much faster and supporting OpenGLES 3 and OpenCL 1.2. The weaker one, RK3328, supports only GLES2 and no OpenCL, plus no ISP camera either.
 
There is also a parallel solution for Odroid XU4, I will document it soon. In that case, VPU decoding capabilities are reduced (no 4K, only 1080p). But GPU is the strongest one, as well as VPU encoding.

Hi robertoenr
 
It's simple like that. Follow guide of SteeMan, but NO NEED to hold Reset while booting, DO NOT PRESS OR HOLD ANYTHING while booting and DO NOT plug USB Keyboard while booting, you can plug USB Keyboard later, after see login screen
 
 

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
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-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
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 (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. 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. 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  
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.

I just posted the announcement for the official Armbian Rockchip Legacy Multimedia Framework. As you can see on the announcement, I say that from now on all multimedia work will be done in Mainline.
 
That means integrating GPU and VPU acceleration into the official Armbian repos. The timeline is for next Armbian release, in February, if possible.
 
As of today, I am planning to include Kodi and MPV. So if anybody wants to help, it will be much appreciated. 

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.

Did you create a bootable microSD card?
The U-Boot image is not on SPI yet - so it needs it will look for it on the SD and eMMC - if you haven't written the image on either of these you won't get any output on the console.

Throw away this intel shit. use the native build on rk3399. This is faster and without any stupid Trojans in Intel x86.
 
You use the source code from Friendlyelec , they are significantly worse. It is better to use the ones that go for rockchip64-legacy (there are also sources for analog audio 8323\8388)
 
https://github.com/150balbes/build/blob/armbian-tv/config/boards/station-p1.conf#L3
https://github.com/150balbes/build/blob/armbian-tv/config/sources/families/include/rockchip64_common.inc#L51
 
And the kernel config that WiFi works with.
https://github.com/150balbes/build/blob/armbian-tv/config/kernel/linux-rockchip64-p1-legacy.config
 
PS I wanted to create a PR with the change, but so far I have suspended it until we discuss and agree on these changes.

Since I had collected as much information from the broken AC adapter brick as possible, I decided to cut off the connector.  This revealed only 2 wires which meant there is only one possible configuration.  Both pins 1 and 2 must be 12V.
 
I grabbed one of my old computer power supplies, and fashioned a terminal connector to tie the 2 wires to the 12V rail and ground.  I verified the 4 pins on the connector, plugged it in and my Helios4 booted up without any issues.  I'm still waiting about a week and I'll swap out my 500W temporary PSU when it arrives.
 
For anyone with similar power issues, hopefully this thread may be helpful to them.
 
 
Here's the appropriate pinouts of the 4-pin AC adapter required for Helios 4 (see previous diagram for pin locations):
PIN 1: +12
PIN 2: +12
PIN 3: GND
PIN 4: GND

Rare mistake by Igor!
 
In few years I been lurking here, this is only time I can recall such thing happening.  Of course everyone make mistakes, and there were probably some I was not aware of, but this is first time I can remember such thing happening.

OK, relevant posts have been moved with the title that was suggested:
 
USB Type-C DisplayPort Alternate Mode Support for NanoPC-T4
 
Thanks @usual user for help keeping the forums organized! 

This is the reason there is the TV Boxes Club to provide a community to help with these unsupported builds.  Since you are using a TV box you will find no/limited support in the general forums for the reasons stated above.  Please read the work in process post in the TV Boxes club that is intended to set expectations around what to expect with armbian and TV boxes:
 

We don't deal with images you find on the internet. We don't know them and they represent extra cost on already extensive support service which you support with nothing. You pay zero and I need to waste lets say 50 EUR for dealing with the problem you have. I would need another few hours to see and understand changes in the image you use. Another lets say 500 EUR worth of research ... you pay nothing for and you press on us for assistance on a problem that is most likely not our work in 1st place.
 
Free support is limited to our work and its also further limited. We can't fix all problems, but we at least try if possible, while when 3rd party image is in question ... we don't even start.
 
Clear?

@grek I've been using compression since the get-go, and can't say I've had similar issues so far. The only time I had a kernel panic was from before I switched to the performance governor for the CPU. LZ4 is also a pretty light-weight compression algorithm, but it does increase CPU to a small degree.
 
Potential changes I have compared to your setup:
I run root (/) on ZFS I use full disk encryption via LUKS (that's an additional layer between ZFS and kernel) I use the performance governor My disks are limited to 3.0 Gbps SATA speed Things you could try:
Upgrade to the latest 5.9.14-rockchip64 kernel Upgrade to the latest ZFS 0.8.6 kernel modules Try the performance governor Do you use a swap partition? If yes, you could try to swapoff before repeating the process that paniced the kernel Wildcard idea: You could also try disabling the Armbian zram config in /etc/default/armbian-zram-config (I have it disabled)

As I said, there is one kernel config per board family, regardless of which packages are installed on userspace the kernel remains the same.  May people will want to download or build a console-only image and then install desktop on it (I do it quite often), so it makes sense to keep it this way.
 
Also, even people running headless may want to use the OpenCL features offered by panfrost, which is an additional reason for keeping it enabled.
 
Besides, having the graphics driver enabled in the kernel should not cause any kind of problem when you are not using the module (that is, no gpu accelerated apps running).  Mali drivers have always been enabled on legacy kernels, without being used in most cases, and it has never been an issue. If some problem ever arose from panfrost on servers, then it would be time to think about the best solution for it. But, as of today, it is not a problem at all, unless the contrary is proven.

It's been fixed to my knowledge. It was the mesa update that was buggy.
Still a few other bugs need to be worked out. But this problem seems to be gone. 

I do think there's another issue. Panfrost is enabled by default in desktop and server images, I don't know if it has a path for correct update. 
Certainly for server images I'd disable it since it can only make problems. For desktop I don't mind.

The other issue with ondemand governor I've not seen anymore. So might also be fixed. If anyone could confirm.

I have tested Focal Xfce desktop on a Rockpi-4b, with Firefox, glmark2, video playing, etc., for over half an hour, and didn't have any problem. I have not been able to reproduce the bug.
 
If someone can give me clear steps to reproduce it, I will try to look into it. Otherwise, I consider it solved.

Could the issue be that every single file can be pulled from a different mirror? E.g. when packages list is pulled form one mirror, the content hashes from another one and the final package again from another one, it is easily possible that one does not match as for sure not all mirrors sync and have caches emptied exactly the same time. E.g. here my apt update which pulls from various different mirrors:
Get:5 https://minio.k-space.ee/armbian/apt buster InRelease [18.3 kB] Get:6 https://minio.k-space.ee/armbian/apt buster/main armhf Packages [591 kB] Ign:6 https://minio.k-space.ee/armbian/apt buster/main armhf Packages Get:7 https://minio.k-space.ee/armbian/apt buster/main arm64 Packages [698 kB] Ign:7 https://minio.k-space.ee/armbian/apt buster/main arm64 Packages Ign:7 https://apt.armbian.com buster/main arm64 Packages Ign:7 https://apt.armbian.com buster/main arm64 Packages Get:8 https://minio.k-space.ee/armbian/apt buster/main arm64 Contents (deb) [11.2 MB] Ign:8 https://minio.k-space.ee/armbian/apt buster/main arm64 Contents (deb) Get:9 https://minio.k-space.ee/armbian/apt buster/main armhf Contents (deb) [17.3 MB] Ign:9 https://minio.k-space.ee/armbian/apt buster/main armhf Contents (deb) Get:6 https://us.mirrors.fossho.st/armbian/apt buster/main armhf Packages [591 kB] Err:6 https://us.mirrors.fossho.st/armbian/apt buster/main armhf Packages   File has unexpected size (591174 != 590754). Mirror sync in progress? [IP: 23.237.182.68 443]   Hashes of expected file:    - Filesize:590754 [weak]    - SHA512:bb903949666449552cda361ee24d4d0579baa72915b5fb3d7418acede319562ce4b93a15bf7605ae270bd9f0e59ececf622fea1365e8aa7a3d8339e2a2644f56    - SHA256:d822f1c4a63ce566baa27d1f5c523057c1d295222f097b072dc8fbeb14a29bc3    - SHA1:0f37871329a6a28cf7c53dd6ffd952342432c7ed [weak]    - MD5Sum:517fa48fb23e17f6c94248da6ce5b44b [weak]   Release file created at: Sat, 12 Dec 2020 15:07:27 +0000 Get:7 https://armbian.systemonachip.net/apt buster/main arm64 Packages [3941 kB] Err:7 https://armbian.systemonachip.net/apt buster/main arm64 Packages Get:8 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 Contents (deb) [11.2 MB] Err:8 https://mirrors.dotsrc.org/armbian-apt buster/main arm64 Contents (deb) Get:9 https://armbian.tnahosting.net/apt buster/main armhf Contents (deb) [17.3 MB] Err:9 https://armbian.tnahosting.net/apt buster/main armhf Contents (deb) Fetched 18.3 kB in 55s (332 B/s) Reading package lists... Done E: Failed to fetch https://us.mirrors.fossho.st/armbian/apt/dists/buster/main/binary-armhf/Packages.bz2  File has unexpected size (591174 != 590754). Mirror sync in progress? [IP: 23.237.182.68 443]    Hashes of expected file:     - Filesize:590754 [weak]     - SHA512:bb903949666449552cda361ee24d4d0579baa72915b5fb3d7418acede319562ce4b93a15bf7605ae270bd9f0e59ececf622fea1365e8aa7a3d8339e2a2644f56     - SHA256:d822f1c4a63ce566baa27d1f5c523057c1d295222f097b072dc8fbeb14a29bc3     - SHA1:0f37871329a6a28cf7c53dd6ffd952342432c7ed [weak]     - MD5Sum:517fa48fb23e17f6c94248da6ce5b44b [weak]    Release file created at: Sat, 12 Dec 2020 15:07:27 +0000 E: Failed to fetch https://armbian.systemonachip.net/apt/dists/buster/main/binary-arm64/Packages E: Failed to fetch https://mirrors.dotsrc.org/armbian-apt/dists/buster/main/Contents-arm64.gz E: Failed to fetch https://armbian.tnahosting.net/apt/dists/buster/main/Contents-armhf.gz E: Some index files failed to download. They have been ignored, or old ones used instead. The reported successful update from @dispo above was one case where everything was pulled from the same mirrors.netix.net mirror.

I'm not sure how e.g. Debian handles this, but it makes IMO sense that somehow tie a client to a fixed mirror for a certain time.

Although I just compared the files of three mirrors and they all match, synced at 15-Dec-2020 09:03. So not sure if this really is the issue.

I was able to set screen resolution on OrangePi4 by appending this line:
extraargs=video=1920x1080@60 To /boot/armbianEnv.txt .
 
On my board the screen is turned on only after a little while after the powering up, so I have figured out that the screen resolution is set by the kernel, not by u-boot. Thus you need to add a parameter to kernel command line.
The line has to be added verbatim without quotes (as suggested elsewhere) and then everything after first = is inserted into the middle of Kernel command line (check dmesg output).
I hope, this helps.

I think there are probably only 2 subforums you might need to monitor:
Announcements
Armbian build framework Both are very low volume.  You could set up an RSS feed (link at bottom of page) or simply peruse them whenever you log in.

I just placed my third (and final) order.  Went through no problem as expected.  This was on US site.
 
Already earlier today I received shipping confirmation of my first order!  With an updated ETA which was some days earlier than originally projected.
 
I guess what I am saying is, if you are on the fence and not sure the stuff will arrive in time, give it a shot, as I think they seem a bit conservative in their initial estimates (when trying to upsell you on faster shipping ).
 
I will update again once orders 2 and 3 ship.

Today is December 15, 2020
I brought the code to the top of armbian master. Built for different kernel versions (5.4 5.9 5.10).
 
debs> ls -gGhR .: итого 807M -rw-r--r-- 1 43K дек 15 22:05 armbian-config_21.02.0-trunk_all.deb -rw-r--r-- 1 6,6M дек 15 22:05 armbian-firmware_21.02.0-trunk_all.deb -rw-r--r-- 1 142M дек 15 22:05 armbian-firmware-full_21.02.0-trunk_all.deb drwxrwxr-x 1 0 дек 15 22:05 extra drwxrwxr-x 1 436 дек 15 22:05 focal -rw-r--r-- 1 77K дек 15 22:05 linux-dtb-current-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 80K дек 15 22:05 linux-dtb-dev-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 57K дек 15 22:05 linux-dtb-legacy-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 12M дек 15 22:05 linux-headers-current-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 12M дек 15 22:05 linux-headers-dev-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 11M дек 15 22:05 linux-headers-legacy-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 26M дек 15 22:05 linux-image-current-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 27M дек 15 22:05 linux-image-dev-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 30M дек 15 22:05 linux-image-legacy-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 1,1M дек 15 22:05 linux-libc-dev-current-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 1,1M дек 15 22:05 linux-libc-dev-dev-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 1,1M дек 15 22:05 linux-libc-dev-legacy-sunxi64_21.02.0-trunk_arm64.deb -rw-r--r-- 1 192M дек 15 22:05 linux-source-5.10.0-dev-sunxi64.deb -rw-r--r-- 1 159M дек 15 22:05 linux-source-5.4.82-legacy-sunxi64.deb -rw-r--r-- 1 190M дек 15 22:05 linux-source-5.9.14-current-sunxi64.deb -rw-r--r-- 1 276K дек 15 22:05 linux-u-boot-current-orangepipc2_21.02.0-trunk_arm64.deb -rw-r--r-- 1 276K дек 15 22:05 linux-u-boot-dev-orangepipc2_21.02.0-trunk_arm64.deb -rw-r--r-- 1 276K дек 15 22:05 linux-u-boot-legacy-orangepipc2_21.02.0-trunk_arm64.deb ./extra: итого 0 ./focal: итого 1,4M -rw-r--r-- 1 162K дек 15 22:05 armbian-focal-desktop_21.02.0-trunk_all.deb -rw-r--r-- 1 405K дек 15 22:05 linux-focal-root-current-orangepipc2_21.02.0-trunk_arm64.deb -rw-r--r-- 1 405K дек 15 22:05 linux-focal-root-dev-orangepipc2_21.02.0-trunk_arm64.deb -rw-r--r-- 1 405K дек 15 22:05 linux-focal-root-legacy-orangepipc2_21.02.0-trunk_arm64.deb  
without any major changes, the two kernel build scripts (builddeb  mkdebian) build different versions in the same way, starting from 5.4 and higher.
Changes were required in the part that concerns the 'armbian' build system itself.
 
To be honest, I spent longer looking for places where temporary folders are created, and those places where they should be deleted after completing their function.
 
You can test this approach as before:
git remote add armbian-build https://github.com/The-going/armbian-build.git git fetch armbian-build packaging git checkout -b packaging armbian-build/packaging git pull -f armbian-build packaging  
 

I never know what to get anyone.  If I'm being honest I have more than a little disdain for how commercialized the holidays have become nowadays.  We were not raised in a materialistic way growing up.  A lot of gifts were socks and other actually useful things like that (which I only appreciate now as I get older ).  Anyway...
 
So when some of the guys shared some pictures of themselves with some Armbian swag in IRC a while back, a little light bulb went off in my head. 
 
So this morning, I went nuts and spent > 400 USD sending everyone in my family some Armbian swag.    I figure, it's a good way to get the word out there to friends and family about a project I care a lot about, while supporting the project a bit financially at the same time.
 
   
 
I don't expect anyone else to spend that sort of money, in fact I am a tight wad and rarely do, myself.  But a coffee mug or something might be nice?
 
I also don't like to rush people (because I don't like to be rushed, myself), however if you are going for delivery before the holidays I would place your order ASAP, maybe even today.
 
One final gotcha, their credit card processor apparently only allow 2 orders per day.  Luckily I had sent orders to other family first, because my third order was denied.  I called their customer support and they confirmed this issue and told me to try again after 24 hours.  So the stuff that is coming here for us I will place that order (again) tomorrow.  I just wanted to give everyone a heads up about that though.

I never know what to get anyone.  If I'm being honest I have more than a little disdain for how commercialized the holidays have become nowadays.  We were not raised in a materialistic way growing up.  A lot of gifts were socks and other actually useful things like that (which I only appreciate now as I get older ).  Anyway...
 
So when some of the guys shared some pictures of themselves with some Armbian swag in IRC a while back, a little light bulb went off in my head. 
 
So this morning, I went nuts and spent > 400 USD sending everyone in my family some Armbian swag.    I figure, it's a good way to get the word out there to friends and family about a project I care a lot about, while supporting the project a bit financially at the same time.
 
   
 
I don't expect anyone else to spend that sort of money, in fact I am a tight wad and rarely do, myself.  But a coffee mug or something might be nice?
 
I also don't like to rush people (because I don't like to be rushed, myself), however if you are going for delivery before the holidays I would place your order ASAP, maybe even today.
 
One final gotcha, their credit card processor apparently only allow 2 orders per day.  Luckily I had sent orders to other family first, because my third order was denied.  I called their customer support and they confirmed this issue and told me to try again after 24 hours.  So the stuff that is coming here for us I will place that order (again) tomorrow.  I just wanted to give everyone a heads up about that though.

There were several 5.8.16 lines, I've selected the topmost (assuming it's the latest), and the LEDs are back!
 
Thanks a lot!

Full disclosure: I was one of the winner of a free Station P1 and they ask to provide a few postings about it.
So this will be my first one where I unbox it.
 
Funnily  I did expect some kind a cardboard box but instead I received a plastic bag. Well, I take it.

Within the Fedex bag was another bag from DHL. No idea what happened there...
Anyway inside the bubble wrap I found a HDMI cable, a remote control a flyer presenting various products and (finally) a car
 

 
Apparently I received one of the first products since mine has the serial number 000049

 
After opening the box I was greeted with the Station P1 itself wrapped in a small bag which I already removed in the picture:

 
I have the say the housing is really nice. Seems well made. I won't bore you with more details because I am pretty confident that others like @NicoD will provide some close-up footage of his product
 
Anyway after digging deeper I found another box containing the antenna, a 100-240V to 12V DC power supply with US plug, a USB to USB-C cable, some buffers and a hex wrench:

 
Unfortunately I cannot power it since I life in Europe and the sent plug does not fit my sockets. Fortunately the power supply is providing far range input voltage so a simple plug adapter will do. Though I have to order one first.
Next I most likely will play with Armbian on Linux 5.10.x and at the end try some desktop playing using TwisterOS.