Re: Telit LE910 failing to find network

2017-07-28 Thread Daniele Palmas
Hi Kelvin,

2017-07-28 10:10 GMT+02:00 Kelvin :
> Hi,
>
>>
>> > And --3gpp-scan on that card showed 'available' for all networks.
>> >
>> > Thanks for any hints,
>>
>> Sorry, I'm not a qmi protocol expert so maybe I'm missing something,
>> but those seem not to be useful to me for understanding the issue.
>>
>> Could you please send AT#MONI in one of the available serial ports and
>> report the output?
>
>
> AT#MONI returns:
> #MONI: EE PSC:393 RSCP:-117 LAC:0489 Id:0D629F4 EcIo:-9.0 UARFCN:10786
> PWR:-108dbm DRX:64 SCR:6288 URA:4294967295
>

PWR: -108 dbm

That can be the issue: signal level is too much low. Maybe some antenna problem?

Regards,
Daniele

>>
>> Has this modem ever worked properly with a different setup (e.g. SIM,
>> OS...) ?
>
>
> It has been a bit intermittent but at the moment is not registering at all
> (with two SIMs from two different providers).
>
>>
>> The only real hint I can provide is to contact Telit technical
>> support: they will probably ask you to update the firmware and retry
>> and, if the problem persists, maybe collect a qxdm trace (that will
>> definitely explain why the modem is not registering).
>
>
> I've tried the latest Telit firmware I was sent (17.0.1.522) and the
> behaviour is pretty much the same. I'll send a separate mail with the logs.
>
> Thanks a lot for the replies,
> Kelvin.
>
>>
>>
>> Regards,
>> Daniele
>>
>> > Kelvin.
>
>
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


Re: Telit LE910 failing to find network

2017-07-28 Thread Kelvin
Hi,


> > And --3gpp-scan on that card showed 'available' for all networks.
> >
> > Thanks for any hints,
>
> Sorry, I'm not a qmi protocol expert so maybe I'm missing something,
> but those seem not to be useful to me for understanding the issue.
>
> Could you please send AT#MONI in one of the available serial ports and
> report the output?
>

AT#MONI returns:
#MONI: EE PSC:393 RSCP:-117 LAC:0489 Id:0D629F4 EcIo:-9.0 UARFCN:10786
PWR:-108dbm DRX:64 SCR:6288 URA:4294967295


> Has this modem ever worked properly with a different setup (e.g. SIM,
> OS...) ?
>

It has been a bit intermittent but at the moment is not registering at all
(with two SIMs from two different providers).


> The only real hint I can provide is to contact Telit technical
> support: they will probably ask you to update the firmware and retry
> and, if the problem persists, maybe collect a qxdm trace (that will
> definitely explain why the modem is not registering).
>

I've tried the latest Telit firmware I was sent (17.0.1.522) and the
behaviour is pretty much the same. I'll send a separate mail with the logs.

Thanks a lot for the replies,
Kelvin.


>
> Regards,
> Daniele
>
> > Kelvin.
>
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


Re: Telit LE910 failing to find network

2017-07-20 Thread Daniele Palmas
Hi Kelvin,

