guidol

@5kft @Hannes Worst @@lex somebody did hear us the analog sound is back in dev kernel/dtb 5.9.1 and now - I think - we have found the missing link: sound was playing but we didnt hear anything on analog-audio because - as I remember right - the option AIF1 Slot 0 Digital DAC was missing. So it couldnt be enabled Now the option is back and the DAC could now enabled again - so no more silence anymore BUT be advised to set AIF DA0 not higher than 17, because then the sound will very fast be distorted/overdriven So here is my kernel

Today I did compile for some SBCs the kernel 5.9.1 dev but had something strange - for me - When I did compile for sunxi I also did get a .deb for sunxi64 and a new sunxi when I did compile for a sunxi64 board. AND as last I did compile for the Odroid C2 (meson64) and I also did get the sunxi and sunxi64 .deb-packages. Is this normal or a new bug? Because in the past I did only get a new .deb-package for the platform which I did actually compile for.

to check if the drive is sleeping: root@npi-neo2-24(192.168.6.24):~# hdparm -C /dev/sda1 /dev/sda1: drive state is: standby Caution: many people report that hdparm -C wakes up the drive

do you got a mount-entry for sda in the /etc/fstab? if yes - how does it look? for my nanoPi Neo2 NAS and its blkid for sda1 it looks like this: root@npi-neo2-24(192.168.6.24):~# blkid /dev/sda1: UUID="4c872e8e-a213-424f-9f10-e4ddd617e848" TYPE="ext4" PARTUUID="20c0b763-01" root@npi-neo2-24(192.168.6.24):~# more /etc/fstab UUID=4e972167-ea53-4c61-9d49-a67b1f839f5f / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 tmpfs /tmp tmpfs defaults,nosuid 0 0 UUID=4c872e8e-a213-424f-9f10-e4ddd617e848 /harddisc ext4 defaults 0 0 [EDIT] I see - "[sda] Unit

Sorry - Iam not a big specialist in dtb-files. So I cant help you with the display It could be very difficult/impossible to support the display via dtb when the kernel doenst support it. But as I remember reading teh forum you did aleready got a own thread for the display (or was it another member of the form)?:

@spender for not loosing the .dtb-change (disabled to okay) you also have to set the dtb-package on hold (here armbian dev example): apt-mark hold linux-dtb-dev-sunxi linux-dtb-dev-sunxi auf Halten gesetzt. apt-mark showhold linux-dtb-dev-sunxi if you are not using dev you could find your dtb-packe with the following command: root@npi-neo-25(192.168.6.25):~# dpkg -l|grep dtb linux-dtb-dev-sunxi 20.08.11 armhf Linux DTB, version 5.9.0-sunxi

@spender PCM5102A-Test with Raspberry did end here - so I could test my instructions with armbian buster and Kernel 5.9.0 again on the NanoPi Neo I had only to - enable (from disabled to okay) i2s@1c22000 in .dtb (decomple and compile) decompile: dtc -I dtb -O dts /boot/dtb/sun8i-h3-nanopi-neo.dtb -o /boot/dtb/sun8i-h3-nanopi-neo.dts compile: dtc -I dts -O dtb /boot/dtb/sun8i-h3-nanopi-neo.dts -o /boot/dtb/sun8i-h3-nanopi-neo.dtb - build / addoverlay ( armbian-add-overlay ./sun8i-h3-I2S-out.dts ) - create /etc/asound.conf [EDIT] - apt-mark

I did it and it does work -rwxr--r-- 1 datashare datashare 43652 Oct 17 17:58 armbian-config_20.11.0-trunk_all.deb -rwxr--r-- 1 datashare datashare 6916332 Oct 17 17:58 armbian-firmware_20.11.0-trunk_all.deb -rwxr--r-- 1 datashare datashare 192712 Oct 17 17:57 linux-dtb-dev-sunxi_20.11.0-trunk_armhf.deb -rwxr--r-- 1 datashare datashare 35322316 Oct 17 17:58 linux-image-dev-sunxi_20.11.0-trunk_armhf.deb -rwxr--r-- 1 datashare datashare 236608 Oct 17 17:48 linux-u-boot-dev-bananapim2berry_20.11.0-trunk_armhf.deb ____ ____ _ __ __ ____ ____ | __ )| _ \(_) | \/ |___ \| __ )

the soundcard H3 Audio Codec is only the "normal" analog audio device - not a I2S-audio device. I also got since 5.8.x kernels the problem with a NanoPi A64 that 1c22c00.codec mapping ok but I cant get any sound out of the I2S-audio-device. I think its not only a NanoPi Neo problem - but when the I2S device like Karte 1: I2Smaster [I2S-master], Gerät 0: 1c22000.i2s-pcm5102a-hifi pcm5102a-hifi-0 [] doenst show up - then there is another problem in your .dtb/.dts

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

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

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 %

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

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 sec

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

@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/

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

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 opti

@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: