It looks like the modem is only registered on the 1xRTT network (ie,On Mon, 2013-05-20 at 21:25 +0800, Heiher wrote:
> Help!
>
> $ mmcli -m 0
> /org/freedesktop/ModemManager1/Modem/0 (device id
> 'e59e0d09c4fdf0d6f4a0ab3d2e45823ad0430e96')
> -------------------------
> Hardware | manufacturer: 'Sierra Wireless, Incorporated'
> | model: 'MC7750'
> | revision: 'SWI9600M_01.00.09.03AP R2492 CARMD-EN-10526
> 2011/07/01 19:31:09'
> | capabilities: 'cdma-evdo, gsm-umts, lte'
> | current: 'cdma-evdo, gsm-umts, lte'
> | equipment id: '351622050024021'
> -------------------------
> System | device: '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4'
> | drivers: 'qcserial, qmi_wwan'
> | plugin: 'Gobi'
> | primary port: 'cdc-wdm0'
> -------------------------
> Numbers | own : 'unknown'
> -------------------------
> Status | lock: 'sim-pin2'
> | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10),
> sim-puk2 (10)'
> | state: 'disabled'
> | power state: 'on'
> | access tech: 'unknown'
> | signal quality: '0' (cached)
> -------------------------
> Modes | supported: '2g, 3g, 4g'
> | allowed: '2g, 3g, 4g'
> | preferred: 'none'
> -------------------------
> Bands | supported: 'cdma-bc0-cellular-800, cdma-bc1-pcs-1900'
> | current: 'unknown'
> -------------------------
> 3GPP | imei: '351622050024021'
> | enabled locks: 'none'
> | operator id: 'unknown'
> | operator name: 'unknown'
> | registration: 'unknown'
> -------------------------
> CDMA | meid: '35162205002402'
> | esn: '80CBB39A'
> | sid: 'unknown'
> | nid: 'unknown'
> | registration: CDMA1x 'unknown'
> | EV-DO 'unknown'
> | activation: 'unknown'
> -------------------------
> SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
>
> $ mmcli -m 0 -e
> successfully enabled the modem
>
> $ mmcli -m 0 --timeout=1000 --simple-connect="apn=ctnet"
> error: couldn't connect the modem:
> 'GDBus.Error:org.freedesktop.libqmi.Error.Protocol.CallFailed: QMI protocol
> error (14): 'CallFailed''
CDMA 2.5G). Can you grab some debug logs of ModemManager (eg, kill MM,
then re-run it with --debug) when this error occurs so we can see if MM
is trying to connect using the right bearer and whether it's connecting
at the right time? (eg, it should be waiting a while for the modem to
find the network before trying to connect).
Thanks!
Dan
> $ mmcli -m 0
>
> /org/freedesktop/ModemManager1/Modem/0 (device id
> 'e59e0d09c4fdf0d6f4a0ab3d2e45823ad0430e96')
> -------------------------
> Hardware | manufacturer: 'Sierra Wireless, Incorporated'
> | model: 'MC7750'
> | revision: 'SWI9600M_01.00.09.03AP R2492 CARMD-EN-10526
> 2011/07/01 19:31:09'
> | capabilities: 'cdma-evdo, gsm-umts, lte'
> | current: 'cdma-evdo, gsm-umts, lte'
> | equipment id: '351622050024021'
> -------------------------
> System | device: '/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4'
> | drivers: 'qcserial, qmi_wwan'
> | plugin: 'Gobi'
> | primary port: 'cdc-wdm0'
> -------------------------
> Numbers | own : 'unknown'
> -------------------------
> Status | lock: 'sim-pin2'
> | unlock retries: 'sim-pin (3), sim-pin2 (3), sim-puk (10),
> sim-puk2 (10)'
> | state: 'registered'
> | power state: 'on'
> | access tech: '1xrtt'
> | signal quality: '80' (recent)
> -------------------------
> Modes | supported: '2g, 3g, 4g'
> | allowed: '2g, 3g, 4g'
> | preferred: 'none'
> -------------------------
> Bands | supported: 'cdma-bc0-cellular-800, cdma-bc1-pcs-1900'
> | current: 'cdma-bc0-cellular-800, cdma-bc1-pcs-1900'
> -------------------------
> 3GPP | imei: '351622050024021'
> | enabled locks: 'none'
> | operator id: 'unknown'
> | operator name: 'unknown'
> | registration: 'idle'
> -------------------------
> CDMA | meid: '35162205002402'
> | esn: '80CBB39A'
> | sid: '14175'
> | nid: '13'
> | registration: CDMA1x 'home'
> | EV-DO 'unknown'
> | activation: 'unknown'
> -------------------------
> SIM | path: '/org/freedesktop/ModemManager1/SIM/0'
>
>
>
> On Thu, Apr 11, 2013 at 3:22 PM, Aleksander Morgado
> <aleksander lanedo com>wrote:
>
> >
> > >>>
> > >>> It took me a little while, but I put together recent builds with the
> > 'aleksander/current-capabilities' branch merged back into trunk. I now
> > have launchpad set up to do daily builds.
> > >>>
> > >>> If anyone else is on debian/ubuntu/mint, you can pull the builds from:
> > >>>
> > >>> https://code.launchpad.net/~dwa/+archive/network-manager-snapshots
> > >>>
> > >>> As for results, this is much better than what I had before. I am NOT
> > getting the error I used to get ("Error: Connection activation failed: The
> > connection was not a 3GPP2 connection."). So the
> > 'aleksander/current-capabilities' branch seems to have fixed this.
> > >>>
> > >>
> > >>
> > >> Good to know. Dan, what's your take on that patch?
> > >
> > > I thought we'd merged that already :) I just looked again, and it still
> > > looks good. It's certainly an improvement, the only thing we still need
> > > to fix is how to handle multi-mode devices that can switch between 3GPP
> > > and 3GPP2 at runtime (eg, UML290 or UMW190).
> > >
> >
> > Merged that branch to git master.
> >
> > For the 3GPP vs 3GPP2 issue during runtime, we may end up needing a
> > SetCurrentCapabilities() method or so :/ And maybe force a reboot of the
> > module if current capabilities change, so that both the internal state
> > of the modem (e.g. exposed ifaces) and also the external state (e.g. NM)
> > get updated accordingly. We already do something very similar with the
> > Firmware interface and the E396, which allows firmware switching through
> > QMI.
> >
> > --
> > Aleksander
> > _______________________________________________
> > networkmanager-list mailing list
> > networkmanager-list gnome org
> > https://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
>
>
>