Raspberry Pi5 kein Ethernet

  • Hallo Leute,

    ich habe einen Pi5 mit Raspbian Bookworm und NVME Hat. Soweit funktioniert alles (Klipper etc. für 3D Drucker).
    Leider kann ich nicht mit Ethernet auf ihn zugreifen. Es scheint so als ob da ein Treiber fehlt... "device at address 1 is missing" und "failed to contact RP1 firmware" kommt beim Bootvorgang. WLAN funktioniert.

    Könnt ihr mir sagen, wie ich das Problem lösen kann? Bin leider kein Linux Profi und ü60 - also bitte in einfachen Worten. ;)

    Danke!

  • Es scheint so als ob da ein Treiber fehlt... "device at address 1 is missing" und "failed to contact RP1 firmware" kommt beim Bootvorgang. WLAN funktioniert.

    Der Treiber fehlt nicht, denn dieser Treiber befindet sich schon im Kernel. Evtl. ist es ein Hardwareproblem. ich habe einen PI4 die auch solche Probleme hat.
    Wie sind nach dem booten, auf deinem PI5 die Ausgaben von:

    Code
    dmesg | grep -i eth0
    ip a

    ?

    EDIT:

    Bekommst Du evtl. u. a. auch diese bzw. so eine:

    Code
    [    2.427713] systemd[1]: Expecting device sys-subsystem-net-devices-eth0.device - /sys/subsystem/net/devices/eth0...

    Meldung?

    Wi-Fi_Signal_Strength  txpower
    iptables chains order scheme iptables-diagram
    nftables-diagram

    Meine PIs

    PI4B/8GB (border device) OpenBSD 7.6 (64bit): SSH-Server, WireGuard-Server, ircd-hybrid-Server, Mumble-Server

    PI3B+ FreeBSD 14.0-R-p10 (arm64): SSH-Serv., WireGuard-Serv., ircd-hybrid-Serv., Mumble-Serv., ddclient

    PI4B/8GB Bookworm-lite (64bit; modifiziert): SSH-Server, WireGuard-Server, ircd-hybrid-Server, Mumble-Server, botamusique, ample

    Edited once, last by rpi444 (March 11, 2025 at 12:40 PM).

  • pi@Hevort:~ $ dmesg | grep -i eth0
    [ 0.713865] macb 1f00100000.ethernet eth0: Cadence GEM rev 0x00070109 at 0x1f00100000 irq 112 (2c:cf:67:13:9b:0a)
    [ 1.069587] macb 1f00100000.ethernet end0: renamed from eth0
    pi@Hevort:~ $ ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
    valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
    valid_lft forever preferred_lft forever
    2: end0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 2c:cf:67:13:9b:0a brd ff:ff:ff:ff:ff:ff
    3: can0: <NOARP,UP,LOWER_UP,ECHO> mtu 16 qdisc pfifo_fast state UP group default qlen 128
    link/can
    4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 2c:cf:67:13:9b:0b brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.49/24 brd 192.168.0.255 scope global dynamic noprefixroute wlan0
    valid_lft 315359870sec preferred_lft 315359870sec
    inet6 2001:8e0:3061:3801:4605:bfe:603b:773a/64 scope global dynamic noprefixroute
    valid_lft 7055sec preferred_lft 3455sec
    inet6 fd7f:40a2:2062:0:1865:9155:35d0:ca7a/64 scope global dynamic noprefixroute
    valid_lft 7054sec preferred_lft 3454sec
    inet6 fe80::e422:8061:45b2:37bb/64 scope link noprefixroute
    valid_lft forever preferred_lft forever

  • [ 1.069587] macb 1f00100000.ethernet end0: renamed from eth0

    2: end0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 2c:cf:67:13:9b:0a brd ff:ff:ff:ff:ff:ff

    Wie ist die Ausgabe von:

    Code
    dmesg | grep -i end0

    ?

  • Und was sagt mir das alles? Zumindest sieht es ja so aus, als ob ein (umbenannter) Ethernetanschluss vorhanden ist...

    ether 2c:cf:67:13:9b:0b txqueuelen 1000 (Ethernet)
    RX packets 1398 bytes 169371 (165.4 KiB)
    RX errors 0 dropped 752 overruns 0 frame 0
    TX packets 367 bytes 70034 (68.3 KiB)
    TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

  • Zumindest sieht es ja so aus, als ob ...

    Siehe z. B. auch: https://github.com/raspberrypi/linux/issues/6420

  • $ nmcli show
    Error: argument 'show' not understood. Try passing --help instead.

    Evtl.:

    Code
    nmcli device show
    nmcli device status
  • Hab mal alle Befehle eingetippt. ;)


    nmcli --show:

    wlan0: connected to preconfigured
    "Broadcom Wi-Fi"
    wifi (brcmfmac), 2C:CF:67:13:9B:0B, hw, mtu 1500
    ip4 default, ip6 default
    inet4 192.168.0.32/24
    route4 192.168.0.0/24 metric 600
    route4 default via 192.168.0.254 metric 600
    inet6 2001:8e0:3061:3801:4605:bfe:603b:773a/64
    inet6 fd7f:40a2:2062:0:1865:9155:35d0:ca7a/64
    inet6 fe80::e422:8061:45b2:37bb/64
    route6 fe80::/64 metric 1024
    route6 fd7f:40a2:2062::/64 metric 600
    route6 2001:8e0:3061:3801::/64 metric 600
    route6 fd7f:40a2:2062::/64 via fe80::7642:7fff:fe1f:643d metric 605
    route6 2001:8e0:3061:3800::/56 via fe80::7642:7fff:fe1f:643d metric 600
    route6 default via fe80::7642:7fff:fe1f:643d metric 600

    lo: connected (externally) to lo
    "lo"
    loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
    inet4 127.0.0.1/8
    inet6 ::1/128


    nmcli device show:

    GENERAL.DEVICE: wlan0
    GENERAL.TYPE: wifi
    GENERAL.HWADDR: 2C:CF:67:13:9B:0B
    GENERAL.MTU: 1500
    GENERAL.STATE: 100 (connected)
    GENERAL.CONNECTION: preconfigured
    GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveC>
    IP4.ADDRESS[1]: 192.168.0.32/24
    IP4.GATEWAY: 192.168.0.254
    IP4.ROUTE[1]: dst = 192.168.0.0/24, nh = 0.0.0.0, mt >
    IP4.ROUTE[2]: dst = 0.0.0.0/0, nh = 192.168.0.254, mt>
    IP4.DNS[1]: 192.168.0.254
    IP4.DOMAIN[1]: fritz.box
    IP6.ADDRESS[1]: 2001:8e0:3061:3801:4605:bfe:603b:773a/64
    IP6.ADDRESS[2]: fd7f:40a2:2062:0:1865:9155:35d0:ca7a/64
    IP6.ADDRESS[3]: fe80::e422:8061:45b2:37bb/64
    IP6.GATEWAY: fe80::7642:7fff:fe1f:643d
    IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 1024
    IP6.ROUTE[2]: dst = fd7f:40a2:2062::/64, nh = ::, mt >
    IP6.ROUTE[3]: dst = 2001:8e0:3061:3801::/64, nh = ::,>
    IP6.ROUTE[4]: dst = fd7f:40a2:2062::/64, nh = fe80::7>
    IP6.ROUTE[5]: dst = 2001:8e0:3061:3800::/56, nh = fe8>
    IP6.ROUTE[6]: dst = ::/0, nh = fe80::7642:7fff:fe1f:6>


    nmcli device status:


    DEVICE TYPE STATE CONNECTION
    wlan0 wifi connected preconfigured
    lo loopback connected (externally) lo
    p2p-dev-wlan0 wifi-p2p disconnected --
    end0 ethernet unavailable --
    can0 can unmanaged --


    NAME UUID TYPE DEVICE
    preconfigured 7e330f30-cfec-4959-b18e-cac7e17e6689 wifi wlan0
    lo cd9082f3-b4ab-46f3-af19-169075e7cff3 loopback lo
    Wired connection 1 9588e6e6-dab5-323a-93fc-bf93a0b65a3e ethernet --


  • Den

    Code
    nmcli connection show

    hätte ich gerne.

    Hat der TE doch, im Beitrag #14 unten:

    Code
    NAME UUID TYPE DEVICE
    preconfigured 7e330f30-cfec-4959-b18e-cac7e17e6689 wifi wlan0
    lo cd9082f3-b4ab-46f3-af19-169075e7cff3 loopback lo
    Wired connection 1 9588e6e6-dab5-323a-93fc-bf93a0b65a3e ethernet --

    Bei "Wired connection 1" wird kein device gezeigt/gefunden.


  • pi@Hevort:~ $ sudo nmcli c up "Wired connection 1"
    Error: Connection activation failed: The device could not be readied for configuration
    Hint: use 'journalctl -xe NM_CONNECTION=9588e6e6-dab5-323a-93fc-bf93a0b65a3e + NM_DEVICE=end0' to get more details.

    Dann kommt

    Mar 13 17:55:39 Hevort NetworkManager[933]: <warn> [1741884939.2322] device (end0): Activation: fa>
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2324] device (end0): state change: >
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2342] device (end0): Activation: st>
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2343] device (end0): state change: >
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2346] device (end0): state change: >
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2350] device (end0): state change: >
    Mar 13 17:55:39 Hevort NetworkManager[933]: <warn> [1741884939.2354] device (end0): Activation: fa>
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2357] device (end0): state change: >
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2367] device (end0): Activation: st>
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2368] device (end0): state change: >
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2371] device (end0): state change: >
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2374] device (end0): state change: >
    Mar 13 17:55:39 Hevort NetworkManager[933]: <warn> [1741884939.2377] device (end0): Activation: fa>
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2379] device (end0): state change: >

  • Hier noch mal komplett...

    pi@Hevort:~ $ journalctl -xe NM_CONNECTION=9588e6e6-dab5-323a-93fc-bf93a0b65a3e + NM_DEVICE=end0
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2281] device (end0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2284] device (end0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2295] device (end0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <warn> [1741884939.2298] device (end0): Activation: failed for connection 'Wired connection 1'
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2300] device (end0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2312] device (end0): Activation: starting connection 'Wired connection 1' (9588e6e6-dab5-323a-93fc-bf93a0b65a3e)
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2313] device (end0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2316] device (end0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2319] device (end0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <warn> [1741884939.2322] device (end0): Activation: failed for connection 'Wired connection 1'
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2324] device (end0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2342] device (end0): Activation: starting connection 'Wired connection 1' (9588e6e6-dab5-323a-93fc-bf93a0b65a3e)
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2343] device (end0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2346] device (end0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2350] device (end0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <warn> [1741884939.2354] device (end0): Activation: failed for connection 'Wired connection 1'
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2357] device (end0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2367] device (end0): Activation: starting connection 'Wired connection 1' (9588e6e6-dab5-323a-93fc-bf93a0b65a3e)
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2368] device (end0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2371] device (end0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2374] device (end0): state change: config -> failed (reason 'config-failed', sys-iface-state: 'managed')
    Mar 13 17:55:39 Hevort NetworkManager[933]: <warn> [1741884939.2377] device (end0): Activation: failed for connection 'Wired connection 1'
    Mar 13 17:55:39 Hevort NetworkManager[933]: <info> [1741884939.2379] device (end0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!