guidol

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

@5kft the 1GB version has: root@npi-neo2-24(192.168.6.24):~# ls -l /sys/class/leds total 0 lrwxrwxrwx 1 root root 0 Sep 6 14:40 nanopi:green:status -> ../../devices/platform/leds/leds/nanopi:green:status lrwxrwxrwx 1 root root 0 Sep 6 14:40 nanopi:red:pwr -> ../../devices/platform/leds/leds/nanopi:red:pwr and the 512MB (Version 1.0) has: root@npi-neo2-22(192.168.6.22):~# ls -l /sys/class/leds total 0 lrwxrwxrwx 1 root root 0 Jan 1 1970 nanopi:blue:status -> ../../devices/platform/leds/leds/nanopi:blue:status lrwxrwxrwx 1 root root 0 Jan 1 1970 nanopi:green:pwr -> ../../devices/platform/leds/leds/nanopi:green:pwr root@npi-neo2-23(192.168.6.23):~# ls -l /sys/class/leds total 0 lrwxrwxrwx 1 root root 0 Jan 1 1970 nanopi:blue:status -> ../../devices/platform/leds/leds/nanopi:blue:status lrwxrwxrwx 1 root root 0 Jan 1 1970 nanopi:green:pwr -> ../../devices/platform/leds/leds/nanopi:green:pwr

@5kft @Hannes Worst it seems that current 5.8.7 is missing some modules for the analog audio (or they are named in a other way) than legacy 5.4.63, because with the legacy image analog-audio does work. I do see much more sound-modules loaded than in current 5.8.7: Module Size Used by sun50i_codec_analog 28672 1 sun8i_codec 28672 1 snd_soc_simple_card_utils 20480 1 snd_soc_simple_card sun4i_i2s 24576 4 sun8i_drm_hdmi 24576 0 snd_soc_core 176128 7 sun4i_i2s,snd_soc_spdif_tx,snd_soc_hdmi_codec,sun50i_codec_analog,sun8i_codec,snd_soc_simple_card_utils,snd_soc_simple_card dw_hdmi 40960 2 sun8i_drm_hdmi,dw_hdmi_i2s_audio ac97_bus 16384 1 snd_soc_core snd_pcm_dmaengine 16384 1 snd_soc_core cec 69632 2 dw_hdmi_cec,dw_hdmi snd_pcm 110592 5 sun4i_i2s,snd_soc_hdmi_codec,sun8i_codec,snd_soc_core,snd_pcm_dmaengine snd_timer 40960 1 snd_pcm snd 86016 8 snd_soc_hdmi_codec,snd_timer,snd_soc_core,snd_pcm soundcore 16384 1 snd sun4i_drm 20480 0 sun4i_frontend 16384 1 sun4i_drm sun4i_tcon 32768 1 sun4i_drm sun8i_mixer 40960 0 sun8i_tcon_top 16384 3 sun8i_drm_hdmi,sun4i_tcon,sun4i_drm dwmac_sun8i 28672 0 mdio_mux 16384 1 dwmac_sun8i

@5kft I think so...got no TTL-Log because all are screwed in the silver NAS-Case from FriendlyARM. I did bought it later than the small ones and it was named Neo2 LTS at this time. Can I check this via commandline?

@5kft another thing: I got a second Neo2, but the 1GB Ram version which was running kernel 5.8.3 with Ubuntu focal This Neo2 has been upgraded via apt update/upgrade to kernel 5.9.0rc2 and DOES BOOT: System diagnosis information will now be uploaded to http://ix.io/2wiQ I did try this also on my first Neo2 (512MB Ram, Version 1.0) which was running kernel 5.8.3 but with Debian buster and it failed via apt update/upgrade like before when I did install the newly compiled .deb files Now I did know how to go back - this one is back on 5.8.3 where the dtb-overlay for usbhost 1&2 could be loaded I do now compile kernel 5.9.0rc2 with Ubuntu focal and try to put this image on my first/smaller Neo2 (I also have a third one in the smaller configuration which is also running 5.8.3 with Debian Buster)

