• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

No network after upgrade to 5.30
2 2

116 posts in this topic

Recommended Posts

Updated my bananapi pro to from 5.30 minutes ago...but now it doesnt boot ;-(

Any possibility to get my system back without setting up completely new? Never had this with all update before.....

Share this post


Link to post
Share on other sites

Seems to be problem with network (using it headless), last line bootscreen says IPv6 ADDRCONF (NETDEV_CHANGE)  : eth0: link becomes ready. In line before it states link is up, ipscan shows no bananapro...

Share this post


Link to post
Share on other sites
49 minutes ago, nihilista said:

Updated my bananapi pro to from 5.30 minutes ago...but now it doesnt boot ;-(

Any possibility to get my system back without setting up completely new? Never had this with all update before.....


Everything is solvable ... but we need more information to help. It might be a problem with u-boot. From where you did upgrade?

giri@nwrk.biz likes this

Share this post


Link to post
Share on other sites
25 minutes ago, tahaea1 said:

Same problem on SuperPi. Can get console with UART but get no networking at all.


Which image?

Share this post


Link to post
Share on other sites
4 minutes ago, tahaea1 said:

Banana Pi Jessie mainline

upgraded with apt-get

using usb hdd as root


Which kernel version and from which Armbian version you made update? Did you start from clean image? You have to tell me everything! btw. Super Pi is not supported even I am almost sure it's exactly the same as Banana Pi ... I never saw one of those ... some minor changes can lead to improper Ethernet initialisation. I also need to wait for others to report - on supported boards.

Share this post


Link to post
Share on other sites
7 minutes ago, Igor said:


Which kernel version and from which Armbian version you made update? Did you start from clean image? You have to tell me everything! btw. Super Pi is not supported even I am almost sure it's exactly the same as Banana Pi ... I never saw one of those ... some minor changes can lead to improper Ethernet initialisation. I also need to wait for others to report - on supported boards.

I don't really remember the kernel version. Armbian version was 5.25 or 5.24. Clean image as in what? I was using 5.25 for about 2 months I think? was apt updating regularly and it updated to 5.30 today. 

Share this post


Link to post
Share on other sites
3 minutes ago, tahaea1 said:

I don't really remember the kernel version. Armbian version was 5.25 or 5.24. Clean image as in what? I was using 5.25 for about 2 months I think? was apt updating regularly and it updated to 5.30 today. 


OK. I'll try to reproduce.

 

In the mean time, you can try to flash (downgrade) u-boot from http://apt.armbian.com/pool/main/l/linux-u-boot-bananapi-default/linux-u-boot-bananapi_5.25_armhf.deb to see if that helps. Extract  u-boot-sunxi-with-spl.bin and write to SD card:

dd if=u-boot-sunxi-with-spl.bin of=/dev/yoursdcard bs=1024 seek=8 status=noxfer

 

Share this post


Link to post
Share on other sites

Using latest 5.25, jessie,  with 4.9.7 mainline kernel here. Will try downgrade u-boot if i found time and got running linux machine ;-)

Share this post


Link to post
Share on other sites

Bananapi armbian 5.27 mainline upgrade to 5.30. Cannot log in remotely from putty.. When connect to hdmi monitor, it boot up normally and can log in. Everything seems ok but no response when attempt to log in remotely (putty). Very strange.

Share this post


Link to post
Share on other sites
5 minutes ago, wsian said:

Bananapi armbian 5.27 mainline upgrade to 5.30. Cannot log in remotely from putty.. When connect to hdmi monitor, it boot up normally and can log in. Everything seems ok but no response when attempt to og in remotely (putty). Very strange.


Most likely u-boot configuration which initialised network is broken for Bananapi. Still checking if this is it. U-boot upgrade has been removed until this is not resolved.

Share this post


Link to post
Share on other sites

Bananapi M1+

Upgrade from 5.24 / 4.7.9 -> 5.30 / 4.11.4: no problems with network. Tested with 100 / 1000Mbit switch.

Share this post


Link to post
Share on other sites

The more I test, the less I know :( This test image works fine on M1+, while network doesn't come up (properly) on: M1, PRO and R1 :)

manuti likes this

Share this post


Link to post
Share on other sites

Hi Igor
With my Banana Pi 1 nothing more about HDMI I see only the cursor flashes.
What could I do?
Or is it death?

Share this post


Link to post
Share on other sites
15 minutes ago, Wolf2000 said:

Hi Igor
With my Banana Pi 1 nothing more about HDMI I see only the cursor flashes.
What could I do?
Or is it death?


Even you wait until network timeouts ? 

If you did an update, you need to rollback u-boot to 5.25 

Share this post


Link to post
Share on other sites

Same here with fresh installed Debian image 5.30. No remote ssh login. Looks like something is broken.

Share this post


Link to post
Share on other sites

I can confirm, on a BPi M1 the internal ethernet is broken with armbian 5.30.

I'm using the BPi M1 as bridge with a second USB ethernet port. After update to armbian 5.30 (from 5.26), the internal BPi ethernet port had 80% packet loss, but the USB ethernet adapter works just fine.

 

Regards

 

Share this post


Link to post
Share on other sites

Hello,

 

I have been just installed Armbian 5.30 ubuntu flavor on my Banana Pi (the first model). Unfortunately, it's impossible to start a SSH session. The session freeze before to get the prompt. 

 

Quote

64 bytes from 192.168.1.37: icmp_seq=1 ttl=64 time=0.487 ms
64 bytes from 192.168.1.37: icmp_seq=4 ttl=64 time=0.267 ms
64 bytes from 192.168.1.37: icmp_seq=6 ttl=64 time=0.287 ms
64 bytes from 192.168.1.37: icmp_seq=7 ttl=64 time=0.271 ms
64 bytes from 192.168.1.37: icmp_seq=8 ttl=64 time=0.334 ms
From 192.168.1.57 icmp_seq=10 Destination Host Unreachable
64 bytes from 192.168.1.37: icmp_seq=13 ttl=64 time=1028 ms
64 bytes from 192.168.1.37: icmp_seq=15 ttl=64 time=0.246 ms
64 bytes from 192.168.1.37: icmp_seq=22 ttl=64 time=0.318 ms
64 bytes from 192.168.1.37: icmp_seq=74 ttl=64 time=0.297 ms
64 bytes from 192.168.1.37: icmp_seq=76 ttl=64 time=0.308 ms

 

304 packets transmitted, 85 received, +5 errors, 72% packet loss, time 310268ms
rtt min/avg/max/mdev = 0.208/24.450/1028.213/155.519 ms, pipe 11

 

As you can see, a lot of packets are lost. 

 

On my Nanopi, I got other network issues with this kernel. I think the 4.11 kernel cannot be used correctly with these boards now.

Share this post


Link to post
Share on other sites

Is the problem related to the BananaPi (family) only? I've just upgraded my OrangePi PC, but didn't reboot yet.

Share this post


Link to post
Share on other sites
9 minutes ago, Echo said:

I've just upgraded my OrangePi PC, but didn't reboot yet.


This problem should not be related ... if you report the problem, we need all possible details :)

Share this post


Link to post
Share on other sites

Hi, its a my first post here :-)

 