2017-07-19 14:51 GMT+02:00 Kelvin :
> Hi
>
>> According to logs shared by Kelvin, the modem seems to be properly
>> replying
>
>
> Thanks, yes QMI commands seem to be working now but it fails to register on
> a network.
>
> I've tried a SIM card for a different network provider now (EE) and the scan
> response is:
>
> Jul 19 12:42:44 linaro-gnome ModemManager[802]:  Running registration
> checks (CS: 'yes', PS: 'yes', EPS: 'no')
> Jul 19 12:42:44 linaro-gnome ModemManager[802]: [/dev/cdc-wdm0] Sent
> message...#012<< RAW:#012<<   length = 13#012<<   data   =
> 01:0C:00:00:03:02:00:36:00:24:00:00:00
> Jul 19 12:42:44 linaro-gnome ModemManager[802]: [/dev/cdc-wdm0] Sent message
> (translated)...#012<< QMUX:#012<<   length  = 12#012<<   flags
> = 0x00#012<<   service = "nas"#012<<   client  = 2#012<<
> QMI:#012<<   flags   = "none"#012<<   transaction = 54#012<<
> tlv_length  = 0#012<<   message = "Get Serving System" (0x0024)
> Jul 19 12:42:44 linaro-gnome ModemManager[802]: [/dev/cdc-wdm0] Received
> message...#012>> RAW:#012>>   length = 76#012>>   data   =
> 01:4B:00:80:03:02:02:36:00:24:00:3F:00:02:04:00:00:00:00:00:28:01:00:00:27:05:00:EA:00:1E:00:00:26:02:00:89:01:21:05:00:01:01:00:01:00:15:03:00:01:05:01:12:05:00:EA:00:1E:00:00:11:01:00:00:10:01:00:01:01:06:00:02:02:02:02:01:05
> Jul 19 12:42:44 linaro-gnome ModemManager[802]: [/dev/cdc-wdm0] Received
> message (translated)...#012>> QMUX:#012>>   length  = 75#012>>
> flags   = 0x80#012>>   service = "nas"#012>>   client  = 2#012>>
> QMI:#012>>   flags   = "response"#012>>   transaction =
> 54#012>>   tlv_length  = 63#012>>   message = "Get Serving
> System" (0x0024)#012>> TLV:#012>>   type   = "Result"
> (0x02)#012>>   length = 4#012>>   value  =
> 00:00:00:00#012>>   translated = SUCCESS#012>> TLV:#012>>   type
> = 0x28#012>>   length = 1#012>>   value  = 00#012>>
> TLV:#012>>   type   = "MNC PCS Digit Include Status"
> (0x27)#012>>   length = 5#012>>   value  =
> EA:00:1E:00:00#012>>   translated = [ mcc = '234' mnc = '30'
> includes_pcs_digit = 'no' ]#012>> TLV:#012>>   type   = "UMTS
> Primary Scrambling Code" (0x26)#012>>   length = 2#012>>   value
> = 89:01#012>>   translated = 393#012>> TLV:#012>>   type   =
> "Detailed Service Status" (0x21)#012>>   length = 5#012>>
> value  = 01:01:00:01:00#012>>   translated = [ status = 'limited'
> capability = 'cs' hdr_status = 'none' hdr_hybrid = 'yes' forbidden = 'no'
> ]#012>> TLV:#012>>   type   = "Roaming Indicator List"
> (0x15)#012>>   length = 3#012>>   value  =
> 01:05:01#012>>   translated = { [0] = '[ radio_interface = 'umts'
> roaming_indicator = 'off' ] '}#012>> TLV:#012>>   type   =
> "Current PLMN" (0x12)#012>>   length = 5#012>>   value  =
> EA:00:1E:00:00#012>>   translated = [ mcc = '234' mnc = '30' description
> = '' ]#012>> TLV:#012>>   type   = "Data Service Capability"
> (0x11)#012>>   length = 1#012>>   value  = 00#012>>
> translated = {}#012>> TLV:#012>>   type   = "Roaming Indicator"
> (0x10)#012>>   length = 1#012>>   value  = 01#012>>
> translated = off#012>> TLV:#012>>   type   = "Serving System"
> (0x01)#012>>   length = 6#012>>   value  =
> 02:02:02:02:01:05#012>>   translated = [ registration_state =
> 'not-registered-searching' cs_attach_state = 'detached' ps_attach_state =
> 'detached' selected_network = '3gpp' radio_interfaces = '{ [0] = 'umts '}' ]
> Jul 19 12:42:44 linaro-gnome ModemManager[802]:  Processing 3GPP
> info...
> Jul 19 12:42:44 linaro-gnome ModemManager[802]:  Modem not yet
> registered in a 3GPP network... will recheck soon
>
>
> The --3gpp-scan is a bit different with this SIM card / network, it shows
> 'current' for the correct network (EE) and forbidden for the others:
>
> linaro@linaro-gnome:~$ sudo mmcli -m 0 --3gpp-scan --timeout=300
>
> Found 7 networks:
> 23410 - O2 - UK (lte, forbidden)
> 23415 - voda UK (lte, forbidden)
> 23420 - 3 UK (umts, forbidden)
> 23410 - O2 - UK (umts, forbidden)
> 23415 - voda UK (gsm, forbidden)
> 23415 - voda UK (umts, forbidden)
> 23430 - EE (umts, current)
>
>
> The SIM card / network I was using earlier looked like this while scanning:
>
> Jul 19 10:07:48 linaro-gnome ModemManager[3663]:  [1500458868.901761]
> [mm-iface-modem-3gpp.c:761] mm_iface_modem_3gpp_run_registration_checks():
> Running registration checks (CS: 'yes', PS: 'yes', EPS: 'no')
> Jul 19 10:07:48 linaro-gnome ModemManager[3663]: [/dev/cdc-wdm0] Sent
> message...#012<< RAW:#012<<   length = 13#012<<   data   =
> 01:0C:00:00:03:02:00:2F:00:24:00:00:00
> Jul 19 10:07:48 linaro-gnome 

