guidol

RTL8211 is used as PHY on all GbE capable SBC I know. The majority of boards uses RTL8211E, some RTL8211F and Olimex used also RTL8211CL a while ago. Pretty much irrelevant since always the GbE MAC implementation lives inside the SoC and the RTL8211 PHY is just attached via RGMII (so the MAC and PCIe parts of these RealTek chips are not used on SBC anyway. Might change soon since more and more SoCs are PCIe equipped).
 
But even on the soon to be released Orange Pi R2 the two RTL8211E are only used as PHY and attached via RGMII (RTD1296 has 3 GbE MACs but only one internal GbE PHY so for the two additional GbE interfaces external PHYs are needed):

I use the OrangePi Zero.  But it is similar to other model.
 
It's very simple:
 
1) use the mainline 4.11.x kernel 
2) enable the uart1 and pps-gpio in /boot/armbianEnv.txt  like this :
  
overlays=uart1 pps-gpio param_pps_pin=PA7  
3) edit /etc/default/gpsd  to use ttyS1 as gps device
# Devices gpsd should collect to at boot time. # They need to be read/writeable, either by user gpsd or the group dialout. DEVICES="/dev/ttyS1" # Other options you want to pass to gpsd GPSD_OPTIONS="-G -n "  
4) If you use ntpd,  edit /etc/ntpd.conf like this:
# GPS Serial data reference server 127.127.28.0 minpoll 4 maxpoll 4 prefer fudge 127.127.28.0 time1 0.135 refid GPS server 127.127.22.0 maxpoll 4 # ATOM(PPS) fudge 127.127.22.0 flag3 1 # enable PPS API  
5) Or if you prefer crony rather than ntp, install chrony instead of ntp, edit /etc/chrony/chrony.conf , add this to end of it:
refclock SHM 0 refid GPS precision 1e-1 offset 0.134 delay 0.2 noselect refclock PPS /dev/pps0 lock GPS 6) connect GPS module to UART1 
    GPS      Zero
---------------------
   TXD        UART1_RX PIN10
   RXD        UART1_TX  PIN8
  PPS          IO-1  PIN12
 
7)  use ntpq -p  or chrony sources. to check it.
 

http://wiki.friendlyarm.com/wiki/index.php/NanoPi_K1_Plus
 
RPi 3 form factor like their K2, maximum DRAM (2GB), Gigabit Ethernet, Wi-Fi with onboard aerial provided by RTL8189ETV, still using their own/new eMMC socket. According to schematics and their Github repo a SY8106A voltage regulator is used which is great news since then it's possible to clock the H5 well above 1.3 GHz.

This worked.
 
 

I do have a serial cable. If i do find the time this evening I'll check the output AND I'll test the arch-linux

Actually, I have no idea why armbian won't boot on the nanopi A64. I can see some u-boot-activity but after that the board goes to a halt. It has to be a kernel issue in my perspective but I have no serial cable so I can't check anything. Sorry that I can't be of more help in this.
The arch-linux image boots fine, gives a fully functional xfce-desktop, automatically in the proper resolution (for me currently 1440x900). I had only to attach a wifi dongle for internet. Sound works flawless to.

Hmm. We had some urgent updates from development branch which is already at 5.42 Splitting master and development branch, in general, brought some confusion and this is a direct consequence. Not that critical but it shell be fixed soon.

For those interested I made some improvements in the GLES display backend of uae4arm:
 
https://github.com/Chips-fr/uae4arm-rpi
 
I tested it on Armbian on my orange Pi Pc+ (H3), was able to get 50fps for some games.
 
The only remaining issue is that vsync is not activated and tearing occurs.
Does anyone know how to solve this ?
 
Feel free to try on others boards...
 

Hello to all
Now I'm doing my device based on Orange PC
It will be in the casing so it needs cooling.
I assembled a small fee for fan control
And he wrote a program for controlling and monitoring work
It can run as a daemon
 

 
To use I chose to 12V FAN 3PIN. To safely manage them with our Pi PC is necessary to collect the scheme in three transistors.
In the transistor Q3 will be lost that is 0.6V 5% of 12V. Therefore, the maximum speed of passport we can not achieve.
I have received the maximum at 2400 rpm of maximum 2500 passport.
Capacitor C1 pick up empirically, since of it will depend on the minimum threshold drawdown tachometer. As the tachometer now use Hall sensor.
For myself, I put 100uF, because with 50uF at a duty ratio of less than 50% control of the lost turnover.
 
