Ethernet not working or RPi 3B+

Question

Ethernet not working or RPi 3B+

BrainStone opened this issue 6 years ago · comments

The image generates just fine and works out of the box, but the ethernet is not working.

While digging around to find a working 64-bit version for my Pi, I came across several pages stating, that the ethernet would not be working due to some outdated drivers, but it should be resolved in a future release.
Would you be able to look into this to make sure the right drivers are downloaded for the 3B+?

I sadly don't remember where I have seen this. But it was multiple different pages for multiple different distributions.

burnbabyburn · Answer 1 · Wed Nov 07 2018 01:49:19 GMT+0800 (China Standard Time)

I am building this for 1-2 weeks now and never got a problem with wired ethernet.
Can u post your buildconfig/template? Did you use static IP or DHCP?

Yannick Schinko · Answer 2 · Wed Nov 07 2018 02:50:20 GMT+0800 (China Standard Time)

That's my template

RPI_MODEL=3P
RELEASE=stretch
BUILD_KERNEL=true
KERNEL_ARCH=arm64
RELEASE_ARCH=arm64
CROSS_COMPILE=aarch64-linux-gnu-
QEMU_BINARY=/usr/bin/qemu-aarch64-static
KERNEL_DEFCONFIG=bcmrpi3_defconfig
KERNEL_BIN_IMAGE=Image
KERNEL_IMAGE=kernel8.img
KERNEL_BRANCH=rpi-4.11.y
ENABLE_WIRELESS=true

# Custom settings
APT_INCLUDES=console-setup,keyboard-configuration,net-tools,systemd-sysv,wpasupplicant
APT_SERVER=ftp.de.debian.org
DEFLOCAL=de_DE.UTF-8
ENABLE_CONSOLE=false
ENABLE_REDUCE=true
HOSTNAME=TESTING
REDUCE_HWDB=false
REDUCE_LOCALE=false
REDUCE_SSHD=false

And I use DHCP.

burnbabyburn · Answer 3 · Wed Nov 07 2018 03:08:18 GMT+0800 (China Standard Time)

Main differences to my config:
RELEASE=stretch i use RELEASE=buster but this shouldn't make a difference
and
ENABLE_IFNAMES=false to get the old naming back.

Maybe thats the problem? does /usr/lib/systemd/network/10-eth.network point to eth0 and your interfaces has the same naming? Didn't see any code to change systemd from default eth0

Yannick Schinko · Answer 4 · Wed Nov 07 2018 03:10:20 GMT+0800 (China Standard Time)

I also have RELEASE=stretch or did you mean that you don't use stretch?

And ENABLE_IFNAMES=false would mean it'll be called eth0?

The other stuff I can't check right now. I don't have access to the Pi.

burnbabyburn · Answer 5 · Wed Nov 07 2018 03:13:38 GMT+0800 (China Standard Time)

i use buster. But i don't think that's the issue here. I think the systemd service points to eth0. This is fine if old naming is used.

And ENABLE_IFNAMES=false would mean it'll be called eth0?

That's how i understand it. I set it right from the start and have eth0 device

https://github.com/drtyhlpr/rpi23-gen-image#enable_ifnamestrue
Enable automatic assignment of predictable, stable network interface names for all local Ethernet, WLAN interfaces. This might create complex and long interface names. This parameter is only supported if the Debian releases stretch or buster are used.
Disabling with ENABLE_IFNAMES=false seems correct

TBH i never tried the new naming scheme so it's possible its broken.
Grüße aus Bonn

Yannick Schinko · Answer 6 · Wed Nov 07 2018 03:18:16 GMT+0800 (China Standard Time)

Ok. I'll bump to buster and add ENABLE_IFNAMES=false. Mostly because I want eth0 back xD.

I'll let you know tomorrow when I'm working on it again.

Is there a decent place to chat about this project? Like a Discord or IRC? I have some ideas I might turn into PRs if they are wanted.

burnbabyburn · Answer 7 · Wed Nov 07 2018 03:20:06 GMT+0800 (China Standard Time)

OK!
But please check if thats actually the problem before flashing a new image ;)
If my guess is correct, we should improve that part

Is there a decent place to chat about this project? Like a Discord or IRC? I have some ideas I might turn into PRs if they are wanted.

No/not yet
Maybe open issue tickets here or in my fork. There is tons of stuff to improve.

Yannick Schinko · Answer 8 · Wed Nov 07 2018 16:35:35 GMT+0800 (China Standard Time)

Maybe thats the problem? does /usr/lib/systemd/network/10-eth.network point to eth0 and your interfaces has the same naming? Didn't see any code to change systemd from default eth0

/usr/lib/systemd/network/10-eth.network doesn't exist but /lib/systemd/network/10-eth.network does.
The content of the file is

[Match]
Name=

[Network]
DHCP=yes

I sadly can't check ifconfig because that wasn't installed on that image. (Should be one of the default packages really)

Yannick Schinko · Answer 9 · Wed Nov 07 2018 18:20:39 GMT+0800 (China Standard Time)

