Am Samstag, 17. Februar 2018, 00:50:17 CET schrieb Gerhard Schmidt:
36: PCI 100.0: 0200 Ethernet controller [Created at pci.378] Unique ID: rBUF.iuyjajpuXd7 Parent ID: 8otl.G5Dfw+ssufC SysFS ID: /devices/pci0000:00/0000:00:04.0/0000:01:00.0 SysFS BusID: 0000:01:00.0 Hardware Class: network Model: "Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd." Device: pci 0x8168 "RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x5100 Revision: 0x07 Driver: "r8169" Driver Modules: "r8169" Device File: eth0 I/O Ports: 0x1000-0x1fff (rw) Memory Range: 0xf0004000-0xf0004fff (ro,non-prefetchable) Memory Range: 0xf0000000-0xf0003fff (ro,non-prefetchable) IRQ: 37 (no events) HW Address: f8:a9:63:53:63:32 Permanent HW Address: f8:a9:63:53:63:32 Link detected: no Module Alias: "pci:v000010ECd00008168sv000017AAsd00005100bc02sc00i00" Driver Info #0: Driver Status: r8169 is active Driver Activation Cmd: "modprobe r8169" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge)
37: PCI 200.0: 0280 Network controller [Created at pci.378] Unique ID: B35A.VzDMlxn7pf2 Parent ID: CvwD.nV9PPa_ZQ2D SysFS ID: /devices/pci0000:00/0000:00:05.0/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Model: "Broadcom BCM43142 802.11b/g/n" Vendor: pci 0x14e4 "Broadcom" Device: pci 0x4365 "BCM43142 802.11b/g/n" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x0611 Revision: 0x01 Driver: "bcma-pci-bridge" Driver Modules: "bcma" Memory Range: 0xf0200000-0xf0207fff (rw,non-prefetchable) IRQ: 17 (28 events) Module Alias: "pci:v000014E4d00004365sv000017AAsd00000611bc02sc80i00" Driver Info #0: Driver Status: bcma is active Driver Activation Cmd: "modprobe bcma" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #17 (PCI bridge)
71: None 00.0: 10700 Loopback [Created at net.126] Unique ID: ZsBS.GQNx7L4uPNA SysFS ID: /class/net/lo Hardware Class: network interface Model: "Loopback network interface" Device File: lo Link detected: yes Config Status: cfg=new, avail=yes, need=no, active=unknown
72: None 00.0: 10701 Ethernet [Created at net.126] Unique ID: usDW.ndpeucax6V1 Parent ID: rBUF.iuyjajpuXd7 SysFS ID: /class/net/eth0 SysFS Device Link: /devices/pci0000:00/0000:00:04.0/0000:01:00.0 Hardware Class: network interface Model: "Ethernet network interface" Driver: "r8169" Driver Modules: "r8169" Device File: eth0 HW Address: f8:a9:63:53:63:32 Permanent HW Address: f8:a9:63:53:63:32 Link detected: no Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #36 (Ethernet controller)
mfg gerd
LAN-Kabel anschließen, alle Updates machen. Neu starten. Zum Thema Wlan: Packman Repo einbinden und: zypper in broadcom-wl broadcom-wl-kmp-default Neustarten oder Netzwerk neu starten. Zum Thema LAN: Ich benutze den r8168 Treiber, den gibt es auch im Packman Repo. zypper in r8168-kmp-default r8168-blacklist-r8169 Neustarten oder Netzwerk neu starten. Stephan -- Um die Liste abzubestellen, schicken Sie eine Mail an: opensuse-de+unsubscribe@opensuse.org Um den Listen Administrator zu erreichen, schicken Sie eine Mail an: opensuse-de+owner@opensuse.org