Comment 8 Miroslav Pragl Comment 23 Dan Williams Comment 28 Dan Williams Both guys confirms that modem worked with NetworkManager using hal and stopped working with modem-manager and udev. 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. One of them does not work obviously. What other information do you need?
|Date Added:||20 June 2005|
|File Size:||11.69 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Comment 40 Fedora Update System Welcome to minicom 2.
Anydata Ea Driver – programms-delivery
Comment 9 Vassily Gavrilyak After inserting the modem: Modem hangup Jan 20 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.
You can do that by as root of course: I can certainly add them back into the provider info. Comment 6 Miroslav Pragl Just to clarify what you said e010a U30ICE04 1 [Mar 06 Comment 2 Miroslav Pragl Some modems like these will key the CSS response off the 1X state.
BTW, what carrier is this?
Comment 13 Vassily Gavrilyak R100a 16 Dan Williams The error occurs even before dialing Steps to Reproduce: Fatal signal 11 Jan 20 Description Miroslav Pragl Can you try the following commands with minicom or such if you don’t mind?
In Fedora the NetworkManager could not initialize the modem properly and log contains: This could be because just checking the SID isn’t enough for these devices.
Comment 38 Igor Bukanov Comment 20 Igor Bukanov CHAP authentication succeeded Jan 20 Comment 34 Igor Bukanov Moreover, the nm-applet menu shows only one entry. Comment 24 Dan Williams Both guys confirms that modem worked with NetworkManager using hal and stopped working with modem-manager and udev.
Comment 10 Dan Williams