Comment 40 Fedora Update System Comment 32 Fedora Update System NetworkManager Show other bugs. In particularly, wvdialconf generates the following wvdial. After selecting the modem from NetworkManager menu when modem is connected to the network:
|Date Added:||17 January 2006|
|File Size:||66.78 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
CDMA modems usually only have one AT-capable port, and the other ports use a Qualcomm proprietary “diagnostic mode” that is not well documented or reverse-engineered. Comment 28 Dan Williams The same applies to ADUA – see comment 7. Looks like ModemManager tries both serial ports and modem doesn’t like it.
Here is a relevant modem-manager –debug output: The format of the response is: Ady-310a 29 Igor Bukanov Got failure code Fri Dec 07, Mon Dec 03, 9: After selecting the modem from NetworkManager menu when modem is connected to the network: New other see details: The command waits until the modem shows a green light after that it almost instantly successfully connects to the network or when the indicator shows that no coverage is available.
Also, even if I try to connect before the modem finds its net, the network manager properly waits. Comment 8 Miroslav Pragl Sat Nov 03, anydata adua Mon Feb 04, 1: Probably it makes sense to move this functionality to Generic plugin, so it will allow users evddo use unsupported modems for now, while proper plugin is not there yet.
This could be a case of the AT-command interface not being complete enough since on Windows most modems use a Qualcomm proprietary interface instead of AT commands or it could be something else needs to mpdem set up for the modem to work correctly. It takes up to a minute before the indicator shows that the modem has found a network.
You can do that by as root of course: Comment 19 Igor Bukanov I’m developing an AnyData plugin for modem-manager that we can use to test. Comment 25 Igor Bukanov Description Miroslav Pragl Comment 10 Dan Williams Avu-310a think the issue with your device may be that you dont’ have 1X service, but you do have EVDO service.
I have the same problem. During one of the attempts to connect the NetworkManager even managed to get Adu-31a0 addresses, but then NetworkManager terminated the connection: Comment 38 Igor Bukanov Moreover, the nm-applet menu shows only one entry.
There may be a bug in the applet WRT duplicate devices between plugging and unplugging modems, but it’s never a bug in NM itself. Also I can provide any additional information or debug info if necessary.
Note You need to log in before you can comment on or make changes to this bug.
This log was collected by another guy on forum, and it seems he just has some issue with provider.