Tido

If you look at my document:  You will download and install a fresh armbian 5.25 Kernel 4.9.x  on your SDcard (based on Debian 8 Jessie),
https://docs.google.com/document/d/1DH8AXCHqUYI6J4L4ujt20aI9BNrYxsWtcthWZEJx8Xs/edit
 
Disable network manager (permanently) to avoid it restarting after a reboot
systemctl disable NetworkManager.service
 
was also part of my document, however, I haven't tested it since then, but lately I put power back on my R1. It is still on of my goal to have it running to store and spread media files and with the increased SATA speed .. bazinga !
 

Ok, here my result from weekend for those who are interested:
 
armbianio needs patch for Lamobo(armbianio.patch):
------------------------------------------
...armbianio.patch
diff --git a/armbianio.c b/armbianio.c
+static int iLamobor1Pins[] = {-1,-1,-1,53,-1,52,-1,259,224,-1,
+                        225,275,226,274,-1,273,244,-1,245,268,
+                        -1,269,272,267,266,-1
+            ,270};
...
------------------------------------------
 
Sending 433-Mhz-codes now also work with WiringBPi on kernel >=4... with WiringPi it does not work.
 
Only thing I do still not unterstand is why on PI19(275) worked with 17 on 3.4.x
But, now my gpio's work like it should, if I change addresses like in io-3.x-vs-4-x.png

There are 3 options to use GPIO in armbian: https://forum.armbian.com/topic/9071-opi-zero-plus-h5-and-gpio-library/?do=findComment&comment=68424
 
By the way, what do you control with the GPIO on R1?
 

Hi Guido,
 
Thank you. As you mentioned several components I wasn't sure what is really needed and to install was a bit overkill, at first sight.
I could have gone ahead with try and error, but as you already have the knowledge, I thought it was better to ask.
 
Apart from that, others can now also easily benefit from your lesson 😊
 
Cheers,
Tido

which of the 2 configs you want to rebuild?
for the non-chromebox (colored on black) prompt line there is already everything you need to put on the end of your ~/.bashrc in the first source-part box above.
 
for the chromebox prompt you need to install the 2 packages fonts-powerline &  powerline via
apt install fonts-powerline powerline
copy powerline.sh to your home-directory:
cp ./powerline.sh ~/
and append at the end of your ~/.bashrc the line:
source ~/powerline.sh
and change pUTTY to UTF8-translation:
Change Setting => Window => Translation => Remote character set => UTF-8 => Apply
or save it directly to your pUTTY session
 
then activate the new ~./bashrc while starting a new bash with
bash
or reboot
 
BTW: you have to change the ~/.bashrc for every user where you want to use it - for me these files are
/home/root/.bashrc    and
/home/guido/.bashrc
 
Do you got any other questions?
 
powerline.sh

Over a year (or two?) I used a PS1-line in my ~/-bashrc with many cryptic ANSI-Escape-codes which were hard to read and edit
 
export PS1='\[\033[1;36m\]\u\[\033[1;37m\]@\[\033[1;33m\]\h\[\033[1;37m\](\[\033[1;32m\]$THEIP\[\033[1;37m\])\[\033[1;31m\]:\[\033[1;36m\]\w\[\033[1;31m\]\$\[\033[0m\] ' Today I did installed Linux Lite 4.6 on a PC (a former Chromebox) and did see the nice Powerline prompt and did try to use that on a nanoPi Neo2.
I installed the packages fonts-powerline &  powerline and copied the powerline-script /usr/share/powerline/bindings/bash/powerline.sh
from the pc to the NanoPi Neo2.
It did work after I used UTF8 translation in pUTTY, but it wasnt very perfomant
 
So I decided to cleanup my PS1 line for better reading,
 
I had to define some variables and then I did put these in my PS1 export line in ~/.bashrc:
 
export THEIP="$(/sbin/ifconfig | grep "inet " | grep -v 127.0.0. | awk '{print $2}')" BRed='\[\033[31;1m\]' BGreen='\[\033[32;1m\]' BYellow='\[\033[33;1m\]' BCyan='\[\033[36;1m\]' BWhite='\[\033[37;1m\]' Reset='\[\033[0m\]' UserPromptPS1='\$' export PS1="${BCyan}\u${BWhite}@${BYellow}\h${BWhite}(${BGreen}${THEIP}${BWhite})${BRed}:${BCyan}\w${BRed}${UserPromptPS1}${Reset} " # \u = User # @ = @ # \h = Host # \w = working directory # \$ = # for root (uid=0) or $ for user That worked well and did give me the same result as my old but bad readable PS1-line
Now its - for me - much more easy to edit
 
