Ubuntu
modemmanager package

Wrong ttyUSB chosen for wind 3g internet key (1bbb:0017)

Bug #819784 reported by f3a97 on 2011-08-02

This bug affects 6 people

Affects		Status	Importance	Assigned to	Milestone
	modemmanager (Ubuntu)	Expired	Medium	Unassigned

Bug Description

Hi,

With my stock ubuntu 10.10 I'm having problems to connect to the internet with my wind 3g key.

Basically, what happens is that sometimes I can connect and sometimes fails. When it fails, I have to unplug the card and replug it a couple of times, until it works.

Taking a look a the logs, I figured out the issue and put in place a workaround. What I have found is that:

- when the connection works, ttyUSB4 is used.
- when the connection doesn't work, ttyUSB3 is used.

Based on this, I've applied the following udev rule which make the connection always work:

$ cat /etc/udev/rules.d/wind-key-avoid-wrong-ttyusb.rules
KERNEL=="ttyUSB[0123]",ACTION=="add",SYSFS{idVendor}=="1bbb",SYSFS{idProduct}=="0017",RUN+="/bin/sleep 2"

However, it is better to fix this in a proper way, since this workaround has some drawbacks (the unlock code wizard seems to fail...)

Thanks in advance.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: modemmanager 0.4+git.20110124t203624.00b6cce-2ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
Uname: Linux 2.6.38-10-generic i686
NonfreeKernelModules: wl fglrx
Architecture: i386
Date: Tue Aug 2 14:11:13 2011
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcEnviron:
LANGUAGE=it_IT:en
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: modemmanager
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

f3a97 (f3a97) wrote on 2011-08-02:

Dependencies.txt Edit (727 bytes, text/plain; charset="utf-8")

Revision history for this message

f3a97 (f3a97) wrote on 2011-08-03:

Sorry guys,

I obviously have ubuntu 11.04, as data says (not 10.10 I have reported above).

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2011-08-05:

This appears to be covered by the 77-mm-x22x-port-types.rules file in udev; but I can't quite make sense of why it fails this way. To understand this, it would be best if you could attach the udev logs:

Run 'udevadm monitor' (and optionally redirect the output to a file),
then plug in the modem.

You should then be able to copy all the information printed by udevadm monitor to this bug report, it should include an indication of what is happening.

Changed in modemmanager (Ubuntu):
status:	New → Incomplete
importance:	Undecided → Medium

Revision history for this message

f3a97 (f3a97) wrote on 2011-08-09: Re: [Bug 819784] Re: Wrong ttyUSB chosen for wind 3g internet key (1bbb:0017)

udevadm.log Edit (8.0 KiB, text/x-log; charset=US-ASCII; name="udevadm.log")
syslog Edit (368.1 KiB, application/octet-stream; name=syslog)

Download full text (5.4 KiB)

Hi Mathieu,

Many thanks for your reply!

Here are the requested information.

I have removed my custom udev rule, unplugged the modem, run the udevadm
monitor command and reinserted the modem.

Please find attached the udevadm log and the syslog.

From the syslog you can easily see that when ttyUSB4 is used the connection
works (you can see it thanks to my custom rule) while without my rule,
ttyUSB3 is used and the connection doesn't work:

$ grep -2 'ppp0.*ttyUSB4' syslog
Aug 8 11:42:30 angela-iMac NetworkManager[596]: SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug 8 11:42:30 angela-iMac pppd[2017]: Using interface ppp0
Aug 8 11:42:30 angela-iMac pppd[2017]: Connect: ppp0 <--> /dev/ttyUSB4
Aug 8 11:42:30 angela-iMac pppd[2017]: CHAP authentication succeeded
Aug 8 11:42:30 angela-iMac pppd[2017]: CHAP authentication succeeded
--
Aug 8 15:16:55 angela-iMac NetworkManager[651]: SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug 8 15:16:55 angela-iMac pppd[1883]: Using interface ppp0
Aug 8 15:16:55 angela-iMac pppd[1883]: Connect: ppp0 <--> /dev/ttyUSB4
Aug 8 15:16:55 angela-iMac pppd[1883]: CHAP authentication succeeded
Aug 8 15:16:55 angela-iMac pppd[1883]: CHAP authentication succeeded
--
Aug 9 10:26:24 angela-iMac NetworkManager[669]: SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug 9 10:26:24 angela-iMac pppd[1934]: Using interface ppp0
Aug 9 10:26:24 angela-iMac pppd[1934]: Connect: ppp0 <--> /dev/ttyUSB4
Aug 9 10:26:24 angela-iMac pppd[1934]: CHAP authentication succeeded
Aug 9 10:26:24 angela-iMac pppd[1934]: CHAP authentication succeeded
--
Aug 9 10:47:40 angela-iMac NetworkManager[669]: SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug 9 10:47:40 angela-iMac pppd[2314]: Using interface ppp0
Aug 9 10:47:40 angela-iMac pppd[2314]: Connect: ppp0 <--> /dev/ttyUSB4
Aug 9 10:47:40 angela-iMac pppd[2314]: CHAP authentication succeeded
Aug 9 10:47:40 angela-iMac pppd[2314]: CHAP authentication succeeded

$ grep -2 'ppp0.*ttyUSB3' syslog
Aug 9 10:51:42 angela-iMac NetworkManager[669]: SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug 9 10:51:42 angela-iMac pppd[2717]: Using interface ppp0
Aug 9 10:51:42 angela-iMac pppd[2717]: Connect: ppp0 <--> /dev/ttyUSB3
Aug 9 10:52:02 angela-iMac NetworkManager[669]: <warn> pppd timed out or
didn't initialize our dbus module
Aug 9 10:52:02 angela-iMac NetworkManager[669]: <info> (ttyUSB3): device
state change: 7 -> 9 (reason 5)

Please let me know if I can help you further.

On 5 August 2011 16:36, Mathieu Trudel-Lapierre <email address hidden>wrote:

Hi Mathieu,

Many thanks for your reply!

Here are the requested information.

I have removed my custom udev rule, unplugged the modem, run the udevadm
monitor command and reinserted the modem.

Please find attached the udevadm log and the syslog.

From the syslog you can easily see that when ttyUSB4 is used the connection
works (you can see it thanks to my custom rule) while without my rule,
ttyUSB3 is used and the connection doesn't work:

$ grep -2 'ppp0.*ttyUSB4' syslog
Aug  8 11:42:30 angela-iMac NetworkManager[596]:    SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug  8 11:42:30 angela-iMac pppd[2017]: Using interface ppp0
Aug  8 11:42:30 angela-iMac pppd[2017]: Connect: ppp0 <--> /dev/ttyUSB4
Aug  8 11:42:30 angela-iMac pppd[2017]: CHAP authentication succeeded
Aug  8 11:42:30 angela-iMac pppd[2017]: CHAP authentication succeeded
--
Aug  8 15:16:55 angela-iMac NetworkManager[651]:    SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug  8 15:16:55 angela-iMac pppd[1883]: Using interface ppp0
Aug  8 15:16:55 angela-iMac pppd[1883]: Connect: ppp0 <--> /dev/ttyUSB4
Aug  8 15:16:55 angela-iMac pppd[1883]: CHAP authentication succeeded
Aug  8 15:16:55 angela-iMac pppd[1883]: CHAP authentication succeeded
--
Aug  9 10:26:24 angela-iMac NetworkManager[669]:    SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug  9 10:26:24 angela-iMac pppd[1934]: Using interface ppp0
Aug  9 10:26:24 angela-iMac pppd[1934]: Connect: ppp0 <--> /dev/ttyUSB4
Aug  9 10:26:24 angela-iMac pppd[1934]: CHAP authentication succeeded
Aug  9 10:26:24 angela-iMac pppd[1934]: CHAP authentication succeeded
--
Aug  9 10:47:40 angela-iMac NetworkManager[669]:    SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug  9 10:47:40 angela-iMac pppd[2314]: Using interface ppp0
Aug  9 10:47:40 angela-iMac pppd[2314]: Connect: ppp0 <--> /dev/ttyUSB4
Aug  9 10:47:40 angela-iMac pppd[2314]: CHAP authentication succeeded
Aug  9 10:47:40 angela-iMac pppd[2314]: CHAP authentication succeeded

$ grep -2 'ppp0.*ttyUSB3' syslog
Aug  9 10:51:42 angela-iMac NetworkManager[669]:    SCPlugin-Ifupdown:
device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown
configuration found.
Aug  9 10:51:42 angela-iMac pppd[2717]: Using interface ppp0
Aug  9 10:51:42 angela-iMac pppd[2717]: Connect: ppp0 <--> /dev/ttyUSB3
Aug  9 10:52:02 angela-iMac NetworkManager[669]: <warn> pppd timed out or
didn't initialize our dbus module
Aug  9 10:52:02 angela-iMac NetworkManager[669]: <info> (ttyUSB3): device
state change: 7 -> 9 (reason 5)

Please let me know if I can help you further.

On 5 August 2011 16:36, Mathieu Trudel-Lapierre <mathieu.tl@gmail.com>wrote:

> This appears to be covered by the 77-mm-x22x-port-types.rules file in
> udev; but I can't quite make sense of why it fails this way. To
> understand this, it would be best if you could attach the udev logs:
>
> Run 'udevadm monitor' (and optionally redirect the output to a file),
> then plug in the modem.
>
> You should then be able to copy all the information printed by udevadm
> monitor to this bug report, it should include an indication of what is
> happening.
>
> ** Changed in: modemmanager (Ubuntu)
>       Status: New => Incomplete
>
> ** Changed in: modemmanager (Ubuntu)
>   Importance: Undecided => Medium
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/819784
>
> Title:
>  Wrong ttyUSB chosen for wind 3g internet key (1bbb:0017)
>
> Status in “modemmanager” package in Ubuntu:
>   Incomplete
>
> Bug description:
>  Hi,
>
>  With my stock ubuntu 10.10 I'm having problems to connect to the
>  internet with my wind 3g key.
>
>  Basically, what happens is that sometimes I can connect and sometimes
>  fails. When it fails, I have to unplug the card and replug it a couple
>  of times, until it works.
>
>  Taking a look a the logs, I figured out the issue and put in place a
>  workaround. What I have found is that:
>
>  - when the connection works, ttyUSB4 is used.
>  - when the connection doesn't work, ttyUSB3 is used.
>
>  Based on this, I've applied the following udev rule which make the
>  connection always work:
>
>  $ cat /etc/udev/rules.d/wind-key-avoid-wrong-ttyusb.rules
>  KERNEL=="ttyUSB[0123]",ACTION=="add",SYSFS{idVendor}=="1bbb",SYSFS{idProduct}=="0017",RUN+="/bin/sleep
> 2"
>
>
>  However, it is better to fix this in a proper way, since this workaround
> has some drawbacks (the unlock code wizard seems to fail...)
>
>
>  Thanks in advance.
>
>  ProblemType: Bug
>  DistroRelease: Ubuntu 11.04
>  Package: modemmanager 0.4+git.20110124t203624.00b6cce-2ubuntu1
>  ProcVersionSignature: Ubuntu 2.6.38-10.46-generic 2.6.38.7
>  Uname: Linux 2.6.38-10-generic i686
>  NonfreeKernelModules: wl fglrx
>  Architecture: i386
>  Date: Tue Aug  2 14:11:13 2011
>  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386
> (20110427.1)
>  ProcEnviron:
>   LANGUAGE=it_IT:en
>   LANG=it_IT.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: modemmanager
>  UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/819784/+subscriptions
>

Revision history for this message

Launchpad Janitor (janitor) wrote on 2011-10-09:

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

Changed in modemmanager (Ubuntu):
status:	Incomplete → Expired

Revision history for this message

Rolf Kutz (vzsze) wrote on 2011-10-24:

This bug affects me on 10.04 LTS. Please reopen.

Revision history for this message

Mathieu Trudel-Lapierre (cyphermox) wrote on 2011-10-28:

Setting back to Confirmed since it affects multiple users...

Changed in modemmanager (Ubuntu):
status:	Expired → Confirmed

Revision history for this message

dalailama (dalailama333) wrote on 2012-06-24:

Ubuntu 12.04 and still the same problem:
dongle connected, ttyusb0,1,2 created;

networkmanager trying connection to ttyusb0 -> connection successfull
networkmanager trying connection to ttyusb2 -> fail

