On 2016-07-08 11:24, Andrei Borzenkov wrote:
On 7/8/16, Carlos E. R. <> wrote:
What can I do?
You can start with showing what actual devices you have.
I bypassed the issue by temporarily switching to Network Manager, which worked instantly, and updating. Now it says: Tumbleweed:~ # hwinfo --netcard 51: PCI 201.0: 0200 Ethernet controller [Created at pci.366] Unique ID: ktq4.5dU8kR7eh2C Parent ID: 7EWs.3XzZP_1GzlF SysFS ID: /devices/pci0000:00/0000:00:11.0/0000:02:01.0 SysFS BusID: 0000:02:01.0 Hardware Class: network Device Name: "Ethernet0" Model: "VMware PRO/1000 MT Single Port Adapter" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x100f "82545EM Gigabit Ethernet Controller (Copper)" SubVendor: pci 0x15ad "VMware, Inc." SubDevice: pci 0x0750 "PRO/1000 MT Single Port Adapter" Revision: 0x01 Driver: "e1000" Driver Modules: "e1000" Device File: eno16777736 Memory Range: 0xfc000000-0xfc01ffff (rw,non-prefetchable) Memory Range: 0xfc020000-0xfc02ffff (rw,non-prefetchable) I/O Ports: 0x1040-0x107f (rw) Memory Range: 0xfc040000-0xfc04ffff (ro,non-prefetchable,disabled) IRQ: 19 (1346 events) HW Address: 00:50:56:2e:d4:dd Link detected: yes Module Alias: "pci:v00008086d0000100Fsv000015ADsd00000750bc02sc00i00" Driver Info #0: Driver Status: e1000 is active Driver Activation Cmd: "modprobe e1000" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #16 (PCI bridge) Tumbleweed:~ # Tumbleweed:~ # cat /etc/os-release NAME=openSUSE VERSION="Tumbleweed" VERSION_ID="20160705" PRETTY_NAME="openSUSE Tumbleweed (20160705) (x86_64)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:20160705" BUG_REPORT_URL="https://bugs.opensuse.org" HOME_URL="https://www.opensuse.org/" ID_LIKE="suse" Tumbleweed:~ # Now I switch to wicked again. [...] It works. It must have been a problem with the version I had of TW. However, YaST shows two network cards, one configured, one not, which I can not delete (it is grayed out). Both are 82545EM Gigabit. I delete the active one and try to configure the other. It still works. I change now the name to eth0 in YaST. This time it also works. I reboot. Still working. That's the same process I did yesterday, failed on all. Except network manager that worked instantly and allowed me to zypper dup and solve the problem. -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar)