guidol

My OPi Zero 512MB with Linux opi-zero 5.9.0-rc7-sunxi #trunk SMP Sat Oct 10 21:41:45 +03 2020 armv7l GNU/Linux after reboot: MiB Mem : 492.1 total, 337.5 free, 56.2 used, 98.4 buff/cache MiB Swap: 246.0 total, 246.0 free, 0.0 used. 419.0 avail Mem governor for all 4 cpus: 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: 5.44 ms. hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz available cpufreq governors: conservative, ondemand, userspace, powersave, performance, schedutil current policy: frequency should be within 480 MHz and 1.01 GHz. The governor "ondemand" may decide which speed to use within this range. current CPU frequency is 816 MHz (asserted by call to hardware). cpufreq stats: 480 MHz:99.80%, 648 MHz:0.05%, 816 MHz:0.07%, 960 MHz:0.03%, 1.01 GHz:0.05% (15687) root@opi-zero(192.168.6.99):~# uptime 15:46:22 up 1 day, 15:25, 1 user, load average: 0.00, 0.00, 0.00

Is that too big? around 1.5MB unzipped root@opi-zero(192.168.6.99):~# armbianmonitor -U > /home/guido/armbianmonitor.txt root@opi-zero(192.168.6.99):~# ls -l /home/guido/armbianmonitor.txt -rw-r--r-- 1 root root 1547948 Oct 11 19:49 /home/guido/armbianmonitor.txt root@opi-zero(192.168.6.99):~# gzip /home/guido/armbianmonitor.txt root@opi-zero(192.168.6.99):~# ls -l /home/guido/armbianmonitor.* -rw-r--r-- 1 root root 500078 Oct 11 19:49 /home/guido/armbianmonitor.txt.gz armbianmonitor.txt.gz

Updated my OPi Zero (512MB) to Armbian 20.08.9 Buster with Linux 5.9.0-rc7-sunxi I got no problems with time/date, because armbian does use chronyd for ntp Is chrony already as ntp-standard included in 4.19.59? And I did read some/most(?) have the 256MB Ram version versus me using the 512MB Ram version. My OPi Zero is using the USB-extension + black cube-case from OPi - connected via Ethernet and not WiFi. BUT armbianmonitor -u doesnt give me a URL at this time: root@opi-zero(192.168.6.99):~# armbianmonitor -u System diagnosis information will now be uploaded to Please post the URL in the forum where you've been asked for.

I got no problems with kernel 5.9.x while using a good power-supply and a 80MB/Sec FAST SanDisk Ultra MicroSD-Card. (Only 12.5 Days because we get here in Turkey from time to time a power-interruption) While using other cards I also got freezes on my 2nd OPi Zero ___ ____ _ _____ / _ \| _ \(_) |__ /___ _ __ ___ | | | | |_) | | / // _ \ '__/ _ \ | |_| | __/| | / /| __/ | | (_) | \___/|_| |_| /____\___|_| \___/ Welcome to Debian GNU/Linux 10 (buster) with Linux 5.9.0-rc5-sunxi System load: 0.00 0.00 0.00 Up time: 12 days 12:36 Memory usage: 11 % of 492MB IP: 192.168.6.99 CPU temp: 73°C

maybe you should - like on my Pinebook- set the display brightness via /etc/rc.local? #set display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --set-brightness 8 I did read out the actual dim value as 2: #read-out display brightness pkexec /usr/sbin/xfpm-power-backlight-helper --get-brightness 2 and I did set (via /etc/rc.local) a for-me-default value of 8 A value of 10 (max.?)was to bright for me

does work fine (console-edition) on my Sunvell T95K Pro (S912) _ ____ __ __ __ _ _ / \ | _ \| \/ | / /_ | || | / _ \ | |_) | |\/| |_____| '_ \| || |_ / ___ \| _ <| | | |_____| (_) |__ _| /_/ \_\_| \_\_| |_| \___/ |_| Welcome to Armbian 20.09 Buster with Linux 5.9.0-rc5-arm-64 No end-user support: built from trunk package bsp-kernel[20.09] u-boot[20.09] dtb [KhadasVim2] firmware [20.09] config[20.09] branch[dev] System load: 1% Up time: 7 min Local users: 2 Memory usage: 8% of 1.85G IP: 192.168.6.62 CPU temp: 57°C Usage of /: 21% of 6.6G Last login: Tue Sep 15 16:53:56 2020 from 192.168.6.17 root@sunvell-t95kpro-arm-64(192.168.6.62):~#

