gounthar

Reboot doesn't seem to be working. It either shuts down, or stays on without doing anything. 
Otherwise it all looks ok. I do have a problem with kazam when the media script is installed. I've had that too on M4V2 with media script in Buster, so it's not the image.
I'm filming everything to make the video. I'll not use Android to write the image, I'll link to the video of @gounthar instead. He clearly has more Android knowledge, and way more patience. 

Armbian is little more than a stock Debian/Ubuntu installation with the aim of providing recent kernel, bootloaders, and some quality of life userspace customizations.
 
None of those seem needed for a docker image. Maybe start with the upstream image of whichever version you're using for your Orange Pi?
 
If you do need certain things from Armbian, you can always copy the apt configuration from /etc/apt/sources.list or sources.list.d into your Dockerfile and go from there.
 
 

Hello everyone!
 
Is there anyone who tried to run Docker on armbian?
 
Ok, let's start from the beginning: I am from the Hypriot Team (we made Docker available on ARM) and recently saw some guys successfully playing with Docker on armbian. Meanwhile, we know, that our Docker runs at least on the Cubietrack and Lamobo R1/BananaPi R1 on top of armbian!
 
This is awesome because, you know, IoT is coming, and Docker on ARM helps get a grip on many challenges induced by IoT. However, we were only able to support Docker on Raspberry Pis so far...  Imagine if Docker would run on more than just a few ARM boards! Armbian seems an awesome platform to extend the family of Docker compatible boards.
 
So, I wonder if there is anyone who tried to run Docker on armbian?
 
If you are now curious about this topic and wanna get started, please see this blog post of how to install Docker on ARM within no time: http://blog.hypriot.com/post/family_arm_hardware_for_docker_more_children/
 
Looking forward to get in touch with you guys!

I did it. Somehow.

I did it. Somehow.

@NicoD Can you shoot a video on how to download and burn an Armbian image to an SD card using only a regular Android on P1 ? I. e. I am interested in a video how to run Armbian with only P1. This instruction allows any user, without any additional devices (PC, laptop, etc.) to get a working Armbian on any supported device.

For start, you might need to install kernel headers. 
 
armbian-config -> software -> install headers
 
Then try again. Regarding display connection or if the method is proper - no idea.

Are you mainly going to participate live, listen later to recordings or not at all? Any topics that are related, close to single board computer world to recommend?

I am still working on my "shopping list", but this is some initial draft from https://fosdem.org/2021/schedule/
 
QA
About the joy and tears of testing Embedded Devices
https://fosdem.org/2021/schedule/event/testing_embedded_devices/
Interactive debugging inside CI systems
https://fosdem.org/2021/schedule/event/debugging_inside_ci/
QAOps - The Latest Trend in QA & Software Delivery
https://fosdem.org/2021/schedule/event/qaops/

Software Composition devroom
Overview Software Bill of Materials (SBOM)
https://fosdem.org/2021/schedule/event/sca_overview/
 
Legal
Protecting against proprietary re-licensing with a community contract
https://fosdem.org/2021/schedule/event/qtproprietaryrelicensing/
 
CI
ARM your continuous integration system with fruits! by @gounthar
https://fosdem.org/2021/schedule/event/arm_your_continuous_integration_system_with_fruits/
 
Community
Mental health and free software
https://fosdem.org/2021/schedule/event/community_devroom_mental_health_free_software/
 
And one fine Belgian beer for each day of the conference also just arrived  
 
 

I regularly delete my branches because all work is eventually merged to  https://github.com/LibreELEC/LibreELEC.tv (you quoted quiet old post).
 
But as @Werner said, H616 is not exactly the same as H6 regarding display stuff so it needs quiet a lot of work. Cedrus will be probably easy, but that comes after display stack.

I tried with an application Pi SDCard image writer, or something like that, but it does not allow to download images, and proposes only images for the Raspberry.
I then found another application that would burn whatever image you give it, but... it needs a rooted device.
I tried lots of one-click root application (bad idea), but none of them worked.
I then switched to recovery mode, and tried to install TWRP (specific to RK3399 TV boxes), but it fails with an error 21.
Even the opengapps fails the same way.
I tried it with adb sideload, but it fails the same way.
Would someone have a link to a working TWRP for this box, or to a way to root it properly?
As @balbes150 asked, the goal would be to write a tutorial for people wanting to switch from Android to Armbian in the case they have just this computer available, and nothing else.
Thanks.

That's a good idea. I'll see what tool is best used in Android to burn the image. I've never used android for it, but since people with P1/M1 certainly have Android it is a great idea.
I've got a video planned where I show a full installation of Armbian Buster Legacy. I can start it in Android. I'll make the video when my NVMe hat arrives. Thanks for the idea. I wouldn't have thought about it. 

p.s. I've got a Mecool KM6 with S905X4 to review Android 10 on it. I don't suppose there will be Armbian for this? Just asking so I don't say anything wrong. 
I like the box, but I can't get used to Android. For watching video it's ok, but for productivity tasks it is bad.

Mine is 000048.

Mine is 000048.

Hey guys!
 
It's the last day to join the M1 giveaway.
 
https://www.stationpc.com/thread-126-1-1.html
 
Good luck to you all.
 
 

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