To work it is necessary:
- Kernel with support for GPIO Support (sysfs interface)
- WiringOP from WereCatf https://github.com/WereCatf/WiringOP.git
git clone https://github.com/WereCatf/WiringOP.git -b h3 cd WiringOP chmod +x ./build sudo ./build  
Installation:
- Unpack the archive
- Define the value set that you need.
    Pina, minimum and maximum temperature, the number of Hall sensor pulses per revolution of the cooler, while the demon of the reaction, the minimum duty cycle.
- compile
g++ OPi-fan.c -o OPi-fan -lpthread -lwiringPi - Copy of your directory in /usr/local/bin
cp ./OPi-fan /usr/local/bin After that it can be used using various keys run.
The daemon reads the CPU temperature and basis of specified minimum and maximum temperature calculates the duty cycle of the PWM.
The software PWM. The same demon able to calculate RPM cooler. Data on the temperature, porosity and number of revolutions can be obtained from the console.
I tried more or less to describe the online help available on the key -h.
 
Legs please do not kick as programmer from me bad:D :D
 
https://github.com/StaLeWaR/OPi-Fan
 
Display in RPi-Monitor

So I flashed the latest nano pi (non-core) image:
 
root@nanopineo:~# dmesg | grep eth [ 0.000000] psci: probing for conduit method from DT. [ 4.313531] dwmac-sun8i 1c30000.ethernet: PTP uses main clock [ 4.313606] dwmac-sun8i 1c30000.ethernet: No regulator found [ 4.313782] dwmac-sun8i 1c30000.ethernet: Current syscon value is not the default 148000 (expect 58000) [ 4.313809] dwmac-sun8i 1c30000.ethernet: Chain mode enabled [ 4.313821] dwmac-sun8i 1c30000.ethernet: No HW DMA feature register supported [ 4.313832] dwmac-sun8i 1c30000.ethernet: Normal descriptors [ 4.313843] dwmac-sun8i 1c30000.ethernet: RX Checksum Offload Engine supported [ 4.313855] dwmac-sun8i 1c30000.ethernet: COE Type 2 [ 4.313865] dwmac-sun8i 1c30000.ethernet: TX Checksum insertion supported [ 4.314836] dwmac-sun8i 1c30000.ethernet: Found internal PHY node [ 4.315018] dwmac-sun8i 1c30000.ethernet: Switch mux to internal PHY [ 4.315031] dwmac-sun8i 1c30000.ethernet: Powering internal PHY [ 16.373120] dwmac-sun8i 1c30000.ethernet eth0: device MAC address 2a:18:44:a1:fb:f6 [ 16.383095] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 16.383114] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 16.383550] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 54.889366] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 54.889461] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready root@nanopineo:~#  
Difference is:
-the inbuild fast ethernet driver is enabled and worked.
-USB<>Serial was disabled and I had to SSH into the board to get my dmesg.

Given the simplicity of it, a ton of holes aren't really a problem.  This rearrangement of the "Lite" version puts a USB power where needed in case you have any "Y" adapter situations, leaves one in the original position to power either the touchscreen, provide power to the sbc the traditional way (probably not the greatest idea), or something completely unrelated (I powered a Tinker Board off of the USB on the power board while powering "Le Potato"). Thicker traces for power and an improved area around the header pins to reduce the drop there as well.
 
@JMCC's slots for cooling, we'll see if the fab gets mad about that.  ;-)
 

OMV is based on Debian. That's the simple reason it won't install on Ubuntu (dependency hell, different package versions). And if someone wants to run OMV I strongly recommend to check first whether there are available images at the download page or otherwise choose an Armbian Stretch next variant and then use armbian-config to install OMV.
 
Even if someone interested in NAS does not want to rely on OMV/Debian looking into the various performance tweaks we did is worth the efforts: https://forum.armbian.com/topic/3953-preview-generate-omv-images-for-sbc-with-armbian/?do=findComment&comment=44097
 
 
And for any NAS usage next kernel is strongly recommended since better hardware support (especially UAS support for USB storage).

I am doing some more research on this topic ... I'll update images when done.