In the past I did also install vsftpd, but some time ago I did see that the package oppenssh not only has openssh-client / openssh-server... As third part there is the openssh-sftp-server which armbian does install. So I never installed vsftpd additionally again The 3 packets in armbian (on my installation) are: openssh-client 1:8.2p1-4ubuntu0.1 arm64 secure shell (SSH) client, for secure access to remote machines openssh-server 1:8.2p1-4ubuntu0.1 arm64 secure shell (SSH) server, for secure access from remote machines openssh-sftp-server 1:8.2p1-4ubuntu0.1 arm64 secure shell (SSH) sftp server module, for SFTP access from remote machines An idea for the configuration of openssh-sftp-server could be found at https://www.allthingsdigital.nl/2013/05/12/setting-up-an-sftp-only-account-with-openssh/

I used Kernel 5.9.0 rc2/rc4 and a NanoPi Neo Core2 - I dont have a Odroid N2

@Igordid see also this partprobe-error-message while transfer from MicroSD to emmc on the NPi Neo Core2 Is this also the reason, why we got this wierd "mountpoint" /var/log.hdd for root?: root@npi-duo-113(192.168.6.113):~# mount /dev/mmcblk0p1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk0p1 on /var/log.hdd type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) root@npi-neo-core2-21(192.168.6.21):~# mount|grep mmc /dev/mmcblk2p1 on / type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) /dev/mmcblk2p1 on /var/log.hdd type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600)

@Igor normally this message should go away when the file /var/run/resize2fs-reboot isnt there/deleted: I tested to delete that file and rebooted, but its recreated at restart System diagnosis information will now be uploaded to http://ix.io/2xc4 Welcome to Armbian 20.11.0-trunk Buster with Linux 5.9.0-rc4-sunxi package bsp-kernel[20.11.0-trunk] u-boot[20.11.0-trunk] dtb [20.11.0-trunk] firmware [20.11.0-trunk] config[20.11.0-trunk] branch[dev] root@npi-duo-113(192.168.6.113):~# rm /var/run/resize2fs-reboot root@npi-duo-113(192.168.6.113):~# ls -l /var/run/resize2fs-reboot ls: cannot access '/var/run/resize2fs-reboot': No such file or directory root@npi-duo-113(192.168.6.113):~# reboot root@npi-duo-113(192.168.6.113):~# ls -l /var/run/resize2fs-reboot -rw-r--r-- 1 root root 0 Sep 11 16:28 /var/run/resize2fs-reboot

isnt a new problem, but I didnt found also a actual solution I did use the little trick to play short "empty" .wav file, wait 2 seconds then play the .wav that should be played. with that the amplifier is enabled (and in 2 secondes it doesnt go in sleep-mode again) so you will hear also the start of your .wav-file aplay -D plughw:0,0 /tmp/empty.wav 2>/dev/null sleep 2 aplay -D plughw:0,0 /tmp/espeak.wav 2>/dev/null

@jscax with lower frequencies than 480Mhz you wouldnt save power or heat... its only a nice lower number

resize message is also here on a actual compiled 5.9.0rc4 and doesnt go away on a NanoPi Neo Core2, but disk is already resized System diagnosis information will now be uploaded to http://ix.io/2x6c Warning: a reboot is needed to finish resizing the filesystem Please reboot the system as soon as possible root@npi-neo-core2-21(192.168.6.21):~# df Filesystem 1K-blocks Used Available Use% Mounted on microsd /dev/mmcblk0p1 7455192 1363500 5983732 19% / emmc /dev/mmcblk2p1 7444644 1402308 5647084 20% / root@npi-neo-core2-21(192.168.6.21):~# resize2fs /dev/mmcblk2p1 resize2fs 1.44.5 (15-Dec-2018) The filesystem is already 1907712 (4k) blocks long. Nothing to do!

