guidol

the last weeks I did read about some SBCs not having a ethernet-connection after update. This time I got this with update from 5.10.3-dev to 5.10.4-dev with armbian buster I had the Network-Manager deinstalled and did see my IP which I did configure via /etc/networks but couldnt arrive the K1Plus via ssh/ping and when I used a TTL-RS232 on the K1Plus I cant ping anything in my network or the internet. But dmesg did say the networkport eth0 is up (yellow and green led are also did "work") dwmac-sun8i 1c30000.ethernet eth0: Link is Up - 100Mbps/Full - flow control rx/tx To switch back to a older kernel I had to configure wlan0, but eth0 keept the old IP and seems also did get a DHCP-IP from my IP-Range, so I had also to ifconfig eth0 down Now with wlan0 up I did switch back to kernel 5.10.0-rc7-sunxi64 via armbian-config. After this reconfiguration and a reboot eth0 does work again Without network I did a armbianmonitor -U - the result has been attached here and after the network reconfiguration I did a armbianmonitor -u : System diagnosis information will now be uploaded to http://ix.io/2KY5 armbianmonitor_offline.txt

Yesterday 1 of my 3 NanoPi Neo2 didnt boot complete anymore. Because I had i the last time - I thought that the internal 2.5" HDD has died and couldnt mounted anymore from /etc/fstab Today I checked the 2.5" HDD externally and its fine So I connected a TTL-RS232 for the boot-output and did get: Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. Begin: Running /scripts/local-block ... done. done. 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=47f29e2a-b4bd-451d-88 does not exist. Dropping to a shell! (initramfs) The NanoPi Neo2 isnt finding the UUID for the root-filesystem = my sdcard? I did pu the card in a reader on my other NanoPi Neo2 and used blkid to check the UUID - and did get: /dev/sdb1: UUID="47f29e2a-b4bd-451d-88a9-35998f669cd1" TYPE="ext4" PARTUUID="53e18e13-01" in /etc/fstab there is UUID=47f29e2a-b4bd-451d-88 and here at the "remote" system UUID=47f29e2a-b4bd-451d-88a9-35998f669cd1 Why and when has this UUID extended/expanded (and why isnt it booting with the short version?)? So I did put the new/longer UUID for root in the /etc/fstab on the sdcard and put it back in the half-booting NanoPi Neo2. armbianmonitor -u System diagnosis information has been uploaded to http://ix.io/2KOz Now this Neo2 is booting fine. Should I check my other 2 Neo2 and compare blkid to the /etc/fstab ? On my second (512MB) Neo2 I got the same long UUID for root: UUID=47f29e2a-b4bd-451d-88a9-35998f669cd1 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 /dev/mmcblk0p1: UUID="47f29e2a-b4bd-451d-88a9-35998f669cd1" TYPE="ext4" PARTUUID="53e18e13-01" but on my third (1GB LTS) Neo2 the UUIDs didnt match and it DOES boot and mount root: UUID=47f29e2a-b4bd-451d-88a9-35998f669cd1 / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 /dev/mmcblk0p1: UUID="4e972167-ea53-4c61-9d49-a67b1f839f5f" TYPE="ext4" PARTUUID="d2f285f3-01" [EDIT] edited /etc/fstab to 4e972167-ea53-4c61-9d49-a67b1f839f5f as seen in blkid and it boots also perfect (maybe a differnt u-boot in "flash"?) System diagnosis information has been uploaded to http://ix.io/2KON Is it normal that all 3 Neo2 got 47f29e2a-b4bd-451d-88a9-35998f669cd1 as root-UUID? (UUID of the flash image - should this change after resize?) The 1GB Neo2 does use a Focal-dev-image and the other use a Buster-dev-image.

@Igor zsh itself doesnt seem to affect a "very low" memory-sbc (only zsh-common installled) - and OK its not armbian but pure debian

@Igorin means of MegaByte - how much is zsh bigger? I dont think another shell does use more CPU-power? or only while typing in the command? from the 60-pages presentation: zsh-syntax-highlighting (page 56) HMM: as bash-replacement my colored (ansi-escape-sequences) prompt doenst work in ~/.zshrc How have I to convert that? The PS1 prompt gives me the sequences but doenst interpret them export THEIP="$(/sbin/ifconfig | grep "inet " | grep -v 127.0.0. | awk '{print $2}')" # \u = User # @ = @ # \h = Host # \w = working directory # \$ = # for root (uid=0) or $ for user BRed='\[\033[31;1m\]' BGreen='\[\033[32;1m\]' BYellow='\[\033[33;1m\]' BCyan='\[\033[36;1m\]' BWhite='\[\033[37;1m\]' Reset='\[\033[0m\]' UserPromptPS1='\$' export PS1="${BCyan}\u${BWhite}@${BYellow}\h${BWhite}${BGreen}${THEIP}${BWhite})${BRed}:${BCyan}\w${BRed}${UserPromptPS1}${Reset} " [EDIT] colors seems to be "easy" - here some examples: PROMPT='%F{240}%n%F{red}@%F{green}%m:%F{141}%d$ %F{reset}' PS1="%{%F{red}%}%n%{%f%}@%{%F{blue}%}%m %{%F{yellow}%}%~ %{$%f%}%% " from https://stackoverflow.com/questions/689765/how-can-i-change-the-color-of-my-prompt-in-zsh-different-from-normal-text so my prompt could look like # zsh # %n = User # @ = @ # %m = Host # %~ = working directory # %# = # for root (uid=0) or $ for user BRed='%F{red}' BGreen='%F{green}' BYellow='%F{yellow}' BCyan='%F{cyan}' BWhite='%F{white}' Reset='%F{reset}' UserPromptPS1='%#' export PS1="${BCyan}%n${BWhite}@${BYellow}%m${BWhite}${BGreen}${THEIP}${BWhite})${BRed}:${BCyan}%~${BRed}${UserPromptPS1}${Reset} "

