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...@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 > ** Attachment added: "udevadm.log" https://bugs.launchpad.net/bugs/819784/+attachment/2263541/+files/udevadm.log ** Attachment added: "syslog" https://bugs.launchpad.net/bugs/819784/+attachment/2263542/+files/syslog -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/819784 Title: Wrong ttyUSB chosen for wind 3g internet key (1bbb:0017) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/819784/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
