All Activity

This stream auto-updates     

  1. Past hour
  2. guidol

    NanoPi R1 and Neo2

    please be aware in your Message-title between the "old" and well supported NanoPi Neo2 (LTS) (=nanopineo2) and the new NanoPi Duo2
  3. Igor

    NanoPi R1 and Neo2 (no dl page yet) Added to DEV and NEXT. Working fine except Bluetooth as on many other AP6212 boards.
  4. Igor

    toilet header logo for NanoPi
  5. Today
  6. @Igor could we please change in /etc/update-motd.d/10-armbian-header from if [ $(echo $BOARD_NAME | wc -c) -ge 17 ]; then TERM=linux toilet -f standard -F metal $(echo $BOARD_NAME | sed 's/Orange Pi/OPi/' | sed 's/Nanopi/NPi/') else TERM=linux toilet -f standard -F metal $BOARD_NAME fi to if [ $(echo $BOARD_NAME | wc -c) -ge 17 ]; then TERM=linux toilet -f standard -F metal $(echo $BOARD_NAME | sed 's/Orange Pi/OPi/' | sed 's/NanoPi/NPi/') else TERM=linux toilet -f standard -F metal $BOARD_NAME fi this mean from Nanopi to NanoPi for the sed-command, because for the NanoPi Neo Core2 the toilet logo will put the 2 of Core2 in the next line. With NPi Neo Core2 it would be OK I think there was never a Nanopi?
  7. TonyMac32

    Daily (tech related) news diet

    ...yes? Well worth it. Export the step file and give it to the designer to design it into either an end product, case, etc. No guesswork. Hmm, I'm not usually opposed to M$ tools, but I'm not sure I understand the need to add it to my life. Might check it out anyway.
  8. ilchenko Evgeny

    Orangepi 3 h6 allwiner chip

  9. guidol

    Orange pi pc2 reboot by him self

    jessie (v8) and stretch (v9) are debian versions ==> see and then there are versions of ubuntu xenial (v16) and bionic (v18) ==> see for debian stretch is the actual stable realease, because jessie is old/unsupported and buster (v10) isnt ready by now. ubuntu is a "fork" or based on debian and has often newer drivers but some software like OpenMediaVault (NAS) wouldnt work. debian is more stable because the drivers are a little bit older and better tested (as I know). You should use default branch which should be stretch or bionic(?) Maybe you should first try to NOT use the parameters and use the menu-driven way? If you enter ./ EXPERT="yes" then you will be asked - only u-boot/kernel or full linux image - Do not change kernel configuration / Show kernel configuration menue before compilation - for which SBC (orange pi PC2) - kernel ((legacy), next=mainline, dev=Development version) - linux flavour (jessie, stretch, buster, xenial, bionic) - Server-headless or Desktop then the compile will start.... At the end of the compile you will get the parameters displayed if you want in future to repeat such comple. Here are the parameters shown from ym last compile: [ o.k. ] Repeat Build Options [ BOARD=nanopineocore2 BRANCH=dev RELEASE=buster BUILD_DESKTOP=no KERNEL_ONLY=no KERNEL_CONFIGURE=no ]
  10. chwe

    Proof of concept - Realtek 1295

    maybe the one soldered on the BPi W2? It's a winbond 25q128jvsq from the few pictures I found online there seems to be a reference design part (likely some sort of pmic related stuff) where it should be possible.
  11. I am not a professional in this subject but I can share with you my experience. Usually if I need to make some operations through the network or if I have to hid me real IP address I am using VeePN service as the VPN client as far as I understood. The main point is to keep an eye on internet connection speed that hasn't be decreased.
  12. windysea

    A64 date/time clock issue

    I should probably put in an update. . . . After running stable for over a week I tried to disable a tickless kernel (standard modern default) to reduce jitter: user@pine64:~$ egrep nohz /boot/armbianEnv.txt extraargs=nohz=off user@pine64:~$ cat /proc/cmdline root=UUID=c80325d7-1d25-4151-85c3-47343b473fae rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 panic=10 consoleblank=0 loglevel=7 ubootpart=0f940383-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u nohz=off cgroup_enable=memory swapaccount=1 Sadly this once again brought about instability. With a non-tickless kernel I start to see rcu_sched self-detected stalls such as I noted in DEV (5.0.y) on PineA64+ seeing occasional CPU stalls. At some point the system clock will jump by 95 years and a reboot ends up being required, potentially forcibly (bad things start to happen) Interestingly, with a non-tickless kernel Andy's test_timer shows considerably different results, confirming there is indeed still a problem despite the workaround being present and active: Unfortunately I likely won't have any time to look at this until after the weekend. I'm still working towards getting the Pine64 back as a stable stratum-1 NTP server with a GPS-based reference clock. With Kernel PPS (requires non-tickless kernel) and proper offset adjustments this was working very well on 4.14.y (and earlier). Oh - and to add to how the RTC got brought into this discussion, though it is not really related: The kernel has a capability to keep the RTC in sync with its system time, primarily for use with NTP or other external service that will discipline the system time. When the symptom of the issue here manifests with the date jumping by a multiple of 95 years, the system time is no longer within the valid range for the RTC so any further attempts to synchronize the RTC from the system time result in failure: [28410.996865] sun6i-rtc 1f00000.rtc: rtc only supports year in range 1970 - 2033 The above message will only appear in the live kernel message buffer (aka 'dmesg') and on the system console, so it can be easily missed. Failures in setting the RTC (aka "hwclock") are only another indirect symptom of the issue and would be expected.
  13. Igor

    Nextcloud slow to load

    OK, but we have to know what is doing when its idle. Perhaps you are using swap file and software you are trying to use gets swapped out? Logs, logs, logs. Otherwise we are bling: armbianmonitor -u
  14. Just for completeness and closure PR #1329 implemented this for 'sunxi' and 'sunxi64' in both NEXT and DEV. Other platforms already have this feature configured. There should be no longer be any need for additional automated or otherwise scripted enhancements to do a separate 'hwclock -s' after boot as the kernel will do this itself very early, where it should be done when possible.
  15. Evgeny  Dmitrichenko

    Orange pi pc2 reboot by him self

    Thank you. Could you answer for one more question, please BRANCH (stretch|jessie|bionic|xenial) and RELEASE (default|next|dev) params is not clear for me... Could you please tell what is difference - what is stretch, jessie, bionic ... Now I use this code to build my custom image: ./ KERNEL_CONFIGURE="no" KERNEL_ONLY="no" BOARD="orangepipc2" BRANCH="next" RELEASE="xenial" BUILD_DESKTOP="yes" If I understand write - for production I must use stable version, which can be build with this params: BRANCH="default" and RELEASE="stratch" Is it write?
  16. mark-aus-51


  17. Igor

    Orange pi pc2 reboot by him self

    No, it's probably kernel related. You are using some old one which we don't deal with. Upgrade / use latest image and try if the problem still exists.
  18. Evgeny  Dmitrichenko

    Orange pi PC2 Powering Off Error

    Thank you very much
  19. Evgeny  Dmitrichenko

    Orange pi pc2 reboot by him self

    Hello, guys. I need help, don`t know what is going on. Yesterday two of my device`s (orange pi PC2) was rebooted by themselves. At different times, in separate areas. In log files I see fact of reboot but don`t see the reason. Temperature was in OK. Power adapter and micro SD card, which I use, in attachment. What should I pay attention? Can it be the reason is unattended upgrades or some armbian cron process? Environment: BOARD=orangepipc2 BOARD_NAME="Orange Pi PC2" BOARDFAMILY=sun50iw2 VERSION=5.67 LINUXFAMILY=sunxi64 BRANCH=next ARCH=arm64 IMAGE_TYPE=custom BOARD_TYPE=conf INITRD_ARCH=arm64 KERNEL_IMAGE_TYPE=Image there is log from one of them: armbianmonitor = go to reboot at Apr 18 22:52:13 I'm stumped armbianmonitor.txt 0045_kern 0045_syslog
  20. mark-aus-51

    Tinkerboard S and Pi-Top CEED

    Works well and without any problems! If you then install all the updates and upgrades, and the media script, you have a current well-running operating system on the pi-topCEED. Many Thanks! Cheers Mark
  21. pkfox

    SATA project Part IV

    I got an invalid argument error with the iozone one unless I removed the -i params
  22. pkfox

    SATA project Part IV

    root@NewNanoPiM4:~# dd if=/dev/zero of=/mnt/Raid/sd.img bs=1M count=4096 conv=fdatasync 4096+0 records in 4096+0 records out 4294967296 bytes (4.3 GB, 4.0 GiB) copied, 19.8072 s, 217 MB/s
  23. Tido

    Daily (tech related) news diet

    boooh, KiCAD takes 5,4Gigabyte of stoarge with all the 3D files. Some news on the developing front, are you also curious how good this Microsoft Visual Studio Code is - people seem to like it! But before you try, watch a 14min video to save time And now you can try and throw it away, if you don't like it... Visual Studio Code 1.33 as Snap-Package direct link
  24. FrankM

    SATA project Part IV

    You can do this sudo dd if=/dev/zero of=sd.img bs=1M count=4096 conv=fdatasync and sudo iozone -e -I -a -s 100M -r 4k -r 16k -r 512k -r 1024k -r 16384k -i 0 -i 1 -i 2 Thanks
  25. pkfox

    SATA project Part IV

    Not yet Frank, I've set the drives up as a software Raid 5 so any benchmarks would be a bit skewed anyway - what tool do you use for benchmarking ?
  26. FrankM

    SATA project Part IV

    Nice project. Do you have some benchmarks?
  1. Load more activity