LIME2 - Can't get an IPv4 address from DHCP server

roukydesbois · January 16, 2021, 07:51:30 PM

Hello everyone!

First post here, I've been having my LIME2 for quite some time now and everything worked perfectly. But (there's always a but), I tried to install a fresh Armbian today and I can't get internet connection. I've tried:
- different SD cards
- both Buster and Focal latest versions

Here is the output of

Code Select

cat /var/log/syslog | grep NetworkManager:
https://paste.chapril.org/?070e1bc546f48c37#4g134CfTkAtqKxHBMtRePfSQxFgfeBpiortZTn8Uxr53

I've tried to look on the forum, on the internet, but haven't found anything that could help me understand what the problem is. The simplest explanation is that there would be a physical failure due to the age of my board, but I don't know how to assess this (I see both lights of the ethernet port blinking).

Any help would be appreciated, thanks!

LubOlimex · January 18, 2021, 09:20:09 AM

We moved away from Armbian some time ago as announced here:

https://olimex.wordpress.com/2020/04/21/olimage-mainline-linux-images-building-script-for-all-of-our-olinuxino-and-som-boards/

I'd recommend testing with the Olimage images.

If you want to use Armbian my advice is to ask in the Armbian forums, because we don't support these images anymore.

roukydesbois · January 20, 2021, 09:34:28 PM

Hello and thanks for your response! I didn't know the Armbian images were not supported, so I used the olimage one and got the same result, here is the log:

https://paste.chapril.org/?c1a032c4f19ab1ea#J611rGNyX4stSGDkuZQcwwytd5mR6JonZXi9tgWcjNQr

So, does my board look broken to you?

LubOlimex · January 21, 2021, 09:39:16 AM

It is hard to say if it looks broken from that log excerpt.

It is probably some discrepancy between DHCP and static IP but it can be any network misconfiguration or router firewall blocking the board. It can be also wrongfully selected board and hardware revision. It can be damaged cable or connector. Show us the full boot log (do a restart and start from the beginning of the boot) and include in it what does the following commands return:

ifconfig -a

and also

cat /etc/network/interfaces

roukydesbois · February 01, 2021, 08:18:12 PM

Hello! I finally got a hold on my board.

Here is the full syslog: https://paste.chapril.org/?161eff81dc8e68c9#AWomnVjvUKYjv2bTRk8NdDU5Fjb1rrj1PAXAn7iW2GiW

Here is the content of my interfaces file:

Code Select

# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/interfaces.d:
source-directory /etc/network/interfaces.d

And the content of eth0 in interfaces.d:

Code Select

allow-hotplug eth0
iface eth0 inet dhcp

I don't have a direct access to ifconfig -a as I don't have a screen to plug in my board right now - but I can tell you that I had a local IPv6 address on the eth0 network but no IPv4 address.

Hope this helps you helping me, and thanks

fivuf · February 05, 2021, 01:43:37 PM

Hello. I have the exact same problem with the newest image.
http://images.olimex.com/release/a20/A20-OLinuXino-buster-minimal-20210203-221802.img.7z

My board is rev G.

I can add that with my current system which use an older kernel(5.9.14), the interface eth0 works fine with the same board.

roukydesbois · February 14, 2021, 01:42:04 AM

I searched a bit more and I found this article where some issues with Ethernet are mentioned, could it be related?

JohnS · February 15, 2021, 09:57:04 AM

Quote from: roukydesbois on February 14, 2021, 01:42:04 AMI searched a bit more and I found this article where some issues with Ethernet are mentioned, could it be related?

I'm confused - why do you refer to that article?

It's about a completely different CPU made by a different chip maker, and the article explains what was different - something not applying to other CPUs (including the A20 etc).

John

roukydesbois · February 15, 2021, 10:39:12 AM

Quote from: JohnS on February 15, 2021, 09:57:04 AMI'm confused - why do you refer to that article?

Hello JohnS and thanks for your answer! I mentioned this article as it said LIME2, ethernet and these are the keywords I used to search for a solution to my issue

I'm not very knowledgeable about hardware - hence my question if it was related!

So this is a dead-end, I'll continue searching then!

LubOlimex · February 15, 2021, 10:54:05 AM

@roukydesbois Which image exactly did you use for your tests? Can you give me a link?

What is the hardware revision of your LIME2 board?

I will try to find same revision LIME2 board and run the same image and see if the problem exists here.

roukydesbois · February 15, 2021, 01:29:42 PM

@LubOlimex I have a LIME2 rev G and I have used both the official images (focal and buster) from https://images.olimex.com/release/a20/ (but the ones from February 3rd, I'm seeing now that there is a new version, I'm going to try this one too).

Thanks for your help!

roukydesbois · February 15, 2021, 03:05:42 PM

Alright I've just tested with the latest buster-minimal image, and I have the same issue.

LubOlimex · February 16, 2021, 02:56:18 PM

I found same revision board (looking at the bottom it seems the Ethernet chip U22 is RTL8211E, can you confirm your board has the same chip) and used same Buster minimal image (from archive "A20-OLinuXino-buster-minimal-20210210-151806.img.7z"). DHCP and Ethernet seem to work fine. My system log looks quite different from yours:

https://justpaste.it/4hkgc

and boot log here:

https://justpaste.it/76ibs

LubOlimex · February 16, 2021, 03:06:39 PM

Also installed ethtool (apt install ethtool) and ran for eth0 interface, the info is:

Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric Receive-only
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 1
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: d
Wake-on: d
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: yes

Can you run comparison with the old image that worked for you? Paste the results here, we are mostely interested in auto-negotiation, speed and duplex values.

roukydesbois · March 11, 2021, 09:44:20 AM

Hello and thanks for your answer. I finally got back home and I have installed the armbian buster 20.05.1 with kernel 5.4.43. Here is the result of running ethtool:

Settings for eth0:
   Supported ports: [ TP MII ]
   Supported link modes: 10baseT/Half 10baseT/Full
     100baseT/Half 100baseT/Full
     1000baseT/Half 1000baseT/Full
   Supported pause frame use: Symmetric Receive-only
   Supports auto-negotiation: Yes
   Supported FEC modes: Not reported
   Advertised link modes: 10baseT/Half 10baseT/Full
     100baseT/Half 100baseT/Full
     1000baseT/Half 1000baseT/Full
   Advertised pause frame use: Symmetric Receive-only
   Advertised auto-negotiation: Yes
   Advertised FEC modes: Not reported
   Link partner advertised link modes: 10baseT/Half 10baseT/Full
     100baseT/Half 100baseT/Full
   Link partner advertised pause frame use: Symmetric
   Link partner advertised auto-negotiation: Yes
   Link partner advertised FEC modes: Not reported
   Speed: 100Mb/s
   Duplex: Full
   Port: MII
   PHYAD: 1
   Transceiver: internal
   Auto-negotiation: on
   Supports Wake-on: d
   Wake-on: d
   Current message level: 0x0000003f (63)
           drv probe link timer ifdown ifup
   Link detected: yes

So it looks exactly the same. I'm going to try again with the latest olimex image in the meantime.