Solved access to PA20 , I2S bus 0 pin for ver1.14.  Find U58 near antenna connector, open  pin 3 connection (Enable pin for Wlan). On the pad remain PA20 , DataOUT  for the I2S DAC. 
Connect IC U58 pin 3 to any 3.3Vcc. The Wlan will be powered continuously and DAC will be up and running. 
 

2 years ago I ordered a blue, red and yellow of these LEGO-cases along with (at this time) 3 new RPi3.
But if you want to change the board its hard to realese it out of the case and some part can break.
For underclocked RPis (and children) its a nice case.

This is a quick notes post for people that want to setup Armbian on AlfaWise H96 Pro+ eMMC and use it as a Headless Server for Docker Microservices
 
Thanks to @balbes150 @guidol and @Jeycop and all the awsome people of this forum
 
Tech stack used
 
Armbian
- Java 8
- Docker
- Spring Framework/Boot 2.0
- Node Js
- Aurelia Freamework
 
Download Files
 
- Android firmware (Optional, required in case of revert from eMMC flash)
 
- New H96 Pro Plus 7.1.2 firmware download By EBox
 
- Armbian Version
 
Armbian_5.41_S9xxx_Ubuntu_xenial_3.14.29_server_20180305.img
 
Flash SDCard or USBDisk
 
1) use rufus with dd, or linux disks, or dd command to flash above image
 
2) plug SDcard/Usb into Box
 
4) Plug power cable into Box while holding reset button pressed

Note:This step is only required if is the first time boot armbian after flash android firmware.....
 
5) See Armbian booting up
 
8) login with `un:root`, `pw:1234` and configure it
 
7) reboot
 
8) login with root
 
9) start "./install.sh" and wait for finish (5-7 minutes)
 
(WARNING above command flash eMMC, You Lost ANDROID, dont do that if you dont know how to recovery android firmware, or dont want to use eMMC, SKIP to step 14 for the setup with SdCard/Usb Only)
 
10) shutdown with `halt` and remove power cable
 
11) remove SDcard/Usb
 
12) plug power cable in Box, now you should see Armbian booting up without SDCard/Usb
 
13) login to catch ip or scan it with `sudo nmap -sS -p 22 192.168.1.0/24 | grep -a4 -b2 00:80:0F:96:E3:01`. Change to your mac and ip
 
14) SSH To it, and get some info
$ uname -a Linux amlogic 3.14.29 #114 SMP PREEMPT Mon Mar 5 12:57:46 MSK 2018 aarch64 aarch64 aarch64 GNU/Linux $ lscpu lscpu Architecture: aarch64 Byte Order: Little Endian CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 2 CPU max MHz: 1512.0000 CPU min MHz: 100.0000 Hypervisor vendor: (null) Virtualization type: full Setup WiFi with 3.14 Mali-6 Image Only (The Version that works with Wifi)
 
this required some hacked script to put it to work, lost a few hours to figure it, its not pretty but works after boot and its stable
 
First remove all modules from `/etc/modules` to leave it initialization for `init.d` script
$ cat /etc/modules #aml_nftl_dev Next Create a `init.d` hacked script, with some magic and optimized sleeps, without that sleep times or with lower times it wont work, Its very strange that I must load and unload module, and reload again, but its seems the only way to put this working, I know its too strange, and hard to find, maybe someone has a better ways, I belive with some knowledge its easy,
 
Why its working only that way, dont ask me why, I dont care, for me its not pretty, but its hugly and working, Im happy with it, who cares LOL, I dont waste more time for an elegant and pretty solution......
 
