guidol

@j___r on the page for the hc1 is written that it is a down-stripped version of the Odroid xu4, so you can check the download-directory of the xu4: https://uk.mirrors.fossho.st/armbian/dl/odroidxu4/archive/ but I think you cant upgrade this via armbian-config from 4.1.4 to Kernel 5.4.x

Which serial ouput do you need/mean? From the boot-process while using eth0?

Also got the problem with the official download-image Armbian_20.08.1_Orangepi-r1_buster_current_5.8.5.img eth0 orange/green led does lit , orange stays, green blink for some seconds, both goes off: like last year: [ 33.780717] vcc3v0: disabling [ 33.780731] vcc5v0: disabling [ 33.877210] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 34.901031] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [ 37.973216] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 38.996979] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [ 40.021229] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 41.044983] dwmac-sun8i 1c30000.ethernet eth0: Link is Down [ 42.069337] dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx [ 43.093067] dwmac-sun8i 1c30000.ethernet eth0: Link is Down or here: https://serverfault.com/questions/585442/eth0-nic-link-is-down-repeating-message-in-kernel-log usb/enx-ether is OK: [ 432.833832] IPv6: ADDRCONF(NETDEV_CHANGE): enxc0742bffe8ff: link becomes ready [ 432.834587] r8152 3-1:1.0 enxc0742bffe8ff: carrier on power is enough/good from a original RPI-powersupply (5.1V)

Yes- the A40i is only another pin-compatible temperature version of the R40. And the R40 (quadcore-A7-cpu) seems to be a NON-pin-compatible version of the "old" A20-CPU (duacore-A7-CPU) which was on the Banana Pi M1 (Pro)

I tested my OPi R1 these days with kernel 5.10.0-rc2 and got problems with eth0 like on some versions in the past. You could see this issue in dmesg showing the eth0-device-link going down/up serveral times (eth0 ist the ethernet-port near the serial-ttl-port, the other enx-ethernet is connectec via usb) My enx-ethernet device is working here fine, but now my eth0 device has stopped working completly I use /etc/network/interfaces for setting the IP. armbian does set the IP but eth0 cant use the net ___ ____ _ ____ _ / _ \| _ \(_) | _ \/ | | | | | |_) | | | |_) | | | |_| | __/| | | _ <| | \___/|_| |_| |_| \_\_| Welcome to Armbian 20.11.0-trunk Buster with Linux 5.10.0-rc2-sunxi No end-user support: built from trunk 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@opi-r1-101(192.168.6.101):~# ifconfig enxc0742bffe8ff: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.6.101 netmask 255.255.255.0 broadcast 192.168.6.255 ether c0:74:2b:ff:e8:ff txqueuelen 1000 (Ethernet) RX packets 247 bytes 17017 (16.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 90 bytes 9447 (9.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 System diagnosis information has been uploaded to http://ix.io/2DDi

Check for R40-CPU, because A40i and A40pro are variants that differ in applicable temperatures range (industrial and military) against the R40: http://linux-sunxi.org/A40i Allwinner R40 (sun8i) SoC features a Quad-Core Cortex-A7 ARM CPU, and a Mali400 MP2 GPU from ARM. It is a not-pin-compatible quad core sucessor of the A20. It's also known as the Allwinner T3 for In-Car Entertainment usage. Allwinner V40 (sun8i) SoC features a Quad-Core Cortex-A7 ARM CPU, and a Mali400 MP2 GPU from ARM. It is the automotive version of R40. and https://www.cnx-software.com/2018/05/06/allwinner-unveils-a40i-a40pro-and-a60i-a60pro-industrial-military-grade-processors/ https://www.facebook.com/pg/sinovoipbpi/photos/?tab=album&album_id=1934780613223842 BPI-M2 Ultra with allwinner A40i chip, A40i is LTS chip design more than 10 years You can check images for the BananaPi M2 Berry or M2 Ultra (R40 / V40 CPU) https://www.armbian.com/bananapi-m2u/ because there seem to be versions of the Ultra with A40i-CPU: https://german.alibaba.com/product-detail/allwinner-a40i-arm-2gb-board-banana-pi-development-board-60776126234.html https://de.aliexpress.com/item/32765110548.html http://forum.banana-pi.org/t/bpi-m2-ultra-and-bpi-m2-berry-can-use-allwinner-a40i-chip-onboard/6584

is your "cleaner" NEO2 under ubuntu or debian?

@5kft I will take the Samba-version which armbian does deliver me for Ubuntu Focal: 2:4.11.6+dfsg-0ubuntu1.6 and for debian buster: 2:4.9.5+dfsg-5+deb10u1 its interesting - for me - that the newer version 4.11.6 does crash with kernel 5.10.0-rc2 on ubuntu focal but the older 4.9.5 has no problems using kernel 5.10.0-rc2 under debain buster... Thanks for the informations/links - so I would stay with kernel 5.9.1 on ubuntu focal for now

