d.h. auch das hier https://en.opensuse.org/SDB:Realtek_8169_driver_problem konnte keine Abhilfe schaffen?toyotafahrer schrieb:... Und es geht immer noch kein LAN.
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Typ | Version | Arch | Repository
---+--------------------------------+--------+---------------------+--------+-----------------------
i+ | devel_kernel | Schema | 20170518-6.1 | x86_64 | openSUSE-Leap-42.3-Oss
i+ | kernel-default | Paket | 4.14.5-2.1.gb0756c5 | x86_64 | (Systempakete)
i+ | kernel-default | Paket | 4.14.6-2.1.g9248b63 | x86_64 | Kernel Stable Repo
i | kernel-default-devel | Paket | 4.14.6-2.1.g9248b63 | x86_64 | Kernel Stable Repo
i+ | kernel-devel | Paket | 4.14.6-1.1.g45f120a | noarch | (Systempakete)
i+ | kernel-devel | Paket | 4.14.6-2.1.g9248b63 | noarch | Kernel Stable Repo
i+ | kernel-firmware | Paket | 20171204-35.1 | noarch | Kernel Stable Repo
i | kernel-macros | Paket | 4.14.6-1.1.g45f120a | noarch | (Systempakete)
i+ | kernel-source | Paket | 4.14.6-1.1.g45f120a | noarch | (Systempakete)
i+ | patterns-openSUSE-devel_kernel | Paket | 20170518-6.1 | x86_64 | openSUSE-Leap-42.3-Oss
i+ | r8168 | Paket | 8.045.08-44.1 | x86_64 | Sauerland_kernel
fritzbox:/home/lutz # uname -a
Linux fritzbox 4.14.6-2.g9248b63-default #1 SMP PREEMPT Fri Dec 15 11:38:40 UTC 2017 (9248b63) x86_64 x86_64 x86_64 GNU/Linux
lo Link encap:Lokale Schleife
inet Adresse:127.0.0.1 Maske:255.0.0.0
inet6 Adresse: ::1/128 Gültigkeitsbereich:Maschine
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:21184 errors:0 dropped:0 overruns:0 frame:0
TX packets:21184 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:1000
RX bytes:1287682 (1.2 Mb) TX bytes:1287682 (1.2 Mb)
wlan0 Link encap:Ethernet Hardware Adresse 50:B7:C3:FE:FC:53
inet Adresse:192.168.178.xx Bcast:192.168.xxx.xxx Maske:255.255.255.0
inet6 Adresse: 2003:d3:33d0:6a00:xxxx:c3ff:fefe:fc53/128 Gültigkeitsbereich:Global
inet6 Adresse: fe80::52b7:c3ff:fefe:xxxx/64 Gültigkeitsbereich:Verbindung
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:70441 errors:0 dropped:0 overruns:0 frame:0
TX packets:64158 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 Sendewarteschlangenlänge:1000
RX bytes:50319828 (47.9 Mb) TX bytes:13128357 (12.5 Mb)
Dez 17 15:15:47 fritzbox systemd-modules-load[202]: Failed to find module 'r8168'
Dez 17 15:15:47 fritzbox kernel: vga_switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle
Dez 17 15:15:48 fritzbox kernel: [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
Dez 17 15:15:49 fritzbox systemd-modules-load[541]: Failed to find module 'r8168'
Dez 17 15:15:49 fritzbox kernel: [Firmware Bug]: battery: (dis)charge rate invalid.
Dez 17 15:15:49 fritzbox kernel: ath: phy0: Set BT/WLAN RX diversity capability
Dez 17 15:15:49 fritzbox systemd-modules-load[847]: Failed to find module 'r8168'
Dez 17 15:15:50 fritzbox kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> monitoring kernel firmware directory '/lib/firmware'.
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> Loaded device plugin: NMVethFactory (internal)
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> Loaded device plugin: NMEthernetFactory (internal)
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> (wlan0): using nl80211 for WiFi device control
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> (wlan0): driver supports Access Point (AP) mode
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> (wlan0): new 802.11 WiFi device (carrier: UNKNOWN, driver: 'ath9k', ifindex: 2)
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: init -> starting
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> (wlan0) supports 4 scan SSIDs
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: starting -> ready
Dez 17 15:15:51 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: ready -> inactive
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: starting connection 'LinuxPower-FB7490' (0da3ea73-cb1b-4132-9555-352787ccc051)
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: (wifi) access point 'LinuxPower-FB7490' has security, but secrets are required.
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <warn> (wlan0): No agents were available for this request.
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: need-auth -> failed (reason 'no-secrets') [60 120 7]
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <warn> (wlan0): Activation: failed for connection 'LinuxPower-FB7490'
Dez 17 15:15:52 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: starting connection 'LinuxPower-FB7490' (0da3ea73-cb1b-4132-9555-352787ccc051)
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: (wifi) access point 'LinuxPower-FB7490' has security, but secrets are required.
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: (wifi) connection 'LinuxPower-FB7490' has security, and secrets exist. No new secrets needed.
Dez 17 15:16:00 fritzbox kernel: wlan0: authenticate with e0:28:6d:2b:d7:e8
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: inactive -> authenticating
Dez 17 15:16:00 fritzbox kernel: wlan0: send auth to e0:28:6d:2b:d7:e8 (try 1/3)
Dez 17 15:16:00 fritzbox kernel: wlan0: authenticated
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dez 17 15:16:00 fritzbox kernel: wlan0: associate with e0:28:6d:2b:d7:e8 (try 1/3)
Dez 17 15:16:00 fritzbox kernel: wlan0: RX AssocResp from e0:28:6d:2b:d7:e8 (capab=0x431 status=0 aid=1)
Dez 17 15:16:00 fritzbox kernel: wlan0: associated
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'LinuxPower-FB7490'.
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv4 state changed unknown -> bound
Dez 17 15:16:00 fritzbox avahi-daemon[1029]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.49.
Dez 17 15:16:00 fritzbox avahi-daemon[1029]: New relevant interface wlan0.IPv4 for mDNS.
Dez 17 15:16:00 fritzbox avahi-daemon[1029]: Registering new address record for 192.168.178.xx on wlan0.IPv4.
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> Policy set 'LinuxPower-FB7490' (wlan0) as default for IPv4 routing and DNS.
Dez 17 15:16:00 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: successful, device activated.
Dez 17 15:16:00 fritzbox nm-dispatcher[1912]: Dispatching action 'up' for wlan0
Dez 17 15:16:01 fritzbox avahi-daemon[1029]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::52b7:c3ff:fefe:fc53.
Dez 17 15:16:01 fritzbox avahi-daemon[1029]: New relevant interface wlan0.IPv6 for mDNS.
Dez 17 15:16:01 fritzbox avahi-daemon[1029]: Registering new address record for fe80::52b7:c3ff:fefe:xxxx on wlan0.*.
Dez 17 15:16:01 fritzbox NetworkManager[1052]: <info> Activation (wlan0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Dez 17 15:16:02 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv6 state changed unknown -> bound
Dez 17 15:16:02 fritzbox NetworkManager[1052]: <info> Policy set 'LinuxPower-FB7490' (wlan0) as default for IPv6 routing and DNS.
Dez 17 15:16:02 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv6 client pid 1948 exited with status 0
Dez 17 15:16:02 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv6 state changed bound -> done
Dez 17 15:16:02 fritzbox nm-dispatcher[1912]: Dispatching action 'dhcp6-change' for wlan0
Dez 17 15:16:04 fritzbox avahi-daemon[1029]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::52b7:c3ff:fefe:xxxx.
Dez 17 15:16:04 fritzbox avahi-daemon[1029]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2003:d3:33d0:6a00:52b7:c3ff:fefe:xxxx.
Dez 17 15:16:04 fritzbox avahi-daemon[1029]: Registering new address record for 2003:d3:33d0:6a00:52b7:c3ff:fefe:xxxx on wlan0.*.
Dez 17 15:16:04 fritzbox avahi-daemon[1029]: Withdrawing address record for fe80::52b7:c3ff:fefe:xxxx on wlan0.
Dez 17 15:16:36 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: activated -> deactivating (reason 'user-requested') [100 110 39]
Dez 17 15:16:36 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: deactivating -> disconnected (reason 'user-requested') [110 30 39]
Dez 17 15:16:36 fritzbox NetworkManager[1052]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 1802
Dez 17 15:16:36 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv4 state changed bound -> done
Dez 17 15:16:36 fritzbox NetworkManager[1052]: <info> (wlan0): canceled DHCP transaction
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Withdrawing address record for 2003:d3:33d0:6a00:52b7:c3ff:fefe:xxxx on wlan0.
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Leaving mDNS multicast group on interface wlan0.IPv6 with address 2003:d3:33d0:6a00:52b7:c3ff:fefe:xxxx.
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::52b7:c3ff:fefe:xxxx.
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Registering new address record for fe80::52b7:c3ff:fefe:xxxx on wlan0.*.
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Withdrawing address record for fe80::52b7:c3ff:fefe:xxxx on wlan0.
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::52b7:c3ff:fefe:xxxx.
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Interface wlan0.IPv6 no longer relevant for mDNS.
Dez 17 15:16:36 fritzbox kernel: wlan0: deauthenticating from e0:28:6d:2b:d7:e8 by local choice (Reason: 3=DEAUTH_LEAVING)
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Withdrawing address record for 192.168.178.xx on wlan0.
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.xx.
Dez 17 15:16:36 fritzbox avahi-daemon[1029]: Interface wlan0.IPv4 no longer relevant for mDNS.
Dez 17 15:16:36 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: completed -> disconnected
Dez 17 15:16:36 fritzbox nm-dispatcher[21417]: Dispatching action 'down' for wlan0
Dez 17 15:17:31 fritzbox purge-kernels[1057]: r8168-kmp-default-8.044.02_k4.4.92_31-4.5.x86_64
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: starting connection 'LinuxPower-FB7490' (0da3ea73-cb1b-4132-9555-352787ccc051)
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: (wifi) access point 'LinuxPower-FB7490' has security, but secrets are required.
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: config -> need-auth (reason 'none') [50 60 0]
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: prepare -> config (reason 'none') [40 50 0]
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: (wifi) connection 'LinuxPower-FB7490' has security, and secrets exist. No new secrets needed.
Dez 17 15:20:27 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: disconnected -> scanning
Dez 17 15:20:28 fritzbox kernel: wlan0: authenticate with e0:28:6d:2b:d7:e8
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: scanning -> authenticating
Dez 17 15:20:28 fritzbox kernel: wlan0: send auth to e0:28:6d:2b:d7:e8 (try 1/3)
Dez 17 15:20:28 fritzbox kernel: wlan0: authenticated
Dez 17 15:20:28 fritzbox kernel: wlan0: associate with e0:28:6d:2b:d7:e8 (try 1/3)
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: authenticating -> associating
Dez 17 15:20:28 fritzbox kernel: wlan0: RX AssocResp from e0:28:6d:2b:d7:e8 (capab=0x431 status=0 aid=1)
Dez 17 15:20:28 fritzbox kernel: wlan0: associated
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: associating -> 4-way handshake
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): supplicant interface state: 4-way handshake -> completed
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network 'LinuxPower-FB7490'.
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: config -> ip-config (reason 'none') [50 70 0]
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv4 state changed unknown -> bound
Dez 17 15:20:28 fritzbox avahi-daemon[1029]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.178.49.
Dez 17 15:20:28 fritzbox avahi-daemon[1029]: New relevant interface wlan0.IPv4 for mDNS.
Dez 17 15:20:28 fritzbox avahi-daemon[1029]: Registering new address record for 192.168.178.xx on wlan0.IPv4.
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> Policy set 'LinuxPower-FB7490' (wlan0) as default for IPv4 routing and DNS.
Dez 17 15:20:28 fritzbox NetworkManager[1052]: <info> (wlan0): Activation: successful, device activated.
Dez 17 15:20:28 fritzbox nm-dispatcher[14767]: Dispatching action 'up' for wlan0
Dez 17 15:20:30 fritzbox avahi-daemon[1029]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::52b7:c3ff:fefe:xxxx.
Dez 17 15:20:30 fritzbox avahi-daemon[1029]: New relevant interface wlan0.IPv6 for mDNS.
Dez 17 15:20:30 fritzbox avahi-daemon[1029]: Registering new address record for fe80::52b7:c3ff:fefe:xxxx on wlan0.*.
Dez 17 15:20:30 fritzbox NetworkManager[1052]: <info> Activation (wlan0) Beginning DHCPv6 transaction (timeout in 45 seconds)
Dez 17 15:20:31 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv6 state changed unknown -> bound
Dez 17 15:20:31 fritzbox NetworkManager[1052]: <info> Policy set 'LinuxPower-FB7490' (wlan0) as default for IPv6 routing and DNS.
Dez 17 15:20:31 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv6 client pid 14794 exited with status 0
Dez 17 15:20:31 fritzbox NetworkManager[1052]: <info> (wlan0): DHCPv6 state changed bound -> done
Dez 17 15:20:31 fritzbox nm-dispatcher[14767]: Dispatching action 'dhcp6-change' for wlan0
Dez 17 15:20:33 fritzbox avahi-daemon[1029]: Leaving mDNS multicast group on interface wlan0.IPv6 with address fe80::52b7:c3ff:fefe:xxxx.
Dez 17 15:20:33 fritzbox avahi-daemon[1029]: Joining mDNS multicast group on interface wlan0.IPv6 with address 2003:d3:33d0:6a00:52b7:c3ff:fefe:xxxx.
Dez 17 15:20:33 fritzbox avahi-daemon[1029]: Registering new address record for 2003:d3:33d0:6a00:52b7:c3ff:fefe:xxxx on wlan0.*.
Dez 17 15:20:33 fritzbox avahi-daemon[1029]: Withdrawing address record for fe80::52b7:c3ff:fefe:xxxx on wlan0.
susejunky schrieb:d.h. auch das hier https://en.opensuse.org/SDB:Realtek_8169_driver_problem konnte keine Abhilfe schaffen?toyotafahrer schrieb:... Und es geht immer noch kein LAN.
Viele Grüße
susejunky
Der SUSE-Support-Datenbank-Artikel sagt aus, dass Windows beim Beenden die LAN-Karte komplett abschaltet und der Linuxtreiber nicht in der Lage ist, sie wieder einzuschalten.toyotafahrer schrieb:... die gehen von einen Win / Suse Rechner aus.
Es gibt aber hier kein Win ... Mit dem Win 10 was hier mal drauf war ging alles
You power down the machine completely and unplug the power supply for a few seconds (about 10 will do). This seems to reset the card and the Linux driver work until you boot Windows again.
oder in deutscher Sprache:
Gerät ausschalten und für einige Sekunden (10 sek. sollten ausreichen) von der Stromversorgung trennen. Das setzt die Karte anscheinend zurück. Anschließend sollte der Linuxtreiber die Karte wieder ansprechen können.
tomm.fa schrieb:Wenn fehlerfrei durchgelaufen den Rechner neu starten.Code:zypper in r8168-kmp-default
Der SUSE-Support-Datenbank-Artikel sagt aus, dass Windows beim Beenden die LAN-Karte komplett abschaltet und der Linuxtreiber nicht in der Lage ist, sie wieder einzuschalten.
Wenn auf Deinem Rechner einst Windows installiert war, besteht also durchaus die Möglichkeit, dass Windows die LAN-Karte (beim allerletzten Beenden) abgeschaltet hat. Und da der Linuxtreiber sie nicht wieder einschalten kann, wird sie weiterhin abgeschaltet bleiben.
So ich mache jetzt hier mal den Strom weg.
Wenn auf Deinem Rechner noch Windows installiert wäre, dann würde sich eher der Workaround 2 aus dem SUSE-Support-Datenbank-Artikel anbieten:toyotafahrer schrieb:... Was würde denn passieren wenn das Win 10 nicht beendet wird sondern im laufenden betrieb den Strom abdrehen , denn kann es doch eigentlich nichts mehr abschalten.
You enable "Wake-on-lan after shutdown." in the Windows device manager. This prevents the Windows driver to disable the card. With newer Windows driver versions this option is not available anymore, instead there is an option "Shutdown Wake On Lan". Changing that new option from "Enabled" to "Disabled" cannot be confirmed to fix the issue.
oder in deutscher Sprache
Im Windows Gerätemanager die Option "Wake-on-lan after shutdown" aktivieren. Das verhindert, dass der Windowstreiber die Karte abschaltet. Bei neueren Versionen des Windowstreibers ist die Option "Wake-on-lan after shutdown" nicht mehr verfügbar. Statt dessen gibt es eine Option "Shutdown Wake On Lan", die von "Enabled" auf "Disabled" umzustellen ist. Es ist allerdings nicht sicher, ob mit dem Umstellen dieser neuen Otion das Problem auch gelöst werden kann.
Alternativ könntest Du nochmals Windows installieren und ausprobieren, ob die oben beschriebene Vorgehensweise funktioniert. Aber das ist natürlich ein sehr aufwendiges Unterfangen mit ungewissem Ausgang.
toyotafahrer schrieb:Das habe ich gemacht
Du hast immer noch nicht verstanden, daß wir nach den einzelnen Versuchen keine Prosa brauchen, sondern Fakten:toyotafahrer schrieb:Ja das war dann leider auch nichts.
zypper se -si kernel r8168
uname -a
lsmod | grep r816
lspci -nnk | grep -iA3 net
journalctl -b | grep -Ei 'r816|firmwa|eth'
Grundsätzlich ja.toyotafahrer schrieb:... Gibt es denn eine Möglichkeit mein Suse so zu sichern wie ich es habe ?
Im Anbetracht der Tatsache, dass man nicht mit Sicherheit sagen kann, dass es den gewünschten Erfolg bringen wird, ist die Installation von Windows ein sehr aufwendiger Lösungsversuch. Der Einsatz eines "Windows-Live-Systems" wäre da die effizientere Lösung.toyotafahrer schrieb:... Das wäre eine Möglichkeit welches Win wäre denn das bessere Win 7 oder Win 10 , aber ich habe da Problem mal gegoogelt die habe ja bei den Umstieg von 7 auf 10 ja auch riesen Probleme. Also ich würde mich für 7 entscheiden .
Metadaten von Repository 'Sauerland_kernel' abrufen .................................................................................................................................[fertig]
Cache für Repository 'Sauerland_kernel' erzeugen ....................................................................................................................................[fertig]
Metadaten von Repository 'Packman Repository' abrufen ...............................................................................................................................[fertig]
Cache für Repository 'Packman Repository' erzeugen ..................................................................................................................................[fertig]
Metadaten von Repository 'openSUSE-Leap-42.3-Update' abrufen ........................................................................................................................[fertig]
Cache für Repository 'openSUSE-Leap-42.3-Update' erzeugen ...........................................................................................................................[fertig]
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
S | Name | Typ | Version | Arch | Repository
---+--------------------------------+--------+----------------------------------+--------+-----------------------
i+ | devel_kernel | Schema | 20170518-6.1 | x86_64 | openSUSE-Leap-42.3-Oss
i+ | kernel-default | Paket | 4.14.6-2.1.g9248b63 | x86_64 | (Systempakete)
i+ | kernel-default | Paket | 4.14.7-1.1.g0598608 | x86_64 | Kernel Stable Repo
i | kernel-default-devel | Paket | 4.14.6-2.1.g9248b63 | x86_64 | (Systempakete)
i | kernel-default-devel | Paket | 4.14.7-1.1.g0598608 | x86_64 | Kernel Stable Repo
i+ | kernel-devel | Paket | 4.14.6-2.1.g9248b63 | noarch | (Systempakete)
i+ | kernel-devel | Paket | 4.14.7-1.1.g0598608 | noarch | Kernel Stable Repo
i+ | kernel-firmware | Paket | 20171204-35.1 | noarch | Kernel Stable Repo
i | kernel-macros | Paket | 4.14.7-1.1.g0598608 | noarch | Kernel Stable Repo
i+ | kernel-source | Paket | 4.14.7-1.1.g0598608 | noarch | Kernel Stable Repo
i+ | patterns-openSUSE-devel_kernel | Paket | 20170518-6.1 | x86_64 | openSUSE-Leap-42.3-Oss
i+ | r8168 | Paket | 8.045.08-44.2 | x86_64 | (Systempakete)
i | r8168-kmp-default | Paket | 8.045.08_k4.14.7_1.g0598608-44.2 | x86_64 | (Systempakete)
Linux fritzbox 4.14.7-1.g0598608-default #1 SMP PREEMPT Sun Dec 17 22:11:47 UTC 2017 (0598608) x86_64 x86_64 x86_64 GNU/Linux
r8168 532480 0
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 09)
Subsystem: Samsung Electronics Co Ltd Device [144d:c0d8]
Kernel driver in use: r8168
Kernel modules: r8169, r8168
03:00.0 Network controller [0280]: Qualcomm Atheros AR9485 Wireless Network Adapter [168c:0032] (rev 01)
Subsystem: Samsung Electronics Co Ltd Device [144d:4105]
Kernel driver in use: ath9k
Kernel modules: ath9k, wl
Dez 19 07:40:33 fritzbox kernel: r8168: loading out-of-tree module taints kernel.
Dez 19 07:40:33 fritzbox kernel: r8168 Gigabit Ethernet driver 8.045.08-NAPI loaded
Dez 19 07:40:33 fritzbox kernel: r8168: This product is covered by one or more of the following patents: US6,570,884, US6,115,776, and US6,327,625.
Dez 19 07:40:33 fritzbox kernel: r8168 Copyright (C) 2017 Realtek NIC software team <nicfae@realtek.com>
Dez 19 07:40:33 fritzbox systemd-modules-load[195]: Inserted module 'r8168'
Dez 19 07:40:33 fritzbox kernel: vga_switcheroo: detected switching method \_SB_.PCI0.GFX0.ATPX handle
Dez 19 07:40:33 fritzbox kernel: [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
Dez 19 07:40:36 fritzbox kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dez 19 07:40:36 fritzbox NetworkManager[1062]: <info> monitoring kernel firmware directory '/lib/firmware'.
Dez 19 07:40:36 fritzbox NetworkManager[1062]: <info> Loaded device plugin: NMVethFactory (internal)
Dez 19 07:40:36 fritzbox NetworkManager[1062]: <info> Loaded device plugin: NMEthernetFactory (internal)
Hattest Du zuerst nur Windows installiert, und damals funktionierte LAN? Dann hast Du Windows durch Linux ersetzt, und hier funktioniert LAN seit Beginn nicht? Es gab also nie ein "dual boot", bei dem LAN nur bei einem Betriebssystem funktionierte? In diesem Fall kann genau zu diesem Zeitpunkt auch ein Defekt der Netzwerkkarte eingetreten sein. Ob Du Dir zur Fehleranalyse die Arbeit antun willst, Windows noch einmal zu installieren, mußt Du entscheiden.
toyotafahrer schrieb:lsmod | grep r816
Code:r8168 532480 0
lspci -nnk | grep -iA3 net
Code:02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 09) Subsystem: Samsung Electronics Co Ltd Device [144d:c0d8] Kernel driver in use: r8168 Kernel modules: r8169, r8168
Ich habe hier eine Meldung über ein Update , ich trau mich gar nicht.
zypper up
S | Name | Typ | Version | Arch | Repository
---+----------------------+-------+---------------------+--------+--------------------------
i+ | kernel-default | Paket | 4.14.6-2.1.g9248b63 | x86_64 | (Systempakete)
S | Name | Typ | Version | Arch | Repository
---+-------------------+-------+----------------------------------+--------+---------------
i+ | r8168-kmp-default | Paket | 8.045.08_k4.14.6_2.g9248b63-44.1 | x86_64 | (Systempakete)