Skip to content

Manjaro Image - LAN Schnittstelle

Verschoben Quartz64
  • Heute haben die Experten mal wieder raus gefunden, warum was nicht klappt. Für die LAN-Schnittstelle fehlt im Manjaro Build ein Kernel Modul.

    Dan vom Manjaro Team hat daraufhin einen neuen Kernel gebaut, der wurde von meinem System auch ordentlich geladen usw.

    pacman -Syu
    

    Kernel-Version

    [root@quartz64 modules-load.d]# uname -a
    Linux quartz64 5.13.0-rc4-0.5-next-20210603-MANJARO-ARM #1 SMP PREEMPT Sat Jul 3 15:34:57 UTC 2021 aarch64 GNU/Linux
    

    Danach neugestartet, aber nix? Nachdenken.....

    lsmod
    

    Kein motorcomm (so heißt das Modul) zu finden. Dann in /etc/modules-load.d ein File angelegt mit Namen net.conf

    Inhalt des Files

    motorcomm
    

    Neustart, danach

    [root@quartz64 modules-load.d]# lsmod
    Module                  Size  Used by
    algif_aead             20480  0
    zram                   36864  2
    cfg80211              401408  0
    algif_skcipher         20480  0
    rfkill                 36864  3 cfg80211
    8021q                  32768  0
    garp                   16384  1 8021q
    algif_hash             20480  0
    mrp                    20480  1 8021q
    af_alg                 32768  3 algif_hash,algif_skcipher,algif_aead
    stp                    20480  1 garp
    llc                    20480  2 stp,garp
    nls_ascii              16384  1
    snd_soc_simple_card    24576  0
    snd_soc_simple_card_utils    28672  1 snd_soc_simple_card
    optee                  28672  0
    ax88179_178a           36864  0
    usbnet                 53248  1 ax88179_178a
    rtc_rk808              20480  1
    sch_fq_codel           20480  3
    motorcomm              16384  1
    fuse                  126976  1
    ip_tables              32768  0
    x_tables               45056  1 ip_tables
    sdhci_of_dwcmshc       16384  0
    nvme                   45056  0
    nvme_core             102400  1 nvme
    

    Ok, das ist es 😊

    [root@quartz64 modules-load.d]# 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 
           valid_lft forever preferred_lft forever
    2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
        link/ether 4e:c4:40:72:9c:35 brd ff:ff:ff:ff:ff:ff
        inet 192.168.3.245/24 brd 192.168.3.255 scope global dynamic noprefixroute eth0
           valid_lft 42520sec preferred_lft 37120sec
        inet6 fd8a:6ff:2880:0:e0ee:811c:d5cb:a139/64 scope global mngtmpaddr noprefixroute 
           valid_lft forever preferred_lft forever
        inet6 2a02:908:1260:xxxx/64 scope global dynamic mngtmpaddr noprefixroute 
           valid_lft 5698sec preferred_lft 2098sec
        inet6 fe80::cfce:6f17:cba1:2b98/64 scope link 
           valid_lft forever preferred_lft forever
    3: ip6tnl0@NONE: <NOARP> mtu 1452 qdisc noop state DOWN group default qlen 1000
        link/tunnel6 :: brd :: permaddr 829b:d7ba:dc5e::
    

    Yeah!

    Und schnell ein

    [root@quartz64 modules-load.d]# iperf3 -c 192.168.3.213
    Connecting to host 192.168.3.213, port 5201
    [  5] local 192.168.3.245 port 52246 connected to 192.168.3.213 port 5201
    [ ID] Interval           Transfer     Bitrate         Retr  Cwnd
    [  5]   0.00-1.00   sec   114 MBytes   953 Mbits/sec    0    411 KBytes       
    [  5]   1.00-2.00   sec   113 MBytes   944 Mbits/sec    0    411 KBytes       
    [  5]   2.00-3.00   sec   112 MBytes   940 Mbits/sec    0    433 KBytes       
    [  5]   3.00-4.00   sec   113 MBytes   947 Mbits/sec    0    502 KBytes       
    [  5]   4.00-5.00   sec   112 MBytes   942 Mbits/sec    0    527 KBytes       
    [  5]   5.00-6.00   sec   112 MBytes   940 Mbits/sec    0    527 KBytes       
    [  5]   6.00-7.00   sec   112 MBytes   940 Mbits/sec    0    527 KBytes       
    [  5]   7.00-8.00   sec   112 MBytes   936 Mbits/sec    0    527 KBytes       
    [  5]   8.00-9.00   sec   113 MBytes   948 Mbits/sec    0    527 KBytes       
    [  5]   9.00-10.00  sec   112 MBytes   937 Mbits/sec    0    527 KBytes       
    - - - - - - - - - - - - - - - - - - - - - - - - -
    [ ID] Interval           Transfer     Bitrate         Retr
    [  5]   0.00-10.00  sec  1.10 GBytes   943 Mbits/sec    0             sender
    [  5]   0.00-10.00  sec  1.10 GBytes   941 Mbits/sec                  receiver
    
    iperf Done.
    [root@quartz64 modules-load.d]# iperf3 -R -c 192.168.3.213
    Connecting to host 192.168.3.213, port 5201
    Reverse mode, remote host 192.168.3.213 is sending
    [  5] local 192.168.3.245 port 52250 connected to 192.168.3.213 port 5201
    [ ID] Interval           Transfer     Bitrate
    [  5]   0.00-1.00   sec   112 MBytes   941 Mbits/sec                  
    [  5]   1.00-2.00   sec   112 MBytes   941 Mbits/sec                  
    [  5]   2.00-3.00   sec   112 MBytes   941 Mbits/sec                  
    [  5]   3.00-4.00   sec   112 MBytes   941 Mbits/sec                  
    [  5]   4.00-5.00   sec   112 MBytes   942 Mbits/sec                  
    [  5]   5.00-6.00   sec   112 MBytes   942 Mbits/sec                  
    [  5]   6.00-7.00   sec   112 MBytes   942 Mbits/sec                  
    [  5]   7.00-8.00   sec   112 MBytes   941 Mbits/sec                  
    [  5]   8.00-9.00   sec   112 MBytes   941 Mbits/sec                  
    [  5]   9.00-10.00  sec   112 MBytes   941 Mbits/sec                  
    - - - - - - - - - - - - - - - - - - - - - - - - -
    [ ID] Interval           Transfer     Bitrate         Retr
    [  5]   0.00-10.00  sec  1.10 GBytes   943 Mbits/sec    0             sender
    [  5]   0.00-10.00  sec  1.10 GBytes   941 Mbits/sec                  receiver
    
    iperf Done.
    

    Funktioniert!

  • Problem ist mittlerweile gefixt.

    [root@quartz64 ~]# uname -a
    Linux quartz64 5.13.0-rc4-0.6-next-20210603-MANJARO-ARM #1 SMP PREEMPT Sat Jul 3 16:52:43 UTC 2021 aarch64 GNU/Linux
    

    Ab dieser Kernelversion wird das Modul automatisch geladen, es ist im Kernel eingebaut.

  • @frankm

    and in 5.13.0-rc4-0.8 you have to do it again 😉

    nice tips 👍 i got the board working

  • FrankMF FrankM verschob dieses Thema von Quartz64 am
  • FrankMF FrankM verschob dieses Thema von Quartz64 - A am

  • Quartz64 - Modell B - Was geht? (Peter Geis Image)

    Quartz64 - B
    1
    0 Stimmen
    1 Beiträge
    120 Aufrufe
    Niemand hat geantwortet
  • Quart64 - Modell B - Was geht? (Manjaro Image)

    Angeheftet Quartz64 - B
    1
    0 Stimmen
    1 Beiträge
    149 Aufrufe
    Niemand hat geantwortet
  • Quartz64 - Modell B - Peter Geis Entwicklungsumgebung

    Images
    2
    0 Stimmen
    2 Beiträge
    134 Aufrufe
    FrankMF
    Was geht? Funktion Status Bemerkung cpufreq ok *3 UART ja *5 LAN hat Fehler *1 USB3 ja ca. 210MB/s *2 PCIe ja ca. 296 MB/s, ist mit einer Lane angeschlossen *4 HDMI nein LAN *1 root@debian:~# iperf3 -c 192.168.3.213 Connecting to host 192.168.3.213, port 5201 [ 5] local 192.168.3.10 port 39124 connected to 192.168.3.213 port 5201 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 434 KBytes 3.55 Mbits/sec 61 2.83 KBytes [ 5] 1.00-2.00 sec 475 KBytes 3.89 Mbits/sec 44 2.83 KBytes [ 5] 2.00-3.00 sec 396 KBytes 3.24 Mbits/sec 43 2.83 KBytes [ 5] 3.00-4.00 sec 318 KBytes 2.61 Mbits/sec 40 2.83 KBytes [ 5] 4.00-5.00 sec 315 KBytes 2.58 Mbits/sec 31 2.83 KBytes [ 5] 5.00-6.00 sec 396 KBytes 3.24 Mbits/sec 46 2.83 KBytes [ 5] 6.00-7.00 sec 396 KBytes 3.24 Mbits/sec 43 2.83 KBytes [ 5] 7.00-8.00 sec 396 KBytes 3.24 Mbits/sec 43 1.41 KBytes [ 5] 8.00-9.00 sec 396 KBytes 3.24 Mbits/sec 47 2.83 KBytes [ 5] 9.00-10.00 sec 317 KBytes 2.59 Mbits/sec 39 2.83 KBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 3.75 MBytes 3.14 Mbits/sec 437 sender [ 5] 0.00-10.00 sec 3.67 MBytes 3.08 Mbits/sec receiver iperf Done. root@debian:~# iperf3 -R -c 192.168.3.213 Connecting to host 192.168.3.213, port 5201 Reverse mode, remote host 192.168.3.213 is sending [ 5] local 192.168.3.10 port 39130 connected to 192.168.3.213 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 112 MBytes 941 Mbits/sec [ 5] 1.00-2.00 sec 112 MBytes 942 Mbits/sec [ 5] 2.00-3.00 sec 112 MBytes 942 Mbits/sec [ 5] 3.00-4.00 sec 112 MBytes 942 Mbits/sec [ 5] 4.00-5.00 sec 112 MBytes 942 Mbits/sec [ 5] 5.00-6.00 sec 112 MBytes 942 Mbits/sec [ 5] 6.00-7.00 sec 112 MBytes 942 Mbits/sec [ 5] 7.00-8.00 sec 112 MBytes 942 Mbits/sec [ 5] 8.00-9.00 sec 112 MBytes 942 Mbits/sec [ 5] 9.00-10.00 sec 112 MBytes 942 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.10 GBytes 943 Mbits/sec 370 sender [ 5] 0.00-10.00 sec 1.10 GBytes 942 Mbits/sec receiver iperf Done. USB3 *2 root@debian:~# lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 002: ID 152d:0578 JMicron Technology Corp. / JMicron USA Technology Corp. JMS578 SATA 6Gb/s Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Disk /dev/sda: 238.47 GiB, 256060514304 bytes, 500118192 sectors Disk model: Generic Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 05AB264B-738E-47BB-9F67-5C04CC24A736 Device Start End Sectors Size Type /dev/sda1 2048 500118158 500116111 238.5G Linux filesystem root@debian:~# mount /dev/sda1 /mnt/sda/ root@debian:~# cd /mnt/sda root@debian:/mnt/sda# dd if=/dev/zero of=sd.img bs=4M count=4096 oflag=direct 4096+0 records in 4096+0 records out 17179869184 bytes (17 GB, 16 GiB) copied, 81.5051 s, 211 MB/s -------------- root@debian:/# lsusb Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 003: ID 04e8:61f5 Samsung Electronics Co., Ltd Portable SSD T5 Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 046d:c31c Logitech, Inc. Keyboard K120 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub root@debian:/mnt/sda# dd if=/dev/zero of=sd.img bs=4M count=4096 oflag=direct 4096+0 records in 4096+0 records out 17179869184 bytes (17 GB, 16 GiB) copied, 83.7618 s, 205 MB/s cpufreq *3 root@debian:~# cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_max_freq 1800000 1800000 1800000 1800000 root@debian:~# cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq 1416000 1416000 1416000 1416000 root@debian:~# cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq 1800000 1800000 1800000 1800000 root@debian:~# cat /sys/devices/system/cpu/cpu*/cpufreq/cpuinfo_cur_freq 1416000 1416000 1416000 1416000 PCIe NVMe SSD *4 root@debian:/mnt/nvme# dd if=/dev/zero of=sd.img bs=4M count=4096 oflag=direct 4096+0 records in 4096+0 records out 17179869184 bytes (17 GB, 16 GiB) copied, 58.0362 s, 296 MB/s Das soll laut Peter die maximal mögliche Geschwindigkeit der PCIe Schnittstelle sein. Diese Schnittstelle ist nur mit einer Lane an den Prozessor angeschlossen! UART Bitte drauf achten, diese Schnittstelle arbeitet mit Level Shifting, was billige Adapter oft nicht abkönnen. Habe ich hier im Beitrag ausführlich erklärt, mit passenden Adapter, wenn es so wie bei mir nicht funktionierte.
  • Quartz64 - Missing SPI ?

    Verschoben Quartz64
    1
    +0
    0 Stimmen
    1 Beiträge
    436 Aufrufe
    Niemand hat geantwortet
  • Quartz64 - sbc-bench

    Verschoben Quartz64
    7
    0 Stimmen
    7 Beiträge
    386 Aufrufe
    FrankMF
    @tkaiser Nein, kein Kühler und kein Lüfter. Nacktes Board
  • Quartz64 - PCIe Schnittstelle

    Verschoben Quartz64 - A
    1
    +0
    0 Stimmen
    1 Beiträge
    216 Aufrufe
    Niemand hat geantwortet
  • Quartz64 - GPIO Modell A

    Angeheftet Verschoben Quartz64 - A
    1
    0 Stimmen
    1 Beiträge
    172 Aufrufe
    Niemand hat geantwortet
  • Pine64 Neuigkeiten Mai 2019

    ROCKPro64
    4
    +1
    0 Stimmen
    4 Beiträge
    393 Aufrufe
    FrankMF
    [image: 1574014324777-f28a1ff9-0ea8-4b25-8aea-6bec3cd495f9-grafik.png]