guidol

Today I tested volumio ( https://volumio.org/ )
on a x86-system and a Raspberry Pi3 and on a webpage I did read that a PCM5102A DAC can be used with the Raspberry Pi (40 Pin header) as a HiFiBerry-DAC.

So I searched how to connect the FriendlyARM (Neo) PCM5102A-Hat to the Raspberry 40-pin header:
 
I2S Raspberry Pi https://raspberrypi.stackexchange.com/questions/76188/how-to-make-pcm5102-dac-work-on-raspberry-pi-zerow https://blog.himbeer.me/2018/12/27/how-to-connect-a-pcm5102-i2s-dac-to-your-raspberry-pi/ http://wiki.friendlyarm.com/wiki/index.php/NanoHat_PCM5102A DAC BOARD > Raspberry Pi 3 Model B connector J8 PCM5102A 12 Pin cablecolor signal ======================================================================================= GND > PIN 6 (GND) Ground BLACK GND . DIN > PIN 40 (GPIO21) WHITE I2S/PCM Serial Data Input BCK > PIN 12 (GPIO18) GREY I2S/PCM Sample Rate Clock LRCK > PIN 35 (GPIO19) VIOLETT I2S/PCM Sample Rate Clock/Sync . . . . . . VIN > PIN 2 (5V) BROWN 5V Power In ======================================================================================= At he first configuration of Volumio configure I2S as active and select as I2S-DAC-type HiFiBerry DAC or Generic I2S DAC

Tested with Windows 10 version 1909 (Build 18363.1049) and Ubuntu 20.04 and default 4.9.109 kernel shipped directly from Microsoft.
Could run through my autobuild I usually do on remote machine flawless.
 
Needs NO_HOST_RELEASE_CHECK=yes

v20.08.1
Due to several - mainly small - problems in last build we are considering pushing out a smaller bug fix release.
 
- fixes that are merged in next 7 days (due = September 4th)
- all images will be rebuild
- an update will go out

Very cool. Remember saving for a BeBox after that.

It seems that the actual install routine of Pihole doenst detect buster with kernel 5.8 correctly.
At "my" normal install command "curl -sSL https://install.pi-hole.net | bash" I did get
[✗] Unsupported OS detected: Armbian 20.08.0-trunk Buster https://docs.pi-hole.net/main/prerequesites/#supported-operating-systems e.g: If you are seeing this message on a fresh install, you can run: 'curl -sSL https://install.pi-hole.net | PIHOLE_SKIP_OS_CHECK=true sudo -E bash' If you are seeing this message after having run pihole -up: 'PIHOLE_SKIP_OS_CHECK=true sudo -E pihole -r' (In this case, your previous run of pihole -up will have already updated the local repository) but after giving (as written above) the install command with the option "to not check the OS"
curl -sSL https://install.pi-hole.net | PIHOLE_SKIP_OS_CHECK=true sudo -E bash
the installation went fine  

Xunlong is putting out another batch of H5 devices at the end of the month.
Is there any particular reason to go with a H5 board these days? As I understand it, the advantage it has over the H3 are the gigabit ethernet and the 64-bit architecture, while being a bit more mature on mainline and Armbian than the H6 or similar Rockchips?
 

To enable I2S is easy. See this thread:
 
 
Have you tried the search function up on the right side?
 
You can do it on your Orange Pi PC Plus the same way Guido did it on Nanopi Neo.
 

Beta repository with latest armbian trunk:
- support for N2+
- sunxi/sunxi64 DEV kernel 5.8.y, most of others stays at 5.7.y.
 
Images will also be rebuild, but update should bring the same experience.

just lately I searched the forum about it.
There was a PR that fixed the bigger trouble we had.
However, I guess this automatic feature was built in in good faith, but I guess the script should ask/support the user like: You seem to live in TR, do want to set this as ur locale?
And if the user says no, give him the standard ncurser  selector.
What do u think  @igor?
 
// sent from mobile phone //
 

We have nightly images built available for the boards below.   Please help us test and report your experience via This Google Form.
 
Images are available via our normal Armbian download page.  Just scroll to the bottom to the "nightly build" section.
 
 
Bananapi Bananapim2plus Bananapim2zero Bananapipro Clearfogbase Clearfogpro Cubietruck Espressobin Helios4 Lepotato Lime-a64 Nanopct4 Nanopiair Nanopim4 Nanopim4v2 Nanopi-r1 Nanopi-r2s Odroidc2 Odroidc4 Odroidn2 Odroidxu4 Orangepi3 Orangepi4 Orangepione Orangepipc Orangepipc2 Orangepipcplus Orangepizero Orangepizeroplus2-h3 Orangepizeroplus2-h5 Pine64 Pinebook-a64 Pineh64 Pineh64-b Rock64 Rockpi-4a Rockpi-4b Rockpi-e Teres-a64 Tinkerboard Tritium-h3 Tritium-h5

@guidol thank you for your reply. You have one of the first versions.In the past I ran many images
meant for this board and they booted fine from sd , so it beats me why balbes150 images won't run
on my device but do run on yours! I'm certain the first test image from Balbes boots ,because their are
files written on sd , but thier is no hdmi output .Now I want to try to connect via a
direct cable connection between two machines ,either with an ethernet cable or a usb cable .

We have moved the forums to a new host with higher availability.  Caches may need to be cleared.  Hopefully performance will be better as well.   Please reply here to report any forum-related issues.

Who did say that I wanted that?  I know thats a problem on all SBCs when getting a new OS.
It was only as information!
Its really cool to get a newer Kernel greater than 3.0x AND armbian-style  Many Thanks!

often the focal image does boot and show the text-boot-log, but then the screen goes blank with no signal/desktop
had this after apt update & upgrade  
 
sometime the desktop does appear, but will blank out after some seconds  
 
The Raxda Rock is available via SSH/ping

Sometimes it seems to work if I move the mouse (no screensaver).
Via armbian-config I have now restricted the CPU to 1008Mhz/ondemand - and this time the Desktop starts.
 
Normally I only got problems with over 1008Mhz with Allwinner H2/H3 Systems, because they dont got a proper power-switching for the CPU.

@balbes150 I did try the image armbian-focal-rk3188_20200629.img 
It does boot - and after setting up the password I do get the armbian-desktop
BUT eth0 didnt get a DHCP-IP
 
The USB-Ethernet-Dongle works:
 
root@arm-32:~# ifconfig enx00123455562b: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.6.152 netmask 255.255.255.0 broadcast 192.168.6.255 inet6 fe80::49f2:70cd:caa7:706e prefixlen 64 scopeid 0x20<link> ether 00:12:34:55:56:2b txqueuelen 1000 (Ethernet) eth0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 ether 26:0b:6f:54:66:12 txqueuelen 1000 (Ethernet) eth0:avahi: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500 inet 169.254.4.216 netmask 255.255.0.0 broadcast 169.254.255.255 _ ____ __ __ _________ / \ | _ \| \/ | |___ /___ \ / _ \ | |_) | |\/| |_____ |_ \ __) | / ___ \| _ <| | | |_____|__) / __/ /_/ \_\_| \_\_| |_| |____/_____| Welcome to Armbian Focal with Linux 5.6.6-arm-32 No end-user support: built from trunk System load: 0.27 0.34 0.25 Up time: 9 min Memory usage: 15 % of 2001MB IP: 192.168.6.152 169.254.4.216 Usage of /: 17% of 15G root@arm-32:~# uname -a Linux arm-32 5.6.6-arm-32 #20.06.0 SMP PREEMPT Mon Jun 29 22:11:12 MSK 2020 armv7l armv7l armv7l GNU/Linux  
Radxa_Rock_armbian_focal_dmesg.txt

@balbes150
I did try your image linux1-rk3188-5.6.6-lubuntu.img on my Raxda Rock using sdcard. 
As I read from other members here I didnt thing it would boot, BUT it does  
 
I wonder about the differnt numbers when start_linux:
DDR Version 1.04 20130517 In DDR3 300MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=2 Die Bus-Width=16 Size=2048MB Memory OK OUT BUILD=====2 SdmmcInit=0 0 FwPartOffset=2000 , 0 run on sd0 OK! 38492 unsigned! SecureBootEn = 0 0 Boot ver: 0000-00-00#0.00 start_linux=====56640 4661552 Starting kernel...@0x60408000 start_linux=====66979 start_linux=====56640 start_linux=====56653 start_linux=====54938 Not on every boot I do get boot-messages and reboot doenst seem to work.
But after a time I do get a LXDE(?) Desktop on my HDMI-Monitor  
Eth0 isnt working (also with a proper /etc/network/interfaces) so I connected a USB-Ethernet-Dongle and did get a eth2  
login as: root root@192.168.6.151's password: Welcome to Linaro 13.09 (GNU/Linux 5.6.6-arm-32 armv7l) * Documentation: https://wiki.radxa.com/ Last login: Thu Jan 1 00:02:12 1970 root@radxa:~# uname -a Linux radxa 5.6.6-arm-32 #20.06.0 SMP PREEMPT Mon Jun 29 22:11:12 MSK 2020 armv7l armv7l armv7l GNU/Linux At the next restart it didnt started with USB-Ethernet and serial TTL-Dongle attached.
So I removed both, started and reattached the USB-Ethernet-Dongle.
 
Now it booted again and I had to enable eth2 as root with
ifconfig eth2 up
 
As attachment here you get the dmesg-log  
 
Raxda_Rock_566_dmesg.txt

If anyone is interested: The UART bootlog from my RK3188 Raxda Rock with debian 8 in nand as attachment
[172723.041565] Restarting system. DDR Version 1.04 20130517 In SRX DDR3 300MHz Bus Width=32 Col=10 Bank=8 Row=15 CS=2 Die Bus-Width=16 Size=2048MB OUT BUILD=====2 SdmmcInit=0 20 No.1 FLASH ID:2c 64 44 4b a9 0 OK! 251802 unsigned! SecureBootEn = 0 0 Boot ver: 2013-12-02#2.08 start_linux=====256654 3252872 Starting kernel...@0x60408000  
Raxda_Rock_UART_Boot_debian_8_nand.txt

they only I know for sdcard are
https://dl.radxa.com/rock/images/ubuntu/sd/radxa_rock_lubuntu_desktop_140626_sdcard.zip
https://dl.radxa.com/rock/images/ubuntu/sd/radxa_rock_ubuntu_14.04_server_140820_sdcard.zip

Maybe also interesting:
https://dl.radxa.com/rock/images/android/Boot_android_from_sdcard/radxa_rock_kitkat_sdcard_boot_update_0621.zip

And the directorys:
https://dl.radxa.com/rock/images/loader/
https://dl.radxa.com/rock/images/parameter/
https://dl.radxa.com/users/dev/3188/

For all rk3188 owners, can you provide a link to any Linux image that you have start and running ? I want to see which version of u-boot and kernel is used there.

hahaha nice find!  I was mad at something so I created a test file.
 
I was trying things out initially in a virtual machine
 
More updates coming. I will focus more on documentation today and maybe finish working on remote backup support

@guidol tested on Libre Computer Tritium with a Pimoroni PHAT DAC (PCM5102A), only changes needed:
 
enable i2s@1c22400   (i2s1)
 
change overlay to use i2s1 instead of i2s0.
 

 
 

Thought you might want to know :-)
 

Another update worth mentioning
 
1. Removed all the unnecessary plugin files reduced the amount of files in general, reworked some of the file hierarchy and layout

Major Updates
 
1. The install.sh script now installs the debian backports version of smartmontools which doesn't depend on Python 2 and is a much newer version. This also sped up the install process a bit.
2. Added single disk support OS/Data
3. Updated the update system, dashboard now shows the latest version, when you choose updates it ill now show the changes between the installed version and the current.
4. We added Rescan disks button to add volume in setup as well as add volume in the main web ui app.
5. The system no longer reboots after setup it now directs you directly to the login screen.
 

Wrong CPU_GOVERNOR and no way to dissipate the heat from inside the enclosure leads to overheating.
 
Some very simple benchmarks on recent kernel:
https://github.com/avafinger/nanopi-r2s-ubuntu-server-minimal-image