<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2014-05-05 23:29 GMT+02:00 Dan Williams <span dir="ltr"><<a href="mailto:dcbw@redhat.com" target="_blank">dcbw@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><div class="h5">On Mon, 2014-05-05 at 22:49 +0200, Marius Kotsbak wrote:<br>
> 2014-04-29 11:41 GMT+02:00 Aleksander Morgado <<a href="mailto:aleksander@aleksander.es">aleksander@aleksander.es</a>>:<br>
><br>
> > On Tue, Apr 29, 2014 at 11:13 AM, Marius Kotsbak <<a href="mailto:marius@kotsbak.com">marius@kotsbak.com</a>><br>
> > wrote:<br>
> > > Is there a way to use QMI to get the current frequency band in use,<br>
> > either<br>
> > > using the current libqmi or some yet unimplemented API? Or possibly using<br>
> > > MBIM?<br>
> > ><br>
> > > It would be interesting to see when the newly opened 800 MHz band for<br>
> > LTE is<br>
> > > in use.<br>
> ><br>
> ><br>
> > QMI has "NAS Get RF Band Information", but there is no qmicli command<br>
> > for that one yet. There is also the "NAS Get System Selection<br>
> > Preference", which will tell you how the modem is configured (i.e.<br>
> > which frequency bands it's allowed to use), and that one has the<br>
> > qmicli --nas-get-system-selection-preference command already. You can<br>
> > update which frequency bands to use through "NAS Set System Selection<br>
> > Preference", but the qmicli counterpart doesn't play with frequency<br>
> > bands at all, only with access techs (e.g. lte, gsm, umts..).<br>
> ><br>
> > ModemManager uses "NAS Get System Selection Preference" to list the<br>
> > current bands (e.g. with mmcli -m 0); and I also implemented support<br>
> > for "NAS Get RF Band Information" in there, but only when compiled<br>
> > with --with-newest-qmi-commands. You can update the bands allowed to<br>
> > use (will use "NAS Set System Selection Preference" ) with mmcli<br>
> > --set-current-bands.<br>
> ><br>
><br>
> I tried building MM 1.2 with that option, but it (Sierra MC7710) then fails<br>
> to connect. Relevant parts of the syslog:<br>
><br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: <info> Modem for<br>
> device at '/sys/devices/pci0000:00/0000:00:14.0/usb3/3-10' successfully<br>
> created<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Checking version info (10 retries)...<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> QMI Device supports 17 services:<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] ctl (1.5)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] wds (1.12)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] dms (1.7)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] nas (1.21)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] qos (1.3)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] wms (1.4)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] pds (1.10)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] auth (1.1)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] at (1.1)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] voice (2.1)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] cat2 (2.0)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] uim (1.4)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] pbm (1.4)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] sar (1.0)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] wda (1.0)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] cat (2.0)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]:<br>
> [/dev/cdc-wdm0] rms (1.0)<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Setting network port data format...<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Network port data format operation finished<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Allocating new client ID...<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Registered 'dms' (version 1.7) client with ID '4'<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Allocating new client ID...<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Registered 'nas' (version 1.21) client with ID '4'<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Allocating new client ID...<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Registered 'wms' (version 1.4) client with ID '4'<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Allocating new client ID...<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: [/dev/cdc-wdm0]<br>
> Registered 'pds' (version 1.10) client with ID '4'<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: <warn><br>
> (ttyUSB2): port attributes not fully set<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: <warn> couldn't<br>
> load list of Own Numbers: 'Couldn't get MSISDN: QMI protocol error (16):<br>
> 'NotProvisioned''<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: <warn> couldn't<br>
> load current Bands: 'Couldn't parse the list of current bands'<br>
> May 5 21:27:41 marius-Precision-M4800 ModemManager[999]: <info> Modem:<br>
> state changed (unknown -> disabled)<br>
> May 5 21:27:41 marius-Precision-M4800 NetworkManager[1078]: <warn><br>
> (cdc-wdm0): failed to look up interface index<br>
> May 5 21:27:41 marius-Precision-M4800 NetworkManager[1078]: <info><br>
> (cdc-wdm0): new Broadband device (driver: 'qcserial, qmi_wwan' ifindex: 0)<br>
> May 5 21:27:41 marius-Precision-M4800 NetworkManager[1078]: <info><br>
> (cdc-wdm0): exported as /org/freedesktop/NetworkManager/Devices/3<br>
> May 5 21:27:41 marius-Precision-M4800 NetworkManager[1078]: <info><br>
> (cdc-wdm0): device state change: unmanaged -> unavailable (reason<br>
> 'managed') [10 20 2]<br>
> May 5 21:27:41 marius-Precision-M4800 NetworkManager[1078]: <info><br>
> (cdc-wdm0): deactivating device (reason 'managed') [2]<br>
> May 5 21:27:41 marius-Precision-M4800 NetworkManager[1078]: <info><br>
> (cdc-wdm0): device state change: unavailable -> disconnected (reason<br>
> 'none') [20 30 0]<br>
><br>
> May 5 21:39:40 marius-Precision-M4800 NetworkManager[1078]: <info><br>
> Activation (cdc-wdm0) starting connection 'Telenor Default'<br>
> May 5 21:39:40 marius-Precision-M4800 NetworkManager[1078]: <info><br>
> (cdc-wdm0): device state change: disconnected -> prepare (reason 'none')<br>
> [30 40 0]<br>
<br>
</div></div>Can you get the ModemManager debug logs from this point forward? That's<br>
what would be interesting here, since the time between the connection<br>
request (21:39:40) and the "network timeout" (21:39:41) is only one<br>
second, which is pretty odd. Lets see what MM is doing once it gets the<br>
Simple Connect request.<br>
<span class=""><font color="#888888"><br></font></span></blockquote><div><br></div><div>Hmm, when trying to do that, it then worked to connect... :/ Anyway, I then get this using mmcli:<br><br> Bands | supported: 'cdma-bc15-aws, dcs, egsm, pcs, u2100, u900, eutran-i, eutran-iii, eutran-vii, eutran-viii, eutran-xx'<br>
| current: 'cdma-bc15-aws, dcs, egsm, pcs, u2100, u900, eutran-i, eutran-iii, eutran-vii, eutran-viii, eutran-xx'<br><br></div><div>Isn't that just listing all enabled bands, not what is currently in use?<br>
</div></div></div></div>