unable to force networkmanager to connect to ttyusb0 with a rule for udev :(

Revision history for this message

Berenyi Peter (berenyi-peter) wrote on 2013-07-04:

This stills exists in Ubuntu 13.04. I have a ZTE modem and I can see the same behavior, only the ttyUSB numbers are different.

Revision history for this message

cd311 (cd311) wrote on 2013-07-17:

#10

I have the same problem on ubuntu 13.04 with a dlink dwm-156.
the network manager uses /dev/ttyUSB1 (which doesnt work) as seen in

$ grep -5 'ppp0.*ttyUSB' syslog
Jul 17 22:29:08 gamma NetworkManager[5268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 17 22:29:08 gamma pppd[5614]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
Jul 17 22:29:08 gamma pppd[5614]: pppd 2.4.5 started by root, uid 0
Jul 17 22:29:08 gamma pppd[5614]: Removed stale lock on ttyUSB1 (pid 4933)
Jul 17 22:29:08 gamma pppd[5614]: Using interface ppp0
Jul 17 22:29:08 gamma pppd[5614]: Connect: ppp0 <--> /dev/ttyUSB1
Jul 17 22:29:08 gamma NetworkManager[5268]: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jul 17 22:29:08 gamma NetworkManager[5268]: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jul 17 22:29:08 gamma NetworkManager[5268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
Jul 17 22:29:08 gamma modem-manager[5253]: <debug> [1374092948.973848] [mm-manager.c:859] device_added(): (net/ppp0): could not get port's parent device

if I use wvdial with "Modem = /dev/ttyUSB2" connecting is no problem

$ grep -5 'ppp0.*ttyUSB' syslog
Jul 17 22:49:12 gamma modem-manager[5643]: <info> Modem /org/freedesktop/ModemManager/Modems/2: unlock no longer required
Jul 17 22:49:16 gamma modem-manager[5643]: <info> (ttyUSB1) closing serial port...
Jul 17 22:49:16 gamma modem-manager[5643]: <info> (ttyUSB1) serial port closed
Jul 17 22:57:47 gamma pppd[6527]: pppd 2.4.5 started by user, uid 1000
Jul 17 22:57:47 gamma pppd[6527]: Using interface ppp0
Jul 17 22:57:47 gamma pppd[6527]: Connect: ppp0 <--> /dev/ttyUSB2
Jul 17 22:57:47 gamma pppd[6527]: CHAP authentication succeeded
Jul 17 22:57:47 gamma pppd[6527]: CHAP authentication succeeded

I couldn't find any way to ether tell modem-manager/network-manager to use /dev/ttyUSB2 instead of /dev/ttyUSB1 nor could I find a way to use udev to rename the usb devices.

I have the same problem on ubuntu 13.04 with a dlink dwm-156.
the network manager uses /dev/ttyUSB1 (which doesnt work) as seen in

$ grep -5 'ppp0.*ttyUSB' syslog
Jul 17 22:29:08 gamma NetworkManager[5268]: <info> Activation (ttyUSB1) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Jul 17 22:29:08 gamma pppd[5614]: Plugin /usr/lib/i386-linux-gnu/pppd/2.4.5/nm-pppd-plugin.so loaded.
Jul 17 22:29:08 gamma pppd[5614]: pppd 2.4.5 started by root, uid 0
Jul 17 22:29:08 gamma pppd[5614]: Removed stale lock on ttyUSB1 (pid 4933)
Jul 17 22:29:08 gamma pppd[5614]: Using interface ppp0
Jul 17 22:29:08 gamma pppd[5614]: Connect: ppp0 <--> /dev/ttyUSB1
Jul 17 22:29:08 gamma NetworkManager[5268]:    SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/ppp0, iface: ppp0)
Jul 17 22:29:08 gamma NetworkManager[5268]:    SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/ppp0, iface: ppp0): no ifupdown configuration found.
Jul 17 22:29:08 gamma NetworkManager[5268]: <warn> /sys/devices/virtual/net/ppp0: couldn't determine device driver; ignoring...
Jul 17 22:29:08 gamma modem-manager[5253]: <debug> [1374092948.973848] [mm-manager.c:859] device_added(): (net/ppp0): could not get port's parent device

if I use wvdial with "Modem = /dev/ttyUSB2" connecting is no problem

$ grep -5 'ppp0.*ttyUSB' syslog
Jul 17 22:49:12 gamma modem-manager[5643]: <info>  Modem /org/freedesktop/ModemManager/Modems/2: unlock no longer required
Jul 17 22:49:16 gamma modem-manager[5643]: <info>  (ttyUSB1) closing serial port...
Jul 17 22:49:16 gamma modem-manager[5643]: <info>  (ttyUSB1) serial port closed
Jul 17 22:57:47 gamma pppd[6527]: pppd 2.4.5 started by user, uid 1000
Jul 17 22:57:47 gamma pppd[6527]: Using interface ppp0
Jul 17 22:57:47 gamma pppd[6527]: Connect: ppp0 <--> /dev/ttyUSB2
Jul 17 22:57:47 gamma pppd[6527]: CHAP authentication succeeded
Jul 17 22:57:47 gamma pppd[6527]: CHAP authentication succeeded

I couldn't find any way to ether tell modem-manager/network-manager to use /dev/ttyUSB2 instead of /dev/ttyUSB1 nor could I find a way to use udev to rename the usb devices.

Revision history for this message

Marius B. Kotsbak (mariusko) wrote on 2014-12-25:

#11

Ubuntu 10.10 has reached end of life. Are you able to reproduce this issue in a recent Ubuntu version?

Changed in modemmanager (Ubuntu):
status:	Confirmed → Incomplete

Revision history for this message

Launchpad Janitor (janitor) wrote on 2015-02-24:

#12

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

Changed in modemmanager (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

Bug attachments

Add attachment

Remote bug watches

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

Ubuntumodemmanager package

Wrong ttyUSB chosen for wind 3g internet key (1bbb:0017)

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
modemmanager package