I dont know if it works for a samba-dialog-box, but you could try the following options with apt-get (not only apt): root@npi-neo2-22(192.168.6.22):~# man apt-get|grep yes -y, --yes, --assume-yes Automatic yes to prompts; assume "yes" as answer to all prompts and run non-interactively. If an Force yes; this is a dangerous option that will cause apt to continue without prompting if it is Force yes; this is a dangerous option that will cause apt to continue without prompting if it is --force-yes Force yes; this is a dangerous option that will cause apt to continue without prompting if it is force-yes can potentially destroy your system! Configuration Item: APT::Get::force-yes. This is --assume-yes; where --assume-yes will answer yes to any prompt, --trivial-only will answer no. So without echo you could try apt-get install vim -y or apt-get install vim --force-yes

@5kft Yes - does work now correctly. I compiled the kernel/dtb 5.9.0.rc4 after your commit and installed all files. Then I activated the 1.0Ghz/1.1v dtbo and rebooted. All dtbo-files are now loaded correctly: And all CPU-frequencies are available up to the 1008Mhz (1.01Ghz)

it looks like you got some devices connected via usb: hub [ 2.593856] usb 4-1: New USB device found, idVendor=05e3, idProduct=0612, bcdDevice=92.26 [ 2.593869] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.593875] usb 4-1: Product: USB3.1 Hub [ 2.593880] usb 4-1: Manufacturer: GenesysLogic hdd-controller/drives [ 3.231356] usb 5-1: New USB device found, idVendor=18a5, idProduct=0237, bcdDevice= 5.10 [ 3.231368] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.231374] usb 5-1: Product: Portable USB 3.0 Drive [ 3.231380] usb 5-1: Manufacturer: Verbatim [ 3.231385] usb 5-1: SerialNumber: 1702050200116299 [ 3.232094] usb-storage 5-1:1.0: USB Mass Storage device detected [ 3.994332] usb 3-1.2: New USB device found, idVendor=04cf, idProduct=9920, bcdDevice=a3.16 [ 3.994339] usb 3-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.994345] usb 3-1.2: Product: CS8819A3-116 [ 3.994351] usb 3-1.2: Manufacturer: Myson Century, Inc. [ 3.994356] usb 3-1.2: SerialNumber: 100 [ 3.996251] usb-storage 3-1.2:1.0: USB Mass Storage device detected [ 5.029542] scsi 1:0:0:0: Direct-Access Myson CS8819A3-116 0 1.01 PQ: 0 ANSI: 0 CCS [ 5.030007] sd 1:0:0:0: Attached scsi generic sg1 type 0 [ 5.030873] scsi 1:0:0:1: Direct-Access Myson CS8819A3-116 1 1.01 PQ: 0 ANSI: 0 CCS [ 5.031187] sd 1:0:0:1: Attached scsi generic sg2 type 0 [ 5.032058] scsi 1:0:0:2: Direct-Access Myson CS8819A3-116 2 1.01 PQ: 0 ANSI: 0 CCS [ 5.032307] scsi 1:0:0:2: Attached scsi generic sg3 type 0 [ 5.033503] scsi 1:0:0:3: Direct-Access Myson CS8819A3-116 3 1.01 PQ: 0 ANSI: 0 CCS [ 5.033819] sd 1:0:0:3: Attached scsi generic sg4 type 0 [ 5.053809] sd 1:0:0:1: [sdc] Attached SCSI removable disk [ 5.055199] sd 1:0:0:3: [sde] Attached SCSI removable disk [ 5.056112] sd 1:0:0:0: [sdb] Attached SCSI removable disk [ 5.061715] sd 1:0:0:2: [sdd] Attached SCSI removable disk realtek-network-devices [ 2.985723] usb 4-1.3: New USB device found, idVendor=0bda, idProduct=8153, bcdDevice=30.00 [ 2.985735] usb 4-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=6 [ 2.985741] usb 4-1.3: Product: USB 10/100/1000 LAN [ 2.985747] usb 4-1.3: Manufacturer: Realtek [ 2.985752] usb 4-1.3: SerialNumber: 000001 [ 3.300801] usb 3-1.1: new high-speed USB device number 3 using xhci-hcd [ 3.401199] usb 3-1.1: New USB device found, idVendor=0bda, idProduct=b812, bcdDevice= 2.10 [ 3.401211] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3.401217] usb 3-1.1: Product: 802.11ac NIC [ 3.401223] usb 3-1.1: Manufacturer: Realtek [ 3.401228] usb 3-1.1: SerialNumber: 123456 Does the OPi Lite2 H6 hang if you disconnect all this while booting? And does your PowerSupply can supply enough power?