As Information some more useable color-definition (B before the color is for Bright and colors starting with On are for the Background):
Black='\[\033[30m\]' Red='\[\033[31m\]' Green='\[\033[32m\]' Yellow='\[\033[33m\]' Blue='\[\033[34m\]' Magenta='\[\033[35m\]' Cyan='\[\033[36m\]' White='\[\033[37m\]' BBlack='\[\033[30;1m\]' BRed='\[\033[31;1m\]' BGreen='\[\033[32;1m\]' BYellow='\[\033[33;1m\]' BBlue='\[\033[34;1m\]' BMagenta='\[\033[35;1m\]' BCyan='\[\033[36;1m\]' BWhite='\[\033[37;1m\]' OnBlack='\[\033[40m\]' OnRed='\[\033[41m\]' OnGreen='\[\033[42m\]' OnYellow='\[\033[43m\]' OnBlue='\[\033[44m\]' OnMagenta='\[\033[45m\]' OnCyan='\[\033[46m\]' OnWhite='\[\033[47m\]' OnBBlack='\[\033[40;1m\]' OnBRed='\[\033[41;1m\]' OnBGreen='\[\033[42;1m\]' OnBYellow='\[\033[43;1m\]' OnBBlue='\[\033[44;1m\]' OnBMagenta='\[\033[45;1m\]' OnBCyan='\[\033[46;1m\]' OnBWhite='\[\033[47;1m\]' Reset='\[\033[0m\]'  

Unfortunately this not the right place to discuss these issues.  However, I would suggest you actually read the website instead of just randomly doing things.
 
If you would have read, you would have use the H3ii image and used etcher or similar to write it to an SDcard instead of using the full installation package.
 
If you read the site we have documentation for H3ii and H3resc on the site which you can use for a better understanding of those tools
 
Cheers!

This will only properly label the existing work done mainly by me in various branches. I started to develop some new feature, but perhaps more has to be fixed and rather make move to a new release. So "arm64", where most of the work and where naming is totally derailed from the actual work shell be renamed to new branch ... its an attempt to make it easy for others to join. If they have an interest, otherwise this will remain just my upgrade. But until nobody knows this is actually an upgrade, not just fixing one function, nobody even look into until its done.
 
You can see what was already fixed, there are pleads what its nice to fix and perhaps some other have an idea to squeeze in some feature. Ideally this process shell be planned within Jira.
 
This is not maintaining a separate LTS branch.

Another edge-router based on the Armada 3700 series...
 
Specs look decent - 1GB, 16MB SPI-NOR, 8GB eMMC - runs OpenWRT, but they promise ubuntu support - shipping mid-October 2019
 
https://www.gl-inet.com/products/gl-mv1000/
 

 
I've done work with other devices in their product lineup - and GL-Inet does a pretty good job on the HW side, and good SW support.
 
Nice that they have USB gadget support on the USB-C port (which is also power)
 
Initial vendor docs here -- https://docs.gl-inet.com/en/3/setup/brume/first-time_setup/
 
 
 
 

Pimp your bash. To be fair I copied some from the link at the bottom:
 
A few commands are needed quite often and to reduce typing a little bit, voila: To create the file nano ~/.bash_aliases ############################ # my personal Aliases list # ############################ # to create the file nano ~/.bash_aliases # **** DIRECTORY LISTING in human-readable units **** alias ll="ls -lhAF" alias ..="cd .." alias ...="cd ../../../" alias back="cd $OLDPWD" alias lsmount="mount |column -t" # * Disk Space Usage in human-readable units, including filesystem type * alias dfh="df -Tha --total" alias df="df -h --exclude=squashfs" # * ALL files in a directory listed, according their size * alias du="du -ach | sort -h" # * listing process table in detail * alias psa="ps auxf" alias dmesg="dmesg --human" # * How to really CLEAR the terminal * alias clr='printf "\033c"' alias h="history" # reload bash config alias reload="source ~/.bashrc" Now execute . ~/.bashrc in your terminal (there should be a space between the . and ~/.bashrc )  
https://pastebin.com/kzPjE8y4    |   http://smlr.us/
 

Please note, the principle of using the button may be different. There are hardware buttons, they work correctly with Linux, there are "soft" buttons, they do not work well with Linux (supported only in Android firmware). What tasks do you plan to solve on this device ? With Tanix products I would recommend to be more careful, there may be problems with running Linux.
 
 

1/2 into that direction.
 

@Tido The power consumption for Helios4 is up-to-date on our wiki. I don't really consider that like too much energy for a NAS board.
 
@barish Just FYI, Helios4 is not a product from Solidrun, we are just using their System-on-Module.

@martinayotte, @TonyMac32, @Igor, @chwe, @gprovost, now that you look at it, do you like the idea or do you see some obstacles ?
 

Is that USB drive powered externally? If not, do it ... and provide logs with:
armbianmonitor -u  

Maybe, maybe not. If their CompaTability nonsense can simply be ignored, and the ARM cores are in control, then yes. If VC6 is running the show, it is the same. :-/

Sent from my Pixel using Tapatalk

See conversation in this commit for background
 
The current default, Next, Dev naming convention for the kernel source trees is confusing, and a bit inconsistent.   I think it's time to rename them and provide clear definitions of what they are supposed to provide.
 
I'll start with some ideas here:

Vendor 
 
This Kernel is currently called Default .  The Vendor kernel would be the BSP-derived kernel or vendor maintained kernel.  Typically there for basic functionality early in a boards life.  Armbian can supply patches for these kernels
 
LTS

This kernel is currently called Next.   The LTS kernel would follow a LTS version of mainline or fork.  Ex: 4.19 of Megous's branch for orangepi, mainline:4.19 for espressobin.   This should be our flagship kernel and the only one we "support" for end users.  Armbian can supply patches for these kernels
 
Unstable
 
This kernel is currently called Dev.  The Unstable kernel would follow a recent branch or fork of a kernel.  Armbian can supply patches for these kernels.
 
Mainline
 
This is new.  It would follow mainline:master.  Its purpose is to provide a 100% mainline experience when practical.  No patches will be supplied by Armbian.

Back in the day I was wondering, why the bloody TV wouldn't show the pictures in logical order..  now I heard about this:
 
FATSort Utility
 
FATSort is a C utility that sorts FAT12, FAT16 and FAT32 partitions. It even can handle long file name entries. It was developed because I wanted to sort my MP3 files on my MP3 hardware player. Unfortunately, there was no utility out there so far, so I had to write it myself. FATSort reads the boot sector and sorts the directory structure recursively.
 
https://fatsort.sourceforge.io/ 
 
If I only new a couple years ago about that.

Merged stuff from private thread. OT posts were left there and are hidden out.

this solution is said to work regardless of which distro:  systemctl set-default multi-user.target
https://unix.stackexchange.com/questions/264393/how-to-disable-x-server-autostart-in-debian-jessie
 
root@tinkerboard:~# systemctl set-default multi-user.target Created symlink from /etc/systemd/system/default.target to /lib/systemd/system/multi-user.target.  

Just a follow up
After changing the driver software some places and testing, without any in-depth understanding about this chip, I was not able to stop kernel hang on X-radio wifi driver.
 
I noticed problems with xradio in 2 modes.
1) When using xradio  in AP mode: kernel hang, reboot -f does not work
 
2) Using xradio in concurrent mode: kernel hang
 
In either cases AP mode had the problem.
I decided to stop using the xradio for good after all the testing.
 
I stopped xradio module loading from boot: commented out 'xradio_wlan' from /etc/modules file
I blacklisted xradio driver by adding  'blacklist xradio_wlan' to /etc/modprobe.d/blacklist.conf file
 
After that there were no kernel hangs or 'reboot -f' problems.
 
I use an external wifi module now. I have tested about 8 wifi modules now and I will make another post with my results and experience of them.
Cheers!

@lanefu hold yourself with sending for production. Let me build the prototype, and when verified, I will publish final production files.

Me ...

Can we take the time and think about the whole package, including cables and adapters?
Also, unless someone like @TonyMac32, hasn't overlooked the design I would wait to order, production takes longer. Who else beside Tony has some electronics know how?
 

Ok chaps, final design of serial mux board, plus zip file full of gerber files.


serial-mux.zip
 
BOM:

 
 
manufacture.pdf
 
Simple example how to control mux from bash (not verified, concept only
 
#!/bin/bash # pin allocation MOSI_PIN=353 #GPIO2 SCK_PIN=3 #GPIO3 EN_PIN=19 #GPIO4 function gpio-setup { for pin in $MOSI_PIN $SCK_PIN $EN_PIN; do [[ -d /sys/class/gpio/gpio$PIN ]] && echo $pin > /sys/class/gpio/export echo "out" > /sys/class/gpio/gpio$PIN/direction done } function gpio-write_byte { for i in {1..8}; do // set data pin to high or low value BIT=0 (( $1 > 127 )) && BIT=1 echo "$BIT" > /sys/class/gpio/gpio$MOSI_PIN/value // set clock high echo "1" > /sys/class/gpio/gpio$SCK_PIN/value $1=$(( $1 << 1 )) // set clock low echo "0" > /sys/class/gpio/gpio$SCK_PIN/value done } # 16 bits: -- -- -- -- -- b3 b2 b1 p7 p6 p5 p4 p3 p2 p1 # px - power status on port x # bx - serial connected to port x function setup_mux { local high_byte=$(( $1 >> 8 )) local low_byte=$(( $1 & 255 )) gpio-setup gpio-write_byte(high_byte) gpio-write_byte(low_byte) # toogle EN bit to latch new value on 595s echo "1" > /sys/class/gpio/gpio$EN_PIN/value echo "0" > /sys/class/gpio/gpio$EN_PIN/value }