Re: Telit LE910 failing to find network

2017-07-19 Thread Kelvin
Hi

According to logs shared by Kelvin, the modem seems to be properly replying


Thanks, yes QMI commands seem to be working now but it fails to register on
a network.

I've tried a SIM card for a different network provider now (EE) and the
scan response is:

Jul 19 12:42:44 linaro-gnome ModemManager[802]:  Running
registration checks (CS: 'yes', PS: 'yes', EPS: 'no')
Jul 19 12:42:44 linaro-gnome ModemManager[802]: [/dev/cdc-wdm0] Sent
message...#012<< RAW:#012<<   length = 13#012<<   data   =
01:0C:00:00:03:02:00:36:00:24:00:00:00
Jul 19 12:42:44 linaro-gnome ModemManager[802]: [/dev/cdc-wdm0] Sent
message (translated)...#012<< QMUX:#012<<   length  = 12#012<<
  flags   = 0x00#012<<   service = "nas"#012<<   client  =
2#012<< QMI:#012<<   flags   = "none"#012<<   transaction =
54#012<<   tlv_length  = 0#012<<   message = "Get Serving
System" (0x0024)
Jul 19 12:42:44 linaro-gnome ModemManager[802]: [/dev/cdc-wdm0] Received
message...#012>> RAW:#012>>   length = 76#012>>   data   =
01:4B:00:80:03:02:02:36:00:24:00:3F:00:02:04:00:00:00:00:00:
28:01:00:00:27:05:00:EA:00:1E:00:00:26:02:00:89:01:21:05:00:
01:01:00:01:00:15:03:00:01:05:01:12:05:00:EA:00:1E:00:00:11:
01:00:00:10:01:00:01:01:06:00:02:02:02:02:01:05
Jul 19 12:42:44 linaro-gnome ModemManager[802]: [/dev/cdc-wdm0] Received
message (translated)...#012>> QMUX:#012>>   length  = 75#012>>
  flags   = 0x80#012>>   service = "nas"#012>>   client  =
2#012>> QMI:#012>>   flags   = "response"#012>>
transaction = 54#012>>   tlv_length  = 63#012>>   message =
"Get Serving System" (0x0024)#012>> TLV:#012>>   type   =
"Result" (0x02)#012>>   length = 4#012>>   value  =
00:00:00:00#012>>   translated = SUCCESS#012>> TLV:#012>>
type   = 0x28#012>>   length = 1#012>>   value  = 00#012>>
TLV:#012>>   type   = "MNC PCS Digit Include Status"
(0x27)#012>>   length = 5#012>>   value  =
EA:00:1E:00:00#012>>   translated = [ mcc = '234' mnc = '30'
includes_pcs_digit = 'no' ]#012>> TLV:#012>>   type   = "UMTS
Primary Scrambling Code" (0x26)#012>>   length = 2#012>>
value  = 89:01#012>>   translated = 393#012>> TLV:#012>>
type   = "Detailed Service Status" (0x21)#012>>   length =
5#012>>   value  = 01:01:00:01:00#012>>   translated = [ status
= 'limited' capability = 'cs' hdr_status = 'none' hdr_hybrid = 'yes'
forbidden = 'no' ]#012>> TLV:#012>>   type   = "Roaming
Indicator List" (0x15)#012>>   length = 3#012>>   value  =
01:05:01#012>>   translated = { [0] = '[ radio_interface = 'umts'
roaming_indicator = 'off' ] '}#012>> TLV:#012>>   type   =
"Current PLMN" (0x12)#012>>   length = 5#012>>   value  =
EA:00:1E:00:00#012>>   translated = [ mcc = '234' mnc = '30'
description = '' ]#012>> TLV:#012>>   type   = "Data Service
Capability" (0x11)#012>>   length = 1#012>>   value  =
00#012>>   translated = {}#012>> TLV:#012>>   type   =
"Roaming Indicator" (0x10)#012>>   length = 1#012>>   value
 = 01#012>>   translated = off#012>> TLV:#012>>   type   =