https://www.adafruit.com/product/3295 -> The PCF8523 is simple and inexpensive but not a high precision device. It may lose or gain up to 2 seconds a day. 

It seems I may have found the "issue" in my failed trials post-May 2020 on my NanoPi M4 (rk3399)..
I discovered today (finally) that Kodi's internal ffmpeg isn't being configured with "--enable-libudev --enable-v4l2-request" resulting in missing hwaccels and obviously, no functional hardware acceleration. How this worked before in my build of May 2020 is a mystery (maybe ffmpeg from then auto-enabled these options by chance?).
I first tried to use the FFMPEG_EXTRA_FLAGS variable set on the commandline when invoking cmake, but since it is passed to the ffmpeg cmake script unquoted (see the commit adding it here: https://github.com/xbmc/xbmc/commit/cdbc12608b947d4afefc5bba48dc82e1f3514e52#diff-efa915ad129932095ae6f2a6d75e0d261386dd442b44338b4f6c705e25f1658eR241), only the first item ends up in ffmpeg_conf (due to CMake language rules I believe: https://gitlab.kitware.com/cmake/cmake/-/issues/17113#note_294727).
I have now added the arguments manually and confirmed they make it to ffmpeg, and am currently running a linuxtv-rkvdec-work-in-progress from @Kwiboo's linux-rockchip repository, rebased onto a clean v5.10.4.
Failing to notice this is kind of silly of me, and I'm sorry if I wasted anyone's time with my build configuration issues.
 
H264 decoding works great again (with DRMPRIME/DirectToPlane rendering enabled in the Kodi settings).
I do notice that the limited HEVC content that I have, which worked before (kernel 5.8-rc1 and Kodi/ffmpeg from May 2020), now shows a black screen.
 
Additionally, I tried merging in the changes from @Kwiboo's v5.10.1-drm-rockchip branch, and that gives me an option for a 4k resolution, but when playing back a 1080p H264 file, it appears only the top-left corner of the video output, including the black band around the 1920x800 movie, is shown full screen.
Playing back a 4k Big Buck Bunny MP4 file gives me "no signal" on my TV (it seems the actual 4k resolution is one of those @Kwiboo mentioned in the linked IRC conversation.
Is there a better branch to merge in from instead?
Is there any useful information I can provide to help this get fixed?
 
I hope the kernel v4l2 request uapi can move from staging soon (5.11?) so that the ffmpeg changes can be pulled in there.
 
As always: keep up the good work, I, along with many others, really appreciate what you're doing for these chips!

Ultimately we should have a single kernel source for all rockchip64 devices ;p
At this point neither rockchip64 nor rk3399 is really fit for that. They do not support rk3308 as a simple example. It should probably be some more or less stable cut from Rockchip's master.
Until recently I was actually more inclined to move devices from rockchip64 to rk3399 and make it a base for switching to Rockchip's master whether it would be 4.4 or 4.19 (FriendlyElec is already using 4.19 for R4S).
 
On the other hand boards are now divided ~50/50 between those kernels so we can move Station P1 to rockchip64 if it fits there better.
We will worry about switching to some form of Rockchip's master later - most probably not earlier than with first rk3568 boards...
 
As stated above I see no harm in that.

Haha if I knew that you were working on this I could have saved three hours earlier today
 
Nice job. Will feed this into the Station P1 soon.

ANNOUNCEMENT: The media script is now deprecated, in favor of the official Legacy Multimedia Framework. Please refer to this topic:
 

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. 

I saw Kwiboo in irc freenode chat #linux-rockchip and he helped me: showed his last changes for main line (I was need only hdmi fixes)
https://freenode.irclog.whitequark.org/linux-rockchip/2020-12-16 - here is log
https://github.com/Kwiboo/linux-rockchip/compare/v5.10.1...v5.10.1-drm-rockchip - here is his patches to mainline rebased on v5.10.1
 

Yes. I grabbed this one: code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } Armbian_20.12_Arm-64_bullseye_current_5.10.1_desktop.img.xz
Added code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } fdtfile=rockhip/rk3399-roc-pc-mezzanine.dtb
and booted right away.
Desktop does not start automatically, needs code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } startx
Resolution is 1920x1080 and cannot be changed to 1920x1200 via GUI.
Renderer is LLVM, so no hardware acceleration OOB. I'll try to install panfrost from source on top. I am stupid. I should have enabled glamor in xorg conf...
Will also try to use code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } xrandr to adjust resolution but I have my doubts that it will work....
 
Edit. Yep, xrandr failed as expected:
code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } xrandr: Configure crtc 0 failed
 

i have everything working. i recommend trying really tested images on p1.
 
http://bbs.t-firefly.com/forum.php?mod=viewthread&tid=2781&page=1#pid13344

I've gotten it from Firefly. Didn't need to pay income taxes or shipping. That's a game of chance. Many times I need to pay for income taxes, sometimes not.
For this I wanted to take my chances. I could use a 2nd RK3399 with 4GB ram. Ideal for running mainline while my M4V2 runs legacy.
It does run too hot for having such a case(85c at 2/1.5Ghz). I'll see to improve that. I suspect thermal pads that I'll replace with copper shims. Done that on my M4V2 and the difference is huge.