|Date Added:||13 December 2011|
|File Size:||14.58 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
I think the issue with your device may be that you dont’ have 1X service, but you do have EVDO service.
anydwta Comment 21 Igor Bukanov I can certainly add them back into the provider info. Comment 43 Vassily Gavrilyak The same applies to ADUA – see comment 7.
AnyDATA | KOMACHINE
The error occurs even before dialing Steps to Reproduce: Unfortunately, I do not own this modem, the previous debug log was from ady-e100a session on forum.
Does that one work? Comment 40 Fedora Update System 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. Comment 33 Dan Williams Comment 49 Stanislav Hanzhin We probably need to write those anyway, but it would be good to figure out what the issue is first.
Comment 12 Igor Bukanov So I suspect the issue is anydatx modem simply hasn’t had enough time to fully register on the network yet. Comment 14 Igor Bukanov U30ICE04 1 [Mar 06 In Fedora the NetworkManager could not initialize the modem properly and log contains: Comment 38 Igor Bukanov Comment 26 Dan Williams Some modems like these will key the CSS response off the 1X state.
After selecting the modem from NetworkManager adk-e100a when modem is connected to the network: The format of the response is: NetworkManager Show other bugs. Comment 1 Dan Williams Comment 42 Igor Bukanov Here is a relevant modem-manager –debug output: So it’s not surprising that you can’t use minicom to talk to ttyUSB1. This could be because just checking the SID isn’t enough for these devices.
So it looks like sometimes modem works one way and sometimes different way. Comment 16 Dan Williams Comment 41 Igor Bukanov Comment 9 Vassily Gavrilyak Often I just need a few of the custom Adu-w100a commands to google around and find the manual or forum posts. But after I rebooted the computer everything has started to work.