move on.....the `init.d` script
$ sudo nano /etc/init.d/wlan paste
#! /bin/sh # /etc/init.d/wlan # ### BEGIN INIT INFO # Provides: wlan # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: AlfaWise H96 Pro+ Wireless Boot Script # Description: This file should be used to construct scripts to be # placed in /etc/init.d. This example start a # single forking daemon capable of writing a pid # file. To get other behavoirs, implemend # do_start(), do_stop() or other functions to # override the defaults in /lib/init/init-d-script. ### END INIT INFO # Some things that run always touch /var/lock/wlan # Carry out specific functions when asked to by the system case "$1" in start) echo "Starting Wlan Script" echo "modprobe wlan" /sbin/modprobe wlan echo "modprobe wlan -r in 28sec..." sleep 28 /sbin/modprobe wlan -r echo "modprobe lan in 28sec..." sleep 28 echo "modprobe wlan..." /sbin/modprobe wlan ;; stop) echo "Stopping script wlan" /sbin/modprobe wlan -r ;; *) echo "Usage: /etc/init.d/wlan {start|stop}" exit 1 ;; esac exit 0 Install systemd service
$ sudo chmod 755 /etc/init.d/wlan $ sudo systemctl enable wlan Reboot
$ sudo reboot Configure wireless with nmtui
$ sudo nmtui $ ifconfig wlan wlan0 Link encap:Ethernet HWaddr 84:5d:d7:??:??:?? inet addr:192.168.1.177 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::865d:d7ff:fe4a:3202/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:15 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3246 (3.2 KB) TX bytes:1556 (1.5 KB) check configs saved from nmtui
$ ls /etc/NetworkManager/system-connections/ -la total 12 drwxr-xr-x 2 root root 4096 Mar 29 18:42 . drwxr-xr-x 8 root root 4096 Mar 5 10:24 .. -rw------- 1 root root 419 Mar 29 18:42 scWF_WDS1 $ sudo cat /etc/NetworkManager/system-connections/scWF_WDS1 > Note: If Problems arrise using WiFi, with/without eth0 cable, try disable eth0 with `sudo ifdown eth0`, sometimes the connection is linked somehow to ethernet to prevent this kinds of problems disable ethernet or boot without cable connected
$ sudo reboot After reboot inspect unload/load driver with
$ sudo tail -f /var/log/syslog | grep wlan Mar 29 18:42:25 localhost dnsmasq[4152]: using nameserver 192.168.1.10#53(via wlan0) Mar 29 18:42:25 localhost nm-dispatcher: req:1 'up' [wlan0]: new request (1 scripts) Mar 29 18:42:25 localhost nm-dispatcher: req:1 'up' [wlan0]: start running ordered scripts... Mar 29 18:42:28 localhost ntpd[3533]: Listen normally on 8 wlan0 192.168.1.177:123 In other PC ping the wifi IP and wait it responds without do anything, here it starts respond after 2:18 (with usb stick) minutes:seconds, not bad since reboot, shutdown and boot, and with time delays for wifi 
 
some info after login
$ cat /etc/modules #aml_nftl_dev $ lsmod Module Size Used by wlan 3435325 0 zram 8953 8 cfg80211 415017 1 wlan Update and Install Stuff
$ sudo apt update && sudo apt upgrade $ sudo apt install docker.io docker-compose samba openvpn lshw hwinfo $ docker -v Docker version 1.13.1, build 092cba3 $ docker-compose -v docker-compose version 1.8.0, build unknown Configure Samba
sudo cp /etc/samba/smb.conf /etc/samba/smb.conf_ORG sudo nano /etc/samba/smb.conf paste above
[users] comment = All users path = /home read only = No inherit acls = Yes veto files = /aquota.user/groups/shares/ [root] comment = Root path = / writable = yes printable = no write list = root browseable = no add a user
$ sudo smbpasswd -a USERNAME # start service $ sudo systemctl restart smbd # enable service $ sudo systemctl enable smbd.service Install Java 8 (Optional currently using Docker Containers, but it may be usefull for running quick prototype protects)
$ sudo -i $ sudo echo "deb http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main" | tee /etc/apt/sources.list.d/webupd8team-java.list $ sudo echo "deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main" | tee -a /etc/apt/sources.list.d/webupd8team-java.list $ sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys EEA14886 $ sudo apt-get update $ sudo apt-get install oracle-java8-installer #####Important######## To set Oracle JDK8 as default, install the "oracle-java8-set-default" package. E.g.: sudo apt install oracle-java8-set-default On Ubuntu systems, oracle-java8-set-default is most probably installed automatically with this package $ sudo apt install oracle-java8-set-default $ java -version java version "1.8.0_161" Java(TM) SE Runtime Environment (build 1.8.0_161-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.161-b12, mixed mode) Create docker-compose.yml to run and test my Spring-Boot IoT Project in Arm64v8 Arquitecture
 
Note: this step is ommited, it simply is a docker-compose file to test my IOT project, with four docker arm64v8 container microservices,
 
- Spring Boot Rest Api /Arm64V8
- Spring Boot Moquette/Mqtt Mongo Server with Auth and ACL
- Aurelia Framework / NodeJS WebApp / Mqtt.js Client / Chart.js
- Mongo DB
 