@Levent Erenler did you try to adress card 0 ( sun50ia64audio [sun50i-a64-audio] ) directly? Internet-Radio-stream: mpg123 -v -b 1024 -a hw:0,0 -@ http://norawebstreams-stream22.radiohost.de/nora-80er_mp3-192 or use a /etc/asound.conf: root@npi-a64-116(192.168.6.116):~# more /etc/asound.conf pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 }

my alsamixer-setting doesnt look very different to yours:

@Levent Erenler I did give you an information in your thread to unmute your headphone in alsamixer - there in the picture its muted.

@Levent Erenler please unmute your muted (MM) Headphone. Select Headphone and press M to unmute (00 in green) your Headphone-Connector in the alsamixer to get analog-audio BTW: the dmesg-message isnt right but aplay does show you the soundcard correct The same here: root@npi-a64-116(192.168.6.116):~# dmesg|grep -i sound [ 1.163817] Advanced Linux Sound Architecture Driver Initialized. [ 2.863443] No soundcards found.

Today I updated some SBCs - 2x NanoPi Neo2 with 512MB Ram (debian buster) - 1x NanoPi Neo2 with 1GB Ram (ubuntu focal) - 1x BanaPI M2 Berry (debian buster) to kernel 5.10.0-rc2 DEV which are running a samba-server which is installed via "apt install samba" and not via the armbian-config SOFTYS. They are do run since serveral kernel-version - also with 5.9.1 But after the update my NanoPi Neo2 with 1GB Ram cant be connected from Linux or Windows 10 to his samba-server. It looks like samba freezed: mount -t cifs -o vers=3.0,user=guido,password=this_isnt_mypwd,domain=guido,dir_mode=0777,file_mode=0777 //192.168.6.24/data /smbtest mount error(11): Resource temporarily unavailable I checked the config and even reinstalled samba on the NanoPi Neo2 1GB Ram but CANT connect to the data-share Because the last change was the kernel I did go back to 5.9.1 via armbian-config on this NanoPi Neo2 1GB Ram and the samba-server is now working again. Another difference between the NanoPi Neo2 is that the 512MB-version do run debian buster and the 1GB-version do run ubuntu focal. So I dont know directly if it is the board-version whcih has the problem or if the ubuntu focal version has a problem with the kernel 5.10.0-rc2 Also here all samba-servers running (debian buster with 5.10.0-rc2 and ubuntu focal with 5.9.1): System diagnosis information NanoPi Neo2 512MB http://ix.io/2Dlw NanoPi Neo2 1GB Ram http://ix.io/2Dlx BPi M2 Berry http://ix.io/2Dlv

For me it does work, but I dont know if @Hannes Worst did had success Here are the "warnings" while decompiling the .dtb to .dts (see attachment) : root@npi-a64-116(192.168.6.116):/boot/dtb/allwinner# dtc -I dtb -O dts /boot/dtb/allwinner/sun50i-a64-nanopi-a64.dtb -o /boot/dtb/allwinner/sun50i-a64-nanopi-a64_kernel_591.dts /boot/dtb/allwinner/sun50i-a64-nanopi-a64_kernel_591.dts: Warning (unit_address_vs_reg): /sound/simple-audio-card,dai-link@0: node has a unit name, but no reg property /boot/dtb/allwinner/sun50i-a64-nanopi-a64_kernel_591.dts: Warning (avoid_unnecessary_addr_size): /sound: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property /boot/dtb/allwinner/sun50i-a64-nanopi-a64_kernel_591.dts: Warning (avoid_unnecessary_addr_size): /soc/dsi@1ca0000: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property I dont know if this .dts will work with lower kernel numbers root@npi-a64-116(192.168.6.116):/boot# uname -a Linux npi-a64-116 5.9.1-sunxi64 #trunk SMP Mon Oct 26 18:14:55 +03 2020 aarch64 GNU/Linux OR Linux npi-a64-116 5.10.0-rc2-sunxi64 #trunk SMP Sat Nov 7 14:11:13 +03 2020 aarch64 GNU/Linux sun50i-a64-nanopi-a64_kernel_591.dts sun50i-a64-nanopi-a64_kernel_510rc2.dts

@Medapayne create a /etc/asound.conf to get the analog audio card as default. whats the output of aplay -l Mine: ___ ____ _ _____ / _ \| _ \(_) |__ /___ _ __ ___ | | | | |_) | | / // _ \ '__/ _ \ | |_| | __/| | / /| __/ | | (_) | \___/|_| |_| /____\___|_| \___/ Welcome to Armbian 20.08.9 Buster with Linux 5.9.1-sunxi root@opi-zero(192.168.6.99):~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: Codec [H3 Audio Codec], device 0: CDC PCM Codec-0 [CDC PCM Codec-0] Subdevices: 1/1 Subdevice #0: subdevice #0 root@opi-zero(192.168.6.99):~# more /etc/asound.conf pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 } and enable [*] analog-codec in armbian-config -> system -> hardware

I didnt got any diiference in function between buster & focal with pihole - but Iam only uing IPv4