"Serving System" (0x01)#012>>   length = 6#012>>   value  =
02:02:02:02:01:05#012>>   translated = [ registration_state =
'not-registered-searching' cs_attach_state = 'detached' ps_attach_state =
'detached' selected_network = '3gpp' radio_interfaces = '{ [0] = 'umts '}' ]
Jul 19 12:42:44 linaro-gnome ModemManager[802]:  Processing 3GPP
info...
Jul 19 12:42:44 linaro-gnome ModemManager[802]:  Modem not yet
registered in a 3GPP network... will recheck soon


The --3gpp-scan is a bit different with this SIM card / network, it shows
'current' for the correct network (EE) and forbidden for the others:

linaro@linaro-gnome:~$ sudo mmcli -m 0 --3gpp-scan --timeout=300

Found 7 networks:
23410 - O2 - UK (lte, forbidden)
23415 - voda UK (lte, forbidden)
23420 - 3 UK (umts, forbidden)
23410 - O2 - UK (umts, forbidden)
23415 - voda UK (gsm, forbidden)
23415 - voda UK (umts, forbidden)
23430 - EE (umts, current)


The SIM card / network I was using earlier looked like this while scanning:

Jul 19 10:07:48 linaro-gnome ModemManager[3663]: 
[1500458868.901761] [mm-iface-modem-3gpp.c:761]
mm_iface_modem_3gpp_run_registration_checks(): Running registration checks
(CS: 'yes', PS: 'yes', EPS: 'no')
Jul 19 10:07:48 linaro-gnome ModemManager[3663]: [/dev/cdc-wdm0] Sent
message...#012<< RAW:#012<<   length = 13#012<<   data   =
01:0C:00:00:03:02:00:2F:00:24:00:00:00
Jul 19 10:07:48 linaro-gnome ModemManager[3663]: [/dev/cdc-wdm0] Sent
message (translated)...#012<< QMUX:#012<<   length  = 12#012<<
  flags   = 0x00#012<<   service = "nas"#012<<   client  =
2#012<< QMI:#012<<   flags   = 

Re: Telit LE910 failing to find network

2017-07-19 Thread Daniele Palmas
Hi Lars,

2017-07-19 13:43 GMT+02:00 Lars Melin :
> On 2017-07-19 16:48, Kelvin wrote:
>>
>>
>> If I'm not wrong qmi_wwan is trying to bind to interface 5, but
>> rmnet
>> is on 2 (that has been wrongly taken by option). Which kernel
>> version
>> are you using? Did you modify the source code of option and
>> qmi_wwan?
>>
>>
>> This does indeed look incorrect - the qmi_wwan.c modification on
>> this kernel uses 5 but the LE910 documents say to use 2. Good catch,
>> thanks!
>
>
> 1bc7:1201 needs special handling (set DTR) in the qmi_wwan driver so the fix
> is not as simple as just changing a 5 to a 2.
> You will not get any reply on the qmi interface without that.

LE910 does not need to have dtr set: the change is needed, instead,
for LE920A4 and other more recent modems that are sharing the same
PID, but need DTR set.

According to logs shared by Kelvin, the modem seems to be properly replying.

Regards,
Daniele

>
> /Lars
>
>
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


Re: Telit LE910 failing to find network

2017-07-19 Thread Aleksander Morgado
On Wed, Jul 19, 2017 at 11:48 AM, Kelvin  wrote:
> Not fully there yet, though, I tried --3gpp-scan and the modem is listed as
> disabled:
>
> linaro@linaro-gnome:~$ sudo mmcli -m 0 --3gpp-scan
> error: modem not enabled yet

You need to enable it yourself:
$ sudo mmcli -m 0 --enable

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


Re: Telit LE910 failing to find network

2017-07-19 Thread Kelvin
>
> CONFIG_MSM_QMI_INTERFACE=y ?
>
> Are you building an Android kernel with both Qualcomm and qmi-wwan
> drivers trying to do QMI?
>

Not deliberately - but the development board is typically used on Android,
with Linux/Ubuntu provided as a secondary platform, so I guess there could
be some Android stuff left over in the vendor's Linux kernel.

config MSM_QMI_INTERFACE
depends on IPC_ROUTER
depends on QMI_ENCDEC
bool "MSM QMI Interface Library"
help
  Library to send and receive QMI messages over IPC Router.
  This library provides interface functions to the kernel drivers
  to perform QMI message marshaling and transport them over IPC
  Router.

