Ubuntu
network-manager package

Not detect a second network card!

Bug #920518 reported by Adrián on 2012-01-23

This bug affects 2 people

Affects		Status	Importance	Assigned to	Milestone
	network-manager (Ubuntu)	Expired	Undecided	Unassigned

Bug Description

Do you have computer with Realtek RTL-8139 network card. When I connect to the cable, restart the Ubuntu, because it does not detect the cable. A few months ago I did not have to reboot when I connected the cable.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager 0.9.2.0+git201201101813.0b30200-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CRDA: Error: [Errno 2] No such file or directory
Date: Mon Jan 23 16:23:32 2012
IfupdownConfig:
auto lo
iface lo inet loopback
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
IpRoute:

IwConfig:
lo no wireless extensions.

eth1 no wireless extensions.

eth0 no wireless extensions.
NetworkManager.state:
[main]
NetworkingEnabled=true
WirelessEnabled=true
WWANEnabled=true
WimaxEnabled=true
RfKill:

SourcePackage: network-manager
UpgradeStatus: Upgraded to precise on 2012-01-18 (4 days ago)
nmcli-con:
NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT READONLY DBUS-PATH
SKS-TS-SEVER 859ac05e-736c-4faa-b18b-b44e58ab0f2c 802-11-wireless 0 never yes no /org/freedesktop/NetworkManager/Settings/2
jaksi 4228bdae-45a2-40de-b824-44968878acb1 802-11-wireless 1327103774 2012. jan. 21., szombat, 00.56.14 CET yes no /org/freedesktop/NetworkManager/Settings/1
Auto Ethernet c5ce564a-0604-4e81-9b33-c399693bc82a 802-3-ethernet 1327332102 2012. jan. 23., hétfő, 16.21.42 CET yes no /org/freedesktop/NetworkManager/Settings/0
Wired connection 1 6b4c43e2-d831-4ca5-8472-464b1d21cebb 802-3-ethernet 1327332100 2012. jan. 23., hétfő, 16.21.40 CET yes no /org/freedesktop/NetworkManager/Settings/3
nmcli-dev:
DEVICE TYPE STATE DBUS-PATH
eth1 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/0
eth0 802-3-ethernet unavailable /org/freedesktop/NetworkManager/Devices/1
nmcli-nm:
RUNNING VERSION STATE NET-ENABLED WIFI-HARDWARE WIFI WWAN-HARDWARE WWAN
running 0.9.3.0 disconnected enabled enabled enabled enabled disabled

Tags:

Revision history for this message

Adrián (jaksi) wrote on 2012-01-23:

Dependencies.txt Edit (2.6 KiB, text/plain; charset="utf-8")
IpAddr.txt Edit (629 bytes, text/plain; charset="utf-8")
NetDevice.eth0.txt Edit (479 bytes, text/plain; charset="utf-8")
NetDevice.eth1.txt Edit (430 bytes, text/plain; charset="utf-8")
NetDevice.lo.txt Edit (206 bytes, text/plain; charset="utf-8")
NetworkManager.conf.txt Edit (69 bytes, text/plain; charset="utf-8")
PciNetwork.txt Edit (721 bytes, text/plain; charset="utf-8")
ProcEnviron.txt Edit (138 bytes, text/plain; charset="utf-8")
WifiSyslog.txt Edit (180.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-23:

After connecting the cable, please run sudo ifconfig in a terminal and post the output.

Changed in network-manager (Ubuntu):
status:	New → Incomplete

Revision history for this message

Adrián (jaksi) wrote on 2012-01-23:

ifconfig Edit (1.2 KiB, text/plain)

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-23:

Hrm... neither interface appears to have an IPv4 address. What are you connecting them to?

Revision history for this message

Adrián (jaksi) wrote on 2012-01-23:

Router is connected to the computer!

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-24:

You are connecting both ports to the same router?

What does ifconfig say when you reboot while already connected? By the way, you can just copy/paste; you don't need to upload an attachment.

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2012-01-24:

Some Realtek cards have been known to not properly detect carrier in the past.

Please paste the output of the 'sudo ethtool eth0' command (when you see that the cable isn't recognized as connected). You'll need to first install the 'ethtool' package for this, though.

Thanks in advance!

Revision history for this message

Adrián (jaksi) wrote on 2012-01-24:

Ifconfig after reboot:

eth0 Link encap:Ethernet HWaddr 00:b0:c4:c6:62:b3
          inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::2b0:c4ff:fec6:62b3/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:402 errors:4 dropped:6 overruns:4 frame:0
          TX packets:646 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:141532 (141.5 KB) TX bytes:93067 (93.0 KB)
          Interrupt:19 Base address:0xb800

eth1 Link encap:Ethernet HWaddr 00:17:31:8e:11:eb
          inet6 addr: fe80::217:31ff:fe8e:11eb/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:706 errors:0 dropped:0 overruns:0 frame:0
          TX packets:838 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:225372 (225.3 KB) TX bytes:80244 (80.2 KB)
          Interrupt:21 Base address:0x2000

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:16436 Metric:1
          RX packets:188 errors:0 dropped:0 overruns:0 frame:0
          TX packets:188 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:14656 (14.6 KB) TX bytes:14656 (14.6 KB)

Revision history for this message

Adrián (jaksi) wrote on 2012-01-24:

#10

ethtool eth0:

Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
                         100baseT/Half 100baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: Yes
Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                      100baseT/Half 100baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Speed: 100Mb/s
Duplex: Full
Port: MII
PHYAD: 32
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000007 (7)
          drv probe link
Link detected: yes

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-24:

#11

Now can you run ethtool eth0 after connecting the cable while the computer is already on ( when it does not work )?

Revision history for this message

Adrián (jaksi) wrote on 2012-01-24:

#12

Settings for eth0:
Cannot get device settings: No such device
Cannot get wake-on-lan settings: No such device
Cannot get message level: No such device
Cannot get link status: No such device
No data available

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-24:

#13

Well now it isn't showing up at all. Can you try again and see if it works? If not, check ifconfig and see if maybe it shows up as eth2 or something?

Revision history for this message

Adrián (jaksi) wrote on 2012-01-24:

#14

ethtool:

Revision history for this message

Adrián (jaksi) wrote on 2012-01-24:

#15

ifconfig:

eth0 Link encap:Ethernet HWaddr 00:b0:c4:c6:62:b3
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:1 errors:5 dropped:4 overruns:5 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:248 (248.0 B) TX bytes:0 (0.0 B)
          Interrupt:19 Base address:0xb800

eth1 Link encap:Ethernet HWaddr 00:17:31:8e:11:eb
          inet6 addr: fe80::217:31ff:fe8e:11eb/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:8769 errors:0 dropped:0 overruns:0 frame:0
          TX packets:37840 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:3190933 (3.1 MB) TX bytes:3335269 (3.3 MB)
          Interrupt:21 Base address:0x2000

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:16436 Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1672 (1.6 KB) TX bytes:1672 (1.6 KB)

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2012-01-24:

#16

If the command "ethtool -s eth0 autoneg off" makes the connection work when the cable is connected but the link isn't detected, then this would be the same old autonegotiation issue as before.

Revision history for this message

Adrián (jaksi) wrote on 2012-01-24:

#17

Not work!

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-24: Re: [Bug 920518] Re: Not detect a second network card!

#18

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 01/24/2012 05:07 PM, Adrián wrote:
> Not work!

I'm afraid this is not a very clear or meaningful statement. What exactly does not work?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPHzeGAAoJEJrBOlT6nu75pVUH/ilkiN8U+bMYhgfcoYQ+muuW
Vlzq0tYQZPAJPDiqhyOHdLan64aJclxzSQkKWwSIL5UyFB9sSohDOfvfQSLCWRLQ
mSkT2ImCWElgSre9jn+jiIeoJskEzB40YcdgMAdDPpydOQBVBnEFWvuoWCWjAHgC
X9bQZ1Mo5tgQReZFk99BJL+byhmNMiochPwCdJdC0vzcnXW16/b8cH3pwbyFkEEw
XnU6pXu4cMMOmN1f5NaPb5X0Ju8TcQeBkH9QFccJVPzi4hk09ptEZZ/CreNLC4p4
I4/acIFisTWPMZUlBi0Nvk64eiGWahqWio2Gf69FfG8bGoDbtK7sYVZT248lkKI=
=dmDL
-----END PGP SIGNATURE-----

Revision history for this message

Adrián (jaksi) wrote on 2012-01-25:

#19

This command not work: ethtool-s eth0 autoneg off

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-25:

#20

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

What do you mean it did not work? What did it say?

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPIBVCAAoJEJrBOlT6nu75vWMH/jGEm40HI6qftQOQSVPqNuwB
GvmzGUHElDYpmH1pEUjhzjAXQq81JfV7yNcmu0Mb4lknI64vt6pFIYY69J1VxzrW
3r5eH+4z6HgIhqGBOESvucOz/djvNZtfVxcxs65VZlv0LJU6uPgmWWkvhJ2yxtCB
IEnpqu4lT7ju56rITLWuR6vTtLFfwpeky/j8dqVjOVQc2rgrAuF9ckQJlK7d5Jwd
4sKBzcZMTfaWCMUzCTn0JjT/d1VNN/lPxP1Qs6bjuIr4bsfHaLLdKQE3es/+5tjc
yXx+ntc4Nsv9ByiZqf6ZGjJZQrQGZ8gnGpqqGuDhVG7mtXsBTYObgkMuuWC0cgk=
=EGv6
-----END PGP SIGNATURE-----

Revision history for this message

Adrián (jaksi) wrote on 2012-01-25:

#21

We still need to restart the computer when I connect the cable!

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-25:

#22

Ok, let's try this again to make sure the sequence is correct. After rebooting the computer without the cables connected, post the output of sudo ifconfig, then run "sudo ethtool -s eth0 autoneg off", then connect the cables, and then post the output of sudo ifconfig once again.

Revision history for this message

Adrián (jaksi) wrote on 2012-01-25:

#23

ifconfig cable before connecting:

eth1 Link encap:Ethernet HWaddr 00:b0:c4:c6:62:b3
          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:19 Base address:0xb800

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:16436 Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:240 (240.0 B) TX bytes:240 (240.0 B)

rename2 Link encap:Ethernet HWaddr 00:17:31:8e:11:eb
          inet addr:192.168.2.100 Bcast:192.168.2.255 Mask:255.255.255.0
          inet6 addr: fe80::217:31ff:fe8e:11eb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:60 errors:0 dropped:0 overruns:0 frame:0
          TX packets:169 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:12068 (12.0 KB) TX bytes:24360 (24.3 KB)
          Interrupt:21 Base address:0x2000

Revision history for this message

Adrián (jaksi) wrote on 2012-01-25:

#24

(eth0), I changed (eth1)
ifconfig cable after connecting :

eth1 Link encap:Ethernet HWaddr 00:b0:c4:c6:62:b3
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:1 dropped:0 overruns:1 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:19 Base address:0xb800

rename2 Link encap:Ethernet HWaddr 00:17:31:8e:11:eb
          inet6 addr: fe80::217:31ff:fe8e:11eb/64 Scope:Link
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:513 errors:0 dropped:0 overruns:0 frame:0
          TX packets:734 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:228656 (228.6 KB) TX bytes:147157 (147.1 KB)
          Interrupt:21 Base address:0x2000

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-25:

#25

It looks like the interface names are changing, which would explain why the ethtool command did not work. After rebooting with the cables unplugged, check ifconfig to make sure of the interface names, and if they are still eth1 and rename2, then run sudo ethtool -s eth1 autoneg off, and then sudo ethtool -s rename2 autoneg off, and then try connecting the cables.

Revision history for this message

Adrián (jaksi) wrote on 2012-01-25:

#26

If wishes you pulled the cord, and restart my computer then renames rename2. I run the commands, but you can not return to the original name. If the cable is plugged in when you restart the computer, then there are the old names (eth0, eth1).

Revision history for this message

Phillip Susi (psusi) wrote on 2012-01-25:

#27

You want to run the ethtool autoneg off command on whatever their names are when you boot up without the cables connected.

Revision history for this message

Adrián (jaksi) wrote on 2012-01-26:

#28

Then run the command when it is the name (eth1, rename2)

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-03-30:

#29

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status:	Incomplete → Expired

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntunetwork-manager package

Not detect a second network card!

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
network-manager package