My Neo2 is/was also with 5.8.3 at -dev: Welcome to Armbian buster with Linux 5.8.3-sunxi64 package bsp-kernel[20.08.0-trunk] u-boot[20.08.0-trunk] dtb [20.08.0-trunk] firmware [20.08.0-trunk] config[20.08.0-trunk] branch[dev] root@npi-neo2-22(192.168.6.22):~# ls -l /toshiba/neo2_kernel_583/ total 41984 -rwxrwxrwx 1 root root 43636 Aug 24 20:56 armbian-config_20.08.0-trunk_all.deb -rwxrwxrwx 1 root root 6671580 Aug 24 20:56 armbian-firmware_20.08.0-trunk_all.deb -rwxrwxrwx 1 root root 77316 Aug 24 20:55 linux-dtb-dev-sunxi64_20.08.0-trunk_arm64.deb -rwxrwxrwx 1 root root 32077924 Aug 24 20:56 linux-image-dev-sunxi64_20.08.0-trunk_arm64.deb -rwxrwxrwx 1 root root 268324 Aug 24 20:47 linux-u-boot-dev-nanopineo2_20.08.0-trunk_arm64.deb 5.8.3 System diagnosis information has been uploaded to http://ix.io/2wfb and my u-boot .deb for 5.9.0rc2 was also at -dev level: root@npi-neo2-22(192.168.6.22):~# ls -l /toshiba/neo2_kernel_590rc2/ total 41984 -rwxrwxrwx 1 root root 43648 Sep 4 18:06 armbian-config_20.08.0-trunk_all.deb -rwxrwxrwx 1 root root 6775404 Sep 4 18:06 armbian-firmware_20.08.0-trunk_all.deb -rwxrwxrwx 1 root root 77584 Sep 4 18:05 linux-dtb-dev-sunxi64_20.08.0-trunk_arm64.deb -rwxrwxrwx 1 root root 32199212 Sep 4 18:06 linux-image-dev-sunxi64_20.08.0-trunk_arm64.deb -rwxrwxrwx 1 root root 268036 Sep 4 17:54 linux-u-boot-dev-nanopineo2_20.08.0-trunk_arm64.deb

@5kft I didnt see (and expect) any errors while installing the u-boot package via dpkg, because it did work for months/years so well on all of my SBCs here the dpkg-output you requested: root@npi-neo2-22(192.168.6.22):~# dpkg --list | grep boot ii klibc-utils 2.0.6-1 arm64 small utilities built with klibc for early boot ii linux-u-boot-nanopineo2-dev 20.08.0-trunk arm64 Uboot loader 2020.04 ii sysfsutils 2.1.0+repack-5 arm64 sysfs query tool and boot-time setup ii u-boot-tools 2019.01+dfsg-7 arm64 companion tools for Das U-Boot bootloader

the last time - I truly know - it worked was on kernel 5.6.2 (also 5.4.x) - but 5.7.x I didnt installed on the NPI A64

