gobi 3000 mc8355 error: couldn't set FCC auth

Wed Aug 17 20:37:00 UTC 2016


On 08/17/2016 01:40 PM, Bjørn Mork wrote:
> ITwrx Info <info at itwrx.org> writes:
>
>> On 08/17/2016 10:08 AM, Bjørn Mork wrote:
>>> "ITwrx.org" <info at itwrx.org> writes:
>>>
>>>> my MM debug log is here:  http://pastebin.com/ev8TGi8J
>>> OK, so that detects the sw radio off state and runs the FCC auth logic
>>> as it is supposed to.  But the result indicates this is not the issue:
>>>
>>> ModemManager[1109]: [/dev/cdc-wdm0] Received MBIM message
>>> ModemManager[1109]: [/dev/cdc-wdm0] Received message...
>>>>>>>>> RAW:
>>>>>>>>>     length = 20
>>>>>>>>>     data   = 01:13:00:80:02:04:02:01:00:5F:55:07:00:02:04:00:01:00:1A:00
>>> ModemManager[1109]: [/dev/cdc-wdm0] Received message (translated)...
>>>>>>>>> QMUX:
>>>>>>>>>     length  = 19
>>>>>>>>>     flags   = 0x80
>>>>>>>>>     service = "dms"
>>>>>>>>>     client  = 4
>>>>>>>>> QMI:
>>>>>>>>>     flags       = "response"
>>>>>>>>>     transaction = 1
>>>>>>>>>     tlv_length  = 7
>>>>>>>>>     message     = "Set FCC Authentication" (0x555F)
>>>>>>>>> TLV:
>>>>>>>>>     type       = "Result" (0x02)
>>>>>>>>>     length     = 4
>>>>>>>>>     value      = 01:00:1A:00
>>>>>>>>>     translated = FAILURE: NoEffect
>>> ModemManager[1109]: error: couldn't set FCC auth: QMI protocol error (26): 'NoEffect'
>> my reading of the log is that it tried to set the fcc auth but
>> failed. to me that doesn't necessarily mean it's not the issue, but i
>> don't know. that's just my reading of it from a layman's perspective.
> Yes, it failed, but the "NoEffect" is usually pretty descriptive.  FWIW,
> that's what I get on my EM7455 if I run  "Set FCC Authentication" twice:
>
>   root at miraculix:/home/bjorn# qmicli -p -d /dev/cdc-wdm0 --device-open-mbim  --dms-set-fcc-authentication
>   [/dev/cdc-wdm0] Successfully set FCC authentication
>
>   root at miraculix:/home/bjorn# qmicli -p -d /dev/cdc-wdm0 --device-open-mbim  --dms-set-fcc-authentication
>   error: couldn't set FCC authentication: QMI protocol error (26): 'NoEffect'
>
>
> So the above indicates that your modem doesn't need "Set FCC
> Authentication".
i still don't understand how it couldn't mean it actually failed the 
first time, but i'll take your word for it.
> There is obviously something keeping it in low-power
> mode, but it is more likely something else.
i tried powering on with "mmcli -m 3 --set-power-state-on"
and it reports
"'error: couldn't set new power state in the modem: 
'GDBus.Error:org.freedesktop.libmbim.Error.Status.Failure: Failure'".
Do you know what is generally required for a modem to be powered on? 
What all kernel modules are required for this modem, do you think? maybe 
i don't have the basics handled. do i need to blacklist anything?
>>> Are you sure your modem requires FCC auth?
>> no.
>>> Are you sure there aren't
>>> enywhting else keeping it in radio off state?
>> no. there very well may be but i don't know what.
> So you haven't seen this e.g. working in Windows?
i don't use windows at all. It's a new modem, so it should work. I had 
previously purchased what should have been a slightly more modern, 
better supported modem but lenovo's uefi whitelist suprised me. so i had 
a choice of two modems that would work with my carrier and band. i 
bought the cheaper one. For future reference, is the em7345 known to 
work out of the box?
>
>
>>> Typically that would a
>>> "missing" firmware image, as required by your operator settings.
>> this was the only guess i had too. i don't know what firmware i may
>> need or where to get it or how to load it. gobi-loader and
>> gobi-firmware were the only things i found but they appear to be for
>> gobi 2000 and 1000.
> Yes.  The gobi 3000 didn't normally need any firmware upload since it
> came with firmware on flash.  But newer modems like the MC73xx and
> MC74xx have a concept of firmware image and operator matching, where
> they will stay in low-power mode if none of the installed images are
> usable.
>
> I don't know if this applies to the gobi 3000 generation, though.
>
>
>>> Hmm, you don't have any AT command port enabled, do you?
>> not that i'm aware of.
>>> A look at the
>>> "AT!PCINFO?" output would be most useful...  Not to mention the
>>> "AT!PCFCCAUTH?" I've just learned about.
>>>
>>> But failing that, could you try this:
>> those commands failed to produce any results.
> You need to run them on the AT command TTY after entering the OEM
> password.  I.e.
>
> AT!ENTERCND="A710"
> AT!PCINFO?
> AT!PCFCCAUTH?
>
> But if you don't have an AT command port, then I guess we would have to
> figure out how to enable that first.
do i have to have a physical serial port or is there a way to send AT 
commands via the terminal using some emulation or something?
> And I really don't have much
> experience with Sierra modems from before the MDM9x00 generation (MC7710
> etc).  There is a Sierra specific QMI command for setting USB
> composition, which might work. But then again, it might not...
>
>>>    qmicli -p -d /dev/cdc-wdm0 --device-open-mbim  --dms-list-stored-images
>> [/dev/cdc-wdm0] Device list of stored images retrieved:
>>
>>      [0] Type:    'modem'
>>          Maximum: '6'
>>
>>          >>>>>>>>>> [CURRENT] <<<<<<<<<<
>>          [modem0]
>>          Unique ID: '8A:6F:98:CD:F2:68:3A:45:97:E0:E8:F2:90:03:1B:F1'
>>          Build ID:      'D3200-SCAUTNZ-331425XN02'
>>          Storage index: '0'
>>          Failure count: '0'
>>
>
> Don't know if that got us (or me at least) any further.  It looks sane,
> but what do I know...
>
>
> Bjørn
>
looks like i have firmware anyways.

thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/modemmanager-devel/attachments/20160817/068a6126/attachment-0001.html>