Ok. Even with the new image it's not working.
I also can't get WiFi to work. The wpa_supplicant service can't seem to connect to it.

I could bet it's a tiny thing that's missing here.

The eth0 intferace doesn't even show up in the command ifconfig. Only lo and wlan0.

Yannick Schinko · Answer 10 · Wed Nov 07 2018 21:47:40 GMT+0800 (China Standard Time)

I did some research and found these threads on the topic. Though they all stay a bit vague...

It looks like CONFIG_USB_LAN78XX=y is missing in the kernel config. Even in the /boot/config-rpi-4.11.y file it says that this config has no value set (Exact line: # CONFIG_USB_LAN78XX is not set).

What do I need to do, to configure that?

Btw you said you were successfully using this project for a few weeks. Though keep in mind that the 3 B+ has an Ethernet chip that's different to all other previous chips.

Yannick Schinko · Answer 11 · Wed Nov 07 2018 22:00:15 GMT+0800 (China Standard Time)

Also looking at the https://github.com/raspberrypi/linux repo, there seem to be way newer versions of the kernel available. Even up until rpi-4.19.y!
Since rpi-4.14.y is the default branch, I'm using that as a test now. Will also try rpi-4.19.y later.

burnbabyburn · Answer 12 · Wed Nov 07 2018 22:09:20 GMT+0800 (China Standard Time)

I always use 4.18. I am scared of current branch.
i compiled your config

`RPI_MODEL=3P
RELEASE=stretch
BUILD_KERNEL=true
KERNEL_ARCH=arm64
RELEASE_ARCH=arm64
CROSS_COMPILE=aarch64-linux-gnu-
QEMU_BINARY=/usr/bin/qemu-aarch64-static
KERNEL_DEFCONFIG=bcmrpi3_defconfig
KERNEL_BIN_IMAGE=Image
KERNEL_IMAGE=kernel8.img
KERNEL_BRANCH=rpi-4.18.y
ENABLE_WIRELESS=true

# Custom settings
APT_INCLUDES=console-setup,keyboard-configuration,net-tools,wpasupplicant
APT_SERVER=ftp.de.debian.org
DEFLOCAL=de_DE.UTF-8
ENABLE_CONSOLE=false
ENABLE_REDUCE=true
HOSTNAME=TESTING
REDUCE_HWDB=false
REDUCE_LOCALE=false
REDUCE_SSHD=false
ENABLE_IFNAMES=false

#ENABLE_INITRAMFS=true
#ENABLE_NONFREE=true`

booted up on a RPI3B+ and got eth0 dhcp auto configured :)

P.S. you really should consider using apt_cache_ng,ccache and mirror the repositorys before. That speeds up building process a lot!!!

Yannick Schinko · Answer 13 · Wed Nov 07 2018 22:11:06 GMT+0800 (China Standard Time)

With rpi-4.11.y? Or rpi-4.18.y?

burnbabyburn · Answer 14 · Wed Nov 07 2018 22:18:11 GMT+0800 (China Standard Time)

With rpi-4.11.y? Or rpi-4.18.y?

4.18

The wpa_supplicant service can't seem to connect to it.
This is a configuration problem:
with wireless=enabled systemd is taking over control of wlan0. You need to get systemd using wpa_supplicant

#WLAN-CLIENT-MODE

echo "
ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=1
update_config=1 

# wlan client

echo "network={
        ssid="mySSID"
        scan_ssid=1
        pairwise=CCMP
        group=TKIP
        proto=RSN
        key_mgmt=WPA-PSK
        psk="mypsk"
}
" >> /etc/wpa_supplicant/wpa_supplicant-wlan0.conf

systemctl enable wpa_supplicant.service
systemctl enable wpa_supplicant@wlan0.service

systemctl start wpa_supplicant.service
systemctl start wpa_supplicant@wlan0.service

you will need crda package for wifi (wlan freq and power output db for not breaking local law)
these packages help with wifi wireless-tools,rda,wireless-regdb

burnbabyburn · Answer 15 · Wed Nov 07 2018 22:22:56 GMT+0800 (China Standard Time)

Btw you said you were successfully using this project for a few weeks. Though keep in mind that the 3 B+ has an Ethernet chip that's different to all other previous chips.

Jap - Actually fixing wired network on RPI3B+ was my first git commit ever :)

Yannick Schinko · Answer 16 · Wed Nov 07 2018 22:24:22 GMT+0800 (China Standard Time)

Ok. I'll first try to build the different kernel versions to see which one works the best for me.

Ah ok. I'll try to find the differences between raspbian and these versions to figure out what exactly I need to do. WiFi is not nearly as important as a wired ethernet.

Thanks for your help. I'll close this as soon as I can get it working.

Yannick Schinko · Answer 17 · Thu Nov 08 2018 00:12:01 GMT+0800 (China Standard Time)

The 4.14 kernel is enough already. In other words it's working. All it was, was the kernel being too old.

I'll make a PR tomorrow bumping the default kernel version in the templates.