guidol

tkaiser has built a new Kernel with i2s Modules. With this Kernel and some cheap DAC  e.g. (http://www.ebay.de/itm/Audiophonics-I2S-DAC-ES9023-Sabre-to-Analog-24bit-192KHZ-fur-Raspberry-PI-/291573327639?hash=item43e31fe717:g:TTwAAOSw~OdVZXtm)  it is possible to get good quality sound  out of the Orange Pis. After installing the Kernel
Two Things have to be changed in the fex File:
 
Change Directory to boot:
cd /boot Turn the script.bin to a fex-File and open it in an Editor
sudo bin2fex script.bin script.fex sudo nano script.fex Now change the following Entries:
[twi1] twi_used = 1 to
[twi1] twi_used = 0 and
[pcm0] daudio_used = 0 to
[pcm0] daudio_used = 1 Save your changes and do :
sudo fex2bin script.fex script.bin After a reboot your done.
 
 
I do not know for what the Section [twi1] is good for, i hope nothing serious..
This connections have to be made:
 
5V > Pin 2
Gnd > Pin6
BCK > Pin 27
LRCK > Pin 28
Data > Pin37
 
(according to the Picture "giachi" has posted on the diyaudio Forum http://www.diyaudio.com/forums/pc-based/285427-i2s-connection-orange-dac.html#post4587580
see below)
 
The second Picture is only for orientation on an Orangepi PC, the red Wire is 5V ! Be aware that the Header is rotated by 180°on the One!
 
That´s all .
 
Regards

Hi,
 
I have received my SCISHION V88 Piano and I can confirm that it boots to a Ubuntu Mate desktop from a micro SD-card with the image in the first post of this topic.
Like rob0809 I did nothing except insert the micro SD-card and power on
Unfortunately after running for a few minutes there were some I/O errors which I must investigate but this is perhaps due to my cheap (Ansonchina) SD-card.
 
I shall try other images and report back later.
 
Updates:
I tried this image:
https://github.com/ayufan-rock64/linux-build/releases/download/0.5.15/xenial-mate-rock64-0.5.15-136-arm64.img.xz
and it also booted directly but still with I/O errors.
I replaced the Ansonchina 8GB SD-card with a Kingston 8GB one and there were no more I/O errors
 
I tried the following images which also booted directly from the Kingston SD-card with no intervention:
http://dietpi.com/downloads/images/DietPi_Rock64-ARMv8-Stretch.7z
https://github.com/Raybuntu/LibreELEC.tv/releases/download/rb-leia23/LibreELEC-rock64.arm-rb-leia23.img.gz
https://github.com/ayufan-rock64/linux-build/releases/download/0.5.15/xenial-i3-rock64-0.5.15-136-arm64.img.xz
 
Most of these images require an external USB Ethernet adapter (internal Ethernet and WiFi don't seem to be supported).
They also run much more slowly than I had expected. Unfortunately I don't think that this is just due to a lack of hardware graphics acceleration  
But this is just a start and at least they do run
 
Later update:
I found an easy hack to greatly speed up simple operations not involving heavy video or graphics.
(Due to the lack of hardware acceleration, YouTube videos, for example, still play frame by frame.)
I copied exactly the same disk image to both a micro SD-card and to a USB 3.0 storage device.
I modified the label on the root partition of the SD-card so that it would use the USB disk as the rootfs instead.
On most of these images the rootfs is labelled linux-root on partition 7.
I used gparted to change the SD-card's partition 7 label to linux-rootX so that it would pick up the partition on the USB drive instead.
 
I also used parted to correct for the size of both the devices and to increase the size of the root partition on the USB drive. However this is not strictly necessary.
As a stability test and a realistic benchmark, I compiled natively the recent mainline v4.15 Linux kernel: "make defconfig && make -j 4 Image" finished successfully in slightly under 100 minutes.
This is not too bad for a box costing about $40.
 
Even later update:
The best Ubuntu image that I have found is this one:
https://dl.armbian.com/rock64/Ubuntu_xenial_default_nightly.7z
This currently redirects to:
https://dl.armbian.com/rock64/nightly/Armbian_5.34.171121_Rock64_Ubuntu_xenial_default_4.4.77.7z
There is only one single partition so I had to:
'- copy the image to a USB storage device
- resize the partition
- add the label linux-root
- copy the appropriate files from the boot directory of this partition to replace the dtb, Image and initrd.img files on the boot partition of the SD-card I used previously
- ensure that there is no partition labeled linux-root on the SD-card
- after booting I installed ubuntu-mate-desktop but this is obviously not mandatory
The advantages of this image are:
- it will find the linux-root partition even if the USB storage device is on a hub (otherwise the USB drive monopolizes the USB 3.0 port)
- YouTube video (nearly) works so there must be some hardware acceleration
Unfortunately the video freezes from time to time. This doesn't seem to be due to a slow Internet connection.
With this image the compilation time for the same kernel dropped to 72 minutes.
 
I also tried this image but it did not seem to boot (at least there was only a blank screen on HDMI).
https://github.com/ayufan-rock64/linux-build/releases/download/0.6.19/bionic-minimal-rock64-0.6.19-181-arm64.img.xz
Maybe it is headless so I shall try again to ssh into it.
(Or to login via a serial console but I have not yet needed to open the case.)
 
Cheers,
Chris

Ayufan’s Armbian on a V88 Piano or V88 Mini III
 
These two TV boxes seem to be electrically identical except that the V88 Mini III has 2 GB RAM and 8 GB ROM whereas the V88 Piano has 4 GB RAM and 16 GB ROM.
They use the same PCB as can be seen from the photos in these FreakTab topics:-
- http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/681869-scishion-v88-piano-tv-box-rk3328-4gb-ram-16gb-rom-android-7-1-usb-3-0-fast-lan
- http://freaktab.com/forum/tv-player-support/rockchip-based-tv-players/rk3328-devices/663248-scishion-v88-mini-iii-tv-box-rk3328-2-8gb-2-4-wifi-fast-lan
 
I do not have a V88 Mini III to test but I believe that my results for the V88 Piano should also be relevant to it.
 
N.B. many sites claim that the V88 Piano has Gigabit Ethernet (1000 Mbps). It does not: it only has Fast Ethernet (100 Mbps) like the V88 Mini III.
 
One nice thing about these TV boxes is that, unlike many others, they will boot easily from a micro-SD card.
Just insert the card and power on
 
My aim was to have Ubuntu running with all version-specific partitions (boot and root) on a USB drive.
I wanted to keep Android in the internal eMMC so that I could dual-boot by just inserting or removing the micro-SD card.
 
I wanted to have the root partition on a USB stick for three reasons:
1) A good USB stick is faster than a micro-SD card.
2) This avoids the system writing repeatedly to the micro-SD card because, if the root partition is on the micro-SD card, after a while it gets corrupted and will no longer boot. This happened to me with both a cheap Ansonchina card and also with a Kingston card. Maybe the write timings in the micro-SD card driver are incorrect.
3) Whilst experimenting on Amlogic boxes I have fried two big micro-SD cards. I have read that others have fried cards on Rockchip boxes. Moving the rootfs to a USB stick enables me to use a smaller and cheaper card.
(I suspect that they were destroyed by over-voltage due to a badly programmed regulator. With a 5 V USB stick and a 5 V PSU there should be no risk as I don’t think the regulators used can step up the voltage.)
 
