Hide Forgot
Created attachment 379218 [details] NetworkManager --no-daemon Description of problem: Version-Release number of selected component (if applicable): NetworkManager-0.7.997-2.git20091214.fc12.i686 ModemManager-0.2.997-2.git20091214.fc12.i686 How reproducible: Steps to Reproduce: 1. install the update to NetworkManager (Update-testing repository) 2. try to connect to a cdma network 3. the icons activate but instantly deactivate the connection Actual results: cannot connect to a cdma network using NetworkManager Expected results: successfully connect to a cdma using Networmanager Additional info: My ISP is sprint using Sierra wireless Compass 597U. Previously i can connect using NetworkManager.
Created attachment 379220 [details] modem-manager --debug output of modem-manager --debug
Created attachment 379224 [details] dmesg log output of dmesg
Created attachment 379226 [details] lsusb log
same 'bad' things for me.
I got a Huawei E220 3G modem on a Vodafone RO broadband 3G+ network.
can you produce the same logs? NetworkManager --no-daemon modem-manager --debug lsusb dmesg
the logs are the same, except the dmesg which is showing me some output from my other stuff.
the differences are at the vendor / product.
strange error adding a new cdma connection with NetworkManager: Saving connection failed: (0) Can't write connection type 'cdma' see nm-error.jpg attachment.
Created attachment 379239 [details] Error Screenshot Error creating new CDMA connection with NM wizard...
one open bug. for my problem? this error appear in my NM logs NetworkManager pppd plugin does not work with latest pppd https://bugzilla.redhat.com/show_bug.cgi?id=548520
yep back-porting to ppp-2.4.4-13.fc12 solve my connection problem and also solve the creating CDMA Connection wizard error see connection.log attachment.
Created attachment 379244 [details] Successful connection Successful connection with NM and ppp version 2.4.4-13.fc12
Created attachment 379248 [details] Successful connection (ModemManager Log) Successful connection output ModemManager Log
*** This bug has been marked as a duplicate of bug 548520 ***