guidol

more elegant would be to know the right moment - when to start- your service and on what it depends.
 
if your service depends (because of the UDP packet = a full working network) then the following page could have an solution for you:
Systemd: how to make a systemd service start after network fully connected?
 
Also have a look at
How to list all services that start AFTER certain service in systemd
 

If the devices aren't plugged in on boot with 4.17+ the hub will go into a suspend state that can't be woken.  I've patched this in the 4.19 dev images by copying the solution for Rockchip (same IP block).  One of the upstream contributors submitted a nearly identical patch within a day of mine, so it will be fixed in the future.

easy enough for the script - I just changed shutdown to reboot... which the UI still shows "Shutdown Yes/No" for now, but I'll take care of that later...
# os.system('systemctl poweroff') os.system('systemctl reboot') Anyways - @guidol - here's my updated script, it's based on the V2 script you posted from the DietPI folks... fixed the padding, and the provision for the second logo/splash screen...
 
 
bakebit_nanohat_oled.py

on a real PC with debian stretch I got the problem of the missing rc.local
 
With instrustions I did rebuild this as a service, but the service was starting too fast - so I had to put a 
sleep 20
as the first command in beginning of the rc.local
 
Maybe your service will also start with pause of 20 seconds? 
Could be a chance because you did wrote it will start successfully when started from commandline.
#!/bin/sh -e # # rc.local # # This script is executed at the end of each multiuser runlevel. # Make sure that the script will "exit 0" on success or any other # value on error. # # In order to enable or disable this script just change the execution # bits. # # By default this script does nothing. sleep 20 systemctl start Announce.service exit 0  
 

On bionic 4.19.12-meson64 #5.67.181226:
$ xrandr -d :0 -q
Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 8192
Composite-1 connected (normal left inverted right x axis y axis)
  720x576i      50.00  
  720x480i      59.94  
HDMI-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 546mm x 352mm
  1920x1200     59.95*+   (yes)
  1920x1080     60.00  (yes)
  1600x1200     60.00  
  1680x1050     59.88   (yes)
  1280x1024     75.02    60.02  (HDMI only)
  1440x900      59.90  (yes)
  1280x960      60.00  
  1152x864      75.00  
  1024x768      75.03    70.07    60.00  
  832x624       74.55  
  800x600       72.19    75.00    60.32    56.25  
  640x480       75.00    72.81    66.67
 
Legenda of test result:
(yes) means that HDMI to HDMI and HDMI to DVI both work
(HDMI only) means HDMI to HDMI works
no () means that HDMI to HDMI and HDMI to DVI both don't work.
 
PS
To change resolution from UART console I used for example:
$ xrandr -d :0 --output HDMI-1 --mode 1920x1080
 

Yes - this will work
 
# .---------------- minute (0 - 59) # | .------------- hour (0 - 23) # | | .---------- day of month (1 - 31) # | | | .------- month (1 - 12) OR jan,feb,mar,apr ... # | | | | .---- day of week (0 - 6) (Sunday=0 or 7) OR sun,mon,tue,wed,thu,fri,sat # | | | | | # * * * * * command to be executed * 3 * * * /sbin/poweroff  

after searching the internet we have to do it the blacklist way

for every module you doenst want to load create a file in /etc/modprobe.d with the name <modulname>.conf that will include the line
blacklist <modulname>
like that :
/etc/modprobe.d/xradio_wlan.conf : blacklist xradio_wlan  
If we do this for all 3 modules we get:
 
root@opi-zero(192.168.6.99):/etc/modprobe.d# cat xradio_wlan.conf mac80211.conf cfg80211.conf blacklist xradio_wlan blacklist mac80211 blacklist cfg80211 After a reboot the modules arent loaded anymore
root@opi-zero(192.168.6.99):~# lsmod Module Size Used by lz4hc 16384 4 lz4hc_compress 24576 1 lz4hc ftdi_sio 40960 0 sun8i_codec_analog 24576 1 sun4i_codec 32768 3 usbserial 24576 1 ftdi_sio snd_soc_core 118784 2 sun4i_codec,sun8i_codec_analog snd_pcm_dmaengine 16384 1 snd_soc_core snd_pcm 69632 2 snd_pcm_dmaengine,snd_soc_core zram 24576 5 snd_timer 24576 1 snd_pcm snd 45056 3 snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd sun4i_gpadc_iio 16384 0 uio_pdrv_genirq 16384 0 uio 16384 1 uio_pdrv_genirq usb_f_acm 16384 1 u_serial 20480 3 usb_f_acm g_serial 16384 0 libcomposite 40960 2 g_serial,usb_f_acm ip_tables 20480 0 x_tables 20480 1 ip_tables pwrseq_simple 16384 1  
for reference:  KernelModuleBlacklisting
 