if someone like to test it with a ESP8266 tell me and paste here the docker-composer.yml 
 
move on
 
Backup Image
 
Use the DD command to create image of `/dev/boot` and `/dev/system`
  
Create a mount point to house images, using a samba share here to //192.168.1.1/root, one can use a spare disk or other media
$ sudo nano fstab add //192.168.1.1/root /mnt/koakhserver cifs username=${USER},password=${PASSWORD},_netdev,noauto 0 0 to the bottom
#/var/swap none swap sw 0 0 #/dev/root / auto noatime,errors=remount-ro 0 1 #proc /proc proc defaults 0 0 /dev/root / ext4 defaults,noatime,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 //192.168.1.1/root /mnt/koakhserver cifs username=${USER},password=${PASSWORD},_netdev,noauto 0 0 Backup eMMC
$ sudo mkdir /mnt/koakhserver -p $ sudo mount /mnt/koakhserver $ sudo dd if=/dev/boot of=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/boot.img bs=1024k status=progress 32+0 records in 32+0 records out 33554432 bytes (34 MB, 32 MiB) copied, 3.3319 s, 10.1 MB/s $ sudo dd if=/dev/system of=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/system.img bs=1024k status=progress 2146435072 bytes (2.1 GB, 2.0 GiB) copied, 150.027 s, 14.3 MB/s 2048+0 records in 2048+0 records out 2147483648 bytes (2.1 GB, 2.0 GiB) copied, 197.892 s, 10.9 MB/s when we need to restore use the reverse process
$ sudo mount /mnt/koakhserver/ $ sudo dd if=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/boot.img of=/dev/boot bs=1024k status=progress $ dd if=/mnt/koakhserver/mnt/1tbdisk2/devices/microcomputers/system.img of=/dev/system bs=1024k status=progress Done......I Think I dont forget nothing.....................
 
Thanks to all

In Python:
  o = open("/sys/class/gpio/export", "w"); o.write("198");  o.close()
  o = open("/sys/class/gpio/gpio198/direction", "w"); o.write("out"); o.close()
  o = open("/sys/class/gpio/gpio198/value", "w"); o.write("1"); o.close()
 

Hello everyone
 
I'm posting here what I did to run Armbian on a 4G LTE EM90 box. The image I'm using is armbian_5.37_S9xx_Debian_stretch_3.14.29_icewm_20171226. I extracted the dtb.img from the rooted android, I had to remove the beginning of the file to make it work. If you don't cut the file until you reach 0xD0 0D FE ED, you will get a magic number error when decompiling and Armbian will not boot with your fresh DTB.
 
WIFI :
The wifi is not well initialized at startup. You must precise to modprobe the firmware to load to AP6330 WIFI + BT4.0 chip
Create the file /etc/modprobe.d/options.conf and add the following line :
options dhd firmware_path=/lib/firmware/brcm/brcmfmac4330-sdio.bin nvram_path=/lib/firmware/brcm/nvram_ap6330.txt then open the file /etc/modules and add the following lines :
cfg80211 dhd I always have issues with DNS with Armbian, to solve this, i'm running these commands (with root privileges)  
echo "nameserver 8.8.8.8" > /etc/resolvconf/resolv.conf.d/base resolvconf -u Bluetooth :
With the DTB, the device shows up with hciconfig but scanning and connecting doesn't work. One more time it's a firmware issue, loading the correct one using patchram solves this problem.
Edit /etc/rc.local with the these lines :
brcm_patchram_plus --patchram /lib/firmware/brcm/BCM40183B2.hcd --enable_hci --bd_addr 11:22:33:44:55:66 --no2bytes --tosleep 1000 /dev/ttyS1 su -c 'hciattach /dev/ttyS1 any' exit 0 I haven't found the way to retrieve factory Bluetooth mac address, running the patchram command without the bd_addr option assign a different mac address witch is not the factory one. I would be interested if you know how to retrieve this address.
 
4G LTE modem :
The cellular modem works out of the box, you just have to put a sim card, install wvdial. I'm pasting a copy of my configuration file /etc/wvdial.conf for reference :
[Dialer Defaults] Init1 = ATZ Init2 = ATQ0 V1 E1 S0=0 Init3 = AT+CGDCONT=1,"IP","yourapnhere" Stupid Mode = true ISDN = 0 Modem Type = Analog Modem Password = " " New PPPD = yes Username = " " Phone = *99# Modem = /dev/ttyUSB0 Baud = 9600 The DTB and the configuration files can be found on my github repo.
 
