Launchpad has imported 21 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=835153.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-06-25T17:01:42+00:00 Deian wrote: Description of problem: When NetworkManager tries to establish ppp connection using 3G USB dongle it is unable to do so. Version-Release number of selected component (if applicable): ppp-2.4.5-22.fc17.i686 NetworkManager-0.9.4.0-9.git20120521.fc17.i686 How reproducible: 1. Create mobile broadband connection 2. Try to connect Actual results: Jun 25 19:47:59 len-netbook NetworkManager[478]: <info> pppd started with pid 1201 Jun 25 19:47:59 len-netbook pppd[1201]: unrecognized option 'wwan0' Jun 25 19:47:59 len-netbook NetworkManager[478]: <warn> pppd pid 1201 exited with error: pppd options error Expected results: expected to connect Additional info: I have never had issues with this USB dongle before fedora 17 Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/0 ------------------------------------------------------------------------ On 2012-06-26T10:10:51+00:00 Michal wrote: I've made only minor fixes on ppp side recently, so I guess this issue is more related to NetworkManager and its use of pppd. I've contacted NM team and someone will take a look at this, but in the meantime can you provide content of your /etc/ppp/options and ~/.ppprc files? Thank you. Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/1 ------------------------------------------------------------------------ On 2012-06-26T11:15:01+00:00 Jirka wrote: Would you attach /var/log/messages file? Also, grab pppd command line so that we can see cmd arguments: "ps aux | grep pppd". You can run e.g. $ while true; do ps aux | grep pppd; sleep 0.5; done in a terminal and then activate a 3G connection via NetworkManager. What modem do you use, what is output of $ lsusb Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/2 ------------------------------------------------------------------------ On 2012-06-26T20:23:07+00:00 Deian wrote: Created attachment 594592 /var/log/messages file since boot Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/3 ------------------------------------------------------------------------ On 2012-06-26T20:23:54+00:00 Deian wrote: Would you attach /var/log/messages file? ==> /var/log/messages file attached. Also, grab pppd command line so that we can see cmd arguments: "ps aux | grep pppd". ===> The command line is: root 4421 0.0 0.0 1404 180 ? D 23:16 0:00 /usr/sbin/pppd nodetach lock nodefaultroute user mtel wwan0 noipdefault noauth usepeerdns lcp-echo-failure 0 lcp-echo-interval 0 ipparam /org/freedesktop/NetworkManager/PPP/0 plugin /usr/lib/pppd/2.4.5/nm-pppd-plugin.so What modem do you use, what is output of $ lsusb Bus 002 Device 005: ID 19d2:0063 ONDA Communication S.p.A. ZTE K3565-Z HSDPA Thank you, Regards, Deyan Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/4 ------------------------------------------------------------------------ On 2012-06-27T07:52:13+00:00 Michal wrote: Based on log I assume that proper ttyname option, which should appear in pppd command-line, is ttyUSB3. I can't tell why NM uses wwan0 instead, thus changing component to NM. If anyone thinks otherwise, feel free to change it back to ppp. Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/5 ------------------------------------------------------------------------ On 2012-06-27T08:47:11+00:00 Deian wrote: When I plug the dongle in, I get new interface created which is called wwan0. I guess it has something to do with this. [deian@kamaz ~]$ ip li show 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN mode DEFAULT link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT qlen 1000 link/ether 00:1e:37:23:de:6a brd ff:ff:ff:ff:ff:ff 3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT qlen 1000 link/ether 00:1f:3b:26:d2:c1 brd ff:ff:ff:ff:ff:ff 5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN mode DEFAULT qlen 100 link/none 6: wwan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT qlen 1000 link/ether a6:b4:4c:b1:1a:94 brd ff:ff:ff:ff:ff:ff Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/6 ------------------------------------------------------------------------ On 2012-07-03T12:24:28+00:00 Deian wrote: Hello, Since I need the USB dongle, can you recommend a workaround until a fix is available ? Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/7 ------------------------------------------------------------------------ On 2012-07-03T12:55:22+00:00 Michal wrote: You can give wvdial a try and use it instead of NM. Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/8 ------------------------------------------------------------------------ On 2012-07-03T15:28:25+00:00 Jirka wrote: The wwan0 interface is pseudo-network interface created by a new 'qmi_wwan' kernel driver http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=blob;f=drivers/net/usb/qmi_wwan.c;h=3767a122586043512cd6ded88b562fd9b97df88f;hb=HEAD So, as another workaround I suggest you blacklist 'qmi_wwan' driver and give NM/MM another try. # echo "blacklist qmi_wwan" > /etc/modprobe.d/blacklist-qmi_wwan.conf Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/9 ------------------------------------------------------------------------ On 2012-07-03T15:31:08+00:00 Jirka wrote: Related discussion: http://markmail.org/thread/7l6svcpv6ddb67mj http://markmail.org/thread/6bkj7qtegvtepf42 http://markmail.org/thread/vvwz4ek3g6ybw43g Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/10 ------------------------------------------------------------------------ On 2012-07-17T10:27:57+00:00 Aleksander wrote: Can anyone get ModemManager debug logs by following the steps given in section "Debugging NetworkManager 0.8 and 0.9 3G connections" of the following page?: https://live.gnome.org/NetworkManager/Debugging Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/11 ------------------------------------------------------------------------ On 2012-07-17T13:41:48+00:00 Dan wrote: Darn, I didn't realize we'd be hit by this so soon. I guess we should probably ignore eth interfaces that are driven by qmi_wwan in ModemManager until we actually have QMI support, which means that for 0.5 and 0.6 we probably just ignore them forever. Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/12 ------------------------------------------------------------------------ On 2012-07-17T14:31:51+00:00 Dan wrote: Fixed upstream as: commit d09375e08e4234ae87c5a1af5e5cbcdc84771742 Author: Dan Williams <d...@redhat.com> Date: Tue Jul 17 09:07:40 2012 -0500 core: ignore unsupported qmi_wwan ports (rh #835153) (for 0.6, also cherry-picked to 0.5) Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/13 ------------------------------------------------------------------------ On 2012-07-20T13:09:03+00:00 Josh wrote: *** Bug 834871 has been marked as a duplicate of this bug. *** Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/14 ------------------------------------------------------------------------ On 2012-07-20T20:12:36+00:00 Fedora wrote: ModemManager-0.5.3.96-1.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/ModemManager-0.5.3.96-1.fc17 Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/15 ------------------------------------------------------------------------ On 2012-07-20T23:47:09+00:00 Fedora wrote: ModemManager-0.5.3.96-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/ModemManager-0.5.3.96-1.fc16 Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/16 ------------------------------------------------------------------------ On 2012-07-21T02:49:23+00:00 Fedora wrote: Package ModemManager-0.5.3.96-1.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ModemManager-0.5.3.96-1.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-10907/ModemManager-0.5.3.96-1.fc17 then log in and leave karma (feedback). Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/17 ------------------------------------------------------------------------ On 2012-07-28T04:16:47+00:00 klaus wrote: The update "ModemManager-0.5.3.96-1.fc17" works!! I tested it with Linux kernel 3.4.5-2. Thanks to the RedHat team for quickly solving my problem (Bug 834871). Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/18 ------------------------------------------------------------------------ On 2012-08-01T18:16:44+00:00 Fedora wrote: ModemManager-0.5.3.96-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/19 ------------------------------------------------------------------------ On 2012-08-31T01:01:24+00:00 Fedora wrote: ModemManager-0.5.3.96-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. Reply at: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1044579/comments/20 ** Changed in: modemmanager (Fedora) Status: Unknown => Fix Released ** Changed in: modemmanager (Fedora) Importance: Unknown => Undecided -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1044579 Title: [Quantal] [regression] ZTE MF 820D unable to connect To manage notifications about this bug go to: https://bugs.launchpad.net/modemmanager/+bug/1044579/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
