Mailinglist Archive: opensuse-bugs (4258 mails)

< Previous Next >
[Bug 1004579] wired network interface not able to connect automatically
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Sat, 28 Jan 2017 20:31:43 +0000
  • Message-id: <bug-1004579-21960-JvwtgDtbuG@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1004579
http://bugzilla.suse.com/show_bug.cgi?id=1004579#c3

Søren Tarp <soren@xxxxxxxxxxxxxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|NORESPONSE |---
Flags|needinfo?(soren@bille-brahe |
|s-vej.dk) |

--- Comment #3 from Søren Tarp <soren@xxxxxxxxxxxxxxxxxxx> ---
With 42.1 and older, the network interface worked fine.
Now, with Tumbleweed, I have to manually issue a command that restricts the
duplex speed of the NIC:

"sudo /usr/sbin/ethtool -s enp2s0f5 speed 100 duplex full"

in order to get it to become active and connect.

When the above command has not been issued, the output of different commands
goes like this:

Output of /usr/sbin/hwinfo --network

32: None 00.0: 10701 Ethernet
[Created at net.125]
Unique ID: Mqes.ndpeucax6V1
Parent ID: hAO_.T2o1rq67Dg8
SysFS ID: /class/net/wlp3s0
SysFS Device Link: /devices/pci0000:00/0000:00:1c.3/0000:03:00.0
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "rtl8192ce"
Driver Modules: "rtl8192ce"
Device File: wlp3s0
HW Address: e0:91:53:56:82:c7
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #21 (Ethernet controller)

33: None 00.0: 10701 Ethernet
[Created at net.125]
Unique ID: XO02.ndpeucax6V1
Parent ID: _Uic.bWH1IUvNrI5
SysFS ID: /class/net/enp2s0f5
SysFS Device Link: /devices/pci0000:00/0000:00:1c.1/0000:02:00.5
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "jme"
Driver Modules: "jme"
Device File: enp2s0f5
HW Address: 80:ee:73:1f:c6:3f
Link detected: no
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #20 (Ethernet controller)

34: None 00.0: 10700 Loopback
[Created at net.125]
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

Output of /sbin/ifconfig

enp2s0f5 Link encap:Ethernet HWaddr 80:EE:73:1F:C6:3F
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:30

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:324 errors:0 dropped:0 overruns:0 frame:0
TX packets:324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:28136 (27.4 Kb) TX bytes:28136 (27.4 Kb)

wlp3s0 Link encap:Ethernet HWaddr E0:91:53:56:82:C7
inet addr:10.0.0.12 Bcast:10.0.0.255 Mask:255.255.255.0
inet6 addr: fe80::e291:53ff:fe56:82c7/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:78896 errors:0 dropped:2150 overruns:0 frame:0
TX packets:53016 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:85186226 (81.2 Mb) TX bytes:6756028 (6.4 Mb)

Output of ls -l /etc/sysconfig/network/ifcfg*

-rw-r--r-- 1 root root 209 14 jun 20:35 /etc/sysconfig/network/ifcfg-enp2s0f5
-rw------- 1 root root 147 14 jun 20:35 /etc/sysconfig/network/ifcfg-lo
-rw-r--r-- 1 root root 21738 5 jun 14:59 /etc/sysconfig/network/ifcfg.template
-rw------- 1 root root 842 14 jun 20:35 /etc/sysconfig/network/ifcfg-wlp3s0

Other post suggests that all this i due to a bug in the jme driver.
(In reply to Takashi Iwai from comment #1)
Is it a regression from previous kernels?

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >