guidol

for non-multimedia: got a Pihole on a C2 Armbian Buster with Linux 5.6.8-meson64 without problems
"sleeping" idle at 33 degree
 
package bsp-kernel[20.05.0-trunk]  u-boot[20.05.0-trunk]   dtb       [20.05.0-trunk]
firmware                 [20.05.0-trunk]   config[20.05.0-trunk]   branch [dev]
 

Ubuntu changed the location of the mini.iso file for the minimal Ubuntu (Server?) installer in their file servers (since the 20.04 release), it's now located here:
 
http://archive.ubuntu.com/ubuntu/dists/focal/main/installer-amd64/current/legacy-images/netboot/mini.iso
 
The docs should be changed since it could be confusing for new users/developers.

I improved the dts of Phicomm N1 again.
The reasons are:
1. The Ethernet card of N1 is not very compatible with some switches. When the ethernet phy is activated, the flow control sometimes cannot be turned on, so  will get bad results during the speedtest.net . For this reason, I added a dts separately force_thresh_dma_mode, which is equivalent to flow control in software mode. But there are also side effects: tx performance is reduced. In addition, as auxiliary optimization items, set snps, aal; snps, txpbl = <0x8>; snps, rxpbl = <0x4>; their role is to improve the performance of the network card.
2. The phy reset-delay-us value of N1 is sometimes not enough. When running openwrt, sometimes the ethernet phy cannot be enabled, so the reset-delay-us value is increased.
Provide two dts files:
meson-gxl-s905d-phicomm-n1.dts: This is the default dts, used in most occasions, when the flow control can be turned on normally, this is the best choice
meson-gxl-s905d-phicomm-n1-thresh.dts: This is a dts with the force_thresh_dma_mode option enabled. It is applicable when flow control cannot be turned on. You can use force_thresh_dma_mode to control flow at the cost of a small amount of performance loss.
meson-gxl-s905d-phicomm-n1.dts meson-gxl-s905d-phicomm-n1-thresh.dts

@Igor  I did this already  
see 
 

Indeed, the configuration in the mvebu64.conf script is wrong.
 
The 2 CS 2 GB image is compiled with the same DDR topology parameter as the 2 CS 1 GB image (DDR_TOPOLOGY=2).
It appears that the configuration for the 2 CS 512 MB version is also wrong, as it points to the same topology file as the 1 CS version.
I guess this is not really a problem, because I'm not even sure that this variant actually exists.
 
So to answer my previous question:
What is used is only 512 MB from each chip.
 
If anyone needs it, here is the bootloader (U-Boot 2018.03-18.12) compiled with the correct topology (DDR_TOPOLOGY=7):
flash-image-ddr3-2g-2cs-1000_800.bin
 
Note that only changing the DDR_TOPOLOGY from 2 to 7 was not enough, because this configuration is also missing from the Marvell sources, even though that's the parameter used in the build examples.
The correct topology exists in the Armbian tree, but with the wrong name:
https://github.com/armbian/build/blob/master/packages/blobs/espressobin/DDR_TOPOLOGY_2-2g.txt
The A3700-utils-marvell/script/buildtim.sh script must also be adapted to accept a DDR_TOPOLOGY value higher than 6.

Great work Guidol! Thanks for all your tireless efforts!

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

I know most of you probably don't want to hear any more about this chip, but I recently fixed quite a few long standing issues.
It's not perfect yet, but it improves scanning/reliable reconnect, incoming frames missed in powersave, ping times, and rate selection.
Here's the patch set: https://github.com/fifteenhex/xradio/pull/12
Edit: rebased from karabek: https://github.com/dbeinder/xradio/commits/karabek_rebase
And some important comments about powersave: https://github.com/fifteenhex/xradio/pull/11#issuecomment-616226880
In short, relative to the current version, with powersave on, idle consumption is lower by 200mW, but with powersave off, it is 300mW higher
- so that should be a consideration if you want to integrate this into Armbian builds for tiny boards like OPZero.

Of course a 65MBit chip will never be fast, but I'd say it is pretty usable as an IoT node now. This hasn't seen much testing,  so your comments are appreciated.

@Ernest Kusa seeing your compile did work so well I was a little bit more "brave" and compiled the dev version
Armbian bullseye with Linux 5.6.5-sunxi   (non-minimal = console only image)
 
Also here no more problems - on my site - with ethernet going down/up.
Audio is working like on your current compiled image
I didnt check emmc, because I want to have there the android inside.
 
Welcome to Armbian bullseye with Linux 5.6.5-sunxi No end-user support: built from trunk & unsupported (bullseye) userspace! package bsp-kernel[20.05.0-trunk.111] u-boot[20.05.0-trunk] dtb [20.05.0-trunk.111] firmware [20.05.0-trunk] config[20.05.0-trunk] branch[dev] System diagnosis information will now be uploaded to http://ix.io/2iOj

