NicoD

Ok, now I understand better how hardware is defined in DTS files. I realized the Orange Pi Lite 2 DTS is really barebones compared to the Orange Pi 3. I can wait for kernel 5.7 to test more.
 
The question I have is: How does it work in LibreELEC if the same DTS is used? (Is it only needed for X11 acceleration?)
 
EDIT: I answered my own question. The LibreELEC pull request for Orange Pi Lite 2 (which I merged on my local repository) adds the GPU and Display Engine entries in the DTS. So Armbian would need to merge that in the first place, @Igor can you take a look at the commits from this pull request (if you have the time of course)?, it has both the GPU and DE added to the DTS unlike Armbian's one. I would do it myself but I fear I would break the working patch since I have to learn more about git and diff. EDIT: I enabled the gpu myself but I found the system to be unstable after doing that, I will try to debug it with UART (SSH crashes too) and report back.
Thanks, I completely forgot about that Linux naming convention inside the kernel.
 
As always, thanks for the useful advice and answers.

No, they are disabled because nobody took time to properly enable them in board DTS until now (it will be in 5.7).
No, sun4i-drm is for all Allwinner SoCs, it supports Display Engine 1.0, 2.0 and 3.0. It's just named by Linux tradition where it takes name of first (oldest) supported platform.

if you use ubuntu, don't build mesa your self, you can use https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers
if you insist to build your self, please also update libdrm and libglvnd. these two deps are also important.
 
 

if you use wayland session, panfrost is used by default.
if you use Xorg, a config file is required, which is same as lima. please follow: https://gitlab.freedesktop.org/lima/web
and make sure your xorg >= 1.20
 
 

Panfrost instructions Armbian
 
!!!! I made a script that does all this, check a few posts later for the script !!!!!  
This tutorial explains how to build an Armbian image with panfrost. And what else you need to make it work.
These are early drivers. Many things don't work yet. Only OpenGL 2.1 works now.
 
You need to build an image with kernel 5.2 or later.
For this you need an x86 pc with Ubuntu 18.04 or a virtual Ubuntu 18.04 x86 image.

First install git, then clone the build folder from Armbian, and enter the build directory.
 
apt-get -y -qq install git git clone --depth 1 https://github.com/armbian/build cd build Now run the script with EXPERT=yes so you can choose to build a dev image.
sudo ./compile EXPERT=yes Choose "Full OS image for flashing" Then "Show a kernel configuration menu before compilation" Choose your board. If it's not in the regular list, look in "Show SCS/WIP/EOS/TVB". Choose Development version kernel configuration -> device drivers -> graphic drivers -> panfrost  
Let it run until it's finished. The image will be in the /build/output/images
Burn it to an SD-card/eMMC/...
 
Now we need to install all the needed software
sudo apt install flex bison python3-mako libwayland-egl-backend-dev libxcb-dri3-dev libxcb-dri2-0-dev libxcb-glx0-dev libx11-xcb-dev libxcb-present-dev libxcb-sync-dev libxxf86vm-dev libxshmfence-dev libxrandr-dev libwayland-dev libxdamage-dev libxext-dev libxfixes-dev x11proto-dri2-dev x11proto-dri3-dev x11proto-present-dev x11proto-gl-dev x11proto-xf86vidmode-dev libexpat1-dev libudev-dev gettext glmark2 glmark2-es2 mesa-utils xutils-dev libpthread-stubs0-dev ninja-build bc python-pip flex bison cmake git valgrind llvm llvm-8-dev python3-pip pkg-config zlib1g-dev wayland-protocols Download and install meson
wget http://ftp.de.debian.org/debian/pool/main/m/meson/meson_0.55.3-1_all.deb sudo dpkg -i meson_0.55.3-1_all.deb Download and install mesa DRM
git clone git://anongit.freedesktop.org/mesa/drm cd drm meson build --prefix=/usr ninja -C build sudo -E ninja -C build install cd .. Download and install mesa graphics
git clone git://anongit.freedesktop.org/mesa/mesa cd mesa meson -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=panfrost,kmsro -Dlibunwind=false -Dprefix=/usr build/ ninja -C build/ sudo ninja -C build/ install REBOOT
 
Optionally, update sdl (recommended)
git clone https://github.com/SDL-mirror/SDL.git cd SDL mkdir build cd build cmake ../ make -j6 sudo make install REBOOT
 