Howto: Create a file '/etc/modprobe.d/<modulename>.conf' containing 'blacklist <modulename>'. Run 'depmod -ae' as root Recreate your initrd with 'update-initramfs -u'  

Very good!! it is working for me as well
 

As Info:
Mxq Project has posted Sunvell TV box firmware that runs perfectly on Opi PC.
Smooth as butter, best firmware to date, up to date Android 7.1.2
https://www.youtube.com/watch?v=peo6mcV12Is
 
Download Firmware Here - https://drive.google.com/file/d/1ZjO47X3H8XHLt3ehzhYI01Ip7ulJLgKE/view
 
You will also need Phoenix Card Maker and an SD card to burn this onto your device.
 

Cool - now we possibly know who to attribute the actual script changes to - it was not attributed over at the WLAN PI distro...
 
I'm not on DietPI's group - but someone should encourage the author to do a pull request on FE's github, as it's obviously a good thing to include.
 
FWIW - on the stats screen, you can change the padding from "2" to "0", which brings the bottom line back onto the screen... (it prints a couple of pixels down)
 
    elif page_index==1:         # Draw some shapes.         # First define some constants to allow easy resizing of shapes.         # padding = 2 # FE's script draws off canvas here, so we remove the pad for this screen padding = 0         top = padding         bottom = height-padding         # Move left to right keeping track of the current x position for drawing shapes.  

Today I swapped my old Neo2 against a Neo2 LTS 1GB in my NAS case - so I had a old Neo2 512MB free for the black Aluminum-OLED-case which I got in a drawer.
 
