musikfant
Anmeldungsdatum: 15. Dezember 2018
Beiträge: 11
|
Hallo liebe Community, leider bekomme ich meine LAN Verbindung nicht zum laufen. Es wird immer nur angezeigt dass das Kabel nicht angeschlossen ist.
Dies ist aber der Fall denn ich habe ebenfalls Windows auf dem PC und dort läuft alles ohne Beanstandungen.
Ich vermute wohl einen Konfigurationsfehler. Könnt ihr mir helfen? (PS: was Terminal angeht bin ich leider ziemlich noob)
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
Zeige alle Terminal-Ausgaben von hier in Codeblöcken zur "Diagnose". Funktioniert WLAN? Gruss praseodym
|
kB
Supporter, Wikiteam
Anmeldungsdatum: 4. Oktober 2007
Beiträge: 8616
Wohnort: Münster
|
musikfant schrieb: […] LAN […] angezeigt dass das Kabel nicht angeschlossen ist […] ebenfalls Windows auf dem PC
MS-Windows hinterlässt Hardware zuweilen in einem desolaten Zustand, insbesondere wenn es nicht richtig und vollständig beendet wurde. Schalte "Fast Boot" im Bios/UEFI und in Windows ab und verwende keinerlei Ruhezustand unter Windows.
|
musikfant
(Themenstarter)
Anmeldungsdatum: 15. Dezember 2018
Beiträge: 11
|
Dann hier mal die Angaben aus dem Terminl
chris@chris-EP35-DS3:~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
chris@chris-EP35-DS3:~$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 00:1f:d0:56:07:36 brd ff:ff:ff:ff:ff:ff
3: enp5s2: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
link/ether 0c:b6:d2:b2:bc:c1 brd ff:ff:ff:ff:ff:ff
4: wlp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
link/ether 00:0e:2e:48:bc:0c brd ff:ff:ff:ff:ff:ff
chris@chris-EP35-DS3:~$ ip -4 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
4: wlp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
inet 192.168.178.38/24 brd 192.168.178.255 scope global dynamic noprefixroute wlp5s0
valid_lft 863669sec preferred_lft 863669sec
chris@chris-EP35-DS3:~$ ip -4 route
default via 192.168.178.1 dev wlp5s0 proto dhcp metric 600
169.254.0.0/16 dev wlp5s0 scope link metric 1000
192.168.178.0/24 dev wlp5s0 proto kernel scope link src 192.168.178.38 metric 600
chris@chris-EP35-DS3:~$ ip -4 neigh
192.168.178.1 dev wlp5s0 lladdr c8:0e:14:8d:c9:58 REACHABLE
chris@chris-EP35-DS3:~$
chris@chris-EP35-DS3:~$ lspci -nnk | grep -i net -A2
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 01)
Subsystem: Gigabyte Technology Co., Ltd Onboard Ethernet [1458:e000]
Kernel driver in use: r8168
Kernel modules: r8168
05:00.0 Network controller [0280]: Ralink corp. RT2561/RT61 802.11g PCI [1814:0301]
Subsystem: Ralink corp. EW-7108PCg/EW-7128g [1814:2561]
Kernel driver in use: rt61pci
--
05:02.0 Ethernet controller [0200]: D-Link System Inc DGE-528T Gigabit Ethernet Adapter [1186:4300] (rev 10)
Subsystem: D-Link System Inc DGE-528T PCI Gigabit Ethernet Adapter [1186:4300]
Kernel driver in use: r8169
Kernel modules: r8169
chris@chris-EP35-DS3:~$ nmcli general ; nmcli device ; nmcli connection
STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN
verbunden vollständig aktiviert aktiviert aktiviert aktiviert
DEVICE TYPE STATE CONNECTION
wlp5s0 wifi verbunden Sandhaas-Lan 24
enp4s0 ethernet nicht verfügbar --
enp5s2 ethernet nicht verfügbar --
lo loopback nicht verwaltet --
NAME UUID TYPE DEV
Sandhaas-Lan 24 a336d00a-503a-41df-bd26-1de62e7ade75 wifi wlp
Kabelgebundene Verbindung 1 5e88ae6d-726e-3cc0-a9d0-b364cb36d146 ethernet --
Kabelgebundene Verbindung 2 8d646aec-0f8d-3b10-9091-b08b9e2c6af8 ethernet --
lines 1-4/4 (END)
chris@chris-EP35-DS3:~$ grep -r "" /etc/NetworkManager/NetworkManager.conf /{usr/lib,run,etc}/NetworkManager/conf.d/
/etc/NetworkManager/NetworkManager.conf:[main]
/etc/NetworkManager/NetworkManager.conf:plugins=ifupdown,keyfile
/etc/NetworkManager/NetworkManager.conf:
/etc/NetworkManager/NetworkManager.conf:[ifupdown]
/etc/NetworkManager/NetworkManager.conf:managed=false
/etc/NetworkManager/NetworkManager.conf:
/etc/NetworkManager/NetworkManager.conf:[device]
/etc/NetworkManager/NetworkManager.conf:wifi.scan-rand-mac-address=no
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf:[keyfile]
/usr/lib/NetworkManager/conf.d/10-globally-managed-devices.conf:unmanaged-devices=*,except:type:wifi,except:type:wwan
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf:[connectivity]
/usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf:uri=http://connectivity-check.ubuntu.com/
/usr/lib/NetworkManager/conf.d/10-dns-resolved.conf:[main]
/usr/lib/NetworkManager/conf.d/10-dns-resolved.conf:# We need to specify "dns=systemd-resolved" as for the time being our
/usr/lib/NetworkManager/conf.d/10-dns-resolved.conf:# /etc/resolv.conf points to resolvconf's generated file instead of
/usr/lib/NetworkManager/conf.d/10-dns-resolved.conf:# systemd-resolved's, so the auto-detection does not work.
/usr/lib/NetworkManager/conf.d/10-dns-resolved.conf:dns=systemd-resolved
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:# Certain drivers are known not to support changing the MAC address.
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:# Disable touching the MAC address on such devices.
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:#
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:# See man NetworkManager.conf
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:#
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:# https://bugzilla.gnome.org/show_bug.cgi?id=777523
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:[device-mac-addr-change-wifi]
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:match-device=driver:rtl8723bs,driver:rtl8189es,driver:r8188eu,driver:8188eu,driver:eagle_sdio,driver:wl
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:wifi.scan-rand-mac-address=no
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:wifi.cloned-mac-address=preserve
/usr/lib/NetworkManager/conf.d/no-mac-addr-change.conf:ethernet.cloned-mac-address=preserve
/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf:[connection]
/etc/NetworkManager/conf.d/default-wifi-powersave-on.conf:wifi.powersave = 3 Ich hoffe ich habe es richtig gemacht und es kann mir jemand helfen
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
|
musikfant
(Themenstarter)
Anmeldungsdatum: 15. Dezember 2018
Beiträge: 11
|
lsmod
Module Size Used by
ccm 20480 6
gpio_ich 16384 0
snd_hda_codec_realtek 94208 1
snd_hda_codec_generic 73728 1 snd_hda_codec_realtek
arc4 16384 2
snd_hda_intel 40960 3
snd_hda_codec 126976 3 snd_hda_intel,snd_hda_codec_generic,snd_hda_codec_realtek
rt61pci 32768 0
snd_hda_core 81920 4 snd_hda_intel,snd_hda_codec,snd_hda_codec_generic,snd_hda_codec_realtek
rt2x00pci 16384 1 rt61pci
rt2x00mmio 16384 1 rt61pci
snd_hwdep 20480 1 snd_hda_codec
rt2x00lib 53248 3 rt2x00pci,rt61pci,rt2x00mmio
mac80211 778240 2 rt2x00pci,rt2x00lib
snd_pcm 98304 3 snd_hda_intel,snd_hda_codec,snd_hda_core
coretemp 16384 0
joydev 24576 0
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
serio_raw 16384 0
cfg80211 622592 2 rt2x00lib,mac80211
input_leds 16384 0
snd_rawmidi 32768 1 snd_seq_midi
eeprom_93cx6 16384 1 rt61pci
sch_fq_codel 20480 7
crc_itu_t 16384 1 rt61pci
lpc_ich 24576 0
snd_seq 65536 2 snd_seq_midi_event,snd_seq_midi
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
snd_timer 32768 2 snd_seq,snd_pcm
snd 81920 16 snd_hda_intel,snd_hwdep,snd_seq,snd_hda_codec,snd_timer,snd_rawmidi,snd_hda_codec_generic,snd_seq_device,snd_hda_codec_realtek,snd_pcm
mac_hid 16384 0
soundcore 16384 1 snd
shpchp 36864 0
parport_pc 36864 1
ppdev 20480 0
lp 20480 0
parport 49152 3 lp,parport_pc,ppdev
ip_tables 28672 0
x_tables 40960 1 ip_tables
autofs4 40960 2
hid_generic 16384 0
nouveau 1716224 3
psmouse 147456 0
mxm_wmi 16384 1 nouveau
wmi 24576 2 mxm_wmi,nouveau
video 45056 1 nouveau
r8169 86016 0
i2c_algo_bit 16384 1 nouveau
ttm 106496 1 nouveau
mii 16384 1 r8169
pata_acpi 16384 0
drm_kms_helper 172032 1 nouveau
ahci 36864 2
usbhid 49152 0
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
hid 118784 2 hid_generic,usbhid
sysimgblt 16384 1 drm_kms_helper
fb_sys_fops 16384 1 drm_kms_helper
drm 401408 6 nouveau,ttm,drm_kms_helper
libahci 32768 1 ahci
pata_jmicron 16384 0
r8168 528384 0
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
Es werden 2 Treiber geladen echo "blacklist r8169" | sudo tee -a /etc/modprobe.d/blacklist.conf Neustart
|
musikfant
(Themenstarter)
Anmeldungsdatum: 15. Dezember 2018
Beiträge: 11
|
Leider hat das nichts geholfen. Er zeigt immer noch an dass kein Kabel angeschlossen ist.
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
Dann
ifconfig -a
cat /etc/resolv.conf
cat /etc/network/interfaces
route -n
lsmod | grep r8
dmesg | grep r8
|
musikfant
(Themenstarter)
Anmeldungsdatum: 15. Dezember 2018
Beiträge: 11
|
chris@chris-EP35-DS3:~$ ifconfig -a
enp4s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 00:1f:d0:56:07:36 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 16 base 0x1000
enp5s2: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 0c:b6:d2:b2:bc:c1 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Lokale Schleife)
RX packets 437 bytes 33173 (33.1 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 437 bytes 33173 (33.1 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.178.38 netmask 255.255.255.0 broadcast 192.168.178.255
inet6 fe80::e093:6a0c:ab7e:447 prefixlen 64 scopeid 0x20<link>
ether 00:0e:2e:48:bc:0c txqueuelen 1000 (Ethernet)
RX packets 1197 bytes 1134522 (1.1 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1094 bytes 161088 (161.0 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
chris@chris-EP35-DS3:~$ cat /etc/resolv.conf
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "systemd-resolve --status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
search fritz.box
chris@chris-EP35-DS3:~$ cat /etc/network/interfaces
# interfaces(5) file used by ifup(8) and ifdown(8)
auto lo
iface lo inet loopback
chris@chris-EP35-DS3:~$ route -n
Kernel-IP-Routentabelle
Ziel Router Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.178.1 0.0.0.0 UG 600 0 0 wlp5s0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 wlp5s0
192.168.178.0 0.0.0.0 255.255.255.0 U 600 0 0 wlp5s0
chris@chris-EP35-DS3:~$ lsmod | grep r8
r8169 86016 0
mii 16384 1 r8169
r8168 528384 0
chris@chris-EP35-DS3:~$ dmesg | grep r8
[ 0.000000] percpu: Embedded 46 pages/cpu @ (ptrval) s151552 r8192 d28672 u524288
[ 0.000000] pcpu-alloc: s151552 r8192 d28672 u524288 alloc=1*2097152
[ 1.944667] r8168: loading out-of-tree module taints kernel.
[ 1.944984] r8168: module verification failed: signature and/or required key missing - tainting kernel
[ 1.945491] r8168 Gigabit Ethernet driver 8.046.00-NAPI loaded
[ 1.945616] r8168 0000:04:00.0: Default use INTx.
[ 1.967299] r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
[ 1.967307] r8168 Copyright (C) 2018 Realtek NIC software team <nicfae@realtek.com>
[ 1.967351] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 1.967610] r8169 0000:05:02.0 (unnamed net_device) (uninitialized): not PCI Express
[ 1.967890] r8169 0000:05:02.0 eth1: RTL8169sb/8110sb at 0x (ptrval), 0c:b6:d2:b2:bc:c1, XID 10000000 IRQ 18
[ 1.967892] r8169 0000:05:02.0 eth1: jumbo features [frames: 7152 bytes, tx checksumming: ok]
[ 2.011416] r8168 0000:04:00.0 enp4s0: renamed from eth0
[ 2.041508] r8169 0000:05:02.0 enp5s2: renamed from eth1
[ 7.312155] r8169 0000:05:02.0 enp5s2: link down
nach Ausführung und Neustart immer noch keine Besserung
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
modprobe -c | grep -i "1186.*4300"
alias pci:v00001186d00004300sv*sd*bc*sc*i* r8169
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8169
alias pci:v00001186d00004300sv00001186sd00004B10bc*sc*i* r8168 Der zweite NIC wird in jedem Fall vom selben Treiber angesprochen, nacheinander laden bringts also nicht. Checke
dmesg | egrep '04:00.0|05:02.0'
sudo apt-get install ethtool
sudo ethtool enp4s0
sudo ethtool enp5s2
|
musikfant
(Themenstarter)
Anmeldungsdatum: 15. Dezember 2018
Beiträge: 11
|
Settings for enp4s0:
Supported ports: [ TP ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
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/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Speed: Unknown!
Duplex: Unknown! (255)
Port: Twisted Pair
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
MDI-X: Unknown
Supports Wake-on: pumbg
Wake-on: ug
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: no
chris@chris-EP35-DS3:~$ sudo ethtool enp5s2
Settings for enp5s2:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: No
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
Speed: 10Mb/s
Duplex: Half
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: d
Current message level: 0x00000033 (51)
drv probe ifdown ifup
Link detected: no
|
praseodym
Supporter
Anmeldungsdatum: 9. Februar 2009
Beiträge: 22097
Wohnort: ~
|
Probiere
sudo ethtool -s enp4s0 speed 1000 duplex full
sudo ethtool -s enp5s2 speed 1000 duplec full Wenn dann nichts mehr geht, dann mit "speed 10 duplex half" entsprechend rückgängig machen
|
kB
Supporter, Wikiteam
Anmeldungsdatum: 4. Oktober 2007
Beiträge: 8616
Wohnort: Münster
|
kB schrieb: musikfant schrieb: […] LAN […] angezeigt dass das Kabel nicht angeschlossen ist […] ebenfalls Windows auf dem PC
MS-Windows hinterlässt Hardware zuweilen in einem desolaten Zustand, insbesondere wenn es nicht richtig und vollständig beendet wurde. Schalte "Fast Boot" im Bios/UEFI und in Windows ab und verwende keinerlei Ruhezustand unter Windows.
Hast Du meinen Rat befolgt? Du hast Dich nicht dazu geäußert.
|
musikfant
(Themenstarter)
Anmeldungsdatum: 15. Dezember 2018
Beiträge: 11
|
hab ich alles versucht, alles erfolglos
|