Only thing that works ok with it is supertuxkart, to install it.
sudo apt install supertuxkart
 
Panfrost - Linux games working from repo
SuperTuxKart - Works well
ExtremeTuxRacer - lots of glitches
AssaultCube - lots of glitches
 
Instructions by Salvador Liébana & NicoD

Thanks NicoD. No hurry here, I checked yesterday official Friend Elec images for NanoPi M4, they are still on 4.4 kernel, so I just installed Buster server with 4.4 and all works fine, and hat should be fine as well. 

mainline amlogic hwvdec with patches still in review, can be directly used by mpv with `-hwdec=auto`
 
cpu usage drop to 10% from 50%

@JMCC The video is ready.
I don't think it will get too many views. But it can help other frustrated users
Thanks for the help.
 

Did you try different dtb files?

Try this thread for more info.
 

If you use an arbitrary u-boot (not files that are already specially prepared and located on my site), then you use two commands to write u-boot.
This is indicated in the instructions in the first message of this topic (in the spoiler for old u-boot). 
 
AML also uses the first bytes, so the universal option (which will work on all platforms the same way) is specified in my message. 
 
Pay attention. A key feature of my ready-made u-boot is the ability to write them in a "dumb" way (by any program), including in the Wibdow system, where there is no easy way to perform complex writing options (for saving the partition table).
 
 
@NicoD  To use your received u-boot file (which you will get yourself), you need to write this file with two commands (these commands are in the first message of the theme in the spoiler). I asked you for this file, just in order to process it at home and make a u-boot file that can be used in a simple "stupid" recording mode by any program in Windows. If you provide me with verified files from other devices (models), I can also make the necessary u-boot options from them (for simple recording) and put them on the site for General use by other users.

You did almost everything right, one small mistake.
 
wrong
sudo dd if=/dev/mmcblk2p1 of=u-boot-opi3.img bs=512 count=8191
 
 
right
sudo dd if=/dev/mmcblk2 of=u-boot-opi3.img bs=512 count=8191
 
 
Note that you need to copy the first sectors of the device (not the partition). The loader is always located in the first sectors of the device. 

I'm always willing to make a video about any subject you guys choose.
Give me the details of what you want to see/hear and I'll do my best with it. 

@Igor Are you at the next Fossdem in Brussels? If so we could try to meet for an interview.
You do not need to prepare for that. Just repeat a sentence when it didn't come out right. I cut and paste everything so nobody notices mistakes.
 
Otherwise I could make a question list(and you can add questions you want to answer). And you could film yourself with a smart-phone answering the questions. I can then use that video and cut/paste my questions in between.

I'm also not a good presenter, so live questions over internet would come out badly. I always have to redo my intros many times for my videos until I feel it's acceptable. I always got more blooper footage than useable video

The U-Boot is located after the partition table but before the first partition. So, when you grabbed the U-Boot from Armbian image, and when you start the extract at byte # 0, it is also grabbing the partition table followed by U-Boot itself. U-Boot location is at byte #8192, so the extract should be done like that :
dd if=ambian.img of=u-boot-only.img bs=1024 skip=8 count=1024 This will extract a 1MB image, big enough since native Armbian U-Boot is sized about 620KB ...
Then, you can place it inside Balbes image without touching it own partition table by doing a "seek" :
dd if=u-boot-only.img of=balbes-image.img bs=1024 seek=8 conv=notrunc That should do the job without scrapping Balbes original partition table ...

Getting the right file is very easy. Run any version of Armbian on OPI3, and run  the command
 
fdisk -l
 
pay attention to the number that indicates the beginning of the first section on the SD card, then run the second command, which uses the number of the beginning of the section minus 1
for example you will get this output
 
/dev/sdf1                32768  1081343 1048576   512M             e W95 FAT16 (LBA)
/dev/sdf2              1081344 10239999 9158656   4,4G            83 Linux
 
32768 - 1 = 32767
 
dd if=/dev/sdf of=u-boot-opi3.img bs=512 count=32767
 
You send the received file u-boot-opi3.img  to me.