@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-information als alsamixer-setting for analog-audio (sun50i-a64-audio): _ _ ____ _ _ __ _ _ | \ | | _ \(_) / \ / /_ | || | | \| | |_) | | / _ \| '_ \| || |_ | |\ | __/| | / ___ \ (_) |__ _| |_| \_|_| |_| /_/ \_\___/ |_| Welcome to Debian GNU/Linux 10 (buster) with Linux 5.9.1-sunxi64 No end-user support: built from trunk 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-a64-116(192.168.6.116):~# uname -a Linux npi-a64-116 5.9.1-sunxi64 #trunk SMP Mon Oct 26 18:14:55 +03 2020 aarch64 GNU/Linux root@npi-a64-116(192.168.6.116):~# more /etc/os-release PRETTY_NAME="Debian GNU/Linux 10 (buster)" NAME="Debian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=debian HOME_URL="https://www.debian.org/" SUPPORT_URL="https://www.debian.org/support" BUG_REPORT_URL="https://bugs.debian.org/" root@npi-a64-116(192.168.6.116):~# aplay -l **** List of PLAYBACK Hardware Devices **** card 0: sun50ia64audio [sun50i-a64-audio], device 0: 1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0 [1c22c00.dai-sun8i-codec-aif1 sun8i-codec-aif1-0] Subdevices: 0/1 Subdevice #0: subdevice #0 card 1: sun50ia64hdmi [sun50i-a64-hdmi], device 0: 1c22800.i2s-i2s-hifi i2s-hifi-0 [1c22800.i2s-i2s-hifi i2s-hifi-0] Subdevices: 1/1 Subdevice #0: subdevice #0 root@npi-a64-116(192.168.6.116):~# alsamixer Card: sun50i-a64-audio Value: Item: 83 Headphone [dB gain: -8.00] Mixer Headphone Source [Mixer] 15 AIF1 DA0 [dB gain: -24.00, -24.00] Stereo AIF1 DA0 Stereo [Stereo] Enable AIF1 Slot 0 Digital DAC 82 DAC [dB gain: 18.75, 18.75] Enable DAC Reversed

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 Not Ready" Does it sleep via hdparm? Maybe the controller is reset the right way only on a hard-reset? If your drive does sleep maybe it doesnt respond right (or in the right time) while using the soft-reset

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 hold linux-dtb-dev-sunxi - reboot and it works again very well: _ _ ____ _ _ _ | \ | | _ \(_) | \ | | ___ ___ | \| | |_) | | | \| |/ _ \/ _ \ | |\ | __/| | | |\ | __/ (_) | |_| \_|_| |_| |_| \_|\___|\___/ Welcome to Armbian 20.08.11 Buster with Linux 5.9.0-sunxi package bsp-kernel[20.08.11] u-boot[20.08.11] dtb [20.08.11] firmware [20.08.11] config[20.08.11] branch[dev] root@npi-neo-25(192.168.6.25):~# aplay -l **** Liste der Hardware-Geräte (PLAYBACK) **** Karte 0: I2Smaster [I2S-master], Gerät 0: 1c22000.i2s-pcm5102a-hifi pcm5102a-hifi-0 [1c22000.i2s-pcm5102a-hifi pcm5102a-hifi-0] Sub-Geräte: 1/1 Sub-Gerät #0: subdevice #0 root@npi-neo-25(192.168.6.25):~# nano /etc/asound.conf # ==================================================== pcm.!default { type hw card 0 device 0 } ctl.!default { type hw card 0 } # ==================================================== root@npi-neo-25(192.168.6.25):/toshiba# mpg123 -v -b 1024 ./Powerup.mp3 sun8i-h3-I2S-out.dts

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 ____ ____ _ __ __ ____ ____ | __ )| _ \(_) | \/ |___ \| __ ) | _ \| |_) | | | |\/| | __) | _ \ | |_) | __/| | | | | |/ __/| |_) | |____/|_| |_| |_| |_|_____|____/ Welcome to Armbian Buster with Linux 5.9.0-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@bpi-m2-berry(192.168.6.20):~# ifconfig eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.6.20 netmask 255.255.255.0 broadcast 192.168.6.255 ether 02:53:bc:93:a8:02 txqueuelen 1000 (Ethernet) RX packets 329 bytes 35595 (34.7 KiB) RX errors 0 dropped 2 overruns 0 frame 0 TX packets 315 bytes 35070 (34.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 37 root@bpi-m2-berry(192.168.6.20):~# dmesg|grep eth0 [ 8.326164] dwmac-sun8i 1c50000.ethernet eth0: PHY [stmmac-0:01] driver [RTL8211E Gigabit Ethernet] (irq=POLL) [ 8.329007] dwmac-sun8i 1c50000.ethernet eth0: No Safety Features support found [ 8.329028] dwmac-sun8i 1c50000.ethernet eth0: No MAC Management Counters available [ 8.329037] dwmac-sun8i 1c50000.ethernet eth0: PTP not supported by HW [ 8.329052] dwmac-sun8i 1c50000.ethernet eth0: configuring for phy/rgmii link mode [ 10.454163] dwmac-sun8i 1c50000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx

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