@Ernest Kusa Thanks for compiling  Did you use some special options in the armbian-build-system or just stadard?

Analog-Audio and HDMI sound is working on my Sunvell R69 with red pcb (1GB Ram).
Analog-Audio is only set to a very low volume.

Do a 
apt install alsa-utils mpg123
and use
alsamixer
to set Line-Out and DAC to a value around 75 (upper limit of the white range)
 
I could play internetradio just fine
 
Analog-Audio: mpg123 -v -b 1024 -a hw:0,0 -@ ./MP3_FFH80s HDMI: mpg123 -v -b 1024 -a hw:1,0 -@ ./MP3_FFH80s aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: allwinnerhdmi [allwinner-hdmi], device 0: 1c22800.i2s-i2s-hifi i2s-hifi-0 [1c22800.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 Welcome to Armbian buster with Linux 5.4.33-sunxi No end-user support: built from trunk package bsp-kernel[20.05.0-trunk] u-boot[20.05.0-trunk] dtb [20.05.0-trunk] firmware [20.05.0-trunk] config[] branch[current]  
MP3_FFH80s

@linuxfan the package syslinux for buster is only referenced for the platforms i386 & amd64:
https://packages.debian.org/buster/syslinux
because this are Boot-Loaders für DOS FAT und NTFS which are mainly not used on ARM-Systems!?
 

there is then also (no more?) NanoPi Neo2/NeoCore2 in a LTS-version - only the Neo/NeoCore/NeoAir H3 line has LTS-support
So - what will be the "big next thing" as CPU?  H6/H64/H313/H616 on a like Neo2-device?
http://www.allwinnertech.com/index.php?c=product&a=index&pid=6

Yes  arrived on my Neo2...
 
Welcome to Armbian Buster with Linux 5.6.5-sunxi64 dpkg -l|grep u-boot linux-u-boot-nanopineo2-dev 20.05.0-trunk arm64 Uboot loader 2020.04  

@AZ8 you could also check if your system actually has to the patch for journald log-size in /var/log:
 

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

Everyone likes to say one word "give" and always for free (all free). Give a new core, and all the functions will work in it. Give support to all the existing equipment in the world and make sure that it turns on automatically, without any settings. Give me a new loader. Give the installation system to eMMC and so that you need to press one button, and better from a mental order. Give full-screen 4K video playback on any shit. Give the perfect job to all the shit that is produced and sold for $ 10-20. Give the source code, and that they would work immediately on the same command and without errors. Give answers to all your questions and be sure to answer everyone personally and in detail. And most importantly, everyone wants it for free and immediately. For everyone who wants to get it-there is a tariff, pay $ 10,000 and you will get full support for your TV box model for 1 year. 

I wasnt also rude, but I copied a part of his first sentence to my answer BUT added a smiley and did put some more in the additional text.
And I did try to help him with some ideas & links - wasnt that nice enough? 

I like this picture - as welcome message
_ _ ____ _ _ _ ____ | \ | | _ \(_) | \ | | ___ ___ |___ \ | \| | |_) | | | \| |/ _ \/ _ \ __) | | |\ | __/| | | |\ | __/ (_) | / __/ |_| \_|_| |_| |_| \_|\___|\___/ |_____| Welcome to Armbian Buster with Linux 5.6.2-sunxi64 package bsp-kernel[20.05.0-trunk] u-boot[20.05.0-trunk] dtb [20.05.0-trunk] firmware [20.05.0-trunk] config[20.05.0-trunk] branch[dev] System load: 0.02 0.02 0.00 Up time: 7:49 hours Local users: 2 Memory usage: 21 % of 477MB IP: 192.168.6.22 CPU temp: 44°C Usage of /: 12% of 15G storage/: 1% of 229G  

Thank you for the detailed answer! Peace to your home!

I like this picture - as welcome message
_ _ ____ _ _ _ ____ | \ | | _ \(_) | \ | | ___ ___ |___ \ | \| | |_) | | | \| |/ _ \/ _ \ __) | | |\ | __/| | | |\ | __/ (_) | / __/ |_| \_|_| |_| |_| \_|\___|\___/ |_____| Welcome to Armbian Buster with Linux 5.6.2-sunxi64 package bsp-kernel[20.05.0-trunk] u-boot[20.05.0-trunk] dtb [20.05.0-trunk] firmware [20.05.0-trunk] config[20.05.0-trunk] branch[dev] System load: 0.02 0.02 0.00 Up time: 7:49 hours Local users: 2 Memory usage: 21 % of 477MB IP: 192.168.6.22 CPU temp: 44°C Usage of /: 12% of 15G storage/: 1% of 229G  

Err I assume it has been committed after all, juist built first 5.6 image :  " Armbian_20.05.0-trunk_Orangepioneplus_buster_dev_5.6.2_minimal.img " using BRANCH=dev RELEASE=buster BUILD_MINIMAL=yes BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no. Now after flashing I noiced
 