I also wanted the boot partition to be on the USB stick so that I could have several GNU/Linux distributions on different USB sticks and boot with the same unmodified micro-SD card containing just the boot loaders.
 
I have deliberately avoided the necessity to have a Linux (or even Windows) PC.
 
N.B. the Ubuntu system will not (yet) have working Wi-Fi.
 
You will need:-
- a rooted V88 Piano (mine was sold pre-rooted)
- a micro-SD card: mine was 8 GB but 4 GB should suffice
- a USB Flash Drive: I have used both 32 GB and 8 GB but 4 GB may suffice for a fairly minimal system
- a USB keyboard (and mouse if installing a desktop): I used a wireless mini-keyboard/mouse
- a wired (RJ45) Ethernet connection with DHCP and Internet access
- an HDMI display
 
WARNING: before using a /dev/ or /dev/block device verify that you are using the correct one, using dmesg for instance. Otherwise you could overwrite precious data.
However if you remove all additional USB drives the names below should be correct.
 
The login is rock64 with password rock64 which is also required for sudo.
 
First step – install Ayfan’s Ubuntu Xenial Minimal 0.5.15 on a micro-SD card and prepare 0.6.25 on a USB stick.
 
Boot Android.
 
I installed and used Google Chrome for the following downloads because, with the stock Lightning browser, I couldn’t see when the download had finished.
(The busybox wget can't be used because it doesn’t support https.)
 
Open https://github.com/ayufan-rock64/linux-build/releases/tag/0.5.15 in the browser.
Download xenial-minimal-rock64-0.5.15-136-arm64.img.xz
 
If you wish to pass directly to Ubuntu Bionic you could use the Bionic 0.6.25 image instead of Xenial below.
However this may make it more difficult to update U-Boot later as I think a Xenial environment is expected to compile it.
Open https://github.com/ayufan-rock64/linux-build/releases/tag/0.6.25 in the browser.
Download xenial-minimal-rock64-0.6.25-193-arm64.img.xz

Insert the micro-SD card and the USB stick.
N.B. all existing files on both will be destroyed.
You will be asked how to use the USB stick: choose "removable storage" and "cancel" if asked whether to format it.
 
Execute the following actions and commands (in the text following the $ or #).
 
Install and start ConnectBot.
 
Open a local shell.
Become root.
$ su
 
Enter the directory where browsers save downloaded files.
# cd /sdcard/Download
 
Decompress the files.
# busybox xz -d xenial-minimal-rock64-0.5.15-136-arm64.img.xz
# busybox xz -d xenial-minimal-rock64-0.6.25-193-arm64.img.xz
 
Write the 0.6.25 image to the USB stick.
# dd if=xenial-minimal-rock64-0.6.25-193-arm64.img of=/dev/block/sda bs=1048576
 
Write the 0.5.15 image to the micro-SD card.
# dd if=xenial-minimal-rock64-0.5.15-136-arm64.img of=/dev/block/mmcblk1 bs=1048576
 
Ensure everything is written.
# sync
 
Power off the box.

Second step – boot Ayfan’s Ubuntu Xenial Minimal 0.5.15 and prepare the switch to 0.6.25 on the USB stick.
 
Insert the micro-SD card.
Boot and login (rock64/rock64).
 
Become root.
$ sudo -s
 
Remove partitions 6 (boot) and 7 (root) from the micro-SD card so that U-Boot and Linux will use the ones on the USB stick next time.
Luckily this only deletes their entries so Linux can continue to use them until they are unmounted.
Reply "Yes" and "Ignore" to the warnings.
# parted /dev/mmcblk1
rm 6
rm 7
q
 
# poweroff

Third step - boot Ayfan’s Ubuntu Xenial Minimal 0.6.25 from the boot and root partitions on the USB stick and prepare to update to a recent version.
 
Insert the USB stick in the middle USB slot and insert the micro-SD card.
Boot and login.
$ sudo -s
 
This DHCP configuration will be necessary for Bionic.
# cd /etc/network/interfaces.d
# sed s/eth0/eth1/ eth0 > eth1
 
At the time of writing there are only pre-release versions of 0.6.x but Ayufan has promised an official release shortly after the official release of Bionic due on 24th April.
If, in addition to Ubuntu updates,  you want to update to Auyufan's pre-release versions with an added risk of instability then:
# vi /etc/apt/sources.list.d/ayufan-rock64.list
Uncomment the last line
 
# apt update
 
The following lines are necessary if you update to a more recent Ayufan version which will disable eth1:
This is needed to re-enable eth1:
# apt install device-tree-compiler
Make rc.local enable eth1 which is disabled in recent versions and disable eth0 which is not used on the V88 Piano:
# vi /etc/rc.local
Add these two lines just before the last line (exit 0):
enable_dtoverlay eth1 ethernet@ff550000 okay
enable_dtoverlay eth0 ethernet@ff540000 disabled
 
# apt dist-upgrade -y
 
If you want a Mate desktop you can:
# install_desktop.sh mate
 
This gave me an error which I corrected with:
# apt -f install
 
If you wish you can also upgrade from Xenial to Bionic with do-release-upgrade.
 
# reboot
 
You should now be running an up-to-date version with the boot and root partitions on the USB stick.

The next step will be to compile and install a more recent U-Boot supporting the USB 3.0 port correctly.
To be continued...

The procedure above may seem convoluted so here are some additional explanations.
0.5.15 is used for its boot loaders as it is the latest version which will boot directly from a micro-SD card. Unfortunately it does not have working Ethernet and its U-Boot will not load correctly from the USB 3.0 slot.
0.6.25 is used because it has working Ethernet to install device-tree-compiler which is needed to re-enable eth1 on recent versions.

I'm starting to regret that we added it in the past, and we need something that works reliably regardless of the daily log size. I have some thoughts, but different ideas have different requirements and expected reliability issues, and anything requires extensive tests.

Did you build your kernel with the armbian build system? Like this:
# git clone --depth 1 https://github.com/armbian/build # cd build # ./compile.sh BOARD=sunvell-r69 Use the <NEXT> kernel. There have been changes recently to DRAM timing which have increased stability.
To transfer the OS from SD-Card to eMMC use $sudo armbian-config. There is an option in the "Systems"-menu to transfer the OS to the internal eMMC.

What I did:
Download: Armbian_5.38_Orangepizero_Debian_stretch_next_4.14.14.img
from https://dl.armbian.com/orangepizero/ Debian_stretch_next.7z
Ubpack with 7zip
Write Armbian_5.38_Orangepizero_Debian_stretch_next_4.14.14.img with Win32 Disk Imager on SD-Card
Connect the OPi Ziro with mein network via Eternet.
Plug in the SD-Card
Connect the powersupply
Waiting a wihle and look in my router for the IP of the OPi zero
First try connect witch WinSCP. User root pass 1234.
the OPi disconnect the session
then start a session via with WinSCP binded Putty (start Putty itselfe)
Type root type 1234 in Putty
following the instructions and OPi reboot.
After a wihle an connect with the new Password via WinSCP is posibel.
Now I can work with WinSCP and the linked Putty-client how used
Now in Putty
apt-get update
apt-get upgade
reboot
armbian-config
->System->Hardware->[space]analog-codec->Save->cancel->cancel->cancel
reboot
testing audio
alsamixer (checking Line-Out)
apt-get install mplayer2
mplayer http://hr-hr3-live.cast.addradio.de/hr/hr3/live/mp3/128/stream.mp3
Yahr an audiosignal on Line Out appers
armbian-config
->Network->wlan0->WiFi->OK
Setup my WiFi->Quit->cancel->cancel theirby the WiFi IP will be shown.
reboot
Unplug ethernetcabel imidetly.
Waitig a wihle
reconnect WinSCP via WiFi IP
open Putty via WinSCP
mplayer http://hr-hr3-live.cast.addradio.de/hr/hr3/live/mp3/128/stream.mp3
It runns. :-)

I just got my board and I'll try to make Armbian ASAP. 

Another pcs of info -  when running 
./cpuminer --benchmark I get a 0.9A draw at the power source. Nothing else except console is attached.

Solved it, I was using Debian Jessie, switched to Ubuntu Xenial and everything worked with no problem. Seems the software Debian Jessie distro uses is too old or incompatible. 

Tinkerboard Onboard audio is now available out of the box for build-it-yourself enthusiasts on default kernel.  New image should be ready in the following days.

Work driver is here https://github.com/SkyRocknRoll/CH341SER_LINUX 
Thanks the all.

Look for links with "default" in the name ...

https://github.com/armbian/build/commit/f6402803c261b7a683eeb091f62a684bfd1ef8e8
https://github.com/armbian/build/commit/518ef98107a6705ba6649acdb1481cafedc9766d

Software support is not fast food.

Yes VCC is 5 or 3.3V but you dont need VCC because the USB-Dongle and the mainboard/pc has its own power
You can connect the cable as written in the Picture (RX<->TX, TX<->RX, GND<->GND)
On some other USB-Dongles it could be to connect RX<->RX and TX<->TX - but mostly not

Thanks for the instrutions - they did help me very much with the AP6330 onboard WiFi of the Sunvell T95K Pro
(S912 device = q201_6255):

Manually:
 
modprobe cfg80211 modprobe dhd firmware_path=/lib/firmware/brcm/fw_bcm40183b2.bin nvram_path=/lib/firmware/brcm/nvram_ap6330.txt On boot:
 
# /etc/modules cfg80211 dhd # /etc/modprobe.d/options.conf options dhd firmware_path=/lib/firmware/brcm/fw_bcm40183b2.bin nvram_path=/lib/firmware/brcm/nvram_ap6330.txt lsmod:
root@sunvell-t95kpro:~# lsmod Module Size Used by brcmfmac 171742 0 brcmutil 5091 1 brcmfmac joydev 10336 0 dhd 817295 0 cfg80211 415017 2 dhd,brcmfmac aml_nftl_dev 95108 0  
Now the WiFi does run very stable and without any big latency

Before I had used an external USB-WiFi Dongle from Edimax where I had a high latency
(and I did disable power-management in the /etc/network/interfaces) 
 

Turning off the GPU/HDMI is only for power consumption and some more memory and not for heat. I use SSH so HDMI is not needed on my PiOne.

With the old Jessie Armbian Pi-hole works without any problem. And I also implemented a 1 CPU core and low DRAM clockspeed during the night (as a some Linux learning on the job).
See running-h3-boards-with-minimal-consumption

For now I left the H3consumption program behind me.

select ubuntu/stretch and desktop-variant from here:
https://yadi.sk/d/pHxaRAs-tZiei/mali-6/5.41

Well - the LEDs are not statically defined, because you can define their usage by yourself - and the OS can have another default funtion like on a other OS (Orange Pi original Linux <--> armbian)
 
Your could find the available LEDs here:
root@pihole:~# ls -l /sys/class/leds
total 0
lrwxrwxrwx 1 root root 0 Jan  1  1970 green_led -> ../../devices/platform/leds-gpio/leds/green_led
lrwxrwxrwx 1 root root 0 Jan  1  1970 red_led -> ../../devices/platform/leds-gpio/leds/red_led
 
and which function is assigned to the LED you could find out while do a "more" an their trigger-file:
root@pihole:~# more /sys/class/leds/red_led/trigger
none mmc0 mmc1 timer [heartbeat] backlight default-on
 
here you could see I assigned the funtion [heartbeat] to the red LED
 
I did this in the /etc/rc.local with the following command (before the line with "exit 0") :
echo "heartbeat" > /sys/class/leds/red_led/trigger
 
heartbeat is this flashing LED - showing the system is running
 
mmc0 will be like a HDD-LED for your uSD-Card:
echo "mmc0" > /sys/class/leds/green_led/trigger
 
The names of your LEDs may varies.
 

Es ist in Februar bistimmt ganz angenehm da am Bosporus. Bin selbst aus den USA aber seit 11 Jahre hier in Babylon.

Mine DID boot without a dtb.img! (but didnt with the wrong .dtb)
But I think - that I did read - that the system does try to use the right dtb by itself

Mine DID boot without a dtb.img! (but didnt with the wrong .dtb)
But I think - that I did read - that the system does try to use the right dtb by itself

WiFi is now working on GT1.   1. Download & Copy AP6255 WiFi drivers extracted from Beelink's Android image: https://dl.dropboxusercontent.com/u/11164079/GT1/wifi.tar.gz   2. Load WiFi kernel modules   2.1. Manually modprobe cfg80211 modprobe dhd firmware_path=/lib/firmware/ap6255/fw_bcm43455c0_ag.bin nvram_path=/lib/firmware/ap6255/nvram.txt 2.2. On boot
# /etc/modules cfg80211 dhd # /etc/modprobe.d/options.conf options dhd firmware_path=/lib/firmware/ap6255/fw_bcm43455c0_ag.bin nvram_path=/lib/firmware/ap6255/nvram.txt SCAN
root@amlogic-s905x:~# iwlist wlan0 scan wlan0     Scan completed :           Cell 01 - Address: XX:54:XX:FA:C8:XX                     ESSID:"SSID_NAME"                     Mode:Managed Connect to SSID with nmcli
nmcli dev wifi connect NETWORK_SSID password NETWORK_PASSWD DMESG
              dhd_bus_devreset: == WLAN ON == [  149.800463] F1 signature read @0x18000000=0x15264345 [  149.806417] F1 signature OK, socitype:0x1 chip:0x4345 rev:0x6 pkg:0x2 [  149.807102] DHD: dongle ram size is set to 819200(orig 819200) at 0x198000 [  149.807543] dhd_conf_read_config: kso_enable = 0 [  149.807633] dhd_conf_set_fw_name_by_chip: firmware_path=/lib/firmware/ap6255/fw_bcm43455c0_ag.bin [  149.807641] dhdsdio_download_firmware: set use_rxchain 0 [  149.807647] dhdsdio_download_firmware: set txglomsize 40 [  149.807653] sdioh_set_mode: set txglom_mode to multi-desc [  149.807659] Final fw_path=/lib/firmware/ap6255/fw_bcm43455c0_ag.bin [  149.807664] Final nv_path=/lib/firmware/ap6255/nvram.txt [  149.807669] Final conf_path=/lib/firmware/ap6255/config.txt [  149.861058] NVRAM version: AP6255_NVRAM_V1.0_29052015 [  149.861683] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded. [  149.939601] dhd_bus_init: enable 0x06, ready 0x06 (waited 0us) [  149.939765] bcmsdh_oob_intr_register: Enter [  149.939769] bcmsdh_oob_intr_register: HW_OOB enabled [  149.939773] bcmsdh_oob_intr_register OOB irq=100 flags=414 [  149.939802] bcmsdh_oob_intr_register: enable_irq_wake [  149.939808] bcmsdh_oob_intr_register: enable_irq_wake failed with -6 [  149.940733] dhd_conf_set_fw_int_cmd: set WLC_SET_BAND 142 0 [  149.941361] dhd_preinit_ioctls: Set tcpack_sup_mode 0 [  149.943237] Firmware up: op_mode=0x0005, MAC=44:2c:05:4b:5b:49 [  149.943243] dhd_conf_set_country: set country ALL, revision 38 [  149.943248] dhd_conf_set_fw_string_struct_cmd: set country [  149.943581] CONFIG-ERROR) dhd_conf_set_fw_string_struct_cmd: country setting failed -2 [  149.947523] Country code: US (US/0) [  149.947863] dhd_conf_set_fw_string_cmd: set roam_off 1 [  149.949492] dhd_conf_set_fw_string_cmd: set txbf 1 [  149.949947] CONFIG-ERROR) dhd_conf_set_fw_string_cmd: txbf setting failed -23 [  149.959389] Firmware version = wl0: Aug 25 2015 18:58:57 version 7.45.69 (r581703) FWID 01-24037f6e [  149.959398]   Driver: 1.201.59.6 (r506368)                  Firmware: wl0: Aug 25 2015 18:58:57 version 7.45.69 (r581703) FWID 01-24037f6e [  149.959611] dhd_txglom_enable: enable 1 [  149.959616] dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0 [  149.959620] dhd_conf_set_txglom_params: txglom_bucket_size=0 [  149.959624] dhd_conf_set_txglom_params: txglomsize=40, deferred_tx_len=40, bus_txglom=0 [  149.959628] dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0 [  149.959632] dhd_conf_set_disable_proptx: set disable_proptx 0 [  149.960335] dhd_wlfc_hostreorder_init(): successful bdcv2 tlv signaling, 64 [  149.960826] wl_android_wifi_on: Success [  150.018061] dhd_open: Exit ret=0 [  150.140579] P2P interface registered [  150.153519] WLC_E_IF: NO_IF set, event Ignored [  150.154635] P2P interface started [  182.422348] dhd_module_cleanup: Enter [  182.422393] sdioh_remove: Enter [  182.422398] dhdsdio_disconnect : no mutex held. set lock [  182.430336] dhdsdio_dpc: Bus down, ret [  182.430350] bcmsdh_oob_intr_unregister: Enter [  182.430364] dhd_wlfc_deinit():3301, Already disabled! [  182.490019] dhd_stop: Enter ffffffc05119b000 [  182.490026] wl_android_wifi_off in 1 [  182.490030] wl_android_wifi_off in 2: g_wifi_on=1 [  182.490036] dhd_prot_ioctl : bus is down. we have nothing to do [  182.490118] bcmsdh_oob_intr_unregister: Enter [  182.490128] bcmsdh_oob_intr_unregister: irq is not registered [  182.490143] dhd_txglom_enable: enable 0 [  182.490150] dhd_conf_set_txglom_params: swtxglom=0, txglom_ext=0 [  182.490156] dhd_conf_set_txglom_params: txglom_bucket_size=0 [  182.490162] dhd_conf_set_txglom_params: txglomsize=0, deferred_tx_len=0, bus_txglom=0 [  182.490168] dhd_conf_set_txglom_params: tx_in_rx=1, tx_max_offset=0 [  182.490175] dhd_bus_devreset:  WLAN OFF DONE [  182.490240] wifi_platform_set_power = 0 [  182.490247] ======== PULL WL_REG_ON LOW! ======== [  182.490252] wl_android_wifi_off out [  182.490258] dhd_stop: Exit [  182.570103] dhd_detach(): thread:dhd_watchdog_thread:ee1 terminated OK [  182.570165] dhd_detach(): thread:dhd_rxf:ee3 terminated OK [  182.570188] dhd_dpc_thread: Unexpected up_cnt 0 [  182.570211] dhd_detach(): thread:dhd_dpc:ee2 terminated OK [  182.571711] P2P interface unregistered [  182.571746] wl_event_handler: was terminated [  182.571944] wl_destroy_event_handler(): thread:wl_event_handler:ee0 terminated OK [  182.799988] dhd_tcpack_suppress_set 376: already set to 0 [  182.800006] dhd_os_prealloc: failed to alloc memory, section: 7, size: 0bytes [  182.800031] dhdsdio_disconnect : the lock is released. [  182.800275] unregister wifi platform drivers [  182.800283] wifi_platform_bus_enumerate device present 0 [  182.800289] ======== Card detection to remove SDIO card! ======== [  182.800315] aml_wifi wifi.33: [extern_wifi_set_enable] WIFI  Disable! 240 [  183.000404] dhd_module_cleanup: Exit

normally a blinking led should show that the system has bootet (heartbeat led).
Maybe you could try to use etcher for Linux or Windows to create the bootable sd-card?
https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card

before reboot /etc/network/interfaces will be active.
Configure via nmtui and set it active at boot, then save and reboot  - this wil activate the connection

Kernel for H3/H5 and A20/A10 has been updated and pushed to the repository. I made 24h severe burn-in testings with three boards: Cubietruck, Orangepi 2E and Orangepi Prime. I did nasty things to them and all are still running.

I did learn much here in the forum from "one to many" teaching or while reading problems and solutions of other boards/users.
Mostly I could solve my problems while reading other post, just because its all armbian and it all board are arm-style

The best for @jiapei100 will also to read a while in differnt threads and the armbian documentation - there are so many answers to questions.
You could learn much from many users here - and maybe later someone from you - if you could faster answer to more easy questions.

And if the armbian-forum isnt enough, then there are the forums of the board-manufacturers or the Facebook-Groups for this board