Gunjan Gupta

The key is at http://fi.mirror.armbian.de/apt/armbian.key you can try adding it with wget -qO - http://fi.mirror.armbian.de/apt/armbian.key | sudo apt-key add -

Thanks for confirming I will raise a PR for this. Yes, modern u-boot detects the frequency sometimes wrong. I added a fix for this that reduced the frequency of the issue. Previously in my tests it was happening 50-80% of times on reboot. After integrating the fix the issue seems to have gone down to like 1 in 10 times or so. I will try to further tweak the fix and see if I can make it non-existent.

I worked with another contributor named @ALIGMSTEN, For him ehternet worked on coldboot but was broken after reboot. We tested a couple of device-tree overlays and this worked for him /dts-v1/; /plugin/; &reg_gmac_3v3 { startup-delay-us = <150000>; }; &mdio { motorcomm,clk-out-frequency-hz = <125000000>; }; @aoleynik@张军 would you guys try this out. Once you guys confirm that it works for you, I will merge it in so that it will be available for everyone.

Yes this thread is about broken ethernet on 6.x kernels. Thanks for reporting the problem. Sadly the logs are not much helpful in this case. Combining with the fact that ethernet works fine for me on both 6.1.54 and 6.5.4 on my Opi 3 LTS makes it pretty hard to trouble shoot the problem. This mostly leaves me with suggesting random things based on the differences between 5.15.x kernel and 6.x kernels to the user and wait for them to confirm if it worked or not. If you are willing to help, could you please try the device tree overlay I posted above and see if it fixes ethernet for you?

I believe they are kept back because they are configured to be on hold via apt. You should be able to upgrade them using armbian-config > system > firmware

edit /etc/apt/source.list and /etc/apt/source.list.d/armbian.list and change kinetic to jammy. Then run "apt-get update && apt-get dist-upgrade"

23.8.3 was generated recently just two days ago. Its possible that bullseye support might be getting dropped due to resource crunch or may be it was just missed when creating the release. Not 100% sure. Anyways, If possible you can try upgrading to bookworm from bullseye by changing the repository urls accordingly in /etc/apt/sources.list and /etc/apt/sources.list.d/armbian.list. Or if you need to stay on bullseye for some reason then just wait and maybe package will get updated to even more newer version in upcoming days.

