Werner

Members
  • Content Count

    241
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Werner reacted to guidol in Orange pi zero alternatives   
    Thats a good choice - does run very stable
  2. Like
    Werner reacted to Lutz Fechner in How to Configure OpenVPN Protocol on Armbian with Orange Pi?   
    Just found this thread after googling around to see if PiVPN works with Armbian on an Orange Pi Zero 512MB.
     
    Can confirm that it workes perfectly fine on Armbian 5.91 using and Orange Pi Zero H2+ 512 MB Board.
     
    Allows me to shut down my open ports on my router :-) Yeah.
     
    This is my 3rd Board using Armbian now. 
     
    1) Orange Pi One as Pi-hole and Webcam
    2) Orange Pi Lite as Webcam
    3) Orange Pi Zero as PiVPN
     
    Just had to donate to Armbian. This stuff is working very good.
  3. Like
    Werner reacted to guidol in show armbian-package versions in login motd   
    A while ago I did create  a armbian-package-information for at the motd of the login:
    Now the line for the kernel does show 2 versions because there are "Version:" and "Config -Version:"
     
    root@npi-neo2-24(192.168.6.24):~# dpkg -s linux-image-$BRANCH-$LINUXFAMILY|grep Version Version: 5.96 Config-Version: 5.96 root@npi-neo2-24(192.168.6.24):~# dpkg -s linux-image-$BRANCH-$LINUXFAMILY|grep Version|cut -f 2 -d ' ' 5.96 5.96 So I had to find another way/command to get the information once
    I did go back from "dpkg -s" to "dpkg -l" and greped there the version-info:
    root@npi-neo2-24(192.168.6.24):~# dpkg -l | awk -v env_var="linux-image-$BRANCH-$LINUXFAMILY" '$2==env_var { print $3 }' 5.96 # end-part of /etc/update-motd.d/10-armbian-header # NEW version # =============================================================================================================== ARMBIAN_bsp=$(more /etc/armbian-release|grep VERSION|cut -f 2 -d '=') ARMBIAN_kernel=$(dpkg -l | awk -v env_var="linux-image-$BRANCH-$LINUXFAMILY" '$2==env_var { print $3 }') ARMBIAN_uboot=$(dpkg -l | awk -v env_var="linux-u-boot-$BOARD-$BRANCH" '$2==env_var { print $3 }') ARMBIAN_dtb=$(dpkg -l | awk -v env_var="linux-dtb-$BRANCH-$LINUXFAMILY" '$2==env_var { print $3 }') ARMBIAN_firmware=$(dpkg -l | awk -v env_var="armbian-firmware" '$2==env_var { print $3 }') ARMBIAN_config=$(dpkg -l | awk -v env_var="armbian-config" '$2==env_var { print $3 }') printf 'package bsp-kernel[\e[0;91m%s\x1B[0m] u-boot[\e[0;91m%s\x1B[0m] dtb[\e[0;91m%s\x1B[0m] firmware[\e[0;91m%s\x1B[0m] config[\e[0;91m%s\x1B[0m]\n' "$ARMBIAN_kernel" "$ARMBIAN_uboot" "$ARMBIAN_dtb" "$ARMBIAN_firmware" "$ARMBIAN_config" printf '\n' # ===============================================================================================================  
    After successfully getting the kernel-version only once- I edited the other commands to the "dpkg -l" version - and the result is clear as before
    _ _ ____ _ _ _ ____ | \ | | _ \(_) | \ | | ___ ___ |___ \ | \| | |_) | | | \| |/ _ \/ _ \ __) | | |\ | __/| | | |\ | __/ (_) | / __/ |_| \_|_| |_| |_| \_|\___|\___/ |_____| Welcome to Debian Buster with Armbian Linux 5.3.3-sunxi64 package bsp-kernel[5.98.191003] u-boot[5.96] dtb[5.98.191003] firmware[5.96] config[5.96] The only drawback is, when you use a dev-kernel/-dtb on a next-installation (using other kernel via armbian-config) then $BRANCH is next and your kernel is dev
    root@npi-neo2-24(192.168.6.24):~# dpkg -l|grep image ii linux-image-dev-sunxi64 5.98.191003 arm64 Linux kernel, version 5.3.3-sunxi64 rc linux-image-next-sunxi64 5.96 arm64 Linux kernel, version 4.19.71-sunxi64 root@npi-neo2-24(192.168.6.24):~# dpkg -l|grep dtb ii linux-dtb-dev-sunxi64 5.98.191003 arm64 Linux DTB, version 5.3.3-sunxi64 # ARMBIAN_kernel=$(dpkg -l | awk -v env_var="linux-image-$BRANCH-$LINUXFAMILY" '$2==env_var { print $3 }') ARMBIAN_kernel=$(dpkg -l | awk -v env_var="linux-image-dev-$LINUXFAMILY" '$2==env_var { print $3 }') # ARMBIAN_dtb=$(dpkg -l | awk -v env_var="linux-dtb-$BRANCH-$LINUXFAMILY" '$2==env_var { print $3 }') ARMBIAN_dtb=$(dpkg -l | awk -v env_var="linux-dtb-dev-$LINUXFAMILY" '$2==env_var { print $3 }')  
     
    PS: I also did try - before this - the package apt-show-versions (lists available package versions with distribution)
    but this takes much too long to resolve and needs this additionally package
     
     

  4. Like
    Werner reacted to vlad59 in Start looking at 5.3.y   
    I rebuilt a full image this morning and I still have no wired network. I went back to kernel 4.19.X. I'll spend some time tonight to compare the device trees between 5.2 and 5.3.
  5. Like
    Werner got a reaction from guidol in Start looking at 5.3.y   
    I always freeze firmware updates when using custom build kernel images on my boards to avoid issues like this.
  6. Like
    Werner reacted to martinayotte in linux-image-next-sunxi 5.92 is missing modules   
    Merged !
  7. Like
    Werner reacted to martinayotte in Start looking at 5.3.y   
    That should be pretty easy to fix by commenting or erasing the duplicate in our patch.
    I will look at it ...
     
    EDIT: removal of guilty patches is now done !
    https://github.com/armbian/build/commit/b53556a5f1ada29169d08b6a106a01f87d763774
  8. Like
    Werner reacted to Igor in Repository uploader 2.0   
    Its (always) a compromise 
     
    The primary reason for this upgrade is to have a better working solution for easy experimenting with things as such: https://forum.armbian.com/topic/11424-playing-with-limamesa-mali-drivers/ 
     
    Initial upload repository size will be addressed (recreating/truncating), while for upload limit, there is nothing I can do. On the other hand Github has advantages, like existing user management ... for one user this is not a problem.
     
    The bulk of the job surrounding this change is elsewhere - package management RFC - rebuild is done much faster/in parallel, cleaning is more efficient ... 
  9. Like
    Werner reacted to martinayotte in OPI3 / H6 / flash eMMC   
    Maybe simply a rare bad luck, because I personally own more than 10x OPis, and all of them are working great ...
  10. Like
    Werner reacted to lanefu in [RFC] New Naming Convention for Kernel Source Trees   
    Looks great@igor!
  11. Like
    Werner reacted to lanefu in False Advertising   
    If you're in the states and interested in selling your Helios4, DM me.
  12. Like
    Werner reacted to martinayotte in Start looking at 5.3.y   
    Tested on forgotten boards in first AllWinner's garden Tour : nanopiduo2, nanopineo2, nanopim1plus2 and bananapim2plus ...
  13. Like
    Werner reacted to Igor in False Advertising   
    Many cheap NAS solutions uses virtually the same hardware and face the same limitation.
    https://www.synology.com/en-global/knowledgebase/DSM/tutorial/Compatibility_Peripherals/What_kind_of_CPU_does_my_NAS_have
     
    You need to invest more to get rid of this.
     

    My NAS has no RAID. System is on SD card, data is rsynced to another hardware. If HDD died, its replaced and rsynced from backup. Speeding up with RAID0? Nonsense.
  14. Like
    Werner reacted to guidol in Start looking at 5.3.y   
    Great Job @martinayotte !
    I did a new compile with 5.3 - and no exception anymore AND restart does work
    (also while using the NAS-Hat for the OPi Zero on the OPi R1  )
    login as: root root@192.168.6.101's password: ___ ____ _ ____ _ / _ \| _ \(_) | _ \/ | | | | | |_) | | | |_) | | | |_| | __/| | | _ <| | \___/|_| |_| |_| \_\_| Welcome to Debian Buster with Armbian Linux 5.3.0-rc3-sunxi package bsp-kernel[5.94] u-boot[5.94] dtb[5.94] firmware[5.94] config[5.94] System load: 0.72 0.26 0.09 Up time: 1 min Memory usage: 32 % of 238MB IP: 192.168.6.101 CPU temp: 46°C Usage of /: 7% of 15G Last login: Fri Aug 16 23:42:39 2019 from 192.168.6.17 root@opi-r1(192.168.6.101):~#  

  15. Like
    Werner reacted to martinayotte in Start looking at 5.3.y   
    Thanks ! ... And the WiFi 8189es is now working ...
  16. Like
    Werner reacted to martinayotte in Start looking at 5.3.y   
    In my case, I've done the tour of my AllWinner's garden : OPiPC+, OPiOne, OPiZero, OPi+2E, OPiPC2, OPi3, OPiOne+, OPiZero+2, OPiWin, OPiPrime, Pine64 and OlinuxinoA64.
  17. Like
    Werner reacted to martinayotte in Start looking at 5.3.y   
    Commit for the 5.3.y switch is now done !
     
    https://github.com/armbian/build/commit/a00375179bbc27bac4b39927133578a3f2dae383
     
  18. Like
    Werner reacted to martinayotte in Sources for armbian kernels   
    If you look at the end of "Start looking" thread, the issue found earlier is now fixed !
    Switching DEV to 5.3.y will occur soon ...
  19. Like
    Werner reacted to raulfm in [SOLVED] Nanopi Fire 3 + Armbianm 5.91 buster: network performance issue   
    And in my case it was the network switch:
     
    Edimax ES-5500G V3 NOK TP-Link tl-sg105 OK  
    Thanks again for your help.
  20. Like
    Werner reacted to guidol in OrangePi Prime, Start Kernel and stopped   
    how long did you wait?
    what kind of monitor dis you use?
    or serial console?
    how fast is your sdcard?
    what kind of powersupply did you use?
  21. Like
    Werner reacted to martinayotte in Start looking at 5.3.y   
    I didn't got any compile error, only one patch rejected, but because already present in 5.3.y.
     
    One more thing I found with my OPiPC+ experiment : reboot doesn't restart, it stall at "reaching restart", but U-Boot "restarting" never appears ...
    (a bit like the early days of H6, but OPiPC+ is H3 and never got this issue)
     
    Now trying again with 5.2.6 to figure out when bugs has been introduced ...
     
    EDIT: 5.2.6 still look good ...
     
    EDIT2: Same behaviours with OPiPlus2E 5.3.0-rc3 image ...
     
    EDIT3: Doing an OPiZeroPlus2-H5 images : No Wifi problem, and since no crash, "reboot" work properly, so, maybe related ...
  22. Like
    Werner got a reaction from sadnblueish in Orangepi 3 h6 allwiner chip   
    I added OPi 3 Buster image as well as kernel debs to my builds and will be available tomorrow following the link mentioned in my signature below.
  23. Like
    Werner reacted to martinayotte in [RFC] New Naming Convention for Kernel Source Trees   
    For me, it is only "naming convention" ... So, I will continue to work on "unstable" images ...
  24. Like
    Werner reacted to Igor in Updated sunxi-next and sunxi64-next kernel   
    I made typo  We are at 5.2.5 ...
  25. Like
    Werner reacted to Igor in Updated htop   
    Fixed on Buster and Disco with apt update / upgrade.