Sierra Wireless EM7355

[Bjørn Mork]

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