just an idea.... you could try to (because wlan0 is renamed to wlxe84e06870185 ) disable power-save for your wifi-device: iw dev wlxe84e06870185 set power_save off

Does your router have a free DHCP-lease for your OPi3 or did you configure a static IP via nmtui? please provide a log-link for the command armbianmonitor -u

@jeyjey For supported SBCs the easiest way to get minimal or server-only images of armbian is to setup a own armbian-buil-system on a 64bit Ubuntu or a VM: https://docs.armbian.com/Developer-Guide_Build-Preparation/ with the armbian-build-system you will have a menu driven selection if you want to create a image for the type minimal, server or desktop you can select between ubuntu and debian flavour of armbian and the version of ubuntu or debian...as long your SBC is supported by armbian.

change of .dtb (activating 1c22000) & creating overlay (armbian-add-overlay ./sun8i-h3-I2S-out.dts) does also work on uname -a Linux npi-neo-25 5.10.0-sunxi #trunk SMP Wed Dec 16 17:45:03 +03 2020 armv7l GNU/Linux package bsp-kernel[21.02.0-trunk] u-boot[21.02.0-trunk] dtb [21.02.0-trunk] firmware [21.02.0-trunk] config[21.02.0-trunk] branch[dev] like before on kernel 5.9.0

Heureka Today I compiled kernel 5.10.0 (no rc) for the NanoPi Neo2 and now it works agan with my Neo2 and Ubuntu focal where it did work before only with debian buster but also with 5.10.0 rc2 - rc7 The sambsa-server from focal also work with the final 5.10.0 without problems System diagnosis information has been uploaded to http://ix.io/2IjU

and now etcher so: v1.5.111 - (2020-11-23) Remove "Validate write on success" setting. Validation is always enabled, press the "skip" button to skip it. [Alexis Svinartchouk]

via SSH? when I try this I do get there "Loading keyboard submodule ..." and then it will fall back to the personal menu - but it works when Iam directly connected via TTL-serial

This image does boot for me and I can use it after generating locales. This does also work for the newer image Armbian_21.02.0-trunk_Orangepizero_buster_current_5.8.16 and Armbian_21.02.0-trunk_Orangepizero_buster_current_5.9.11 @Igor BTW: Is there a chance to change the following behavior? (why is armbian - like many webpages on the world- thinking I want a TR locales only because Iam in turkey? ) - I want to select a de_DE.UTF-8 or a en_US.UTF-8 - I want a german keyboard - and why we cant change the locale keyboard in armbian-config via a ssh-sesssion? Detected timezone: Europe/Istanbul (+03, +0300) At your location, more locales are possible: 1) ku_TR.UTF-8 2) tr_TR.UTF-8 Please enter your choice:2 Generating locales: tr_TR.UTF-8 Adding console keyboard layout: tr

it seems to be only for a memory-remap function and not for the whole system

looks like a problem with the DHCP-Server - so your sbc isnt getting an DHCP-IP but also get a timeout from the DHCP-transaction.

seems to tbe a problem on devices with A64-CPU We got the "same" problem with Pine64 and the NanoPi A64 Maybe you could get a idea for a solution by checking the attached .dts for the NanoPi A64 in this message?:

Tested SAM again and here some infos for compile and usage ( if you have a "late switching" amplifier on your SBC) : If you want to use direct output via sdl instead of generating .wav / using aplay the .wav ( libsdl2-2.0-0 libsdl2-dev doenst work with SAM ): ------------------------------------------------------------------------------------------ apt install libsdl1.2-dev libsdl1.2debian wget https://github.com/s-macke/SAM/archive/master.zip -O SAM_original_master.zip unzip SAM_original_master.zip cd SAM-master edit flags in Makefile if you want to use of Non-SDL (and save 30MB download and 300MB on HDD) make ./sam 'Hello, how do you do?' ./sam -wav sam_ouput.wav 'Hello, how do you do?' && aplay ./sam_output.wav Creating a empty .wav for activating the amplifier: --------------------------------------------------- ./sam -wav /home/guido/SAM-master/sam_empty.wav '' Shell-Script waiting for audio-amplifier to be ready: ----------------------------------------------------- # Non-SDL sam_amp_nonsdl.sh # ======================================== ./sam -wav /tmp/sam_output.wav $1 aplay /home/guido/SAM-master/sam_empty.wav 2> /dev/null sleep 1 aplay /tmp/sam_output.wav 2> /dev/null rm /tmp/sam_output.wav # ======================================== OR # SDL sam_amp_sdl.sh # ======================================== aplay /home/guido/SAM-master/sam_empty.wav 2> /dev/null sleep 1 ./sam $1 # ======================================== Examples: ------------------------------------------ ./sam_amp_nonsdl.sh 'My name is SAM' ./sam_amp_sdl.sh 'My name is SAM'

@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 I did give you an information in your thread to unmute your headphone in alsamixer - there in the picture its muted.