It came into existence sometime close(before or after I don't remember exactly) to 23.02 release. Do a full upgrade first and then check if any armbian-bsp-cli-nanopineo-* package is installed. If its not installed, then install it manually

Tried with 5v 3A supply. My Orange Pi 3 LTS behaved bit unstable but ethernet still worked. @aoleynikCould you please try the following Install 6.1.53. If the following command doesn't work, then try armbian-config > system > other and choose 6.1.53 kernel to install apt-get install --upgrade linux-image-current-sunxi64 linux-dtb-current-sunxi64 Create a file called sun50i-h6-ethernet-fix.dts with following content /dts-v1/; /plugin/; &emac { snps,reset-active-low; snps,reset-delays-us = <0 10000 1000000>; snps,reset-gpio = <&pio 3 14 1>; }; &ext_rgmii_phy { /delete-property/ reset-gpios; /delete-property/ reset-assert-us; /delete-property/ reset-deassert-us; }; Compile the file to dtbo dtc -@ -I dts -O dtb -o sun50i-h6-ethernet-fix.dtbo sun50i-h6-ethernet-fix.dts Copy sun50i-h6-ethernet-fix.dtbo file to /boot/dtb/allwinner/overlay directory and then enable the overlay by using armbian-config > system > hardware. Reboot the system for the changes to apply. See if ethernet works after reboot. PS: The above actually breaks the working ethernet for me. But as yours is already broken, this might fix it for you

Fixes are now available in stable kernel as well. so you should be able to upgrade the kernel without needing to switch to beta repository.

@aoleynik Another small question. My Opi3 lts is running headless. No monitor keyboard, mouse or any other accessories connected. For you I know you have some lcd screen connected, Is there anything else connected as well? The 3d printer you have mentioned before, is it connected via USB?

Tried upgrading from 22.11.1 image. Wifi was already broken in that image. Ethernet worked. First tried upgrading using apt (I am new to Armbian and personally I refer docs only after when something doesn't work 😁) . Used --allow-unauthenticated as apt was complaining about key apt-get --allow-unauthenticated update apt-get --allow-unauthenticated dist-upgrade This upgraded most packages to 23.8.3. However kernel was not upgraded. So I used armbian-config > system > firmware to upgrade further. That upgraded the kernel to 6.1.53. Rebooted OPi 3 LTS to boot from new kernel. During reboot, noticed that u-boot version was still 2022.07 as seen on serial console. After reboot completed, ethernet still works and wifi also worked now. Used armbian-config > system > install > install/update the bootloader on sd/emmc option. Rebooted the system and noticed u-boot is now 2023.07.02. Ethernet still works, wifi still works. Powered off and restarted using onboard power button. Logged in to find ethernet still works, wifi still works. Powered off. Disconnected power cable. Waited 30 seconds and plugged the power cable back in. Logged in and everything still works All this with Raspberry Pi 15.3 watt power supply. Logs uploaded for reference https://paste.armbian.com/zibuyibeqi Now going to do all of the above again with Xiaomi 15 watt mobile phone power adapter.

Is it safe to assume those chargers produce exactly 5v and nothing above the same like 5.1v produced by Raspberry pi charger? I faintly remember reading somewhere that orange pi boards require slightly above 5v to function correctly. I have a Xiaomi PD adapter that can deliver 5V 3A. Will try with the same as well.

@aoleynikJust to rule power supply out. How are you powering your orangepi3 lts? For example, I am using official Raspberry Pi power supply rated at 15.3 watts, delivers 5.1 volt with maximum 3 Amps

5.15.130+ kernels should have wifi working as well. 5.15.131 should be available from beta repository. You can give this a try. This issue is specially a hard one to trace. I will try recreating your environment by installing 22.11.4 and upgrading from the same. Lets hope I face the same issue.

Yeah, about that. He doesn't have issue with wifi. instead he seems to be having issues with ethernet. Same one that you found with Orange Pi One Plus. Its strange that I am not having that issue on my Opi3 lts. @aoleynikyou can use armbian-config to switch to legacy 5.15.125 or what ever kernel is available. Once you do and if it brings back ethernet. Could you please again share logs for comparision with the non-working state?

And you also have motorcomm chip like the one shown in the attached photo. Motorcomm is the black chip below 859, behind IR sensor. If you zoom in, you can read motorcomm written on it

ok...Thats weird. Could you please upload logs using armbianmonitor -u and share the link? I don't have this issue on my Opi3 LTS. So need to check if yours uses same chip as mine. Mine uses motorcom chip for ethernet. I heard there is also some batches with a realtek chip. Also whats the version of your board. Mine is version 1.4

This should have had yesterday's date. Found in docs. upgrade only installs the package. You then have to install u-boot manually using steps mentioned here https://docs.armbian.com/User-Guide_Getting-Started/#how-to-update-u-boot

ok no problem. Probably @Werner can help to mark it resolved

Happy to help. Do you have a option to mark this thread as solved? If so please do mark the thread as resolved

hmm... What is the version reported by u-boot on serial console during boot?

In a couple of hours or may be by tomorrow 6.5.3 kernel will also get available The file should be provided by armbian-bsp-cli-nanopineo-edge package. Check if its installed, Install it if its missing. Do you mean the lqqqqq thing from the screenshot? it can renders differently based on ssh client, whether you are doing running it over serial cable or whether you are doing it in graphical terminal. If you are using ssh, try using a different client like if previously you were using putty, then try mobaxterm. If you experienced it on serial, try using ssh

you need to update your linux-uboot-<something> package as well. Don't remember the exact name, but name should be visible in the output of "dpkg -l | grep linux". The issue will then get resolved after a cold boot. That is shut it down, unplug the power and plug the power back in. The network should continue to work fine after that. To properly test the fix, make sure to also do a soft reboot as the issue you have reported is only visible on reboot and doesn't happen on cold boot

If you need instant fix, edit /etc/apt/sources.list.d/armbian.list. Use beta repository by change apt.armbian.com to beta.armbian.com and install the kernel from beta repository Note: issue is already reported and fix is also discussed on another thread. In future, please take some time searching the forum before opening a new issue