guidol

Probably because it is still .wip and packages are made only for .conf ... not 100% sure but possible. 

new version v5.60 20180922.
 

Since I got rid of network manager (configured in old good way) my SBC connection is rock solid. Network Manager is not reliable somehow...

The main repository was updated to 5.60 at this moment. 

Fixed with this commit for NEXT, stable builds. DEV (4.18.y) has other problems and there is no rush to fix it there,
https://github.com/armbian/build/commit/acf84bac596c6110d87f7e92389ecd05fb42ce64
 
Images at the download section were also fixed.

DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware.
Please don't ask about support or assistance in other non-community forums nor in the official Armbian github repository, instead post your questions in this thread, in the TV Boxes forum section (hardware related) or in the Peer-to-peer support section (general linux/software related).
Thank you!
 
This is CSC Armbian for XT-Q8L-V10 boards, also known as Chiptrip Q8, Vsmart Q8, ENY 3288 Q8, etc...
 

 
All source code has been merged into Armbian mainline project.
I still keep my personal public Armbian fork for experimental features: https://github.com/paolosabatino/armbian-build
 
Nightly images: download directory
 
Quick installation instructions on eMMC:
Build or download your preferred Armbian image from Download directory and a copy of the Multitool; Burn the Multitool on an SD card; once done, place the Armbian image in images folder of the SD card NTFS partition; Plug the SD card in the TV box and plug in the power cord. After some seconds the blue led starts blinking and the Multitool appears; OPTIONAL: you can do a backup of the existing firmware with "Backup flash" menu option; Choose "Burn image to flash" from the menu, then select the destination device (usually mmcblk2) and the image to burn; Wait for the process to complete, then choose "Shutdown" from main menu; Unplug the sd card, then push the power button for 1 second (the led will turn blue) After 10 seconds HDMI will turn on and you will get logging messages; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed!  
Boot from SD Card/USB stick (with Armbian already installed in eMMC, empty eMMC or no eMMC😞
Build or download your preferred Armbian image from Download directory; Burn the image on your SD card/USB stick; Plug the SD card/USB stick in the device; Push the power button for 1 second (the led will turn blue); After 10 seconds HDMI will turn on and you will get logging messages; On first boot you will be asked for entering a password for root user of your choice and the name and password for a regular user Run armbian-config to configure timezone, locales and other personal options Congratulations, Armbian is now installed!  
Boot from SD Card/USB stick (with original firmware or other firmware):
In case your box has the original firmware installed, use the Multitool to erase the internal flash.
Don't worry, you will not brick your box: once the eMMC is emptied, the box will automatically boot from SD Card. This is called Maskrom mode and is common to all Rockchip devices. Instructions and download links for the Multitool are at the bottom of this post.
After erasing the internal eMMC, just follow the "Boot from SD Card" procedure above and then you are fine.
 
Boot priority:
Newer images (those with mainline kernel >= 4.14.50) now support booting from multiple devices.
Priority is fixed and boot devices are probed in this order:
 
External SD card External USB storage device (Any USB Stick/Hard drive attached to USB host ports) Internal eMMC  
This way even if you install armbian to internal eMMC, you can still easily test different images booting from external devices.
Experts notes: when armbian is installed into eMMC you get U-boot installed too in eMMC. This is important to know because the box won't boot in Maskrom Mode, but instead will always boot the embedded U-boot, no matter if you put an sdcard/usb stick. In practice the embedded U-boot is totally responsible for the boot priority. If you want to restore the Maskrom Mode, just erase U-boot from eMMC using this command:
dd if=/dev/zero of=/dev/mmcblk2 seek=64 count=8128 conv=sync,fsync  
Current status:
Wireless: works. pretty fast and stable, signal is strong on my box; Bluetooth: works. I was able to transfer files and stream audio without problems USB ports: works, with autosuspend too. A quick benchmark show that transfer rate is quite good (topped at 34 MB/s) USB OTG: works in host mode. Transfer rate is very good (> 40 MB/s) MMC: works and is perfectly accessible as storage device. The images above with "eMMC friendly" have been tested and work when installed in eMMC using the standard armbian-config eMMC installer SDCard: works. legacy kernel is limited to high speed, while mainline works fine in UHS mode too. A quick benchmark with a Samsung EVO card shows the promised 48Mb/s read speed. Gigabit Ethernet: works, fast and reliably HDMI: works perfectly Serial: works Audio: both HDMI audio and SPDIF connector works IR remote: works on legacy and mainline kernels Reboot/Suspend process: rebooting the device is a working in progress, at the moment sometimes it works and sometimes it doesn't. Suspend is still not available. Hardware acceleration: everything which works for rk3288 boards applies here too. This guide or maybe the Media Testing Script will help you gain an hardware accelerated X11 and Chromium (using GL4ES I enjoyed Quake 2 from the start till the end, but also Quake and Quake III Arena work flawlessy, here a quick how-to to compile and install GL4ES)  
Multimedia:
On mainline kernel 3D acceleration is provided by Panfrost driver and is already enabled.
Hardware video decoding: https://forum.armbian.com/topic/19258-testing-hardware-video-decoding-rockchip-allwinner/
 
Multitool:
The Multitool is a small but powerful tool to easy operate on internal eMMC flash of RK3288 devices.
 
Features:
Backup the content of internal eMMC Restore a previously backed-up image to eMMC Erase the eMMC (via fast blkdiscard or zero-fill as fallback) Burn an Armbian (or LibreELEC) image directly on the eMMC Provide a recovery shell for manual maintenance Windows-friendly: everything is placed in a NTFS partition Image compression format autodetection: they are decompressed on-the-fly during burn process Network support for remote maintenance via SSH (instructions to access via network here)  
Instructions are simple:
Download the image from here Burn it on an sdcard Open the NTFS partition with your preferred file manager Place the images you want to burn on the device in images directory (backups will be stored in backups directory) Plug the sd card in the RK3288 device Power the device and wait few seconds, the Multitool menu will appear on screen and can be navigated with the keyboard  
Last edit: 07/06/2020 - updated installation instructions
 

in short:
https://www.cnx-software.com/2018/09/11/sunvell-h3-allwinner-h3-tv-box-2gb-ram/

Thank you a LOT!
You help me very much!
I'll study this

-

@Igor I fixed this by using armbian-config, clearing interfaces and using /etc/network/interfaces. Now I can reboot with a static address. With NanoPi Duo I had to remove netplan and use ifupdown for eth0, but the xradio wifi stuff seems to be missing from the kernel (modules, etc.). But in essence they exhibited the same issue with eth0.

I got Mainline 4.18.5 working on BPi-M2-Ultra, but without on-board Wifi.
 

Thanks for the fast reply.
 
This morning I could test it, with the older kernel 1-wire is working.
 
thanks

Hallo Guido,  I just burned for the tinker board K4.14 and now K4.4, it works like a charm   it wrote that it writes with up to 34MB/second on the Samsung EVO Plus 32, can you ask for more?
As my device is 'young' compared to yours I already have the latest firmware on it.  Vielen Dank für den Tipp, Tido
 

https://github.com/armbian/documentation/blob/master/docs/Release_Changelog.md (please add what you think I forgot and is relevant to mention, up to 6 months back)
all images were rebuilt, except boards which support ended, and with a few exceptions which are still in the works (Tinkerboard, MiQi and perhaps we can move T4/RockPRO to the stable) and will be added probably next week. I already test a few and so far I couldn't find troubles. I record them here: https://github.com/armbian/testings. The result is displayed in this https://beta.armbian.com/buildlogs/report.html table and when it is filled up, an update to the main repository on all images can be rolled out.

virtual USB2-port

I have a Custom SOM with A40i because we change from R40 to this core and the kernel that I use is 4.14 Stable or development on 4.18... and itś working ok... I don't change anything to run kernel on A40i because is the same (pin to pin compatible) with R40...

OK - I have requested the boot log:

Guido Imran Lehwalder:
Lion Wang If you got an example of the board with A40i would it be possible to get a bootlog of armbian with kernel 4.18.y from this A40i device?
This would much help for working on armbian for the A40i version of the board ;)
And maybe if you logged in in armbian also a the info from:
armbianmonior -u

Lion Wang:
Guido Imran Lehwalder Ok ,i will let my R&D ( Research and development ) do this work ,thank you.
i see armbian have a beta image for Ultra and berry .
 
I also doubled the request in their forum.
 

By comparing https://github.com/friendlyarm/linux/blob/sunxi-4.14.y/arch/arm/boot/dts/sun8i-h3-nanopi-duo2.dts and https://github.com/friendlyarm/linux/blob/sunxi-4.14.y/arch/arm/boot/dts/sun8i-h2-plus-nanopi-duo.dts the only real difference is replacing the crappy XR819 Wi-Fi with RTL8189 (the other change being H2+ being replaced by H3)
 
NanoPi Hero also features RTL8189 Wi-Fi, is limited to Fast Ethernet and has an I2C accessible voltage regulator allowing the board to clock at up to 1368 MHz (at 1.4V VDD_CPUX): https://github.com/friendlyarm/linux/blob/sunxi-4.14.y/arch/arm/boot/dts/sun8i-h3-nanopi-hero.dts
 
Maybe @mindee is so kind to provide an early picture of the latter?

Mikey from Sinovoip showed me some photos on kernel logs that is said to be booting A40i with mainline U-Boot.
 
(Of course this makes no difference as mainline U-Boot doesn't try to recognize the print on the chip ;-) )

there a good chances, because the BPI M2 Ultra and the M2 Berry do share the same download section at
http://www.banana-pi.org/downloadall.html

 
I will test it - because I got the Berry here

Take a look at the first post at this page (thread page 4, post from 5kft at July 29):
 
 

Thank you!! But nothing useful happens when you run this command:). Or doing something wrong...
 
Thank you too:). Cleaned dependencies, nothing has changed, but suggested that it is necessary to remove all third-party repositories))). It worked)
 
 
Openhab2 may also need to put in the repository Arabian?)

Did you edit your /etc/apt/sources.list or did you add additionally any sources?
Which armbian do you use (do you use a armbian distro? - because I never had problems with the sources of armbian)
 
What do you get for a message after?:
sudo apt autoremove && sudo apt autoclean && sudo apt clean
sudo apt-get update
sudo apt-get -f install
sudo apt-get install mosquitto mosquitto-clients
 
 

@dimraz you only do:
 
armbianmonitor -u
 
 

the OPi Zero header is also available on the OPi R1