Thanks,
Kelvin.



> --
> Aleksander
> https://aleksander.es
>
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


Re: Telit LE910 failing to find network

2017-07-19 Thread Aleksander Morgado
On Tue, Jul 18, 2017 at 9:30 PM, Kelvin  wrote:
> Also QMI-related:
> grep QMI .config
> # CONFIG_MSM_TEST_QMI_CLIENT is not set
> CONFIG_USB_NET_QMI_WWAN=y
> CONFIG_MSM_QMI_INTERFACE=y
> # CONFIG_MEM_SHARE_QMI_SERVICE is not set
> CONFIG_QMI_ENCDEC=y
> # CONFIG_QMI_ENCDEC_DEBUG is not set

CONFIG_MSM_QMI_INTERFACE=y ?

Are you building an Android kernel with both Qualcomm and qmi-wwan
drivers trying to do QMI?

-- 
Aleksander
https://aleksander.es
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


Re: Telit LE910 failing to find network

2017-07-18 Thread Kelvin
>
> > Thanks a lot, the full syslog is here: https://pastebin.com/6X5K0gXU
>
> It shows the modem is using regular AT commands, when it should really
> be using QMI instead.  What is "lsusb -v -d 1bc7:1201" for this device?
>
> The problem appears to be:
>
> Jan  1 20:48:44 linaro-gnome kernel: [   10.661323] qmi_wwan 1-2.1:1.5:
> bogus CDC Union: master=0, slave=0
>
> Jan  1 20:48:44 linaro-gnome kernel: [   10.661409] qmi_wwan: probe of
> 1-2.1:1.5 failed with error -1
>
> Bjorn/Carl/others would probably know more about why the probe fails
> for this device.  But if you could grab the lsusb -v output I asked for
> above, that would help figure it out.
>

Thanks for looking at the logs, the lsusb results are as below (shows both
devices).

Many thanks,
Kelvin.


lsusb -v -d 1bc7:1201

Bus 001 Device 016: ID 1bc7:1201 Telit
Couldn't open device, some information will be missing
Device Descriptor:
  bLength18
  bDescriptorType 1
  bcdUSB   2.00
  bDeviceClass0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize064
  idVendor   0x1bc7 Telit
  idProduct  0x1201
  bcdDevice2.32
  iManufacturer   1
  iProduct2
  iSerial 3
  bNumConfigurations  1
  Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength  281
bNumInterfaces  7
bConfigurationValue 1
iConfiguration  0
bmAttributes 0x80
  (Bus Powered)
MaxPower  500mA
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber0
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81  EP 1 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01  EP 1 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber1
  bAlternateSetting   0
  bNumEndpoints   2
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass 66
  bInterfaceProtocol  1
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82  EP 2 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02  EP 2 OUT
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
Interface Descriptor:
  bLength 9
  bDescriptorType 4
  bInterfaceNumber2
  bAlternateSetting   0
  bNumEndpoints   3
  bInterfaceClass   255 Vendor Specific Class
  bInterfaceSubClass255 Vendor Specific Subclass
  bInterfaceProtocol255 Vendor Specific Protocol
  iInterface  0
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84  EP 4 IN
bmAttributes3
  Transfer TypeInterrupt
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0008  1x 8 bytes
bInterval   9
  Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83  EP 3 IN
bmAttributes2
  Transfer TypeBulk
  Synch Type   None
  Usage Type   Data
wMaxPacketSize 0x0200  1x 512 bytes
bInterval   0
  

Re: Telit LE910 failing to find network

2017-07-18 Thread Dan Williams
On Tue, 2017-07-18 at 20:30 +0100, Kelvin wrote:
> Hi,
> 
> 
> > could you please attach the full debug logs, so we can have a
> > complete
> > picture of what's going on?
> > 
> 
> Thanks a lot, the full syslog is here: https://pastebin.com/6X5K0gXU

It shows the modem is using regular AT commands, when it should really
be using QMI instead.  What is "lsusb -v -d 1bc7:1201" for this device?

The problem appears to be:

Jan  1 20:48:44 linaro-gnome kernel: [   10.661323] qmi_wwan 1-2.1:1.5: 
bogus CDC Union: master=0, slave=0

Jan  1 20:48:44 linaro-gnome kernel: [   10.661409] qmi_wwan: probe of
1-2.1:1.5 failed with error -1

