Werner

Hm indeed. I think I found something.
sun50i-h6-orangepi-lite2.dts includes sun50i-h6.dtsi
 
while in sun50i-h6-orangepi-one-plus.dts includes sun50i-h6-orangepi.dtsi which THEN includes sun50i-h6.dtsi and that one contains gpu information
So maybe this step is missing in the lite2 dt

Script for automatically enabling audio on all known ARM models (in my images, it runs automatically when the system is first started and includes all known audio devices for the model being used).
 
By the way, today, T4 has almost full support for all hardware (WiFi BT NVMe sound etc) and copes well with any tasks. It remains only to solve the issue with 4K resolution.
sound.sh

We resolved it with the module manufacturer and once done it simply popped up as soon as the USB was connected (using the default qualcomm module).  Thanks for your responsiveness

so
wget http://ftp.de.debian.org/debian/pool/main/m/meson/meson_0.54.0-1_all.deb sudo dpkg -i meson_0.54.0-1_all.deb Or just use my script I wrote that does all that and has the correct file included.
https://forum.armbian.com/applications/core/interface/file/attachment.php?id=5683

Or use the graphics repo repo
 
sudo apt-get install software-properties-common -y sudo add-apt-repository ppa:oibaf/graphics-drivers sudo apt-get update sudo apt-get upgrade Or Werner his method,
apt build-dep mesa Grab sources Compile like described here: https://panfrost.freedesktop.org/building-panfrost-mesa.html Restart X

These are 4 different ways to do the same. The first way is how it was done at the start. you don't have to make it that hard. My way is only good if you want to try different versions of MESA.
When using the 3th method with graphics repo (fastest) you do not need to install anything more. I'd go for Werner his example.

Be sure the kernel module for panfrost is activated and you use the latest 5.x kernel. Best to build the image yourself to be sure o have latest kernel. Good luck, I've still not found time to look into it for the H6.

I just noticed you don't even have to go to dev branch. In current it is enabled already. If your 5.4.x-current kernel is halfway up-to-date you should be able to modprobe cedrus.

Mini tutorial
I am putting here some notes for posterity
In the current version of armbian (testing H6) I use X11 / Xorg only reaches 1024x768, but my display reaches 1440x900.
To add this new resolution to the list of Settings/Display you have to give these commands:
 
# xrandr --listmonitors
(this command serves to see what it's called, the hdmi output)
 
# cvt 1440 900
(output: 
# 1440x900 59.89 Hz (CVT 1.30MA) hsync: 55.93 kHz; pclk: 106.50 MHz
Modeline "1440x900_60.00"  106.50  1440 1528 1672 1904  900 903 909 934 -hsync +vsync )
 
# xrandr --newmode "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
 
# xrandr --addmode HDMI-1 1440x900_60.00
 
# xrandr --output HDMI-1 --mode 1440x900_60.00
 
If it works then modify Xorg with:
 
# sudo mcedit /etc/X11/xorg.conf.d/40-monitor.conf
 
Section "Monitor"
Identifier "HDMI-1"
Modeline "1440x900_60.00" 106.50 1440 1528 1672 1904 900 903 909 934 -hsync +vsync
Option "PreferredMode" "1440x900"
EndSection
 
# reboot
 
 
 
 

Thanks for the instructions @NicoD!
 
I modified the mesa build options to enable egl:
meson -D egl=true -D gles1=true -D gles2=true -D shared-glapi=true -Ddri-drivers= -Dvulkan-drivers= -Dgallium-drivers=panfrost,kmsro -Dlibunwind=false -Dprefix=/usr build/  
With egl one can compile and run git version of supertuxkart.

to begin with... yeah!  
https://www.armbian.com/nanopi-a64/
 

Alright, I rebased my changes on karabek's repository: https://github.com/dbeinder/xradio/tree/karabek_rebase
The powersave commit is now split, with the power-lowering fix in the first part, and enabling userspace control over powersave in the second.

After some more direct comparison, I'm starting to think the part about removing driver-level TX rate selection doesn't make a measurable difference, in either throughput or dropped packets.
But since my much simpler code doesn't seem to make it worse either, I think that was just hacks built around the CW11x0 and simply never removed.
But as long as there is no upside,  it's probably better not to diverge too much from the CW1200 mainline version, so I left that in a separate branch for now: https://github.com/dbeinder/xradio/commits/karabek_rebase_minstrel

They are finally here. Still waiting for the thermal adhesive.

Merged.
 
dmesg |grep -i cedr [ 5.459706] sunxi_cedrus: module is from the staging directory, the quality is unknown, you have been warned. [ 5.461530] cedrus 1c0e000.video-codec: Device registered as /dev/video0 It is there. No idea how to use it though.

Same for me One Plus. Running on 5.6.5 with U-Boot 2020.04

Most of the boards just got one freshly build test image - check bottom of download pages.
 
- minimal image only
- mainly kernel 5.6.y
- Ubuntu Focal 20.04 based
- u-boot 2020.04
- xz compressed
- no end-user support

I know it is working fine as Focal is, but still wanted to point out that it is not support (yet) .

I know it is working fine as Focal is, but still wanted to point out that it is not support (yet) .

Maybe a small timer relay triggere by mains voltage that opens the 5v to the sbc for a second?

Hi!
 
Unless mistaken, I believe audio is missing from 3.5mm jack on the RockPi4b. To enable it, I had:
- To update the dts by adding definitions close to the RockPro64 (some available starting in mainline 5.6)
- Change them to use I2S0 instead of I2S1
- Enable audio-graph-card in kernel config (I also removed some audio modules which issued warnings/errors during boot)
- Patch es8316.c to prevent a kernel panic during boot (found in Ayufan's latest mainline kernel for RockPro64)
 
yannick@rockpi-4b:~$ aplay -l **** List of PLAYBACK Hardware Devices **** card 0: rockchiprk3399 [rockchip,rk3399], device 0: ff880000.i2s-ES8316 HiFi ES8316 HiFi-0 [ff880000.i2s-ES8316 HiFi ES8316 HiFi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: hdmisound [hdmi-sound], device 0: ff8a0000.i2s-i2s-hifi i2s-hifi-0 [ff8a0000.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0  
And finally, activate the proper DACs with amixer:
 
amixer set 'Right Headphone Mixer Right DAC' on amixer set 'Left Headphone Mixer Left DAC' on  
Would you like a PR for this?
 
Cheers, and thanks for your work on Armbian!

Here my video where I show how to download and install everything. And some gameplay.
Again thank you to @balbes150 for the images.
 

Bit off topic, that's what the topic is for
So I've been using the NanoPi M4/V2 for over a half year as main desktop and left my pc off most of the times. That today gave me a nice advantage in my electrical bill.
While the price of electricity goes up, I consumed 8.8% less only by using SBC's instead of my pc. And that not for a full year even. I can still improve with LED lights. And keep using my SBCs.

This does give an example why using ARM can be very benificial. I even made a quick video about it. Not really Armbian related. I don't think I need to convince any of you of the advantages of using arm.
But it is a good thing to think about where we can save money/energy in replacing x86 machines with arm boards.

Arm also has disadvantages off course. Less user friendly, do it yourself... I also talk about that. So you don't need to see the video any more actually, bit if you do, please enjoy.
Greetings, NicoD
 

Thanks a lot ... I'll try to see if I was lucky ... otherwise I'll go for "expensive education" :D

Agree! I am sick and tired reading this every fu***** day: "we want Armbian on XXX Please help", "i need instructions how to ..." "do this" There is a forum https://forum.armbian.com/forum/22-board-bring-up/ full of insane demands like "make Armbian on this and that board", but nobody asks themselves how much does this costs and who (will) pay(s) this shit ... !?
 
The other day one come to IRC starting to ask me if I can explain him how TV boxes boots. I said, we don't support that, but he didn't take this as an legit answer. And the more I explained that I don't know and even I knew I would not write manuals because he asked, the more aggressive he got ... he - while abusing my time - accused me (!) for hiding the information about boot processes ... amazing.
 

I estimate core crew makes 30-50h every day to keep this project running which means even with 10.000 USD per device we are not covered, but we can at least silence insane wishes and demands.
 
We have to work on this problem properly.

It is fine to use technical resources - they are dirt cheap compared to our time, but you can't hook on "armbian" if anything doesn't work or if you want support / ask questions. Official Armbian or unofficial: https://github.com/armbian/build#support
 
We also have boards that we don't support even images exists and you can build an image. I agree that the line is blurred but from my POW the only concern is lower quality of support on the TV boxes side since hacking advance development - not changing boot loaders, which prevents making standards.
 
We have too many boards and too little time.
 
Anyway, support for free software is never granted, so I don't know why we are making this difference important? Sometimes users ideas, due to not knowing how things are, are translated to projects worth millions and which we will certainly just ignore. Which is why we pointed out what we consider under https://docs.armbian.com/#what-is-supported
 
Branches should come together at some point, to lower maintenance costs. We tried once, but its insane lot of work. Perhaps once we merge more families together, this will finally become possible. Maintenance is still the biggest cost on those projects. And its those few developers private cost!
 
 
This and serious lack of resources - we don't accept new boards because:
 
- there are just a few people that have fun playing with them. Fun is absolutely needed.
- we can't hire help. End user donations only covers servers electricity.
- i have no desire to do anything with those boxes but I am fine to share technical resources - Repository, perhaps once even download if things are made in some automated fashion and doesn't put a pressure to the main stream or any maintenance resource.
 

First thing to do when installing a Linux is to wipe out Android and never look back  Only thing you need here is a boot loader for which you don't have sources and vendor never updates. The rest is easy to change, but the problem is that its different and no Android tool can make this easier.
 
My 2c.

I know you are our specialist on  Pi-Hole, and I am grateful for that.
However, the OP had very specific questions/requests like I did the same just recently (Spam).  Then every other post is simply spam that doesn't answer the question.
So, he wasn't wasting your time    he just wanted to know how to get his install back to the state it was before and really get rid of everything.
 
To me, fair enough, because even Linux leaves back some traces (not only Windows) - as I had to learn it the hard-way myself.

Two new boards have been tested.
This one did not work for me, partially because I did not understand what it is supposed to do... It's written in Chinese, and I have not been able to get 5V out of it... yet, only 4.2V.
This second one worked for me despite my very crude soldering job and the salvaged 18650.
So, after a few dozens of minutes charging the battery, I just unplugged the power on the charging board, and did not get any error on the OrangePi Zero...
Now, I would like to get some information on the voltage and other relevant information on the board to see if that's working properly, or if it's just luck...
And... I have to plug the 3.3V step down converter to one GPIO pin (linked to the main power), and see what's going on.