• Content Count

  • Joined

  • Last visited

Reputation Activity

  1. Like
    Tido got a reaction from pschasch in BPi-R1 with new B53 switch driver (DSA)   
    Essentials of Hardware and Software
    I decided to reduce complexity and to follow a plan. To do so I must leave aside as much as I can.

    Before the network starts, the switch driver must be loaded and the connections defined.
    OpenWrt first executed a 'reset' and then loaded the configuration.
    find a way to easily reset (flush) previous settings for a clean start activate eth0 Create two (2) VLANs:
    allocate to each port of the switch a VLAN-ID  (LAN 102 | WAN 101) allocate /define the connection to the SoC (A20) I do not care about WiFi yet, because this is attached via USB and not connected to the BCM53125 switch.

    The beast

    previous OpenWrt switch configuration:
    ifconfig eth0 up swconfig dev eth0 set reset 1 swconfig dev eth0 set enable_vlan 1 swconfig dev eth0 vlan 101 set ports '3 8t' swconfig dev eth0 vlan 102 set ports '4 0 1 2 8t' swconfig dev eth0 set apply 1
    Once the above works and all ports are 'up', next steps:
    interfaces configuration file DHCP-Server configuration file hostapd configuration file RealTek WiFi driver Security = IPtables settings So, this is my plan and if it happend, that you are an owner of an R1 and you have a spare mSDcard.. I would appreciate you join the journey.
    I use this Debian image with current updates.
    Some useful links:
    about this dsa thingy
    man page
  2. Like
    Tido got a reaction from pschasch in Lamobo-r1 b53 switch not working with newer kernels   
    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),
    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 !
  3. Like
    Tido reacted to pschasch in GPIO not working on Armbian_5.31_Lamobo-r1_Debian_jessie_next_4.9.7.img (sysfs)   
    Ok, here my result from weekend for those who are interested:
    armbianio needs patch for Lamobo(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

  4. Like
    Tido got a reaction from pschasch in GPIO not working on Armbian_5.31_Lamobo-r1_Debian_jessie_next_4.9.7.img (sysfs)   
    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?
  5. Like
    Tido got a reaction from guidol in [Info] colored bash-prompt   
    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 😊
  6. Like
    Tido reacted to guidol in [Info] colored bash-prompt   
    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
    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
    Do you got any other questions?
  7. Like
    Tido reacted to guidol in [Info] colored bash-prompt   
    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\]'  

  8. Like
    Tido reacted to TheLinuxBug in H2: Sunvell R69 Android TV Box (AliExpress)   
    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
  9. Like
    Tido reacted to Igor in [RFC] New Versioning Convention for Armbian Releases   
    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.
  10. Like
    Tido reacted to sfx2000 in Another 3720 box - GL.Inet MV1000   
    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

    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/
  11. Like
    Tido got a reaction from NicoD in My most useful Linux terminal commands for Ubuntu/Debian   
    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/
  12. Like
    Tido reacted to balbes150 in Armbian for Amlogic S912   
    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.
  13. Like
    Tido reacted to Igor in [RFC] New Naming Convention for Kernel Source Trees   
    1/2 into that direction.

  14. Like
    Tido reacted to gprovost in Survey: Any reliable EspressoBin V7 around?   
    @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.
  15. Like
    Tido got a reaction from qblueRed42 in Rock Pi S, RK3308 CPU, is it supported by anything?   
    is aimed at ALLWINNER SoC, not the ones from Rockchip
  16. Like
    Tido got a reaction from lanefu in [RFC] New Naming Convention for Kernel Source Trees   
    @martinayotte, @TonyMac32, @Igor, @chwe, @gprovost, now that you look at it, do you like the idea or do you see some obstacles ?
  17. Like
    Tido reacted to Igor in LMS not continuously running on Tinker Board   
    Is that USB drive powered externally? If not, do it ... and provide logs with:
    armbianmonitor -u  
  18. Like
    Tido reacted to TonyMac32 in Support of Raspberry Pi   
    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

  19. Like
    Tido reacted to lanefu in [RFC] New Naming Convention for Kernel Source Trees   
    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:

    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

    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
    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.
    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.
  20. Like
    Tido got a reaction from lanefu in Daily (tech related) news diet   
    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.
    If I only new a couple years ago about that.
  21. Like
    Tido reacted to Igor in THE testing thread   
    Merged stuff from private thread. OT posts were left there and are hidden out.
  22. Like
    Tido got a reaction from guidol in How to disable autologin and gui   
    this solution is said to work regardless of which distro:  systemctl set-default multi-user.target
    root@tinkerboard:~# systemctl set-default multi-user.target Created symlink from /etc/systemd/system/default.target to /lib/systemd/system/multi-user.target.  
  23. Like
    Tido reacted to sunzone in OPi Zero: xradio_wlan driver Kernel hang   
    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.
  24. Like
    Tido reacted to Hijax in THE testing thread   
    @lanefu hold yourself with sending for production. Let me build the prototype, and when verified, I will publish final production files.
  25. Like
    Tido reacted to martinayotte in THE testing thread   
    Me ...