Since - in my eyes - at least - there is a likelihood of confusion regarding the "Supporter" tag of members that actually (recurring) donating to the project. People could think "Supporter" means staff member that actually support people with their issues. The real staff rank, Moderator and Administrator to say, is "hidden" in their individual profiles. Since I like the idea of flat hierarchy I do not suggest to make the actual staff visible in forum postings but simply rename the Supporter to something like "Donator" to make it clear that these people donated to the project but are not necessarly involved into it.
 
Tell me what you think,

I'm still getting nowhere with it. After installing panfrost onto Armbian Bionic and reboot I get this result. (OPi3)
I think I'll throw in the towel. 
If anyone fas more succes then I have, please let me know.

I think that this is faster way
sudo apt-get install software-properties-common -y
sudo add-apt-repository ppa:oibaf/graphics-drivers 
sudo apt-get update
sudo apt-get upgrade
but oibaf provide only arm64 packages!
 

I don't have OPI3, I can assume that OPI3 needs its own u-boot. The version from Tanix TX6 will not work. You can try pulling u-boot from any working image (which runs on OPI3) and try using it. If you get a working u-boot, send it my, I can process it for use in the specified mode (writing from Windows) on universal images for writing them to OPI3.

This is not an Armbian image ...
Try one of those : https://dl.armbian.com/nanopineo2/

I think very strongly that validating email should be (one of?) main steps to graduate from Validation -> Member. Anybody can put in whatever they want for an email address, it's all BS until they have validated it. And in the meantime they can be posting already...
 
Most of spammers I see, never even validated their email...
 
Some number of Likes (perhaps along with other criteria like post count, and/or time on forum) I think is probably a good idea for this "Trusted Member" (or whatever we want to call it) intermediate level. I think Likes especially are hard to fake.

Need to limit the time for regular users to edit messages to 2-3 hours or 1 day.
 
I don't see any reason for regular users to be able to edit messages after 1-2 days.

This is the Armbian forum... Armbian is a Linux distro where you don't need a remote control.
 
Go ask on an Android forum or a forum of the product manufacturer. You are at the wrong place here.

I also don't get this. Isn't their goal to sell more chips? Then wouldn't they sell a lot more with good/better software/support?
Seems like they don't want people to use Linux on them. 
 
They do make the most powerful SoC's on cheaper SBC's. I use Amlogic SoC's for video editing. For that you only need a good cpu(multicore+single core), and gpu/vpu is of lesser importance. In power per watt the A311D/S922X are just the best. 
But I'd like to be able to do a lot more than just video editing on them. I loved the Odroid C2 with S905. Was more versatile. But then again they claimed 2Ghz clockspeed.  

I can't wait for the RK3358 to show up on a board. That should be able to outmatch the Amlogic SoC's. It is to see what consumption and how much heat it'll produce.
Rockchip used to be worse than amlogic in their support. But they did make that up. Allwinner is no match in performance. But they are very usable boards for lighter tasks. OPi+ is my MP3 player and NAS with a sata hd and 1.5TB USB2 external HD. No other board does that better.

The RK3399's are my most used SBC's for light desktop tasks/surfing/watching video. But no match for video editing. RK3399 can edit/render 1080p videos well. But A311D does 1440p. The C2 used to do 720p. So it did improve quickly last years.

I'm very happy you make these images. Me with a lot of other people. It makes many boards a lot more useful where otherwise they'd be paperweights. I love your efforts in making more compatible images. One of my next videos will be about that. Nobody else ever came so close to universal images as you have. I take my hat off for that.

I just bought the X96 Air since it's S905X3. Made me nostalgic to my Odroid C2 and it was dirt cheap. If only I had the SMD soldering skills, then I could take the 32GB eMMC and 4GB ram from X96 and solder them onto my 2GB+16GB Khadas VIM3. For the 30euro I payed, the 32gb eMMC and 4GB ram are worth it. I just don't want to risk the VIM3.
Cheers.
 

That seems a very paradoxical question. To ask that question you have to first start writing a question, but the question you ask can't be written before you start asking a question.  It's like a new big bang is happening in my head.
Welcome to the forum.

Thank you.
Here are all of them in a bit better quality.

Number 1 :  Beach Island

Number 2 : Armbian Car

Number 3 : Penguin Clouds

Number 4 : Penguin Clear Background

Number 5 : Armbian Space

Number 6 : Armbian Terracota

Number 7 : Penguin Clear Background

 
Bonus : Rounded Penguin