1/ no 1.8 GHz (yet) or this needs to be added specifically to overlay first, eg " cpu-clock-X-Yv "
available frequency steps: 480 MHz, 720 MHz, 816 MHz, 888 MHz, 1.08 GHz, 1.32 GHz, 1.49 GHz
 
2/ wireguard is now incorporated in to kernel 5.6 so I assume flag " WIREGUARD=no " has no value anymore
 
etc etc, but yes this looks promising :-), thanks
___ ____ _ ___ / _ \| _ \(_) / _ \ _ __ ___ _ | | | | |_) | | | | | | '_ \ / _ \_| |_ | |_| | __/| | | |_| | | | | __/_ _| \___/|_| |_| \___/|_| |_|\___| |_| Welcome to Armbian buster with Linux 5.6.2-sunxi64 No end-user support: built from trunk System load: 0.01 0.07 0.06 Up time: 6 min Local users: 2 Memory usage: 9 % of 988MB IP: 192.168.10.235 CPU temp: 43°C Usage of /: 5% of 15G  
 

I can enable bananpi M2 ultra sound (headphone and mic on pcb)  You must add this on the dtsi file.
 
        dma: dma-controller@01c02000 {
            compatible = "allwinner,sun8i-h3-dma";
            reg = <0x01c02000 0x1000>;
            interrupts = <GIC_SPI 27 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&ccu CLK_BUS_DMA>;
            resets = <&ccu RST_BUS_DMA>;
            #dma-cells = <1>;
        };
        codec: codec@01c22c00 {
            #sound-dai-cells = <0>;
            compatible = "allwinner,sun8i-h3-codec";
            reg = <0x01c22c00 0x300>;
            interrupts = <GIC_SPI 30 IRQ_TYPE_LEVEL_HIGH>;
            clocks = <&ccu CLK_BUS_CODEC>, <&ccu CLK_CODEC>;
            clock-names = "apb", "codec";
            resets = <&ccu RST_BUS_CODEC>;
            dmas = <&dma 19>, <&dma 19>;
            dma-names = "rx", "tx";
            allwinner,codec-analog-controls = <&codec_analog>;
            allwinner,audio-routing =
                "Headphone", "HP",
                "LINEIN", "Line In",
                "MIC1",    "MBIAS",
                "MIC1", "Mic",
                "MIC2", "HBIAS",
                "MIC2", "Headset Mic";
            status = "okay";
        };
        codec_analog: codec-analog@01c22f00 {
            compatible = "allwinner,sun8i-a23-codec-analog";
            reg = <0x01c22f00 0x4>;
        };
 
Then modules that must be loaded are
 
sun8i_codec_analog     24576  1
sun4i_codec            32768  3
snd_soc_core          118784  2 sun4i_codec,sun8i_codec_analog
snd_pcm_dmaengine      16384  1 snd_soc_core
snd_pcm                65536  2 snd_pcm_dmaengine,snd_soc_core
snd_timer              24576  1 snd_pcm
snd                    45056  3 snd_timer,snd_soc_core,snd_pcm
soundcore              16384  1 snd
 
to test the player execute that to check the sound
$ aplay /usr/share/sounds/alsa/Front_Center.wav
 
then execute
$ alsamixer
to control the volumen and gain
 
To enable mic do that.
1) open alsamixer;
2) press "tab" to switch to capture;
3) press "bar" on the first capture channel;
"L_____R" red sign should appear;
4) select by arrow key MIC as the source of the first
input source;
2) record a test file:
arecord -f cd -D hw:0,0 -d 10 test.wav
play it back to test i.e.:
mplayer test.wav
 
Thats all ...
 
best regards Asimov
 
 

There I only have the default-file-entrys:
 
 
I did now edit my /usr/lib/armbian/armbian-zram-config and inserted the lines from the fix at the right place (which were missing).
The fix inserted/corrected the SystemMaxUse=20M in /etc/systemd/journald.conf
 
Before a reboot I did enter a "journalctl --vacuum-size=5M"
 
And after the reboot I have:
root@opi-one(192.168.6.114):~# df Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf /dev/zram0 49584 19676 26324 43% /var/log Many thanks at @Igor
 
 

There I only have the default-file-entrys:
 
 
I did now edit my /usr/lib/armbian/armbian-zram-config and inserted the lines from the fix at the right place (which were missing).
The fix inserted/corrected the SystemMaxUse=20M in /etc/systemd/journald.conf
 
Before a reboot I did enter a "journalctl --vacuum-size=5M"
 
And after the reboot I have:
root@opi-one(192.168.6.114):~# df Dateisystem 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf /dev/zram0 49584 19676 26324 43% /var/log Many thanks at @Igor
 
 

I encountered this running apt-get update, not during a build.
 
Tried several fixes without success.
Eventually fixed it using info from the bug report for the last time it occurred in 2018.
here
sudo apt-key adv --keyserver pool.sks-keyservers.net --recv-keys ED75B5A4483DA07C Harry