maybe it does help running htop after the login and checking which processes may block the system in the first place... or running dmesg -w after login if there is a kernel-message?

@5kft could you please tell us when @Igor has accepted this commit? I couldnt see the accept at the url above...

@5kft - No Problem - its nice to help getting a stable armbian I could recognize what your fix for the overlay patch will do What will I see as rection when I would recompile the kernel/dtb? For now I edited the dtbs on v1.0 and v1.1 Neo2 that also 960Mz and 1008Mhz is using the same voltage as 816Mhz - so I got these frequencies again (because they where stable for me the last years ) : root@npi-neo2-24(192.168.6.24):~# cpufreq-info hardware limits: 480 MHz - 1.01 GHz available frequency steps: 480 MHz, 648 MHz, 816 MHz, 960 MHz, 1.01 GHz current policy: frequency should be within 480 MHz and 1.01 GHz. The governor "conservative" may decide which speed to use within this range.

@5kft Today I had a strange thing Because the Neo2 does run normally fine - with the default voltage - up to 1008Mhz I did try to activate the 1.0Ghz/1.1V dtb-overlay, but after activating the dtbo and reboot the Neo2. But the Neo2 failed in appying all dtbo (also USB) and does only start in emergency mode (which isnt accessable from outside the NAS-case): After booting with TTL-serial-dongle I logged in emergency mode with the root-password and deactivated the 1.0Ghz/1.1V-dtbo saves/rebootet. And now its working fine again - this the the NEW INSTALLED 5.9.0rc2/debian buster on my small Neo2 (512MB) cpufreq-info only does show cpu-frequencys from 480 to 816Mhz So the dev-dtb is very conservative at the CPU-Speed for the Neo2

USBImager V1.0..4 is now 2 months old, but I today recommend by cnx-software: https://www.cnx-software.com/2020/09/08/usbimager-a-lightweight-alternative-to-balenaetcher/ Filter out drives on the same disk as C: https://gitlab.com/bztsrc/usbimager/-/commit/1775cdc628a3d28ce454c181952aa283334d0991

Default User/Password for a new flashed image on SDCard is User: root Initial Password: 1234 after that you have to enter a new root-password

got this dmesg-output alos in 5.8.7, but no output from analog-audio from the NPi A64

The small Neo2 is also booting fine with 5.9.0rc2 debian buster: System diagnosis information will now be uploaded to http://ix.io/2wjt USB port are recognized ans also the /dev/sda(1) on the USB-Port-controller Dont know why this didnt work as upgrade from 5.8.3 Now I will mount the old SDCard and transfer the config-files- now for the first small Neo2 - laster for the second one

the .debs I did compile on my armbian-build-system. But I also got the same problem with the 5.9.0rc2-dtb-deb from apt update/upgrade. The newly compiles 5.9.0rc2 Ubuntu focal does start without problem (no dtbo-errors) on the small Neo2. Now Iam thinking about doing the same with a fresh compiled 5.9.0rc2 with debian buster? 5_8_3_linux-dtb-dev-sunxi64_20.08.0-trunk_arm64.deb 5_9_0_rc2_linux-dtb-dev-sunxi64_20.08.0-trunk_arm64.deb