Bug 804501 - Nokia E7-00: Networkmanager fails to connect where wvdial succeeds
Summary: Nokia E7-00: Networkmanager fails to connect where wvdial succeeds
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: ModemManager
Version: 16
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-19 05:32 UTC by David Anderson
Modified: 2013-02-13 13:54 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-02-13 13:54:07 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Syslog of attempt to dial out using NetworkManager/Nokia E7-00 (12.68 KB, text/plain)
2012-03-19 05:32 UTC, David Anderson
no flags Details
Requested ModemManager output (18.51 KB, application/octet-stream)
2012-07-21 07:28 UTC, David Anderson
no flags Details

Description David Anderson 2012-03-19 05:32:35 UTC
Created attachment 571013 [details]
Syslog of attempt to dial out using NetworkManager/Nokia E7-00

My Nokia E7-00 is detected by NetworkManager and shows up in the applet.

Attempts to dial out using it fail. A log (syslog) is attached.

wvdial succeeds with the following configuration file:

[Dialer Defaults]
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Modem Type = USB Modem
Phone=*99#
ISDN = 0
Username = any
Password = any
Init1 = ATZ
Modem = /dev/ttyACM0
Baud = 460800

I filed a very similar bug for a ZTE MF-192 USB HSPA modem, and spent some time debugging the cause - it looks much the same. But that bug has had no attention in 3 months; did I do something wrong? https://bugzilla.redhat.com/show_bug.cgi?id=770202

Comment 1 Dan Williams 2012-07-20 21:59:40 UTC
So we need to figure out what the "unsupported" operation is for this device.  Can you do the following for me?

mv /usr/sbin/modem-manager /
killall -TERM modem-manager
/modem-manager --debug

then try to connect and grab the output and attach it to this bug.  You can return MM to its normal location by:

mv /modem-manager /usr/sbin/modem-manager

THanks!

Comment 2 David Anderson 2012-07-21 07:28:18 UTC
Created attachment 599492 [details]
Requested ModemManager output

Comment 3 David Anderson 2012-07-21 07:29:10 UTC
Hi,

I've attached that now.

David

Comment 4 Fedora End Of Life 2013-01-16 13:11:58 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Fedora End Of Life 2013-02-13 13:54:10 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.