Bjorn/Carl/others would probably know more about why the probe fails
for this device.  But if you could grab the lsusb -v output I asked for
above, that would help figure it out.

Thanks,
Dan

> 
> > Moreover, what's the PID of your modem?
> > 
> 
> From lsusb:
> Bus 001 Device 076: ID 1bc7:1201 Telit
> Bus 001 Device 075: ID 1bc7:1201 Telit
> 
> They are both LE910s, the one I'm using (ttyUSB3 in the above syslog)
> is an
> LE910 EUG (Euro / Aus). The other which I don't have a SIM card in is
> an
> LE910 SVG (North America).
> 
> 
> > By default LE910 uses QMI protocol (cdc-wdmX device, instead of
> > ttyUSB).
> > 
> 
> Perhaps missing support from the kernel? Here are the CDC-related
> ones:
> 
> grep CDC .config
> CONFIG_USB_NET_CDCETHER=y
> # CONFIG_USB_NET_CDC_EEM is not set
> CONFIG_USB_NET_CDC_NCM=y
> # CONFIG_USB_NET_CDC_MBIM is not set
> CONFIG_USB_NET_CDC_SUBSET=y
> # CONFIG_DRM_TILCDC is not set
> # CONFIG_USB_CDC_COMPOSITE is not set

> Also QMI-related:
> grep QMI .config
> # CONFIG_MSM_TEST_QMI_CLIENT is not set
> CONFIG_USB_NET_QMI_WWAN=y
> CONFIG_MSM_QMI_INTERFACE=y
> # CONFIG_MEM_SHARE_QMI_SERVICE is not set
> CONFIG_QMI_ENCDEC=y
> # CONFIG_QMI_ENCDEC_DEBUG is not set
> 
> Many thanks for any hints,
> Kelvin.
> ___
> ModemManager-devel mailing list
> ModemManager-devel@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel


Re: Telit LE910 failing to find network

2017-07-17 Thread Kelvin
Hi Aleksander,

I tried upgrading to modemmanager-1.6.4 and similar results. Comments below.


> The 3GPP module should by default auto-register in the best network it
> finds. When using a SIM card for a provider for which there is a real
> network available, that should happen instantly, not sure why it's not
> happening here.
>
> Can you try to to explicitly request the home connection with mmcli
> --3gpp-register-home?
>

"error: couldn't register the modem: 'Timeout was reached"'


> Also, can you try to register in a specific network with
> --3gpp-register-in-operator=[MCCMNC] ?
>

The same:
"error: couldn't register the modem: 'Timeout was reached"'


> > Is the "EPS supported: No" relevant? The LE910 supports 2G, 3G, 4G.
> >
>
> Since ModemManager 1.6.x we enable by default registration checks in
> the EPS (LTE) network, it was disabled by default in previous
> releases.
>

With 1.6.4 it still doesn't seem to check for EPS, though I'm not sure if
that matters:

Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  Running
registration checks (CS: 'yes', PS: 'yes', EPS: 'no')
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  (ttyUSB3) device
open count is 2 (open)
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  (ttyUSB3): -->
'AT+CREG?'
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  (ttyUSB3): <--
'+CREG: 2,2OK'
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  (ttyUSB3) device
open count is 3 (open)
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  (ttyUSB3) device
open count is 2 (close)
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  (ttyUSB3): -->
'AT+CGREG?'
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  (ttyUSB3): <--
'+CGREG: 2,2OK'
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  (ttyUSB3) device
open count is 1 (close)
Jul 17 22:26:16 linaro-gnome ModemManager[3108]:  Modem not yet
registered in a 3GPP network... will recheck soon


> Oh, please update to MM 1.6.x and retry, please. MM 1.4.x is quite
> old, and MM 1.2.x is veery old. The MM 1.6.x release also comes
> with a Telit plugin, not available in earlier releases.
>

Still not having luck with 1.6.4, even though there are still 11 networks
showing in 3gpp-scan including the on I'm interested in.

>   | drivers: 'option1'
> >   | plugin: 'Generic'
> >   | primary port: 'ttyUSB8'
> >   | ports: 'ttyUSB8 (at)'
>
>

> Is this supposed to be a single-TTY modem?
>

Each Telit has 4x ttyUSB devices (I've got 2 connected to this board but
one is not in use, has no SIM card etc).

Thanks a lot for any hints, much appreciated.

Kelvin.
___
ModemManager-devel mailing list
ModemManager-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/modemmanager-devel