piknew

Members
  • Posts

    108
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Applications

Posts posted by piknew

  1. After upgrade to Debian Bullseye MOTD is displaying as below. Is (will be) Bullseye supported? BTW. I have also noticed that package armbian-tools-buster does not have equivalent armbian-tools-bullseye

     

    obraz.png.3cfd0cdfcefde8b99aaa3234f88f7ec9.png

     

     

    [root@PKOTHER /etc/update-motd.d]# cat /etc/armbian-release
    # PLEASE DO NOT EDIT THIS FILE
    BOARD=orangepiplus
    BOARD_NAME="Orange Pi+"
    BOARDFAMILY=sun8i
    BUILD_REPOSITORY_URL=https://github.com/armbian/build
    BUILD_REPOSITORY_COMMIT=f3a8c1769-dirty
    DISTRIBUTION_CODENAME=bullseye
    DISTRIBUTION_STATUS=csc
    VERSION=21.05.8
    LINUXFAMILY=sunxi
    ARCH=arm
    IMAGE_TYPE=stable
    BOARD_TYPE=conf
    INITRD_ARCH=arm
    KERNEL_IMAGE_TYPE=Image
    

     

  2. Question: can this kind of issue to be handled? Unfortunatelly I am not able to get clear information how it is possible to report such an issue (it is not really a bug, it is somehow enhancement for particular use case, in this situation chroot'ed env):

     

    https://github.com/armbian/build/issues/2533

     

    I went also through https://www.armbian.com/bugs/ and it seems that there is no place to report enhancement (which I understand shall be evaluated properly).

     

  3. It is upstream (Debian's), you may add buster-backports (read what are pros and cons: https://wiki.debian.org/Backports). As you can see there are two versions:

     

    [root@PKOTHER ~]# apt show openssh-server -a
    Package: openssh-server
    Version: 1:8.4p1-2~bpo10+1
    Priority: optional
    Section: net
    Source: openssh
    Maintainer: Debian OpenSSH Maintainers <debian-ssh@lists.debian.org>
    Installed-Size: 1,299 kB
    Provides: ssh-server
    Depends: adduser (>= 3.9), dpkg (>= 1.9.0), libpam-modules (>= 0.72-9), libpam-runtime (>= 0.76-14), lsb-base (>= 4.1+Debian3), openssh-client (= 1:8.4p1-2~bpo10+1), openssh-sftp-server, procps, ucf (>= 0.28), debconf (>= 0.5) | debconf-2.0, libaudit1 (>= 1:2.2.1), libc6 (>= 2.28), libcom-err2 (>= 1.43.9), libgssapi-krb5-2 (>= 1.17), libkrb5-3 (>= 1.13~alpha1+dfsg), libpam0g (>= 0.99.7.1), libselinux1 (>= 1.32), libssl1.1 (>= 1.1.1), libsystemd0, libwrap0 (>= 7.6-4~), zlib1g (>= 1:1.1.4)
    Recommends: default-logind | logind | libpam-systemd, ncurses-term, xauth
    Suggests: molly-guard, monkeysphere, ssh-askpass, ufw
    Conflicts: sftp, ssh-socks, ssh2
    Replaces: openssh-client (<< 1:7.9p1-8), ssh, ssh-krb5
    Homepage: http://www.openssh.com/
    Download-Size: 345 kB
    APT-Sources: http://deb.debian.org/debian buster-backports/main armhf Packages
    Description: secure shell (SSH) server, for secure access from remote machines
    
    Package: openssh-server
    Version: 1:7.9p1-10+deb10u2
    Priority: optional
    Section: net
    Source: openssh
    Maintainer: Debian OpenSSH Maintainers <debian-ssh@lists.debian.org>
    Installed-Size: 1,240 kB
    Provides: ssh-server
    Depends: adduser (>= 3.9), dpkg (>= 1.9.0), libpam-modules (>= 0.72-9), libpam-runtime (>= 0.76-14), lsb-base (>= 4.1+Debian3), openssh-client (= 1:7.9p1-10+deb10u2), openssh-sftp-server, procps, ucf (>= 0.28), debconf (>= 0.5) | debconf-2.0, libaudit1 (>= 1:2.2.1), libc6 (>= 2.28), libcom-err2 (>= 1.43.9), libgssapi-krb5-2 (>= 1.17), libkrb5-3 (>= 1.13~alpha1+dfsg), libpam0g (>= 0.99.7.1), libselinux1 (>= 1.32), libssl1.1 (>= 1.1.1), libsystemd0, libwrap0 (>= 7.6-4~), zlib1g (>= 1:1.1.4)
    Recommends: default-logind | logind | libpam-systemd, ncurses-term, xauth
    Suggests: molly-guard, monkeysphere, rssh, ssh-askpass, ufw
    Conflicts: sftp, ssh-socks, ssh2
    Replaces: openssh-client (<< 1:7.9p1-8), ssh, ssh-krb5
    Homepage: http://www.openssh.com/
    Tag: admin::login, implemented-in::c, interface::daemon, network::server,
     protocol::ssh, role::program, security::authentication,
     security::cryptography, use::login, use::transmission
    Download-Size: 319 kB
    APT-Manual-Installed: no
    APT-Sources: http://deb.debian.org/debian buster/main armhf Packages
    Description: secure shell (SSH) server, for secure access from remote machines
    

     

  4. 2 hours ago, Igor said:

    I assume its this problem, but since I have no hardware to test, someone will need to build from sources to confirm:
    https://github.com/armbian/build/commit/535650da96bb585a7dad47237f283a780189f0fb

     

    It works! Thank you.

     

    Screenshot_1.png.cabedd984774914661180e03c1ae51f4.png

     

    Attached are:

    • decompiled source (command: dtc -I dtb -O dts sun8i-h3-orangepi-plus.dtb >sun8i-h3-orangepi-plus.dts ) with modified line 540 to be phy-mode = "rgmii-id"; (as given in patch): sun8i-h3-orangepi-plus.dts
    • compiled dtb (command: dtc -O dtb -o sun8i-h3-orangepi-plus.dtb sun8i-h3-orangepi-plus.dts ), to be placed in /boot/dtb-5.10.4-sunxi (then I have executed command: update-initramfs -u just in case): sun8i-h3-orangepi-plus.dtb

     

  5. 12 hours ago, ejs said:

    I can verify that I have the same issue after upgrading my Orange Pi 2+. with the latest kernel upgrade.

     

     

    Thank you for confirmation. It seems that this board is affected.

     

    11 hours ago, Werner said:

    As a temporary fix for now is use WiFi to provide connection and armbian-config to revert to an older kernel version.

     

    Thanks, however, I will use "chroot" method when fixed kernel / packages will be available. For now I have just restored system from my backup image with previous kernel.

     

    I am able to help with any other diagnostics. First step I would suggest to check if code for driver has been changed: 8189es - which I guess is used only by OPI+2. "OPI+2e" version which I also own is using 8189fs - and there is no problem there.

  6. Done, U-Boot is updated:

     

    U-Boot SPL 2020.10-armbian (Dec 12 2020 - 00:52:34 +0100)
    DRAM: 2048 MiB
    Trying to boot from MMC2
    
    
    U-Boot 2020.10-armbian (Dec 12 2020 - 00:52:34 +0100) Allwinner Technology
    
    CPU:   Allwinner H3 (SUN8I 1680)
    Model: Xunlong Orange Pi Plus / Plus 2
    DRAM:  2 GiB
    MMC:   mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1
    Loading Environment from FAT... Unable to use mmc 1:1... In:    serial@1c28000
    Out:   serial@1c28000
    Err:   serial@1c28000
    Net:   phy interface7
    eth0: ethernet@1c30000
    starting USB...
    Bus usb@1c1b000: USB EHCI 1.00
    Bus usb@1c1d000: USB EHCI 1.00
    scanning bus usb@1c1b000 for devices... 2 USB Device(s) found
    scanning bus usb@1c1d000 for devices... Device NOT ready
       Request Sense returned 02 3A 00
    2 USB Device(s) found
           scanning usb for storage devices... 0 Storage Device(s) found
    Autoboot in 1 seconds, press <Space> to stop
    switch to partitions #0, OK
    

     

    However, it doesn't helped with network. All interfaces are up, activity LEDs are blinking, switch is reporting connection 1Gbit/s but no traffic goes in/out. The same board but with previous kernel - everything is ok.

     

    Maybe anybody else with Orange Pi + 2 can verify if this problem occurs as for my board?

  7. This is full log from Serial connection:

     

    
    U-Boot SPL 2018.05-armbian (Sep 19 2018 - 13:00:01 +0200)
    DRAM: 2048 MiB
    Trying to boot from MMC2
    
    
    U-Boot 2018.05-armbian (Sep 19 2018 - 13:00:01 +0200) Allwinner Technology
    
    CPU:   Allwinner H3 (SUN8I 1680)
    Model: Xunlong Orange Pi Plus / Plus 2
    DRAM:  2 GiB
    MMC:   SUNXI SD/MMC: 0, SUNXI SD/MMC: 1
    Loading Environment from EXT4... MMC: no card present
    ** Bad device mmc 0 **
    Failed (-5)
    In:    serial
    Out:   serial
    Err:   serial
    Net:   phy interface7
    eth0: ethernet@1c30000
    MMC: no card present
    ** Bad device mmc 0 **
    MMC: no card present
    ** Bad device mmc 0 **
    starting USB...
    USB0:   USB EHCI 1.00
    USB1:   USB EHCI 1.00
    scanning bus 0 for devices... 2 USB Device(s) found
    scanning bus 1 for devices... Device NOT ready
       Request Sense returned 02 3A 00
    2 USB Device(s) found
           scanning usb for storage devices... 0 Storage Device(s) found
    Autoboot in 1 seconds, press <Space> to stop
    switch to partitions #0, OK
    mmc1(part 0) is current device
    Scanning mmc 1:1...
    Found U-Boot script /boot/boot.scr
    3708 bytes read in 5 ms (723.6 KiB/s)
    ## Executing script at 43100000
    U-boot loaded from eMMC or secondary SD
    Boot script loaded from mmc
    212 bytes read in 4 ms (51.8 KiB/s)
    MMC: no card present
    ** Bad device mmc 0 **
    12396787 bytes read in 598 ms (19.8 MiB/s)
    7932912 bytes read in 387 ms (19.5 MiB/s)
    Found mainline kernel configuration
    33456 bytes read in 35 ms (932.6 KiB/s)
    374 bytes read in 21 ms (16.6 KiB/s)
    Applying kernel provided DT overlay sun8i-h3-i2c0.dtbo
    393 bytes read in 5 ms (76.2 KiB/s)
    Applying user provided DT overlay ds1307.dtbo
    4185 bytes read in 21 ms (194.3 KiB/s)
    Applying kernel provided DT fixup script (sun8i-h3-fixup.scr)
    ## Executing script at 44000000
    ## Loading init Ramdisk from Legacy Image at 43300000 ...
       Image Name:   uInitrd
       Image Type:   ARM Linux RAMDisk Image (gzip compressed)
       Data Size:    12396723 Bytes = 11.8 MiB
       Load Address: 00000000
       Entry Point:  00000000
       Verifying Checksum ... OK
    ## Flattened Device Tree blob at 43000000
       Booting using the fdt blob at 0x43000000
       Loading Ramdisk to 4942d000, end 49fff8b3 ... OK
       reserving fdt memory region: addr=43000000 size=6e000
       Loading Device Tree to 493bc000, end 4942cfff ... OK
    
    Starting kernel ...
    
    Loading, please wait...
    Starting version 241
    Begin: Loading essential drivers ... done.
    Begin: Running /scripts/init-premount ... done.
    Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
    Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
    done.
    Begin: Will now check root file system ... fsck from util-linux 2.33.1
    [/sbin/fsck.ext4 (1) -- /dev/mmcblk2p1] fsck.ext4 -a -C0 /dev/mmcblk2p1
    /dev/mmcblk2p1: recovering journal
    /dev/mmcblk2p1: clean, 58384/901600 files, 510156/3753728 blocks
    done.
    done.
    Begin: Running /scripts/local-bottom ... done.
    Begin: Running /scripts/init-bottom ... done.
    
    Welcome to Armbian 20.11.6 Buster!
    
    [  OK  ] Listening on Device-mapper event daemon FIFOs.
    [  OK  ] Listening on Journal Socket (/dev/log).
    [  OK  ] Started Forward Password R…uests to Wall Directory Watch.
    [  OK  ] Created slice system-getty.slice.
    [  OK  ] Listening on LVM2 poll daemon socket.
    [  OK  ] Listening on Journal Audit Socket.
    [  OK  ] Reached target Swap.
    [  OK  ] Set up automount Arbitrary…s File System Automount Point.
    [  OK  ] Listening on udev Kernel Socket.
    [  OK  ] Created slice system-serial\x2dgetty.slice.
    [  OK  ] Created slice User and Session Slice.
    [  OK  ] Reached target Slices.
    [  OK  ] Reached target System Time Synchronized.
    [  OK  ] Listening on fsck to fsckd communication Socket.
    [  OK  ] Listening on RPCbind Server Activation Socket.
    [  OK  ] Started Dispatch Password …ts to Console Directory Watch.
    [  OK  ] Reached target Local Encrypted Volumes.
    [  OK  ] Reached target Paths.
    [  OK  ] Listening on Journal Socket.
             Starting Monitoring of LVM…meventd or progress polling...
             Starting Journal Service...
             Mounting POSIX Message Queue File System...
             Starting Remount Root and Kernel File Systems...
             Starting Load Kernel Modules...
             Mounting Kernel Debug File System...
             Mounting RPC Pipe File System...
             Starting Set the console keyboard layout...
    [  OK  ] Listening on udev Control Socket.
    [  OK  ] Listening on initctl Compatibility Named Pipe.
             Starting udev Coldplug all Devices...
             Mounting Temporary Directory (/tmp)...
             Starting Create list of re…odes for the current kernel...
             Starting Availability of block devices...
    [  OK  ] Started Monitoring of LVM2… dmeventd or progress polling.
    [  OK  ] Mounted POSIX Message Queue File System.
    [  OK  ] Started Remount Root and Kernel File Systems.
    [  OK  ] Started Journal Service.
    [  OK  ] Started Load Kernel Modules.
    [  OK  ] Mounted Kernel Debug File System.
    [  OK  ] Mounted RPC Pipe File System.
    [  OK  ] Mounted Temporary Directory (/tmp).
    [  OK  ] Started Create list of req… nodes for the current kernel.
    [  OK  ] Started Availability of block devices.
             Starting Apply Kernel Variables...
             Mounting FUSE Control File System...
             Mounting Kernel Configuration File System...
             Starting RTC-I2C device driver...
             Starting Load/Save Random Seed...
             Starting Create System Users...
             Starting Flush Journal to Persistent Storage...
    [  OK  ] Started Set the console keyboard layout.
    [  OK  ] Started Apply Kernel Variables.
    [  OK  ] Mounted FUSE Control File System.
    [  OK  ] Mounted Kernel Configuration File System.
    [  OK  ] Started Load/Save Random Seed.
    [  OK  ] Started Create System Users.
    [  OK  ] Started udev Coldplug all Devices.
             Starting Helper to synchronize boot up for ifupdown...
             Starting Create Static Device Nodes in /dev...
    [  OK  ] Started Flush Journal to Persistent Storage.
    [  OK  ] Started Create Static Device Nodes in /dev.
             Starting udev Kernel Device Manager...
    [  OK  ] Reached target Local File Systems (Pre).
    [  OK  ] Reached target Local File Systems.
             Starting Set console font and keymap...
             Starting Load AppArmor profiles...
             Starting Create Volatile Files and Directories...
             Starting Preprocess NFS configuration...
    [  OK  ] Started Set console font and keymap.
    [  OK  ] Started udev Kernel Device Manager.
    [  OK  ] Started Preprocess NFS configuration.
    [  OK  ] Reached target NFS client services.
    [  OK  ] Started Create Volatile Files and Directories.
             Starting Update UTMP about System Boot/Shutdown...
             Starting Network Name Resolution...
             Starting RPC bind portmap service...
    [  OK  ] Started Load AppArmor profiles.
    [  OK  ] Started Entropy daemon using the HAVEGE algorithm.
    [  OK  ] Started RPC bind portmap service.
    [  OK  ] Started Update UTMP about System Boot/Shutdown.
    [  OK  ] Found device /dev/ttyS0.
    [  OK  ] Started Network Name Resolution.
    [  OK  ] Started Helper to synchronize boot up for ifupdown.
    [  OK  ] Listening on Load/Save RF …itch Status /dev/rfkill Watch.
             Starting Raise network interfaces...
    [  OK  ] Reached target Host and Network Name Lookups.
    [  OK  ] Reached target System Initialization.
    [  OK  ] Started Discard unused blocks once a week.
    [  OK  ] Started Clean PHP session files every 30 mins.
    [  OK  ] Started Daily man-db regeneration.
    [  OK  ] Started Daily rotation of log files.
    [  OK  ] Started Daily Cleanup of Temporary Directories.
    [  OK  ] Reached target Timers.
    [  OK  ] Listening on D-Bus System Message Bus Socket.
    [  OK  ] Reached target Sockets.
    [  OK  ] Reached target Basic System.
    [  OK  ] Started Manage Sound Card State (restore and store).
             Starting Login Service...
             Starting System Logger Daemon...
             Starting Save/Restore Sound Card State...
    [  OK  ] Started D-Bus System Message Bus.
             Starting WPA supplicant...
             Starting Resets System Activity Data Collector...
    [  OK  ] Reached target Remote File Systems (Pre).
    [  OK  ] Reached target Remote File Systems.
             Starting LSB: Load kernel …d to enable cpufreq scaling...
    [  OK  ] Started Regular background program processing daemon.
             Starting LSB: saslauthd startup script...
             Starting Deferred execution scheduler...
    [  OK  ] Reached target RPC Port Mapper.
    [  OK  ] Started Save/Restore Sound Card State.
    [  OK  ] Started Resets System Activity Data Collector.
    [  OK  ] Started Deferred execution scheduler.
             Starting Load/Save RF Kill Switch Status...
    [  OK  ] Reached target Sound Card.
    [  OK  ] Started LSB: saslauthd startup script.
    [  OK  ] Started RTC-I2C device driver.
    [  OK  ] Started Load/Save RF Kill Switch Status.
    [  OK  ] Started Login Service.
    [  OK  ] Started WPA supplicant.
    [  OK  ] Started LSB: Load kernel m…ded to enable cpufreq scaling.
             Starting LSB: set CPUFreq kernel parameters...
    [  OK  ] Started LSB: set CPUFreq kernel parameters.
             Starting LSB: Set sysfs variables from /etc/sysfs.conf...
    [  OK  ] Started System Logger Daemon.
    [  OK  ] Started LSB: Set sysfs variables from /etc/sysfs.conf.
    [  OK  ] Started Raise network interfaces.
    [  OK  ] Reached target Network.
             Starting Permit User Sessions...
    [  OK  ] Started Unattended Upgrades Shutdown.
             Starting OpenVPN service...
             Starting Network Time Service...
             Starting OpenBSD Secure Shell server...
             Starting The PHP 7.3 FastCGI Process Manager...
    [  OK  ] Reached target Network is Online.
             Starting Automounts filesystems on demand...
             Starting LSB: disk temperature monitoring daemon...
             Starting /etc/rc.local Compatibility...
    [  OK  ] Started Permit User Sessions.
    [  OK  ] Started OpenVPN service.
    [  OK  ] Started Network Time Service.
    [  OK  ] Started /etc/rc.local Compatibility.
    [  OK  ] Started OpenBSD Secure Shell server.
    [  OK  ] Started LSB: disk temperature monitoring daemon.
    [  OK  ] Started Getty on tty1.
    [  OK  ] Started Serial Getty on ttyS0.
    [  OK  ] Started The PHP 7.3 FastCGI Process Manager.
    [  OK  ] Created slice User Slice of UID 0.
             Starting User Runtime Directory /run/user/0...
    [  OK  ] Started User Runtime Directory /run/user/0.
             Starting User Manager for UID 0...
    [  OK  ] Started User Manager for UID 0.
    [  OK  ] Started Session 2 of user root.
    
    Armbian 20.11.6 Buster ttyS0
    
    PKTEST login: root
    Password:
    Last login: Mon Jan  4 20:57:51 CET 2021 from 192.168.10.126 on pts/0
    Device "bonding_masters" does not exist.
      ___  ____  _
     / _ \|  _ \(_)  _
    | | | | |_) | |_| |_
    | |_| |  __/| |_   _|
     \___/|_|   |_| |_|
    
    Welcome to Armbian 20.11.6 Buster with Linux 5.10.4-sunxi
    
    System load:   18%              Up time:       0 min
    Memory usage:  4% of 1.97G      IP:            192.168.10.250
    CPU temp:      48°C             Usage of /:    13% of 15G
    
    HXproc_run_async: pmvarrun: No such file or directory
    [root@PKTEST ~]# ifconfig
    bond0: flags=5187<UP,BROADCAST,RUNNING,MASTER,MULTICAST>  mtu 1500
            inet 192.168.10.250  netmask 255.255.255.0  broadcast 192.168.10.255
            inet6 fe80::81:cbff:fecd:fcf  prefixlen 64  scopeid 0x20<link>
            ether 02:81:cb:cd:0f:cf  txqueuelen 1000  (Ethernet)
            RX packets 61  bytes 3797 (3.7 KiB)
            RX errors 0  dropped 37  overruns 0  frame 0
            TX packets 39  bytes 2568 (2.5 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    enx0281cbcd0fcf: flags=6211<UP,BROADCAST,RUNNING,SLAVE,MULTICAST>  mtu 1500
            ether 02:81:cb:cd:0f:cf  txqueuelen 1000  (Ethernet)
            RX packets 61  bytes 3797 (3.7 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 39  bytes 2568 (2.5 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
            device interrupt 41
    
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 1000  (Local Loopback)
            RX packets 74  bytes 12232 (11.9 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 74  bytes 12232 (11.9 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    wlxd84710fed46b: flags=6147<UP,BROADCAST,SLAVE,MULTICAST>  mtu 1500
            ether d8:47:10:fe:d4:6b  txqueuelen 1000  (Ethernet)
            RX packets 0  bytes 0 (0.0 B)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 0  bytes 0 (0.0 B)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    [root@PKTEST ~]# ping 192.168.10.1
    PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
    From 192.168.10.250 icmp_seq=1 Destination Host Unreachable
    From 192.168.10.250 icmp_seq=2 Destination Host Unreachable
    From 192.168.10.250 icmp_seq=3 Destination Host Unreachable
    ^C
    --- 192.168.10.1 ping statistics ---
    5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 79ms
    pipe 4
    [root@PKTEST ~]#
    

     

  8. Orange Pi + 2 - still issue with network.

     

    I do not know if this is important, but other board has upgraded 6 packages (which 1 is Debian's), for example Opi Zero:

     

    [root@PKCHECKER /var/log]# cat dpkg.log | grep upgrade
    2021-01-04 20:24:19 upgrade libp11-kit0:armhf 0.23.15-2 0.23.15-2+deb10u1
    2021-01-04 20:24:22 upgrade armbian-config:all 20.11.4 20.11.6
    2021-01-04 20:24:24 upgrade linux-buster-root-current-orangepizero:armhf 20.11.3 20.11.6
    2021-01-04 20:24:30 upgrade linux-dtb-current-sunxi:armhf 20.11.3 20.11.6
    2021-01-04 20:24:45 upgrade linux-image-current-sunxi:armhf 20.11.3 20.11.6
    2021-01-04 20:27:01 upgrade linux-u-boot-orangepizero-current:armhf 20.11.3 20.11.6

     

    I noticed this when was about to reboot. Please note last lines - package "u-boot" is still in version 20.11.3:

     

    [root@PKTEST ~]# apt update
    Hit:1 http://deb.debian.org/debian buster InRelease
    Get:2 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
    Get:3 http://deb.debian.org/debian-security buster/updates InRelease [65.4 kB]
    Get:4 http://deb.debian.org/debian buster-proposed-updates InRelease [54.5 kB]
    Get:5 https://armbian.systemonachip.net/apt buster InRelease [18.3 kB]
    Get:6 http://deb.debian.org/debian-security buster/updates/main armhf Packages [319 kB]
    Get:7 http://deb.debian.org/debian buster-proposed-updates/main armhf Packages.diff/Index [27.8 kB]
    Get:8 http://deb.debian.org/debian buster-proposed-updates/main armhf Packages 2020-12-28-1401.36.pdiff [5,356 B]
    Get:9 http://deb.debian.org/debian buster-proposed-updates/main armhf Packages 2020-12-29-2000.40.pdiff [2,130 B]
    Get:9 http://deb.debian.org/debian buster-proposed-updates/main armhf Packages 2020-12-29-2000.40.pdiff [2,130 B]
    Get:10 https://armbian.systemonachip.net/apt buster/main armhf Packages [669 kB]
    Get:11 https://armbian.systemonachip.net/apt buster/buster-desktop armhf Packages [28.2 kB]
    Fetched 1,241 kB in 5s (270 kB/s)
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    5 packages can be upgraded. Run 'apt list --upgradable' to see them.
    [root@PKTEST ~]# apt list --upgradable
    Listing... Done
    armbian-config/buster 20.11.6 all [upgradable from: 20.11.4]
    libp11-kit0/stable 0.23.15-2+deb10u1 armhf [upgradable from: 0.23.15-2]
    linux-buster-root-current-orangepiplus/buster 20.11.6 armhf [upgradable from: 20.11.3]
    linux-dtb-current-sunxi/buster 20.11.6 armhf [upgradable from: 20.11.3]
    linux-image-current-sunxi/buster 20.11.6 armhf [upgradable from: 20.11.3]
    [root@PKTEST ~]# apt upgrade -y
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Calculating upgrade... Done
    The following packages will be upgraded:
      armbian-config libp11-kit0 linux-buster-root-current-orangepiplus linux-dtb-current-sunxi linux-image-current-sunxi
    5 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    Need to get 36.3 MB of archives.
    After this operation, 72.7 kB of additional disk space will be used.
    Get:1 http://deb.debian.org/debian-security buster/updates/main armhf libp11-kit0 armhf 0.23.15-2+deb10u1 [292 kB]
    Get:2 https://mirrors.dotsrc.org/armbian-apt buster/main armhf armbian-config all 20.11.6 [44.5 kB]
    Get:3 https://minio.k-space.ee/armbian/apt buster/main armhf linux-buster-root-current-orangepiplus armhf 20.11.6 [415 kB]
    Get:5 https://mirrors.netix.net/armbian/apt buster/main armhf linux-image-current-sunxi armhf 20.11.6 [35.3 MB]
    Get:4 https://armbian.systemonachip.net/apt buster/main armhf linux-dtb-current-sunxi armhf 20.11.6 [193 kB]
    Fetched 36.3 MB in 13s (2,785 kB/s)
    (Reading database ... 51412 files and directories currently installed.)
    Preparing to unpack .../libp11-kit0_0.23.15-2+deb10u1_armhf.deb ...
    Unpacking libp11-kit0:armhf (0.23.15-2+deb10u1) over (0.23.15-2) ...
    Setting up libp11-kit0:armhf (0.23.15-2+deb10u1) ...
    (Reading database ... 51412 files and directories currently installed.)
    Preparing to unpack .../armbian-config_20.11.6_all.deb ...
    Unpacking armbian-config (20.11.6) over (20.11.4) ...
    Preparing to unpack .../linux-buster-root-current-orangepiplus_20.11.6_armhf.deb ...
    Unpacking linux-buster-root-current-orangepiplus (20.11.6) over (20.11.3) ...
    Preparing to unpack .../linux-dtb-current-sunxi_20.11.6_armhf.deb ...
    Unpacking linux-dtb-current-sunxi (20.11.6) over (20.11.3) ...
    Preparing to unpack .../linux-image-current-sunxi_20.11.6_armhf.deb ...
    update-initramfs: Deleting /boot/initrd.img-5.9.14-sunxi
    Removing obsolete file uInitrd-5.9.14-sunxi
    Unpacking linux-image-current-sunxi (20.11.6) over (20.11.3) ...
    Setting up linux-image-current-sunxi (20.11.6) ...
    update-initramfs: Generating /boot/initrd.img-5.10.4-sunxi
    update-initramfs: Converting to u-boot format
    Setting up linux-dtb-current-sunxi (20.11.6) ...
    Setting up armbian-config (20.11.6) ...
    Setting up linux-buster-root-current-orangepiplus (20.11.6) ...
    Failed to enable unit: Unit file /etc/systemd/system/armbian-ramlog.service is masked.
    Processing triggers for libc-bin (2.28-10) ...
    Processing triggers for initramfs-tools (0.133+deb10u1) ...
    update-initramfs: Generating /boot/initrd.img-5.10.4-sunxi
    update-initramfs: Converting to u-boot format
    [root@PKTEST ~]# apt list --installed | grep u-boot
    
    WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
    
    linux-u-boot-orangepiplus-current/buster,now 20.11.3 armhf [installed]
    u-boot-tools/stable,now 2019.01+dfsg-7 armhf [installed]
    [root@PKTEST ~]#
    

     

  9. I have reflashed SD card for OPI Zero with previous kernel (5.9.14-sunxi) - it works. So, next step will be apt update && apt upgrade to see if problem occurs again.

    This is currently working version: http://ix.io/2KRL

    Edit: it works. So, problem with Opi Zero was related to some "unknown unknown" :).

     

    Also now I am flashing other SD card with previous kernel (5.9.14-sunxi) for OPI+2 and I will check the same as above.

     

    BTW. When I am referring "previous kernel" - I mean my own images of configured system (which is kept with every upgrade since legacy 3.14), not original image from Armbian website.

     

  10. Remark: on my Orange Pi PC and Orange Pi Plus 2e - everything is OK. Problem occurred on Orange Pi Plus 2 and Orange Pi Zero

     

    After upgrading to:

     

    [root@PKTEST ~]# uname -a
    Linux PKTEST 5.10.4-sunxi #20.11.6 SMP Sun Jan 3 21:28:45 CET 2021 armv7l GNU/Linux
    

     

    My "headless" Orange Pi Plus 2 "disappeared from network. I switch it off and connected via serial. I was able to login. Device runs successfully, it is assigning IP to network interface (static assignment) but... there is no connectivity at all (both egress and ingress).

     

    [root@PKTEST ~]# ifconfig
    enx0281cbcd0fcf: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
            inet 192.168.10.250  netmask 255.255.255.0  broadcast 192.168.10.255
            inet6 fe80::81:cbff:fecd:fcf  prefixlen 64  scopeid 0x20<link>
            ether 02:81:cb:cd:0f:cf  txqueuelen 1000  (Ethernet)
            RX packets 71  bytes 4397 (4.2 KiB)
            RX errors 0  dropped 38  overruns 0  frame 0
            TX packets 44  bytes 2484 (2.4 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
            device interrupt 41
    
    lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
            inet 127.0.0.1  netmask 255.0.0.0
            inet6 ::1  prefixlen 128  scopeid 0x10<host>
            loop  txqueuelen 1000  (Local Loopback)
            RX packets 80  bytes 12802 (12.5 KiB)
            RX errors 0  dropped 0  overruns 0  frame 0
            TX packets 80  bytes 12802 (12.5 KiB)
            TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
    
    [root@PKTEST ~]# ping localhost
    PING localhost(localhost (::1)) 56 data bytes
    64 bytes from localhost (::1): icmp_seq=1 ttl=64 time=0.129 ms
    64 bytes from localhost (::1): icmp_seq=2 ttl=64 time=0.166 ms
    64 bytes from localhost (::1): icmp_seq=3 ttl=64 time=0.154 ms
    ^C
    --- localhost ping statistics ---
    3 packets transmitted, 3 received, 0% packet loss, time 52ms
    rtt min/avg/max/mdev = 0.129/0.149/0.166/0.020 ms
    [root@PKTEST ~]# ping 127.0.0.1
    PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
    64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.107 ms
    ^C
    --- 127.0.0.1 ping statistics ---
    1 packets transmitted, 1 received, 0% packet loss, time 0ms
    rtt min/avg/max/mdev = 0.107/0.107/0.107/0.000 ms
    [root@PKTEST ~]# ping 192.168.10.1
    PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
    From 192.168.10.250 icmp_seq=1 Destination Host Unreachable
    From 192.168.10.250 icmp_seq=2 Destination Host Unreachable
    From 192.168.10.250 icmp_seq=3 Destination Host Unreachable
    ^C
    --- 192.168.10.1 ping statistics ---
    4 packets transmitted, 0 received, +3 errors, 100% packet loss, time 78ms
    

     

  11. Please post dmesg output after changes are committed to emmc (with "w"). I had exactly the same issue - dmesg was reporting a lot of serious write errors. I already assumed that emmc is not usable anymore, however, after couple of weeks... I tried again and everything was OK. I am not sure if this was really hardware issue or software.

     

    So, please check dmesg output...

     

  12. I need to revert statement as above. My OPi+2E has "frozen". So, entry MIN_SPEED=408000 is not valid for my SBCs. Until it is corrected I have added following to /etc/cron.d/cpufrequtils-fix

     

    */5 * * * * root /bin/grep 'MIN_SPEED=408000' /etc/default/cpufrequtils 1>/dev/null 2>&1 && /bin/sed --in-place s/MIN_SPEED=408000/MIN_SPEED=480000/ /etc/default/cpufrequtils 1>/dev/null 2>&1 && /bin/systemctl restart cpufrequtils 1>/dev/null 2>&1

     

    Edit. My mistake. It was that I have put my SBC on quite warm router. And during scheduled job (performing backup of my NAS) it was simply shut down:

     

    Feb  4 05:11:48 PKBACKUP kernel: thermal thermal_zone0: critical temperature reached (90 C), shutting down
    Feb  4 05:11:48 PKBACKUP systemd[1]: Stopped target Sound Card.
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopping Save/Restore Sound Card State...
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopping Initialize i2c hardware RTC device driver...
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopped target Timers.
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopped Clean PHP session files every 30 mins.
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopped Daily Cleanup of Temporary Directories.
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopped target Graphical Interface.
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopped target Multi-User System.
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopped target Login Prompts.
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopping Getty on tty1...
    Feb  4 05:11:49 PKBACKUP systemd[1]: Stopping Serial Getty on ttyS0...
    
    ........

     

  13. It seems that with kernel 4.19.13-sunxi the typo is no longer causing issues (at least on OPi+2, which I've selected to perform test):

     

      ___                               ____  _
     / _ \ _ __ __ _ _ __   __ _  ___  |  _ \(_)  _
    | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | |_| |_
    | |_| | | | (_| | | | | (_| |  __/ |  __/| |_   _|
     \___/|_|  \__,_|_| |_|\__, |\___| |_|   |_| |_|
                           |___/
    
    Welcome to ARMBIAN 5.70 stable Debian GNU/Linux 9 (stretch) 4.19.13-sunxi
    System load:   2.25 1.43 0.62   Up time:       10 days
    Memory usage:  4 % of 2014MB    IP:            192.168.10.230
    CPU temp:      68°C
    Usage of /:    16% of 15G
    
    Last login: Fri Jan 25 08:14:57 2019 from 192.168.10.106
    
    [root@PKHELPER ~]# uptime
     08:19:41 up 10 days, 14:22,  2 users,  load average: 2.31, 1.46, 0.63
    [root@PKHELPER ~]# date
    Fri Jan 25 08:19:48 CET 2019
    [root@PKHELPER ~]# cpufreq-info
    cpufrequtils 008: cpufreq-info (C) Dominik Brodowski 2004-2009
    Report errors and bugs to cpufreq@vger.kernel.org, please.
    analyzing CPU 0:
      driver: cpufreq-dt
      CPUs which run at the same hardware frequency: 0 1 2 3
      CPUs which need to have their frequency coordinated by software: 0 1 2 3
      maximum transition latency: 2.04 ms.
      hardware limits: 120 MHz - 1.37 GHz
      available frequency steps: 120 MHz, 240 MHz, 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.30 GHz, 1.34 GHz, 1.37 GHz
      available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
      current policy: frequency should be within 408 MHz and 1.10 GHz.
                      The governor "ondemand" may decide which speed to use
                      within this range.
      current CPU frequency is 1.10 GHz (asserted by call to hardware).
      cpufreq stats: 120 MHz:0.00%, 240 MHz:0.00%, 480 MHz:99.18%, 648 MHz:0.00%, 816 MHz:0.00%, 960 MHz:0.00%, 1.01 GHz:0.00%, 1.06 GHz:0.00%, 1.10 GHz:0.14%, 1.15 GHz:0.00%, 1.20 GHz:0.00%, 1.22 GHz:0.00%, 1.25 GHz:0.00%, 1.30 GHz:0.68%, 1.34 GHz:0.00%, 1.37 GHz:0.00%  (9633)
    analyzing CPU 1:
      driver: cpufreq-dt
      CPUs which run at the same hardware frequency: 0 1 2 3
      CPUs which need to have their frequency coordinated by software: 0 1 2 3
      maximum transition latency: 2.04 ms.
      hardware limits: 120 MHz - 1.37 GHz
      available frequency steps: 120 MHz, 240 MHz, 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.30 GHz, 1.34 GHz, 1.37 GHz
      available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
      current policy: frequency should be within 408 MHz and 1.10 GHz.
                      The governor "ondemand" may decide which speed to use
                      within this range.
      current CPU frequency is 1.10 GHz (asserted by call to hardware).
      cpufreq stats: 120 MHz:0.00%, 240 MHz:0.00%, 480 MHz:99.18%, 648 MHz:0.00%, 816 MHz:0.00%, 960 MHz:0.00%, 1.01 GHz:0.00%, 1.06 GHz:0.00%, 1.10 GHz:0.14%, 1.15 GHz:0.00%, 1.20 GHz:0.00%, 1.22 GHz:0.00%, 1.25 GHz:0.00%, 1.30 GHz:0.68%, 1.34 GHz:0.00%, 1.37 GHz:0.00%  (9633)
    analyzing CPU 2:
      driver: cpufreq-dt
      CPUs which run at the same hardware frequency: 0 1 2 3
      CPUs which need to have their frequency coordinated by software: 0 1 2 3
      maximum transition latency: 2.04 ms.
      hardware limits: 120 MHz - 1.37 GHz
      available frequency steps: 120 MHz, 240 MHz, 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.30 GHz, 1.34 GHz, 1.37 GHz
      available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
      current policy: frequency should be within 408 MHz and 1.10 GHz.
                      The governor "ondemand" may decide which speed to use
                      within this range.
      current CPU frequency is 1.10 GHz (asserted by call to hardware).
      cpufreq stats: 120 MHz:0.00%, 240 MHz:0.00%, 480 MHz:99.18%, 648 MHz:0.00%, 816 MHz:0.00%, 960 MHz:0.00%, 1.01 GHz:0.00%, 1.06 GHz:0.00%, 1.10 GHz:0.14%, 1.15 GHz:0.00%, 1.20 GHz:0.00%, 1.22 GHz:0.00%, 1.25 GHz:0.00%, 1.30 GHz:0.68%, 1.34 GHz:0.00%, 1.37 GHz:0.00%  (9633)
    analyzing CPU 3:
      driver: cpufreq-dt
      CPUs which run at the same hardware frequency: 0 1 2 3
      CPUs which need to have their frequency coordinated by software: 0 1 2 3
      maximum transition latency: 2.04 ms.
      hardware limits: 120 MHz - 1.37 GHz
      available frequency steps: 120 MHz, 240 MHz, 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz, 1.06 GHz, 1.10 GHz, 1.15 GHz, 1.20 GHz, 1.22 GHz, 1.25 GHz, 1.30 GHz, 1.34 GHz, 1.37 GHz
      available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
      current policy: frequency should be within 408 MHz and 1.10 GHz.
                      The governor "ondemand" may decide which speed to use
                      within this range.
      current CPU frequency is 1.10 GHz (asserted by call to hardware).
      cpufreq stats: 120 MHz:0.00%, 240 MHz:0.00%, 480 MHz:99.18%, 648 MHz:0.00%, 816 MHz:0.00%, 960 MHz:0.00%, 1.01 GHz:0.00%, 1.06 GHz:0.00%, 1.10 GHz:0.14%, 1.15 GHz:0.00%, 1.20 GHz:0.00%, 1.22 GHz:0.00%, 1.25 GHz:0.00%, 1.30 GHz:0.68%, 1.34 GHz:0.00%, 1.37 GHz:0.00%  (9633)
    [root@PKHELPER ~]#
    

     

  14. I will change it on one of my platforms to verify. It will be Orange Pi+ 2 - just a moment ago I have changed it back to original package version (with "408") and rebooted:

     

      ___                               ____  _
     / _ \ _ __ __ _ _ __   __ _  ___  |  _ \(_)  _
    | | | | '__/ _` | '_ \ / _` |/ _ \ | |_) | |_| |_
    | |_| | | | (_| | | | | (_| |  __/ |  __/| |_   _|
     \___/|_|  \__,_|_| |_|\__, |\___| |_|   |_| |_|
                           |___/
    
    Welcome to ARMBIAN 5.70 stable Debian GNU/Linux 9 (stretch) 4.19.13-sunxi
    System load:   1.43 0.34 0.11   Up time:       0 min
    Memory usage:  3 % of 2014MB    IP:            192.168.10.230
    CPU temp:      61°C
    Usage of /:    16% of 15G
    
    Last login: Mon Jan 14 17:56:01 2019 from 192.168.10.210
    
    [root@PKHELPER ~]# cat /etc/default/cpufrequtils
    # WARNING: this file will be replaced on board support package (linux-root-...) upgrade
    ENABLE=true
    MIN_SPEED=408000
    MAX_SPEED=1296000
    GOVERNOR=ondemand
    [root@PKHELPER ~]# date && uptime
    Mon Jan 14 17:58:24 CET 2019
     17:58:24 up 0 min,  1 user,  load average: 0.73, 0.29, 0.10
    [root@PKHELPER ~]# apt list --installed | grep next
    
    WARNING: apt does not have a stable CLI interface. Use with caution in scripts.
    
    linux-dtb-next-sunxi/stretch,now 5.70 armhf [installed]
    linux-headers-next-sunxi/stretch,now 5.70 armhf [installed]
    linux-image-next-sunxi/stretch,now 5.70 armhf [installed]
    linux-stretch-root-next-orangepiplus/stretch,now 5.70 armhf [installed]
    linux-u-boot-orangepiplus-next/stretch,now 5.70 armhf [installed]
    [root@PKHELPER ~]#
    

     

  15. On 1/8/2019 at 7:57 PM, Igor said:


    Move to 4.19.y and it should work as expected. It is available in beta.armbian.com repository for now. Beware that you are going into developer areas where things might be broken.

     

    @Igor, with latest upgrade the "typo" (408 vs 480) is still in cpufrequtils. Is there a chance (I mean: time to do it) to have it corrected in the source? THe related thread:

     

  16. Still OK (I can confirm this for all of my "orange" SBCs):

     

    [root@PKBACKUP ~]# date
    Mon Oct 29 20:21:27 CET 2018
    [root@PKBACKUP ~]# uptime
     20:21:32 up 8 days,  2:32,  1 user,  load average: 0.10, 0.03, 0.01
    [root@PKBACKUP ~]# ll /etc/default/cpufrequtils
    -r--r--r-- 1 root root 175 Oct 18 18:01 /etc/default/cpufrequtils
    [root@PKBACKUP ~]# cat /etc/default/cpufrequtils
    # WARNING: this file will be replaced on board support package (linux-root-...) upgrade
    ENABLE=true
    MIN_SPEED=480000
    MAX_SPEED=1296000
    GOVERNOR=ondemand
    #GOVERNOR=performance
    [root@PKBACKUP ~]#
    

     

  17. After correcting cpufrequtils file - no issues so far:

     

    [root@PKBACKUP ~]# date
    Fri Oct 26 11:03:47 CEST 2018
    [root@PKBACKUP ~]# uptime
     11:03:53 up 4 days, 16:14,  1 user,  load average: 0.00, 0.00, 0.00
    [root@PKBACKUP ~]# ll /etc/default/cpufrequtils
    -r--r--r-- 1 root root 175 Oct 18 18:01 /etc/default/cpufrequtils
    [root@PKBACKUP ~]# cat /etc/default/cpufrequtils
    # WARNING: this file will be replaced on board support package (linux-root-...) upgrade
    ENABLE=true
    MIN_SPEED=480000
    MAX_SPEED=1296000
    GOVERNOR=ondemand
    #GOVERNOR=performance
    [root@PKBACKUP ~]#
    

    Anybody else (who's SBC was impacted by this issue) can verify the same?

  18. For now I have modified cpufrequtils as following for my three boards (orangepipc, orangepiplus 2 GB, orangepiplus2e):

    [root@PKBACKUP ~]# cat /etc/default/cpufrequtils
    # WARNING: this file will be replaced on board support package (linux-root-...) upgrade
    ENABLE=true
    MIN_SPEED=480000
    MAX_SPEED=1296000
    GOVERNOR=ondemand
    #GOVERNOR=performance
    

     

    For orangepizero as following:

    [root@PKOTHER ~]# cat /etc/default/cpufrequtils
    # WARNING: this file will be replaced on board support package (linux-root-...) upgrade
    ENABLE=true
    MIN_SPEED=240000
    MAX_SPEED=1200000
    GOVERNOR=ondemand
    #GOVERNOR=performance
    

     

    Only orangepiplus2e is somehow loaded. With my own backup software, which is run twice a day - but in the past it was enough to freeze the board after a few days.

     

    I will update if the change helped or not.

     

    Question: I have noticed that orangepizero is using lower "MAX" settings. I understand as this device had an issue with overheating. How about other platforms, why lowest frequency settings is 480 MHz, not 240 MHz (which is also supported by H3)?

     

    Some results for my platforms (please note that 816 MHz is common lowest choice for H3):

     

    orangepiplu2e:

    [root@PKBACKUP ~]# armbianmonitor -m
    Stop monitoring using [ctrl]-[c]
    Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
    
    16:36:53: 1296MHz  0.00   6%   1%   2%   0%   1%   0% 42.5°C  0/9
    16:36:58:  816MHz  0.00   0%   0%   0%   0%   0%   0% 43.0°C  0/9
    16:37:03:  816MHz  0.00   0%   0%   0%   0%   0%   0% 42.8°C  0/9
    16:37:08:  816MHz  0.00   0%   0%   0%   0%   0%   0% 42.8°C  0/9
    16:37:14:  816MHz  0.00   0%   0%   0%   0%   0%   0% 40.2°C  0/9
    16:37:19:  816MHz  0.00   0%   0%   0%   0%   0%   0% 43.4°C  0/9
    16:37:24:  816MHz  0.00   0%   0%   0%   0%   0%   0% 41.7°C  0/9
    16:37:29:  816MHz  0.00   0%   0%   0%   0%   0%   0% 41.6°C  0/9
    16:37:34:  816MHz  0.00   0%   0%   0%   0%   0%   0% 42.5°C  0/9^C

     

    orangepiplus:

    [root@PKHELPER ~]# armbianmonitor -m
    Stop monitoring using [ctrl]-[c]
    Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
    
    16:39:34:  816MHz  0.13   0%   0%   0%   0%   0%   0% 44.2°C  0/9
    16:39:39: 1296MHz  0.18   0%   0%   0%   0%   0%   0% 43.8°C  0/9
    16:39:44:  816MHz  0.17   0%   0%   0%   0%   0%   0% 43.9°C  0/9
    16:39:49: 1296MHz  0.16   0%   0%   0%   0%   0%   0% 43.7°C  0/9
    16:39:54:  816MHz  0.14   0%   0%   0%   0%   0%   0% 44.0°C  0/9
    16:39:59: 1296MHz  0.13   0%   0%   0%   0%   0%   0% 44.3°C  0/9
    16:40:04:  816MHz  0.12   0%   0%   0%   0%   0%   0% 44.3°C  0/9
    16:40:09:  816MHz  0.11   0%   0%   0%   0%   0%   0% 43.7°C  0/9
    16:40:15:  816MHz  0.10   0%   0%   0%   0%   0%   0% 43.1°C  0/9
    16:40:20:  816MHz  0.09   0%   0%   0%   0%   0%   0% 43.7°C  0/9^C
    

     

    orangepipc:

    [root@PKTEST ~]# armbianmonitor -m
    Stop monitoring using [ctrl]-[c]
    Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
    
    16:41:11: 1296MHz  0.07   0%   0%   0%   0%   0%   0% 35.7°C  0/9
    16:41:16:  816MHz  0.06   0%   0%   0%   0%   0%   0% 36.7°C  0/9
    16:41:21:  816MHz  0.06   0%   0%   0%   0%   0%   0% 36.8°C  0/9
    16:41:26:  816MHz  0.05   0%   0%   0%   0%   0%   0% 35.7°C  0/9
    16:41:31:  816MHz  0.05   0%   0%   0%   0%   0%   0% 35.9°C  0/9
    16:41:37:  816MHz  0.04   0%   0%   0%   0%   0%   0% 36.5°C  0/9
    16:41:42:  816MHz  0.04   0%   0%   0%   0%   0%   0% 35.8°C  0/9
    16:41:47:  816MHz  0.04   0%   0%   0%   0%   0%   0% 36.4°C  0/9
    16:41:52:  816MHz  0.03   0%   0%   0%   0%   0%   0% 36.2°C  0/9^C
    

    orangepizero:

    [root@PKOTHER ~]# armbianmonitor -m
    Stop monitoring using [ctrl]-[c]
    Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU  C.St.
    
    16:42:33: 1200MHz  0.00   0%   0%   0%   0%   0%   0% 43.0°C  0/8
    16:42:38:  648MHz  0.00   0%   0%   0%   0%   0%   0% 43.1°C  0/8
    16:42:43:  648MHz  0.00   0%   0%   0%   0%   0%   0% 43.1°C  0/8
    16:42:48:  648MHz  0.00   0%   0%   0%   0%   0%   0% 42.6°C  0/8
    16:42:54:  648MHz  0.08   0%   0%   0%   0%   0%   0% 42.5°C  0/8
    16:42:59:  648MHz  0.07   0%   0%   0%   0%   0%   0% 43.6°C  0/8
    16:43:04:  648MHz  0.06   0%   0%   0%   0%   0%   0% 43.0°C  0/8
    16:43:09:  648MHz  0.06   0%   0%   0%   0%   0%   0% 42.6°C  0/8^C
    

     

     

  19. On 9/30/2018 at 7:20 PM, menno said:

    I was able to get the machine stable by setting cpufreq to a fixed frequency. It does not matter if I set it to low or high so mine's now stable running at 1.37Ghz for days.

     

    Could you please point out how to achieve this? All my H3 (also H2+) devices suffer from the issue as described. Even with newest kernel. So, after reading I decided to test stability with "constant cpu frequency".

     

    EDIT: I've done it by:

     

    [root@PKTEST ~]# cat /etc/default/cpufrequtils
    # WARNING: this file will be replaced on board support package (linux-root-...) upgrade
    ENABLE=true
    MIN_SPEED=408000
    MAX_SPEED=1296000
    #GOVERNOR=ondemand
    GOVERNOR=performance
    [root@PKTEST ~]#

     

    Question: would it be possible not to overwrite cpufrequtils file once support package is installed/upgraded?

  20. SUCCESS :)

     

    Story: I have used armbian-config to check Hardware (if my I2C bus is enabled). I have noticed very strange behavior of function: grep was outputted in "usage" mode. I revieved all the scripts and it appeared that line which is searching for "overlays=" is throwing this error. My /boot/armbianEnv.txt didn't have any overlay, especially for I2C, enabled. So, I have added as following (+ overlay prefix):

     

    [root@PKTEST ~]# cat /boot/armbianEnv.txt
    rootdev=UUID=f8301761-6756-4f97-aa80-12c05ea037cf
    extraargs=pty.legacy_count=2
    overlays=i2c0 i2c1 i2c2
    user_overlays=ds1307
    overlay_prefix=sun8i-h3
    usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u,0x1058:0x10b8:u
    [root@PKTEST ~]#

     

    Then I have modified my user overlay file to be as following:

     

    [root@PKTEST ~]# cat /boot/overlay-user/ds1307.dts
    /dts-v1/;
    /plugin/;
    
    / {
            compatible = "allwinner,sun4i-a10", "allwinner,sun7i-a20", "allwinner,sun8i-h3", "allwinner,sun50i-a64", "allwinner,sun50i-h5";
    
            /*
             * Aliases can be used to set the external RTC as rtc0
             * Needs supplying the correct path to the I2C controller RTC is connected to,
             * this example is for I2C1 on H3
             * NOTE: setting time at boot by the kernel
             * may not work in some cases if the external RTC module is loaded too late
             */
            fragment@0 {
                    target-path = "/aliases";
                    __overlay__ {
                            rtc0 = "/soc/i2c@1c2ac00/ds1307@68";
                    };
            };
    
            fragment@1 {
                    target = <&i2c0>;
                    __overlay__ {
                            #address-cells = <1>;
                            #size-cells = <0>;
                            ds1307@68 {
                                    compatible = "dallas,ds1307";
                                    reg = <0x68>;
                                    status = "okay";
                            };
                    };
            };
    };
    [root@PKTEST ~]#
    

     

    The address in fragment@0 is determined by looking where system placed i2c0 bus (I am sure that my RTC is connected to bus 0).

     

    It is giving /dev/rtc1,m which I have verified as following:

     

    [root@PKTEST ~]# ll /dev/rtc*
    crw------- 1 root root 253, 0 May 22  2016 /dev/rtc0
    lrwxrwxrwx 1 root root      4 May 22  2016 /dev/rtc -> rtc0
    crw------- 1 root root 253, 1 May 22  2016 /dev/rtc1
    [root@PKTEST ~]# hwclock -r -f /dev/rtc0
    Sun 22 May 2016 12:38:25 AM CEST  -1.593015 seconds
    [root@PKTEST ~]# hwclock -r -f /dev/rtc1
    Fri 05 Oct 2018 11:57:03 AM CEST  -0.927469 seconds
    [root@PKTEST ~]#
    

     

    Unfortunately it seems that line frogment@0 is not making this device available as rtc0 (it is assigning rtc1):

     

    [root@PKTEST ~]# dmesg | grep -i rtc
    [    3.636229] [drm] Cannot find any crtc or sizes
    [    3.756932] sun6i-rtc 1f00000.rtc: rtc core: registered rtc-sun6i as rtc0
    [    3.756939] sun6i-rtc 1f00000.rtc: RTC enabled
    [    4.641465] [drm] Cannot find any crtc or sizes
    [    9.740172] rtc-ds1307 0-0068: /aliases ID 0 not available
    [    9.741555] rtc-ds1307 0-0068: registered as rtc1
    [root@PKTEST ~]#
    

     

    Can anybody help and answer if it is possible somehow "override" the device? Of course I have my own systemd script to use it and set correct date at boot time. If "overriding" is not possible then I will use it.