same issue with update from Armbian 5.25 to 5.30 bootloop on Banana Pi.

Have now done backup back, Will now wait until the problem is solved...

Share this post


Link to post
Share on other sites
37 minutes ago, Igor said:


This problem should not be related ... if you report the problem, we need all possible details :)

OrangePi PC update was successfully. A reboot succeeded. Thanks for the update!

Share this post


Link to post
Share on other sites
59 minutes ago, zador.blood.stained said:

Please try testing after recompiling the u-boot now.

 

M1 and PRO are O.K., will check R1 and M1+ too

 

4 minutes ago, Aux said:

same issue with update from Armbian 5.25 to 5.30 bootloop on Banana Pi.


Using u-boot from previous version is a way to go - you have to update it on another computer if you already issued an update.

 

1 minute ago, Echo said:

OrangePi PC update was successfully. A reboot succeeded. Thanks for the update!

 

You are welcome.

Share this post


Link to post
Share on other sites
2 minutes ago, Igor said:

Using u-boot from previous version is a way to go - you have to update it on another computer if you already issued an update.

I tried  

Quote

dd if=u-boot-sunxi-with-spl.bin of=/dev/yoursdcard bs=1024 seek=8 status=noxfer

but had not worked,  Had possibly flashed wrong drive mmcblk0p1 instead of mmcblk0  ??

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

2 2

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.