/boot is big enough, because armbian is only using 1 partition (on my install) and Iam using a 8GB MicroSDCard After using a TTL-serial-dongle I did found that kernel 5.9.0rc2 had give me the 2 following problems: 1.) is seems to be searching for a UUID/BKLID which is too short: Its searching for f17c5ebe-dc6c-4c52-831e-f2265 but the full name is f17c5ebe-dc6c-4c52-831e-f226539501a5 which was correct in /boot/armbianEnv.txt and /etc/fstab Gave up waiting for root file system device. Common problems: - Boot args (cat /proc/cmdline) - Check rootdelay= (did the system wait long enough?) - Missing modules (cat /proc/modules; ls /dev) ALERT! UUID=f17c5ebe-dc6c-4c52-831e-f2265 does not exist. Dropping to a shell! Rebooting automatically due to panic= boot argument [ 43.246465] reboot: Restarting system I mounted the MicroSDCard on my other Neo2 and did a fschk /dev/sdb1 (for the card). After that the Neo2 did boot from this card, but couldnt find the NAS-HDD which is connected via USB (USB3-SATA on USB2.0 port) 2.) the kernel 5.9.0rc2 couldnt load the dtb-overlays (also while now booting from the card and root 7 is there, but the overlays doenst seem to be compatibe): Applying kernel provided DT overlay sun50i-h5-cpu-clock-1.0GHz-1.1v.dtbo failed on fdt_overlay_apply(): FDT_ERR_NOTFOUND 504 bytes read in 6 ms (82 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost1.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ 504 bytes read in 5 ms (97.7 KiB/s) Applying kernel provided DT overlay sun50i-h5-usbhost2.dtbo failed on fdt_overlay_apply(): FDT_ERR_BADMAGIC base fdt does did not have a /__symbols__ node make sure you've compiled with -@ Error applying DT overlays, restoring original DT Because booting the 5.9.0rc2 did work - I reinstalled the kernel 5.8.3 (Image, u-boot, dtb, firmware and config) via dpkg. After reboot the complete system is working like before without reinstalling I only deleted some kernel 5.4.x-dtb directorys from /boot Here some more TTL-Boot-log for your information: Dont know why kernel 5.9.0rc2 was booting in the TTL-Log with U-Boot 2019.04-armbian (Nov 18 2019 - 21:52:14 +0100) Is there more to do as installing the new u-boot.deb? Wasnt there a option to update u-boot via armbian-config? e.g. Install to/update boot loader ==> (2) Install/Update Bootloader on SD/eMMC I think (1) Boot from SD - system on SATA, USB or NVMe isnt the right for me

Today I did compile Kernel 5.9.0rc2 dev (u-boot/dtb etc) for NanoPi Neo2 and after installing the .debs to the NanopI Neo2 it doenst boot anymore... Tomorrow(?) I have to get the Neo2 out of the NAS-Case and check with a serial-TTL what is failing Before this it was running kernel 5.8.3 Is there a way to "install" the debs from 5.8.3 to the card "offline"?

Also no analog sound with Kernel 5.9.0rc2 and (for me) strange: root@npi-a64(192.168.6.116):~# dmesg|grep -i sound [ 1.283838] Advanced Linux Sound Architecture Driver Initialized. [ 2.771885] No soundcards found. [ 6.301885] input: sun50i-a64-audio Headphone Jack as /devices/platform/sound/sound/card0/input1

@Hannes Worst also on the NanoPi A64 with newer mainline kernel is missing the full function of the analog audio (its shown, but doenst make any sound) HDMI-Audio is working on the NanoPi A64 - but I couldnt find any .dtb-changes for the problem with the analog-audio

stockfish v12 with NNUE (neural network) is now available https://blog.stockfishchess.org/post/628172810852925440/stockfish-12 https://github.com/official-stockfish/Stockfish/commit/84f3e867903f62480c33243dd0ecbffd342796fc for compiling v12 with NNUE on aarch64 (64bit) I had to change a few bits in the makefile: for the first time I inserted aarch64 in the check of supported platforms: ( but you could also use the SUPPORTED_ARCH=true while compiling) without one of these 2 the compile will end with a error 1 # explicitly check for the list of supported architectures (as listed with make help), # the user can override with `make ARCH=x86-32-vnni256 SUPPORTED_ARCH=true` ifeq ($(ARCH), $(filter $(ARCH), \ x86-64-vnni512 x86-64-vnni256 x86-64-avx512 x86-64-bmi2 x86-64-avx2 \ x86-64-sse41-popcnt x86-64-modern x86-64-ssse3 x86-64-sse3-popcnt \ x86-64 x86-32-sse41-popcnt x86-32-sse2 x86-32 ppc-64 ppc-32 \ armv7 armv7-neon armv8 aarch64 apple-silicon general-64 general-32)) SUPPORTED_ARCH=true else SUPPORTED_ARCH=false endif as before I deleted the "else if" from this check - for not getting the unsupported -m64 option: (here we dont use Android ) ifeq ($(COMP),gcc) comp=gcc CXX=g++ CXXFLAGS += -pedantic -Wextra -Wshadow ifeq ($(arch),$(filter $(arch),armv7 armv8)) ifeq ($(OS),Android) CXXFLAGS += -m$(bits) LDFLAGS += -m$(bits) endif endif ifeq ($(arch),$(filter $(arch),armv7)) LDFLAGS += -latomic endif ifneq ($(KERNEL),Darwin) LDFLAGS += -Wl,--no-as-needed endif endif and created a new aarch64 platform entry. This time with arch=armv8 and popcnt = yes and neon = yes, because a gcc check did show me armv8 and cortex-a53 as tune options - and armv8 has in the original Makefile these options active included. GCC Check: ============================================================ gcc -march=native -Q --help=target | grep -- '-march=' -march= armv8-a+crypto+crc gcc -mtune=native -Q --help=target | grep -- '-mtune=' -mtune= cortex-a53 ============================================================ Also activated the 64bits for the aarch64-platform: ifeq ($(ARCH),aarch64) arch = armv8 prefetch = yes popcnt = yes neon = yes bits = 64 endif BUT stockfish doesnt show the 64 for 64bit at the version string - stockfish v10 and v11 did this before: