Ubuntu
network-manager package

[hardy] Ethernet port of USB replicator no longer working

Bug #183124 reported by Hervé Cauwelier
2
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: udev

I use a port replicator connected to the PC through USB.

When I connect it, /var/log/messages reports this:

Jan 15 09:46:11 xiong kernel: [ 160.000641] usb 7-2: new high speed USB device using ehci_hcd and address 10
Jan 15 09:46:11 xiong kernel: [ 160.038619] usb 7-2: configuration #1 chosen from 1 choice
Jan 15 09:46:11 xiong kernel: [ 160.039022] hub 7-2:1.0: USB hub found
Jan 15 09:46:11 xiong kernel: [ 160.039270] hub 7-2:1.0: 4 ports detected
Jan 15 09:46:11 xiong kernel: [ 160.337496] usb 7-2.1: new high speed USB device using ehci_hcd and address 11
Jan 15 09:46:11 xiong kernel: [ 160.384834] usb 7-2.1: configuration #1 chosen from 1 choice
Jan 15 09:46:11 xiong kernel: [ 160.385407] hub 7-2.1:1.0: USB hub found
Jan 15 09:46:11 xiong kernel: [ 160.385763] hub 7-2.1:1.0: 4 ports detected
Jan 15 09:46:12 xiong kernel: [ 160.582022] usb 7-2.4: new low speed USB device using ehci_hcd and address 12
Jan 15 09:46:12 xiong kernel: [ 160.598881] usb 7-2.4: configuration #1 chosen from 1 choice
Jan 15 09:46:12 xiong kernel: [ 160.601373] input: Logitech Optical USB Mouse as /devices/pci0000:00/0000:00:1d.7/usb7/7-2/7-2.4/7-2.4:1.0/input/input12
Jan 15 09:46:12 xiong kernel: [ 160.652695] input,hidraw0: USB HID v1.10 Mouse [Logitech Optical USB Mouse] on usb-0000:00:1d.7-2.4
Jan 15 09:46:12 xiong kernel: [ 160.757835] usb 7-2.1.1: new high speed USB device using ehci_hcd and address 13
Jan 15 09:46:12 xiong kernel: [ 160.778139] usb 7-2.1.1: configuration #1 chosen from 1 choice
Jan 15 09:46:13 xiong kernel: [ 161.113719] eth1: register 'asix' at usb-0000:00:1d.7-2.1.1, ASIX AX88772 USB 2.0 Ethernet, f4:ff:ff:ff:20:31
Jan 15 09:46:13 xiong kernel: [ 161.117534] udev: renamed network interface eth1 to eth5
Jan 15 09:46:13 xiong kernel: [ 161.139690] eth5: link down
Jan 15 09:46:13 xiong kernel: [ 161.147489] ADDRCONF(NETDEV_UP): eth5: link is not ready
Jan 15 09:46:13 xiong kernel: [ 161.296334] usb 7-2.1.2: new full speed USB device using ehci_hcd and address 14
Jan 15 09:46:13 xiong kernel: [ 161.401047] usb 7-2.1.2: configuration #1 chosen from 1 choice
Jan 15 09:46:13 xiong kernel: [ 161.417078] usblp0: USB Bidirectional printer dev 14 if 0 alt 1 proto 2 vid 0x067B pid 0x2305
Jan 15 09:46:14 xiong kernel: [ 161.634363] usb 7-2.1.3: new full speed USB device using ehci_hcd and address 15
Jan 15 09:46:14 xiong kernel: [ 161.689022] usb 7-2.1.3: configuration #1 chosen from 1 choice
Jan 15 09:46:14 xiong kernel: [ 161.689546] pl2303 7-2.1.3:1.0: pl2303 converter detected
Jan 15 09:46:14 xiong kernel: [ 161.689723] usb 7-2.1.3: pl2303 converter now attached to ttyUSB0
Jan 15 09:46:14 xiong kernel: [ 161.910774] usb 7-2.1.4: new full speed USB device using ehci_hcd and address 16
Jan 15 09:46:14 xiong kernel: [ 161.977311] usb 7-2.1.4: configuration #1 chosen from 1 choice
Jan 15 09:46:14 xiong kernel: [ 162.023008] input: USB Audio as /devices/pci0000:00/0000:00:1d.7/usb7/7-2/7-2.1/7-2.1.4/7-2.1.4:1.3/input/input13
Jan 15 09:46:14 xiong kernel: [ 162.071164] input,hidraw1: USB HID v1.00 Device [USB Audio] on usb-0000:00:1d.7-2.1.4

(A mouse is already connected to it.)

My concern here is the Ethernet over USB adapter:

Jan 15 09:46:13 xiong kernel: [ 161.113719] eth1: register 'asix' at usb-0000:00:1d.7-2.1.1, ASIX AX88772 USB 2.0 Ethernet, f4:ff:ff:ff:20:31
Jan 15 09:46:13 xiong kernel: [ 161.117534] udev: renamed network interface eth1 to eth5
Jan 15 09:46:13 xiong kernel: [ 161.139690] eth5: link down
Jan 15 09:46:13 xiong kernel: [ 161.147489] ADDRCONF(NETDEV_UP): eth5: link is not ready

When I plug the Ethernet cable, Network Manager tries and tries again to get a
DHCP response:

Jan 15 09:51:11 xiong kernel: [ 221.147346] ADDRCONF(NETDEV_CHANGE): eth5: link becomes ready
Jan 15 09:51:11 xiong kernel: [ 221.149323] eth5: link down
(The line above is repeated 10 times.)
(Then the whole pattern is repeated forever.)

Sometimes I read variants:

Jan 15 09:51:33 xiong kernel: [ 227.683931] eth5: link up, 10Mbps, half-duplex, lpa 0x0000

Jan 15 09:41:24 xiong dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth5 for sub-path eth5.dbus.get.reason

If I plug the cable to the built-in Ethernet port, it's all OK:

Jan 15 09:43:41 xiong kernel: [ 100.062179] tg3: eth0: Link is up at 100 Mbps, full duplex.
Jan 15 09:43:41 xiong kernel: [ 100.062189] tg3: eth0: Flow control is on for TX and on for RX.
Jan 15 09:43:41 xiong kernel: [ 100.066551] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
Jan 15 09:43:41 xiong dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.reason
Jan 15 09:43:56 xiong dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.host_name
Jan 15 09:43:56 xiong dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.domain_name
Jan 15 09:43:56 xiong dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_domain
Jan 15 09:43:56 xiong dhcdbd: message_handler: message handler not found under /com/redhat/dhcp/eth0 for sub-path eth0.dbus.get.nis_servers

The Ethernet port of the replicator used to work in Gutsy. It also registered
as eth1, yet I don't find traces of eth1 later on. The connexion was given to
eth2. I only find the registration of eth2 when the replicator was disconnected
and connected back again, then the Ethernet port was directly mapped to eth2.
So my guess is that udev was already renaming it in Gutsy, but didn't tell so
in the logs.

As it is related to hardware activation and I wonder about this ethernet port
renaming, I file this bug against udev. Nothing personal. ;-)

Any help is welcome.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please provide output of "ifconfig -a"

Changed in udev:
status: New → Incomplete
Revision history for this message
Hervé Cauwelier (hcauwelier-deactivatedaccount) wrote :

The current "ifconfig" with the cable connected on the "working" eth0 port:

$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:15:c5:7f:0a:5f
          inet adr:10.0.0.25 Bcast:10.0.0.255 Masque:255.255.255.0
          adr inet6: fe80::215:c5ff:fe7f:a5f/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Packets reçus:74475 erreurs:0 :0 overruns:0 frame:0
          TX packets:46368 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          Octets reçus:102477513 (97.7 MB) Octets transmis:4143083 (3.9 MB)
          Interruption:17

eth1 Link encap:UNSPEC HWaddr 00-1B-77-DF-14-0B-00-00-00-00-00-00-00-00-00-00
          BROADCAST MULTICAST MTU:1500 Metric:1
          Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)

eth6 Link encap:Ethernet HWaddr f4:ff:ff:ff:20:81
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)

lo Link encap:Boucle locale
          inet adr:127.0.0.1 Masque:255.0.0.0
          adr inet6: ::1/128 Scope:Hôte
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          Packets reçus:1082 erreurs:0 :0 overruns:0 frame:0
          TX packets:1082 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0
          Octets reçus:718381 (701.5 KB) Octets transmis:718381 (701.5 KB)

wlan0_rename Link encap:Ethernet HWaddr 00:1b:77:df:14:0b
          BROADCAST MULTICAST MTU:1500 Metric:1
          Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)

Revision history for this message
Hervé Cauwelier (hcauwelier-deactivatedaccount) wrote :

The output when the cable is plugged into the USB replicator is the same, except for that new entry:

eth6:avahi Link encap:Ethernet HWaddr f4:ff:ff:ff:20:81
          inet adr:169.254.9.0 Bcast:169.254.255.255 Masque:255.255.0.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

And indeed the Ethernet interface is now "up" for Network Manager.

The ":avahi" suffix reminds me that I restored the Avahi service yesterday to try network discovery. Would it be mandatory to support Ethernet-over-USB adapters?

But as the IP is the DHCP fallback one, the connexion is useless.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

This isn't a udev bug then, the driver is loaded -- because your interface is visible.

Are you sure that you have a DHCP server on the other end of that connection?

Revision history for this message
Hervé Cauwelier (hcauwelier-deactivatedaccount) wrote :

Yes I have, we all use it here at the office, and it's working fine with the built-in Ethernet port.

It's when I plug the cable into the USB replicator that things go wrong.

Revision history for this message
Iulian Udrea (iulian) wrote :

You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? If you still have this issue please add /var/log/syslog to this report. For more information please see https:/wiki.ubuntu.com/DebuggingNetworkManager

Revision history for this message
Hervé Cauwelier (hcauwelier-deactivatedaccount) wrote :

I've switched to Debian meanwhile, so I doubt I could report further anytime soon.

Feel free to close the bug if you think no one could replace me as the reporter.

Revision history for this message
NoOp (glgxg) wrote :

I can confirm the same or similar problem. On my IBM ThinkPad A21M I use an Airlink 101 USB to ethernet adaptor. the device has always worked from Dapper to Edgy to Gutsy, and even following a Hardy Beta upgrade on this and other machines. However, yesterday I decided to do a fresh Hardy Beta install on the machine (for testing) and the device is no longer working. Not during the install, nor following. Hence no ethernet connection at all.

I have configured (using the network manager) for a static IP, and for DHCP - no difference. Messages log shows the device as up:

eth0: register 'asix' at usb-0000:00:07.2.1, ASIX AX88772 USB 2.0 Ethernet, 00:50:5b:04:aa:23
usbcore: registered new interface driver asix
[snip]
eth0: link up, 100Mbps, full-duplex, lpa 0x45E1

However: ifconfig shows no IP (even when fixed IP is assigned). sudo /etc/init.d/networking restart makes no difference, nor does sudo ifconfig eth0 up, ifconfig lo up/down etc.

The device is working just fine - I can remove and use it without problems on the other laptop which is a Gutsy to Hardy Beta upgrade.

Unfortunately, I cannot provide much more information at this point as the machine has no ethernet, so I'm having to hand type info from messages log etc. I *can* put in an old Netgear PCMCIA ethernet card and it is recognized instantly and gets a DHCP address. So I can get a network connect that way if necessary. But I'm reluctant to use that for samba to get the logs and updates just yet as I'd like to first find out why the Airlink 101 was not recognized at install and continues to not be recognized. Note: the Airlink 101 is *not* a wireless device, see http://www.airlink101.com/products/asohousb.html for details.

Again, this is a test laptop, so I can leave it in it's present state for awhile - advise on what you'd like me to check and I'll be happy to do it.

Revision history for this message
NoOp (glgxg) wrote : Re: [Bug 183124] Re: [hardy] Ethernet port of USB replicator no longer working

Followup:

1. I became impatient & used the PCIMCA card to update (as of April 1
PDST). I also noticed that I had
authorization/policy-kit/gnome-system-tools issues in doing basic
authorization services (see:
https://bugs.launchpad.net/ubuntu/+source/policykit/+bug/202449 and
https://bugs.launchpad.net/ubuntu/+bug/198172) so I changed my root to
/root vs /home/root, and completed the updates.
2. I still was unable to use the USB to ethernet device following the
updates.
3. I then went to the Network Manager and configured the USB adaptor for
DHCP again (was fixed IP), and this time I was able to get an IP
address. So I then reconfigured (again in NM) for the fixed IP
(192.168.x.x) and the device again came up correctly.

So, I'm not sure if it was: 1) the updates or, 2) the
policy-kit/gnome-system-tools that was the problem. However, I can
perform another fresh reinstall from Hardy Beta (alternate CD) and try
to troubleshoot further if necessary.

Revision history for this message
Alexander Sack (asac) wrote :

still an issue in 7.10 for you?

Revision history for this message
NoOp (glgxg) wrote :

No as I no longer use Gutsy (7.10) and instead use 8.04.1 (Hardy). All
is working well on the 8.04.1 version - tested using both DHCP and fixe
IP, so the bug can be closed as the OP switched to Debian per the
comment in:
 <https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/183124/comments/7>

Thanks & I'll try to go through any other issues that I've filed/posted
to clean up any old/outstanding issues.

Revision history for this message
Alexander Sack (asac) wrote :

Thanks :) ... help on bugs much appreciated. If you want to do more on NM bugs than just cleaning up yours, ping me on #ubuntu-bugs.

Changed in network-manager:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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