Now I did try to activate the OLED in 
ARMBIAN 5.67 user-built Debian GNU/Linux 9 (stretch) 4.19.4-sunxi64 Linux npi-neo2-27 4.19.4-sunxi64 #6 SMP Fri Nov 30 14:02:43 +03 2018 aarch64 GNU/Linux
First (like on a i2c-clock" I activated i2c0 in armbian-config:
 
root@npi-neo2-27(192.168.6.27):~# armbian-config System --> Hardware --> [*] i2c0 After the reboot I checked for the i2c-OLED-device and got:
 
root@npi-neo2-27(192.168.6.27):~# apt install i2c-tools root@npi-neo2-27(192.168.6.27):~# i2cdetect -y 0      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  After some trial and error(-messages) I did found the following dependencies for compiling/installing the software for the OLED-Board:
apt-get install python-setuptools libjpeg-dev  
After that I did the normal "5 Enable NanoHat-OLED manually" from
http://wiki.friendlyarm.com/wiki/index.php/NanoHat_OLED
with
 
root@npi-neo2-27(192.168.6.27):~# cd /home/guido root@npi-neo2-27(192.168.6.27):~# git clone https://github.com/friendlyarm/NanoHatOLED.git root@npi-neo2-27(192.168.6.27):~# cd NanoHatOLED root@npi-neo2-27(192.168.6.27):~# ./install.sh And after the next reboot the OLED-Display did work

Thanks for the information
Additionally I did found "this" patch also in the dietpi-forum:
[Tutorial] How to get your NanoHatOLED to work

For dietpi there are much more dependencies, because it claims to be smaller than armbian in the basic-configuration
 
There are also the .zip files of the complete patch - in 2 versions - written by the user Phillski (see inside the spoiler)
 
for backup-reasons I will attach the 2 versions also here
 
I had only to extract the .zip above the NanHatOLED-Directory and reboot - no need for an additinally installation
 
 
NanoHatOLED_v2_2Minutes_DietPi.zip
NanoHatOLED_v1_5Minutes_DietPi.zip

Save the diff I posted about as bakebit_nanohat_oled.patch - then using patch, patch your corresponding file like this...
 
patch -b < bakebit_nanohat_oled.patch
 
This will patch the existing file, and create a back up of the original...
 
That should do it - then for your logo file - you'll see where to put the name of the logo file, and keep the logo in the same dir...
 
Then just run the install script, which will pick everything up and rebuild the nanohat oled

Here's my local copy of the file in case you get stuck...
 
 
bakebit_nanohat_oled.py

Works perfect - sorting the dependency for pillow was the key....
 
Works fine with 5.65 stable for Neo2
 
 
 
Plays well with NanoPI NEO (the H3 version) as well.
 
Thx!

The OPi Zero doesnt need much power.
I only disabled the Wifi - because I do use Ethernet - with the following commands in the /etc/rc.local (I know are are also other/better ways):
 
ifconfig wlan0 down rmmod xradio_wlan rmmod mac80211 rmmod cfg80211  

Update:
 
I have bought
https://www.fasttech.com/products/0/10020192/5321900-3-5-320-480-tft-lcd-display-touch-board-for
Sold with the following specs:
which seems to me very similar to
https://www.amazon.fr/gp/product/B06X191RX7/ref=oh_aui_detailpage_o02_s00?ie=UTF8&amp;psc=1
 
I started with image Armbian_5.35_Orangepizero_Ubuntu_xenial_next_4.13.16.img
 
And then, ran the following commands to get the LCD working on oPi0:

 
aptitude dist-upgrade vim /root/myili9431.dts # see previous message reboot aptitude install linux-headers-next-sunxi armbian-add-overlay myili9431.dts reboot modprobe fbtft_device custom name=fb_ili9486 gpios=dc:18,reset:2 speed=16000000 busnum=1  
and now I have a console in portrait mode.
 
# cat /root/myili9431.dts /* author: Adrian Brzezinski: adrb at wp.pl, adrian.brzezinski at adrb.pl */ /dts-v1/; /plugin/; / { compatible = "allwinner,sun8i-h3"; fragment@0 { target-path = "/aliases"; __overlay__ { spi1 = "/soc/spi@01c69000"; }; }; fragment@1 { target = <&spi1>; __overlay__ { status = "okay"; spidev { compatible = "spidev"; reg = <0>; spi-max-frequency = <50000000>; }; }; }; }; To get X:

 
# Some of the following packages may be facultative. aptitude install startx xinit x11-xserver-utils xinput-calibrator xinput xserver-xorgxserver-xorg-video-all xterm x11-utils startx # gives a black console # or xinit # gives a white console  
Mouse does not work very well. Did not try keyboard. No touchpad (I don't need it, so, no time to loose on this).
 
Rotation of screen works, but produces crappy output.
 
# Need reboot each time modprobe fbtft_device custom name=fb_ili9486 gpios=dc:18,reset:2 speed=16000000 busnum=1 rotate=90 modprobe fbtft_device custom name=fb_ili9486 gpios=dc:18,reset:2 speed=16000000 busnum=1 rotate=180 modprobe fbtft_device custom name=fb_ili9486 gpios=dc:18,reset:2 speed=16000000 busnum=1 rotate=270 # 90 and 270 produce a rectangle in landscape orientation; unusable in neither console or X. # 180 works fine. Bed time; more tries later.
 
Some tips to make conf persistent:
https://kaspars.net/blog/linux/spi-display-orange-pi-zero

Today I swapped my old Neo2 against a Neo2 LTS 1GB in my NAS case - so I had a old Neo2 512MB free for the black Aluminum-OLED-case which I got in a drawer.
 
Now I did try to activate the OLED in 
ARMBIAN 5.67 user-built Debian GNU/Linux 9 (stretch) 4.19.4-sunxi64 Linux npi-neo2-27 4.19.4-sunxi64 #6 SMP Fri Nov 30 14:02:43 +03 2018 aarch64 GNU/Linux
First (like on a i2c-clock" I activated i2c0 in armbian-config:
 
root@npi-neo2-27(192.168.6.27):~# armbian-config System --> Hardware --> [*] i2c0 After the reboot I checked for the i2c-OLED-device and got:
 
root@npi-neo2-27(192.168.6.27):~# apt install i2c-tools root@npi-neo2-27(192.168.6.27):~# i2cdetect -y 0      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- --  After some trial and error(-messages) I did found the following dependencies for compiling/installing the software for the OLED-Board:
apt-get install python-setuptools libjpeg-dev  
After that I did the normal "5 Enable NanoHat-OLED manually" from
http://wiki.friendlyarm.com/wiki/index.php/NanoHat_OLED
with
 
root@npi-neo2-27(192.168.6.27):~# cd /home/guido root@npi-neo2-27(192.168.6.27):~# git clone https://github.com/friendlyarm/NanoHatOLED.git root@npi-neo2-27(192.168.6.27):~# cd NanoHatOLED root@npi-neo2-27(192.168.6.27):~# ./install.sh And after the next reboot the OLED-Display did work

Hi all!
 
I've tried Xulong Extension board for Orange Pi Zero and found it useless waste of my money. Almost two months ago I've decided to make my own hacking shield which allows me much more in terms of control and peripherals. 
 

 
 I've tested functionality most important to me and I'm pretty happy with result. I2C works, USB power switch works, power measurement works. Project page on GitHub
 
Now I'm in progress making peripherals accessible to the system and user.  Userspace tools for python/node/C works and later I will publish tutorial (or more than one) how to make it (because it is not clear to me and take huge amount of time).

So the problem was solved!
sed -i -e '1imw.l 0x01C20020 0x80101810\' /boot/boot.cmd mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr The reason of crashes was DRAM PLL value which seems too high for the boards I have.
Default DRAM_PLL value set by u-boot 2017.05+ is 624MHz. It seems not all board support this value.
I changed it to 600MHz by setting 0x01c20020 register to 0x1810 value (instead of 0x1910 set by u-boot) and there's no any crash anymore.
 
The script adds "mw.l 0x01C20020 0x80101810" line to boot.cmd and then compiles boot.scr.
After that u-boot will change DRAM_PLL value to a bit lower one to avoid crashes.
 
Thanks everybody who helped me to find a solution.
Special thanks to @znoxx for testing and logging :)
 

Yes I read this on the power adaptor it says Output 12V/2A and the adaptor size is even smaller than those of Netgear routers.  This is a really cool device!

Not for $20 shipped, but with the -for me - cheap NAS case the NanoPi Neo2 LTS is a option.
The Neo2 is available with 512MB or 1GB of Ram and works fine inside the NAS-Case
(I got 2 of these combinations running over a year).
 
armbian-support for the Neo2 (H5-CPU) is fine. HDMI isnt included, but with the NAS-case he has 2 USB 2.0-Ports, GBE,
a power-switch AND a proper Power-connector for a normal 12V power-supply

Neo2 LTS:
https://www.friendlyarm.com/index.php?route=product/product&amp;path=69&amp;product_id=180

NAS-case:
https://www.friendlyarm.com/index.php?route=product/product&amp;path=85&amp;product_id=222

Not for $20 shipped, but with the -for me - cheap NAS case the NanoPi Neo2 LTS is a option.
The Neo2 is available with 512MB or 1GB of Ram and works fine inside the NAS-Case
(I got 2 of these combinations running over a year).
 
armbian-support for the Neo2 (H5-CPU) is fine. HDMI isnt included, but with the NAS-case he has 2 USB 2.0-Ports, GBE,
a power-switch AND a proper Power-connector for a normal 12V power-supply

Neo2 LTS:
https://www.friendlyarm.com/index.php?route=product/product&amp;path=69&amp;product_id=180

NAS-case:
https://www.friendlyarm.com/index.php?route=product/product&amp;path=85&amp;product_id=222

We all know there are several shortcomings which causes mess in the config files and prevent simple implementing of more complex scripting. In order to make build system future proof and to cleanup the exception mess, which is virtually everywhere, I decided to start working on a part of the build system. Now the concept works and it is not that far to be mad if idea is bad
 
packages/extras was moved into this, then board support package and (for now) Cubietruck and Tinkerboard hacks from config/sources/ All others have to be implement into packages and their scripts. It's one time job and it will be much easier in the future, with new boards or functions.
 
New board support packages are now broken into unlimited number of packages. Currently there are three main groups and already present logical packages. Most of present are tested and are fully operational. Mostly its copy/past with bug fixed here and there. Perhaps some bugs were made in this process, but in essence system works - for those two boards. Upgrade path is not determined yet - I only focused on packaging and installing. All those packages can be installed from freshly build ones or from the repository. Each package can have their own number and package is rebuild only if number upstream doesn't exists.
 
This RFC includes preliminary merge of @balbes150 TV boxes fork so it's ATM a bit messy. Cubietruck and Tinkerboard images were tested (Bluetooth briefly, audio need to check again), the rest is not prepared and it requires some manual work. I hope someone else, not just the usual suspects, will help doing this.
 
I will slowly move forward and keep it mergeable/synced with upstream.
 
This approach is more or less only a working proposal for changes. IMHO it's better than what we have now but not perfect.

(WIP) Readme with some more details https://github.com/armbian/build/tree/tvboxes/config/packages
 
You can try this by adding LIB_TAG="tvboxes"
 
Edit:
 
Skeleton is done, images can be build from this branch ... Most but not all of our current families and board specialities has been moved under this packaging system. I tested Cubietruck, RockPro, Tinkerboard. At least they works fine - checked for Bluetooth (TB/CB3) and video acceleration on Cubietruck.

TBD: adjust changes in armbian-config regarding desktop (nodm is gone, lightdm only with possible autologin) and kernel switching.

@JMCC Welcome to try adding perhaps Tinkerboard MM script as a new multimedia/something package. What shall be its name? If some 3rd party packages needs to be placed to the repository, put them here: https://github.com/armbian/upload
 
@gprovost mvebu family is not there yet, but if you got time it should be clear what to do? If not, I wrote lousy docs or scripting is more complicated as before  
 
@selfbg Added Olimex SOM204. Check when possible.

@zador.blood.stained Are packages relations alright? I hope they are future proof. Upgrade is planned from armbian-config and is actually optional. Older packages, except boot and kernel are no more.
 
@tkaiser cpufreq is not overwriting anymore, serial consoles are board property SERIALCON="ttyS0,ttyGS0", board config is reloaded right before packages building. Shell we move hardware-optimisations.sh to per board script? Changes should not affect OMV.
 
@Staars Z28Pro merged but untested
 
@lanefu @5kft @TonyMac32 .... check.

@balbes150 have a lot of work to move his scripting into the build engine. Helping him, testing, fixing, ... @all Check and join if you can.
 
beta.armbian.com can be switched to this new world order ASAP.

Expected merge due: 2/2019 ?

Happy 19!

Edit by lanefu 7/2019:

A project #1 has been created on github.   There are several tasks, which will be tracked as issues on the board.

Hellow there,
I installed Armbian_5.67_Aml-s9xxx_Ubuntu_bionic_default_4.19.0-rc7_desktop_20181117 to my Phicomm N1 box and found that the WIFI/Bluetooth is not available. 
 
Anyone can help me install the drivers?
 
 ____  ___                   
/ ___|/ _ \__  ____  ____  __
\___ \ (_) \ \/ /\ \/ /\ \/ /
 ___) \__, |>  <  >  <  >  < 
|____/  /_//_/\_\/_/\_\/_/\_\
                             
Welcome to ARMBIAN 5.67 user-built Ubuntu 18.04.1 LTS 4.19.0-rc7-aml-s9xxx   
System load:   2.45 1.19 0.57            Up time:       9 min        
Memory usage:  16 % of 1844MB     IP:            192.168.9.46
CPU temp:      49°C               
Usage of /:    9% of 29G        storage/:      51% of 128M       
[ General system configuration (beta): armbian-config ]
Last login: Wed Nov 28 12:14:46 2018
 
hardware info:
 
CPU: Amlogic S905D
RAM: 2G DDR3
8G eMMC
Ethernet: RTL8211F Gigabit Ethernet
WIFI/Bluetooth: CYW43455 ( same as Raspberry Pi 3B+ ) 5G WiFi IEEE 802.11n/ac with Integrated Bluetooth 4.1 
Datasheet
http://www.cypress.com/documentation/datasheets/cyw43455-single-chip-5g-wifi-ieee-80211nac-macbaseband-radio-integrated