Created attachment 412556 [details]
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible: uhm, always for me...
Steps to Reproduce:
1. insert md400
2. enable mobile broadband
3. try activate operators network access
Activation of mobile broadband unsuccessful
Activation of mobile broadband successful
We'll need some modem-manager output here. Check out the "Debugging NetworkManager 0.8.x 3G connections" section of:
and attach the modem-manager debug output when you can get it? THanks!
Created attachment 413329 [details]
Requested additional information.
The debug log files were collected during, insertion, restart in debug mode of NetworkManager and ModemManager, entering SIM PIN code (without successful activation) a few times, enabling Mobile Broadband, trying to activate the operators Mobile Broadband connection (unsuccessful).
So you'll want to make sure "allow roaming when home network is not available" checkbox in nm-connection-editor. It appears that your SIM detects the network as a roaming network and thus the connection is terminated. After that, if you pull down the menu, you should see the network listed as "roaming".
GSM connection failed: (32) Roaming is not allowed.
This is a function of your SIM since your provider has set your SIM to detect the network that's being registered with as a roaming network. I know that telenor and Three share the 3G network, but your modem is detecting the network as a roaming network.
If you re-check the "allow roaming" checkbox, does that solve the problem for you?
well, roaming outside home network... that box is indeed ticked. I get the network, it's registered as "SWEDEN (UMTS roaming)" but then I cannot activate, i.e., get into that network (under rawhide, I can with other os). I tried booting with selinux=0, same thing. I am a little suspicious on the dbus message being rejected, though...
Hmm, I'll have to add some debugging info to modem-manager to verify that the 'home-only' config option is correct when we send it from NM to MM I guess. Because that's the only thing I can think of in your case.
great, pls let me know when and how I can complement this bug report further to your recent proposition
So apparently MVNO networks often show up as roaming networks, which is completely unhelpful. And there aren't standard commands to get roaming status off the phone besides CREG which in this case reports taht you're roaming, unless the device implements specific commands for this which some do, and most don't.
I still need to verify that home-only works as expected.
I believe home-only works as expected...
There are a few other oddities in the md400 NM/MM logs that I'll have to add more debugging for.
If there's any chance you can connect to the device with minicom when it's in this state, and grab the output of both:
that would be very helpful. It may be the case that the device's roaming indicator reported by CIND is more useful than CREG.
Also, can you get updated modem-manager logs after installing this version of MM?
(look near the bottom for your architecture, grab the ModemManager package, and use 'rpm -Uhv <rpm file>' to install it).
well, as of now, I can enable the device. I'm still on rawhide, quite up to date as of today, not able to run the current kernel, am using ModemManager-0.4-2.git20100628.fc14.i686. The NetworkManager icon, I presume, still says UMTS roaming.
let me know if you do indeed need additional info and I will try to produce that to you.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.
More information and reason for this action is here:
(In reply to comment #10)
> well, as of now, I can enable the device.