Sierra Wireless EM7355

Erinn Looney-Triggs erinn.looneytriggs at gmail.com
Thu Jun 19 10:27:02 PDT 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 06/18/2014 02:38 AM, Bjørn Mork wrote:
> Erinn Looney-Triggs <erinn.looneytriggs at gmail.com> writes:
>> On 06/17/2014 04:24 PM, Dan Williams wrote:
>>> On Tue, 2014-06-17 at 13:42 -0600, Erinn Looney-Triggs wrote:
>>>> I am having trouble getting this device to work under Fedora
>>>> 20. It is detected on first boot, though in a dual boot
>>>> environment after booting into windows, it is still detected,
>>>> though not configured. However, that is another issue.
>>> 
>>> Until Bjorn drops some righteous knowledge on us...
>>> 
>>> Bjorn posted some driver patches for the 7355 which just hit
>>> the 3.14 stable kernel two weeks ago:
>>> 
>>> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-3.14.y&id=d2c3d4f3bcfd826546cabcc1850b1a14ab2b4749
>>>
>>>
>>> 
so make sure you're using the 3.14.5 or later kernel, which is
>>> available in Fedora updates since early June.  Can you confirm
>>> that you are using the 3.14.5 or later kernel, and if not, try
>>> it after updating?
>>> 
>>> Dan
>>> 
>> 
>> Dan, Thanks for the suggestion, I am running against 3.14.7 right
>> now, so no luck there.
> 
> No, that patch doesn't really matter here.  It is for qmi_wwan
> which you won't use unless you choose to switch the modem to cfg
> #1.  MBIM is supported by the class driver and does not depend on
> device IDs being added.
> 
> 
> 
>>>> [/dev/cdc-wdm0] Sent message... <<<<<< RAW: <<<<<<   length =
>>>> 16 <<<<<<   data   = 
>>>> 01:00:00:00:10:00:00:00:01:00:00:00:00:10:00:00 
>>>> ModemManager[3238]: [/dev/cdc-wdm0] Sent message
>>>> (translated)... <<<<<< Header: <<<<<<   length      = 16
>>>> <<<<<<   type        = open (0x00000001) <<<<<<   transaction
>>>> = 1 <<<<<< Contents: <<<<<<   max_control_transfer = 4096
>>>> ModemManager[3238]: [/dev/cdc-wdm0] Received message...
>>>> 
>>>> ModemManager[3238]: [/dev/cdc-wdm0] No transaction matched
>>>> in received message ModemManager[3238]: [/dev/cdc-wdm0] Sent 
>>>> message... <<<<<< RAW: <<<<<<   length = 16 <<<<<<   data
>>>> = 01:00:00:00:10:00:00:00:02:00:00:00:00:10:00:00 
>>>> ModemManager[3238]: [/dev/cdc-wdm0] Sent message
>>>> (translated)... <<<<<< Header: <<<<<<   length      = 16
>>>> <<<<<<   type        = open (0x00000001) <<<<<<   transaction
>>>> = 2 <<<<<< Contents: <<<<<<   max_control_transfer = 4096
>>>> ModemManager[3238]: [/dev/cdc-wdm0] Received message...
>>>> 
>>>> ModemManager[3238]: <debug> [1403033722.441276] 
>>>> [mm-port-probe.c:498] mbim_port_open_ready():
>>>> (usbmisc/cdc-wdm0) error checking MBIM support: 'Failure'
>>>> ModemManager[3238]: <debug> [1403033722.441300]
>>>> [mm-port-probe.c:317] mm_port_probe_set_result_mbim():
>>>> (usbmisc/cdc-wdm0) port is not MBIM-capable
> 
> 
> Hmm, so MM fails to get any MBIM response at all.  That's not good.
> I have no idea why.
> 
> 
>>>> Attempting to interact with the device via mbimcli does not
>>>> give anything particularly useful to my untrained eye.
> 
> Which means?  No response at all, just like MM sees?
> 
> Is there something else opening the /dev/cdc-wdmX device and 
> interfering?
> 
> If there isn't then I guess we'll have to start with usbmon dumps
> again.
> 
> 
> Bjørn
> 

Sorry for the delay, I am traveling currently (hence the need for the
modem) so connections are sporadic.

This modem is acting pretty erratically to be honest, sometimes it
appears modemmanager detects it on boot, sometimes not. No particular
rhyme or reason that I can divine at this point.

I don't believe anything else is using the device, best way I know to
check for this is lsof of /dev/cdc-wdm0, and nothing is showing.

So on this boot the modem doesn't appear to be detected by
modemmanager, though dmesg shows a listing for it being detected:
dmesg | grep cdc
[    3.661711] usbcore: registered new interface driver cdc_ncm
[    3.663117] usbcore: registered new interface driver cdc_wdm
[    3.668520] cdc_mbim 3-10:2.12: cdc-wdm0: USB WDM device
[    3.668686] cdc_mbim 3-10:2.12 wwan0: register 'cdc_mbim' at
usb-0000:00:14.0-10, CDC MBIM, d6:97:d6:76:77:18
[    3.668704] usbcore: registered new interface driver cdc_mbim

sudo mmcli -L

No modems were found

I'll read up on usbmon, and any other suggestions are appreciated.

- -Erinn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJTox1hAAoJEFg7BmJL2iPOBBAIAL1Qu0nH9vS7quZ9Fsp7U6wv
O6D7I/A6OOC6PpOaWrKmmT+LHsryIzOHAa0dULQ6moNnTP93kslhpkJE6TSIhhAu
bYmcV+OHiOGTLVqyEj3Z/eqyoKFj5xfpopWZojQ/Ah53V+SZDfYg5b9vPmtGuaQk
wTN8TNtPB4gwiDL7++SCXP0YPdt6viFg+ple+H39RYqvG/Vjj/8UVQkvD7cWkFPa
bUJdlHMAcDjhYayC6Sq0ha6MFzA1yF0SJbLABKVNxwXfMGa055yIMegW5gN5R5at
pM6QnlDGeO3iJNwdoG7CXy9RaRe/RoYI3u1m4viGHe7vLTl+SGIJveWQipBhvnc=
=qtLN
-----END PGP SIGNATURE-----


More information about the ModemManager-devel mailing list