I hope this information is helpful.

Image update Armbian 20180323 kernel 4.14.11 .
Works wired network, USB, monitor (you can change the screen resolution on the fly). The images are in the "test"directory.

thx foor the help.
 
now I can see the problem.
this command works echo "heartbeat" > /sys/class/leds/nanopi\:green\:pwr/trigger
however the RED power LED is now flashing on my NanoPi Neo Core 2.
 
When I use the echo "heartbeat" > /sys/class/leds/nanopi:blue:status/trigger nothing happens.
I think the Core 2 has some different LEDs at different Ports...
 
Andy
 
 

It's not a battery soldered on to that small module, it's a tiny supercapacitor

It's somewhat common decision by the developers. When:
 
- known critical problems are solved
- less critical are at least acknowledged and marked at the board download page
- not very much reported troubles on the forum
- if/when we can afford to provide end-user support. This part is getting more and more problematic due to large board count.
 
Even labeled experimental, they are usually in a (much) better shape than factory/stock ones. They just don't label it.

I have seen many tutorials about connecting real time clock hardware on Orange Pi and Raspberry Pi.
What i didn't like was removing of fake-hwclock service, because I want that RTC works when it is connected, and fake-hwclock when RTC is not connected.
Therefore, I changed /sbin/fake-hwclock script to work in this way.
 
So, here is how to do this, tested on OrangePi+2E, Armbian Ubuntu legacy kernel:
Purchase cheap DS3231 module on eBay (cca. $1) like this one:
http://www.ebay.com/itm/DS3231-AT24C32-IIC-Modul-High-Precision-Real-Time-Clock-Module-Arduino-New-/292041844936?hash=item43ff0ce8c8:g:d80AAOSwdGFYtsFP
Put battery in module.
Shutdown and powerof OPi and connect module:
Orange (i2c0 bus) RTC module (DS3231 RTC + 24C32 eeprom) 1 3.3V 2 VCC 3 PA12 (TWI0_SDA/DI_RX/PA_EINT12) 3 SDA 5 PA11 (TWI0_SCK/DI_TX/PA_EINT11) 4 SCL 9 GND 1 GND Power up OPi
Install i2c-tools.
sudo apt install i2c-tools Type command:
i2cdetect -y 0 You should see:
0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- 68 -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- This means that module is connected properly and that we have DS3231 on address 0x68 and eeprom 24C32 on address 0x57.
Type:
sudo echo ds1307 0x68 > /sys/class/i2c-adapter/i2c-0/new_device i2cdetect -y 0 You should see:
0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- 57 -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- This means that system is now using our RTC. Also, now should exist new device /dev/rtc1
Be sure that your system time is right, and type:
sudo hwclock -w -f /dev/rtc1 Now our RTC must have right time. Check with:
sudo hwclock -r -f /dev/rtc1 If everithing was ok, copy /sbin/fake-hwclock to bacup (just in case)
sudo cp ~/programming/sh/fake_hwclock/sbin/fake-hwclock /sbin/fake-hwclock Edit /sbin/fake-hwclock and place this code in it:
Reboot.
Now you should have right system time backed up by RTC.
 

you could try to create a script which does check the mounts and create a auto-mount in cron every minute if isnt mounted.
take a look here for commands:
https://serverfault.com/questions/50585/whats-the-best-way-to-check-if-a-volume-is-mounted-in-a-bash-script

I do not know if i understand this question the right way. After you have connected the DAC there are three soundcards
aplay -l will show us this:
root@orangepipc:~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: audiocodec [audiocodec], device 0: SUNXI-CODEC sndcodec-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: snddaudio [snddaudio], device 0: SUNXI-TDM0 snddaudio-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: sndhdmi [sndhdmi], device 0: SUNXI-HDMIAUDIO sndhdmi-0 [] Subdevices: 1/1 Subdevice #0: subdevice #0 In this case it is possible to access the i2s card with hw:1 or better  hw:snddaudio in your audio applications. (Be aware , that you can see this three cards even when only the Modules are loaded,[pcm0]
daudio_used = 1 is changed in the fex File and there is no Card connected)
 
Regards