guidol

Yes its seems also like a 2019-version (didnt changed the count - becaus it isnt a backup - only to get version: root@odroid-c2 : /home/guido# dd if=/dev/mmcblk0 of=./installed_uboot.bin skip=97 count=1376 1376+0 records in 1376+0 records out 704512 bytes (705 kB, 688 KiB) copied, 0.0463896 s, 15.2 MB/s root@odroid-c2 : /home/guido# strings ./installed_uboot.bin | grep "U-Boot 20" U-Boot 2019.10-armbian (Dec 01 2019 - 09:31:42 +0300) odroid-c2

but I dont know if the content of u-boot.bin is installed in my mmcblk0 And I dont want to install the newer one, when my eth0 may be stop to work

The command strings /dev/mmcblk0 | grep 'U-Boot 20' gives me U-Boot 2019.10-armbian (Dec 01 2019 - 09:31:42 +0300) odroid-c2 # U-Boot 2020.04 Configuration Compiled with U-Boot 2019.01+dfsg-7 # U-Boot 2021.01 Configuration # U-Boot 2021.01 Configuration # U-Boot 2019.10 Configuration U-Boot 2013.10-rc2-08400-g0490093 (Oct 11 2013 - 00:40:21) Allwinner Technology U-Boot 2011.09-rc1-00000-geb98797 (Dec 13 2017 - 15:44:38) Allwinner Technology U-Boot 2011.09-rc1-00000-gc1cb2f9 (May 30 2014 - 10:19:03) Allwinner Technology U-Boot 2021.01-armbian (Feb 11 2021 - 21:19:38 +0300) odroid-c2 U-Boot 2013.10-rc2-08400-g0490093 (Oct 11 2013 - 00:40:21) Allwinner Technology U-Boot 2011.09-rc1-00000-geb98797 (Dec 13 2017 - 15:44:38) Allwinner Technology U-Boot 2011.09-rc1-00000-gc1cb2f9 (May 30 2014 - 10:19:03) Allwinner Technology U-Boot 2013.10-rc2-08400-g0490093 (Oct 11 2013 - 00:40:21) Allwinner Technology U-Boot 2011.09-rc1-00000-geb98797 (Dec 13 2017 - 15:44:38) Allwinner Technology U-Boot 2011.09-rc1-00000-gc1cb2f9 (May 30 2014 - 10:19:03) Allwinner Technology U-Boot 2020.10-armbian (Jan 26 2021 - 12:00:46 +0300) odroid-c2 U-Boot 2020.10-armbian (Jan 12 2021 - 14:55:44 +0300) odroid-c2 # U-Boot 2021.01 Configuration U-Boot 2021.01-armbian (Feb 04 2021 - 00:09:42 +0100) odroid-c2 U-Boot 2013.10-rc2-08400-g0490093 (Oct 11 2013 - 00:40:21) Allwinner Technology U-Boot 2011.09-rc1-00000-geb98797 (Dec 13 2017 - 15:44:38) Allwinner Technology U-Boot 2011.09-rc1-00000-geb98797 (Dec 13 2017 - 15:44:38) Allwinner Technology U-Boot 2011.09-rc1-00000-gc1cb2f9 (May 30 2014 - 10:19:03) Allwinner Technology U-Boot 2013.10-rc2-08400-g0490093 (Oct 11 2013 - 00:40:21) Allwinner Technology U-Boot 2021.01-armbian (Feb 04 2021 - 00:09:42 +0100) odroid-c2 So I think the real on my C2 working version (booting only from SDCard- so no newer u-boot flashed to emmc) is U-Boot 2019.10-armbian (Dec 01 2019 - 09:31:42 +0300) odroid-c2 because its the first entry. The later ones may be from the first partition? mmcblk0p1?

Is there any way (away from serial TTL boot-log) to found out which u-boot is installed on mmcblk0? I know I got the u-boot package linux-u-boot-odroidc2-dev 21.02.1 arm64 Uboot loader 2021.01 on my C2, but doent know if this is with the .deb installed on mmcblk0. Because the C2 hasnt a standard pin-header (and I think 3.3V? ) I didnt got the chance for a serial boot-log on my C2 and I often do update the u-boot-packages (u-boot, kernel-image, dtb, firmware etc) but didnt flash a new image for this to the card there could be a chance that Iam using an older u-boot in mmcblk0!?

@Igor and who also have an interest in this issue/topic After a long time - today Ethnernet is since hours stable again on my NanoPi Neo (no Network/eth0 down/up) BUT I didnt changed the software (armbian) Yesterday my NanoPi Neo had down/up (also) with Kernel 5.11.2-dev and debian buster and now today its stable since hours! What I did? No it wasnt the software, nor the ethernet-cable, nor the Power-Supply, nor the eth0-setting. I have a 16-port-Ethnernet-Hub with 100MBit, but its optical devided in 2x(2x4): 1st 2nd 2x4 + 2x4 = 16 ports #### #### #### #### The nanoPi Neo was in the 2nd 2x4 ports with the problem and after putting him in the 1st 2x4 port section the NanoPi Neo port did go stable. In the 1st 2x4 ports are more or mostly (or only?) 100MBit devices and in the 2nd 2x4 are some/more 1GBit-devices. I - personally - think the NanoPi Neo Ethernet-PHY didnt/doesnt tolerate some sort of ethernet-phy at the 2nd 2x4 port-part. At the 1st 2x4port-part it seems he found ethernet-phys he could tolerate. This is for today my "absurd" theory - BECAUSE it does work now for hours without a single up/down message in dmesg

from the extracted (example) u-boot.deb there are 2 directorys under /usr/lib/ with 5 files, but I think it isnt a good idea to change them by hand. I think the best way would be via a "u-boot" .deb-file (and the kernel/dtb and so on - created via the armbian-build-system)

Yes - thats because I only got a 5-port GBit-Switch. There is my primary-PC and the Samba-Servers. The other part of my Network is on a 24-port 100MBit-Switch - and my C2 as DNS-Filter doenst need 1GBit

I disabled the module in the "path" not in the "patch" (corrected this now) - so it shouldnt be present. Thanks for your commit

NPi K1 Plus is now on current. Started with 5.10.12 and is now after update at 5.10.16 - and all is working again (I dont use WiFi ) System diagnosis information will now be uploaded to http://ix.io/2RdP [EDIT] After build-update (u-boot build packages) I did get 5.10.18-trunk: _ _ ____ _ _ ___ ____ _ | \ | | _ \(_) | |/ / | | _ \| |_ _ ___ | \| | |_) | | | ' /| | | |_) | | | | / __| | |\ | __/| | | . \| | | __/| | |_| \__ \ |_| \_|_| |_| |_|\_\_| |_| |_|\__,_|___/ Welcome to Armbian 21.02.2 Buster with Linux 5.10.18-sunxi64 package bsp-kernel[21.05.0-trunk] u-boot[21.05.0-trunk] dtb [21.05.0-trunk] firmware [21.05.0-trunk] config[21.05.0-trunk] branch[current]

actual current image does work on my C2: ___ _ _ _ ____ ____ / _ \ __| |_ __ ___ (_) __| | / ___|___ \ | | | |/ _` | '__/ _ \| |/ _` | | | __) | | |_| | (_| | | | (_) | | (_| | | |___ / __/ \___/ \__,_|_| \___/|_|\__,_| \____|_____| Welcome to Armbian 21.02.1 Buster with Linux 5.10.12-meson64 System load: 2% Up time: 6 min Memory usage: 6% of 1.85G IP: 192.168.6.150 CPU temp: 37°C Usage of /: 6% of 29G root@odroidc2:/home/guido# dmesg|grep -i phy [ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034] [ 0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys). [ 1.720168] libphy: Fixed MDIO Bus: probed [ 2.250710] libphy: stmmac: probed [ 9.661249] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy) [ 91.543652] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=46) [ 91.557566] meson8b-dwmac c9410000.ethernet eth0: configuring for phy/rgmii link mode C2 was booted from MicroSD-Card (no emmc) System diagnosis information has been uploaded to http://ix.io/2Rdc My C2 is a REV0.2 20160226 /proc/cpuinfo:

@martinayotte My OPi One with Pihole & Kernel 5.11.1 does work - so its up to a problem with the NPI K1 Plus ans 5.11.1, but not only the WiFi-module For now I will go back to current (have to check kernel No) with the NPi K1 Plus

I disabled the module on my NPi K1 Plus in the sunxi64 path, but with the new created 5.11.1-dev image the NPi K1 Plus doenst give me a right login. It try to give me a automatic login, but there is no prompt and the heartbeat led is blinking very fast Starting kernel ... nanopik1plus login: root (automatic login) Last login: Sun Feb 28 15:14:43 UTC 2021 on tty1 Login timed out after 60 seco nanopik1plus login: root (automatic login) Last login: Sun Feb 28 15:15:58 UTC 2021 on tty1 Login timed out after 60 s nanopik1plus login: root (automatic login) Last login: Sun Feb 28 15:17:13 UTC 2021 on tty1 Also no login-prompt at ttys0 (and no more console at Ctrl-Alt-F2 etc)

Thanks I will keep that in mind when - in a half hour - do my new install. I did already wiped the sdcard....if bnot I had checked against this wifi.module

Thats a bit problematic, because my C2 is my primary PiHole-Server But in the past DEV was also at 5.10.12 and did work fine - because (I think) old dev will become current? and I do also user Buster

does this prevent from booting up complete? Iam only using ethernet on the NPi K1 Plus

I dont know which revision my C2-board has, but it does work with ethernet and since many apt-updates ___ _ _ _ ____ ____ / _ \ __| |_ __ ___ (_) __| | / ___|___ \ | | | |/ _` | '__/ _ \| |/ _` | | | __) | | |_| | (_| | | | (_) | | (_| | | |___ / __/ \___/ \__,_|_| \___/|_|\__,_| \____|_____| Welcome to Armbian 21.02.2 Buster with Linux 5.10.15-meson64 package bsp-kernel[21.02.0-trunk] u-boot[21.02.1] dtb [21.02.0-trunk] firmware [21.02.2] config[21.02.2] branch[dev] System load: 2% Up time: 8 days 6:04 Memory usage: 7% of 1.86G IP: 192.168.6.3 CPU temp: 31°C Usage of /: 6% of 29G root@odroid-c2(192.168.6.3):~# dmesg|grep -i phy [ 1.716216] libphy: Fixed MDIO Bus: probed [ 2.153195] libphy: stmmac: probed [ 6.620887] meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy) [ 7.055166] meson8b-dwmac c9410000.ethernet eth0: PHY [stmmac-0:00] driver [RTL8211F Gigabit Ethernet] (irq=46) [ 7.069497] meson8b-dwmac c9410000.ethernet eth0: configuring for phy/rgmii link mode armbianmonitor -u System diagnosis information has been uploaded to http://ix.io/2Rc2

As a test I updated on a secondary Pihole-Server (buster on NanoPi K1 Plus) the kernel to 5.11.1-dev and at startup Pihole did seem to make some trouble The server isnt getting to the login prompt and on the serial console the last info is "Starting kernel..." I updated some of my SMB-Servers with kernel 5.11.1-deb without problems. Will later try a new resinstall with buster and 5.11.1 and see if Pihole will run on a complete new installation.

Did you try to sudo apt update -y && apt upgrade -y before you install mosquitto? For the "broken packages" try sudo dpkg –configure -a or sudo apt -f install

Yes - the people who maintain a thing or theme (supported images on suupported boards should not waste their time - Iam on your side Its also Ok that its never nice to tell the people that the supporters cant help (because of time or they didnt know) - but because you are in germany you surely know the sentence "Der Ton macht die Musik". That means not so "hardly" tell them that they have to pay for support, but guide them nicely to the peer-to-peer/user-to-user support (ak.a. the beginners or user-supported-section). One "little problem" for most new users could be that the bug-tracker section is named for "supported boards" but it should named "supported boards with supported images". The new users mostly see the hardware sections and put their question in the right hardware section, but may have a self-compiled image (armbian-buid-system) or additional hardware/software questions which are not in the supported scope. To not spread more these topics around other sections but to organize them I would suggest to create in the peer-to-peer section also these hardware sections or like in the past a mandatory pulldown-menu entry to sort the themes and make them more moveable in the future. A few times - I dont know why - I did @Igor wrote about payed support in the peer-to-peer/user-to-user section and I did think the only solution is to write the users that they are wrote in a unsupported section and if they would get payed support the have to use another section (or maybe using better supported boards with supported images - then there is a better chance to have a public-interest-problem which can archive a higher-list-rang) Sure - peer-to-peer / user-to-user is somehting like a "garbage"-collector, but also a pool for new ideas or guideing existing users to new topics/themes.... and YES @Igor nobody should demand realtime-support if they dont want to spent money on it. free-support should be a free-gift who is given by one's own choice.

I did try the form at https://www.armbian.com/bugs and found it not very helpful. I mean its ok to tell the people they are in the wrong place to ask or there isnt not enough information to answer the problem, but this form isnt any help for many people. Often I try to help people with simple questions and later they could provide some good informations. But when we cant help they wouldnt learn much to use the system. It would be better - in my personal opinion - to move simple questions to a beginner area or guide them to google or the forum-search and not to tell them something like "shut up" (so this unpersonal sample text sounds to me ) I know we havent enough manpower to solve every puzzle - but when there is a space for a tv-box-club, why not offer them a beginners-place? If some of these invalids request had been moved to the right forum position and keept open I had answer some of the questions or had them guide a little bit.

its working again with 5.10.10 (with my - at this time- local .dts/.dtb-change) _ _ ____ _ _ __ _ _ | \ | | _ \(_) / \ / /_ | || | | \| | |_) | | / _ \| '_ \| || |_ | |\ | __/| | / ___ \ (_) |__ _| |_| \_|_| |_| /_/ \_\___/ |_| Welcome to Armbian 21.02.0-trunk Buster with Linux 5.10.10-sunxi64 No end-user support: built from trunk 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] System load: 4% Up time: 14:55 Memory usage: 10% of 985M IP: 192.168.6.116 CPU temp: 27°C Usage of /: 10% of 15G System diagnosis information has been uploaded to http://ix.io/2Npi

@Igor I created https://github.com/armbian/build/pull/2579 but please ignore the old part about the configuration.sh from 2019 - its only the 2021-part about the phy-mode patch

@Igor I was already thinking about this change, but couldnt find the thread. I changed in the actual used 5.9.0 image the .dts/dtbs to rgmii-id mode and restarted: [ 40.812499] dwmac-sun8i 1c30000.ethernet eth0: PHY [stmmac-0:07] driver [RTL8211E Gigabit Ethernet] (irq=POLL) [ 40.814234] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found [ 40.814255] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 40.814264] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 40.814863] dwmac-sun8i 1c30000.ethernet eth0: configuring for phy/rgmii-id link mode root@npi-a64-116:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_seq=1 ttl=113 time=21.8 ms 64 bytes from 8.8.8.8: icmp_seq=2 ttl=113 time=22.0 ms 64 bytes from 8.8.8.8: icmp_seq=3 ttl=113 time=21.8 ms If that will also work in 5.10.10 - then I will have to create a PR but I have to find the "entry-point" for the dts-file in github....

At first I compiled today armbian buster dev with kernel 5.10.10 and had no chance to connect eth0 nor wlan0 to my network Only a USB-Ethernet did connect instantly via DHCP. I did try to go back to kernel 5.9.1 via armbin-config, because with older installations with kernel 5.9.1 (up to 5.9.5) it did work, but also cant connect via onboard ports But onboard ethernet get a link and did show the right speed and wlan0 is also displaying the available WiFi networks. Next try was to build the armbian buster current (which gave me also kernel 5.10.10) and it also doesnt connect with onboard devices (here not via Network-Manager nor /etc/network/interfaces) Also a downgrade to kerrnel 5.9.0 doesnt did the trick Here the USB-Ethernet also does work fine. eth0 is also in the same phy-mode as on other devices here: dwmac-sun8i 1c30000.ethernet eth0: configuring for phy/rgmii link mode [ 41.158508] dwmac-sun8i 1c30000.ethernet eth0: PHY [stmmac-0:07] driver [RTL8211E Gigabit Ethernet] (irq=POLL) [ 41.160228] dwmac-sun8i 1c30000.ethernet eth0: No Safety Features support found [ 41.160252] dwmac-sun8i 1c30000.ethernet eth0: No MAC Management Counters available [ 41.160260] dwmac-sun8i 1c30000.ethernet eth0: PTP not supported by HW [ 41.173024] dwmac-sun8i 1c30000.ethernet eth0: configuring for phy/rgmii link mode kernel 5.10.10: System diagnosis information will now be uploaded to http://ix.io/2NnI kernel 5.9.0 : System diagnosis information will now be uploaded to http://ix.io/2NnV Now I do compile "legacy" with kernel 5.4 and will see it that will work But why did 5.9.x did work in the past and not now?

Today I compiled armbian buster 5.4.88 legacy Had not the armbian-logo with the Win10 Circle (after the kernel-screen) but a working boot-log. After creating User/Password the Desktop was starting normally (but in turkish, because I cant select english/german in my timezone ) But after configuring some settings in armbian-config and reboot after that the desktop wouldnt come on again - I only do get a blinking cursor Last Line in dmesg: [ 64.079236] broken atomic modeset userspace detected, disabling atomic System diagnosis information has been uploaded to http://ix.io/2Nic [EDIT] Had disabled Desktop with "Enable Desktop" because it did show "Enable Desktop" when the Desktop is already enabled Now Desktop came up again (also after asking to auto-login into the desktop) PS: I deleted language tr_TR and installed de_DE additionally to en_US, but now the terminal says "LC_ALL: cannot change locale (tr_TR.UTF8" but in .bashrc I also removed the tr_TR lines /etc/environment is empty ....