piknew

Members
  • Content count

    49
  • Joined

  • Last visited

  1. Problems with 5.38 update

    Done "just in case" (on already up & running opi+2): root@PKHELPER:/boot# ll total 14276 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp -rw-r--r-- 1 root root 2372 Jun 5 2016 boot.cmd -rw-r--r-- 1 root root 2444 Jun 5 2016 boot.scr lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i root@PKHELPER:/boot# wget https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd --2018-01-30 17:32:16-- https://raw.githubusercontent.com/armbian/build/master/config/bootscripts/boot-sunxi.cmd Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.112.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.112.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 3636 (3.6K) [text/plain] Saving to: ‘boot-sunxi.cmd’ boot-sunxi.cmd 100%[=======================================================================================>] 3.55K --.-KB/s in 0.001s 2018-01-30 17:32:16 (6.88 MB/s) - ‘boot-sunxi.cmd’ saved [3636/3636] root@PKHELPER:/boot# ll total 14280 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp -rw-r--r-- 1 root root 2372 Jun 5 2016 boot.cmd -rw-r--r-- 1 root root 2444 Jun 5 2016 boot.scr lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i -rw-r--r-- 1 root root 3636 Jan 30 17:32 boot-sunxi.cmd root@PKHELPER:/boot# mv boot-sunxi.cmd boot.cmd root@PKHELPER:/boot# mkimage -C none -A arm -T script -d boot.cmd boot.scr Image Name: Created: Tue Jan 30 17:33:53 2018 Image Type: ARM Linux Script (uncompressed) Data Size: 3644 Bytes = 3.56 kB = 0.00 MB Load Address: 00000000 Entry Point: 00000000 Contents: Image 0: 3636 Bytes = 3.55 kB = 0.00 MB root@PKHELPER:/boot# ll total 14276 -rw-r--r-- 1 root root 6944 Jun 5 2016 boot.bmp lrwxrwxrwx 1 root root 20 Aug 4 23:09 script.bin -> bin/orangepiplus.bin -rwxr-xr-x 1 root root 4752384 Jan 24 22:10 vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 2056747 Jan 24 22:10 System.map-3.4.113-sun8i -rw-r--r-- 1 root root 97199 Jan 24 22:10 config-3.4.113-sun8i drwxr-xr-x 2 root root 4096 Jan 29 17:57 bin lrwxrwxrwx 1 root root 21 Jan 29 17:59 zImage -> vmlinuz-3.4.113-sun8i -rw-r--r-- 1 root root 3839674 Jan 29 17:59 initrd.img-3.4.113-sun8i -rw-r--r-- 1 root root 3839738 Jan 29 17:59 uInitrd-3.4.113-sun8i lrwxrwxrwx 1 root root 21 Jan 29 17:59 uInitrd -> uInitrd-3.4.113-sun8i -rw-r--r-- 1 root root 3636 Jan 30 17:32 boot.cmd -rw-r--r-- 1 root root 3708 Jan 30 17:33 boot.scr root@PKHELPER:/boot# Device is still booting - OK ...
  2. Problems with 5.38 update

    Thanks, for me solution with manual download and "dd" to emmc works as well. Opi+2 is up & running now. For Opi+2e - tomorrow I will try (have a little more issues with physical access to device).
  3. Problems with 5.38 update

    In my case - both Orange Pi+ 2 and Orange Pi+ 2e are using emmc. Currently I am not able to provide any output from serial as I have no physical access to my devices (btw. I do not have serial/usb cable to investigate it ). Information (common for both devices, also the same for 2 devices which have no issues: Orange Pi PC and Orange Pi Zero 512MB H2+): - upgrade from 5.35 to 5.36 was OK - upgrade from 5.36 to 5.37 was OK (I have seen this upgrade was very minor, only 1 package has been updated) - upgrade from 5.37 to 5.38 failed for Opi+2 and Opi+2e (actually I am able to confirm for 100% that I am not able to connect to devices and I am 100% sure that this is not an issue related to e.g. different hwaddres, IP etc.) - either device hasn't booted at all or network interfaces are down (this one can be confirmed by anybody who can check by serial interface) - upgrade from 5.37 to 5.38 was OK for OpiPC and OpiZero - there ware no issues during upgrade process - it was completed without any warnings/errors. - Opi+2 and Opi+2e are using eMMC as main boot device - OpiPC and OpiZero are using SD cards as main boot device (obviously) - All 4 platforms are running with legacy kernel I will have physical access to both devices on Friday, 02.02.2018. I have "tool" SD card which will allow me to boot both devices and if there is any suggestion from this forum - I will be able to make necessary corrections (eg. "dd" new file to emmc boot sectors etc.).
  4. Problems with 5.38 update

    Confirmed - both of my Opi+ and Opi+2e are not booting after upgrade to 5.38. OpiPC and OpiZero - no issues.
  5. RTC on Banana Pro

    Hi, what you need to do is just check this parameters (do not touch others): BUS="0" ADAPTER=/sys/class/i2c-adapter/i2c-$BUS For example in my Orange Pis (all) it is: root@PKSERVER:~# ls -l /sys/class/i2c-adapter/i2c-0 lrwxrwxrwx 1 root root 0 Jan 1 1970 /sys/class/i2c-adapter/i2c-0 -> ../../devices/platform/twi.0/i2c-0 I do not know Banana SBCs, so that's why I suggested to check and correct path (which is given by two variables as above). BTW. Have you tried running the script without any change? Then try to run script as suggested. Expected result is that your rtc on i2c bus will be registered as /dev/rtc1 (please note that script is not changing original symlink which is /dev/rtc - it is explicitly running hwclock with /dev/rtc1)
  6. RTC on Banana Pro

    Any success?
  7. Heatsink / fan vs. [ddrfreq]

    Everything is OK.
  8. RTC on Banana Pro

    You may try to use my script ( for external RTC - please adjust it as I do not know if paths for devices are the same as on H3 OrangePi ): rtc-i2c.zip the script "rtc-i2c.sh" (of course please add executable attribute) shall be located at /etc/conf.d (please create this folder or choose your own - but then you need to edit "rtc-i2c.service" content). root@PKPRINT:/etc/conf.d# pwd /etc/conf.d root@PKPRINT:/etc/conf.d# ls -l rtc-i2c.sh -rwxr-x--- 1 root root 1941 Mar 2 2017 rtc-i2c.sh root@PKPRINT:/etc/conf.d# ./rtc-i2c.sh show Current date on RTC (/dev/rtc0): Thu 01 Jan 1970 01:25:24 AM CET -1.749911 seconds Current date on RTC (/dev/rtc1): Mon 16 Oct 2017 09:30:18 PM CEST -0.899079 seconds Current system date: Mon 16 Oct 2017 09:30:18 PM CEST root@PKPRINT:/etc/conf.d# if everything is ok then you may try to put file "rtc-i2c.service" into /lib/systemd/system and execute: systemctl enable rtc-i2c.service Reboot and check if everything is working correctly: systemctl status rtc-i2c.service and in dmesg: [ 7.564372] systemd[1]: Starting Initialize i2c hardware RTC device driver... [ 7.691503] systemd[1]: Mounting FUSE Control File System... [ 7.821186] systemd[1]: Starting Apply Kernel Variables... [ 7.861767] rtc-ds1307 0-0068: rtc core: registered ds1307 as rtc1 [ 7.861811] rtc-ds1307 0-0068: 56 bytes nvram [ 7.861882] i2c i2c-0: new_device: Instantiated device ds1307 at 0x68 [ 7.892466] systemd[1]: Mounted Configuration File System.
  9. Heatsink / fan vs. [ddrfreq]

    Yes. You are right - this points (624->672) are really on ~75+ level of SoC Temperature. Meanwhile I have changed fex file for both of boards (OPI+2e and OPI+2) as stated in the fix. Rebooted - I will let know if there are any issues (should not be as fix is quite clear and obvious).
  10. Heatsink / fan vs. [ddrfreq]

    Thanks and thank for the fix . I am using cheap heatsink from aliexpress (do you think I shall put different heatsink or revert to using fan?) - which under heavy load gives (cpuburn-a7 was started at "13:09:02", finished at "13:10:39"): admin@PKSERVER:~$ sudo armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU 13:08:31: 1248MHz 1.04 25% 2% 22% 0% 0% 0% 59°C 13:08:36: 1008MHz 1.04 25% 2% 22% 0% 0% 0% 60°C 13:08:42: 1008MHz 1.04 29% 2% 23% 0% 1% 1% 60°C 13:08:47: 1296MHz 1.03 28% 3% 22% 0% 1% 0% 59°C 13:08:52: 1296MHz 1.03 28% 3% 22% 0% 1% 0% 60°C 13:08:57: 1200MHz 1.03 26% 2% 23% 0% 0% 0% 62°C 13:09:02: 1200MHz 1.43 26% 2% 23% 0% 0% 0% 76°C 13:09:07: 1200MHz 1.71 26% 2% 23% 0% 0% 0% 78°C 13:09:12: 1200MHz 1.98 66% 2% 62% 0% 1% 0% 78°C 13:09:17: 1200MHz 2.22 99% 2% 96% 0% 0% 0% 80°C 13:09:22: 1200MHz 2.44 99% 2% 95% 0% 0% 0% 81°C 13:09:27: 1200MHz 2.65 99% 2% 95% 0% 0% 0% 81°C 13:09:33: 1200MHz 2.83 98% 3% 94% 0% 0% 0% 79°C 13:09:38: 1200MHz 3.01 98% 3% 94% 0% 0% 0% 82°C Time CPU load %cpu %sys %usr %nice %io %irq CPU 13:09:43: 1008MHz 3.17 98% 3% 94% 0% 0% 0% 83°C 13:09:48: 1008MHz 3.31 99% 2% 96% 0% 0% 0% 83°C 13:09:53: 1008MHz 3.45 99% 3% 94% 0% 0% 0% 77°C 13:09:58: 1200MHz 3.57 99% 3% 94% 0% 0% 0% 79°C 13:10:03: 1200MHz 3.77 99% 3% 94% 0% 0% 0% 83°C 13:10:08: 1200MHz 3.87 99% 3% 94% 0% 0% 0% 79°C 13:10:14: 1008MHz 4.04 99% 3% 94% 0% 0% 0% 80°C 13:10:19: 1008MHz 4.11 99% 2% 95% 0% 0% 0% 80°C 13:10:24: 1008MHz 4.35 98% 4% 93% 0% 0% 0% 83°C 13:10:29: 1008MHz 4.40 98% 4% 93% 0% 0% 0% 80°C 13:10:34: 1008MHz 4.53 98% 3% 93% 0% 0% 1% 81°C 13:10:39: 1296MHz 4.56 98% 3% 93% 0% 0% 1% 69°C 13:10:44: 1008MHz 4.28 98% 3% 93% 0% 0% 1% 68°C 13:10:49: 1008MHz 4.02 55% 2% 51% 0% 0% 0% 67°C 13:10:55: 1008MHz 3.77 28% 3% 21% 0% 1% 0% 67°C Time CPU load %cpu %sys %usr %nice %io %irq CPU 13:11:00: 1056MHz 3.55 28% 3% 21% 0% 1% 0% 65°C 13:11:05: 1008MHz 3.43 29% 3% 23% 0% 1% 0% 64°C 13:11:10: 1008MHz 3.23 29% 3% 23% 0% 1% 0% 63°C 13:11:15: 1008MHz 3.05 29% 3% 23% 0% 1% 0% 63°C 13:11:20: 1008MHz 2.97 26% 3% 21% 0% 1% 0% 62°C 13:11:25: 1296MHz 2.89 25% 3% 18% 0% 2% 0% 63°C 13:11:30: 1200MHz 2.74 25% 3% 18% 0% 2% 0% 66°C 13:11:35: 1296MHz 2.60 27% 2% 23% 0% 0% 0% 66°C 13:11:40: 1296MHz 2.47 27% 2% 23% 0% 0% 0% 67°C^Cadmin@PKSERVER:~$ Following confirms as you have mentioned: 1. Overall temperature graph by time (this one peak above 60 degrees is rather coincidence, maybe my play with fan connectors ) - in general the highest temperature does not exceed 55-57 degrees). 2. This is before removing fan (the highest temperature is ~57): 3. This is after removing fan (the highest temperature is above 70 degrees - however, the logic of ddrfreq seems to be set with lower threshold: around 65 degrees?):
  11. Hi, if anybody can suggest if mentioned situation is OK? Thanks in advance. Originally all my OPI boards have been running on 624 MHz for DDR frequency. 2 days ago I decided to remove fans from My Orange Pi+ 2e and Orange Pi+ 2 (following suggestions from forum as fan is maybe not required). 1. Orange Pi+ 2e (this is running all my services which is: nextcloud, mail server, svn and web server to access mentioned) - originally with heasink and fan (as you can see downtime on Oct 14th - when I have removed fan and keep only heatsink). But something happened - with fan ddr frequency was always 624 MHz. Without fan some time after reboot it is increasing frequency to 672MHz, for example: [ 10.850313] gmac0 gmac0: eth0: eth0: PHY ID 001cc915 at 0 IRQ poll (gmac0-0:00) [ 14.850329] PHY: gmac0-0:00 - Link is Up - 1000/Full [ 24.680720] ADDRCONF(NETDEV_UP): wlan0: link is not ready [12328.080061] [ddrfreq] DDR: 624000KHz->672000KHz start [12328.080074] [ddrfreq] current cpu is cpu2 [12328.081263] [ddrfreq] elapsed: 1041us [12328.081276] [ddrfreq] DDR: 624000KHz->672000KHz ok! Currently it is: ... and 1 minute later: The same happened with my Orange Pi+ 2. Orange Pi PC was always running without fan and always is on 624 MHz level:
  12. root@PKSERVER:/lib/modules/3.4.112-sun8i/kernel# find . -name "*7601*" root@PKSERVER:/lib/modules/3.4.112-sun8i/kernel# uname -a Linux PKSERVER 3.4.112-sun8i #14 SMP PREEMPT Wed Sep 14 20:29:31 CEST 2016 armv7l GNU/Linux root@PKSERVER:/lib/modules/3.4.112-sun8i/kernel# I guess the module is not included in Armbian 5.20...
  13. Backup script for block devices

    I answered you already, but you have asked the same question again... If something is not clear you have to point "what" exactly should be elaborated.
  14. Without compiling - is there any way to compile just module? I have just "server" release. If I am abl to run the driver then the rest should not be a problem (wpa_applicant etc.). I see also a lot of discussion if sources are OK or not OK (so basically would be goo to post git URL with the most up-to-dated source which is OK). Then some part related that driver will be included in package (from apt.armbian repository). Is dis available already?
  15. Backup script for block devices

    If you have it on SD then put card in SD Card reader and make an backup (by for example Win32DiskImager). If you have it on emmc then you may use script from this thread. Of course you must boot your device from SD card (it can be fresh Armbian, with pv tool installed and enabled authorization by public key). BTW. I think I will adjust my script to support also "local" image storage (not only by SSH). "local" == locally mounted file system.