QMI protocol error (3): 'Internal' when running dms-set-operating-mode

[Isaac Raway]

On Mon, Jan 26, 2015, at 09:45 AM, Isaac Raway wrote:
>
> On Mon, Jan 12, 2015, at 09:22 AM, Dan Williams wrote:
>> On Mon, 2015-01-12 at 07:15 -0600, Isaac Raway wrote:
>>> On Wed, Jan 7, 2015, at 09:55 AM, Dan Williams wrote:
>>>> On Tue, 2014-12-30 at 11:37 -0600, Isaac Raway wrote:
>>>>> One interesting note, this card works perfectly if I boot into
>>>>> Windows from a USB drive (Windows was banished from the internal
>>>>> SSD on purchase), connect via Dell's "SkyLight" program, then
>>>>> warm-boot back to Fedora 20. In that case, the initial power mode
>>>>> read from dms-get-operating-mode is "online" rather than
>>>>> "low-power".
>>>>
>>>> This smells like rfkill driver issues. What do you get for 'rfkill
>>>> list' run in a terminal under Linux from cold-boot, and does that
>>>> change if you boot windows, then warm-boot to Linux?
>>>
>>> Cold boot and wam boot both seem to respond with the same results
>>> for rfkill list and do not seem to mention the WWAN card. Although
>>> it is interesting that the ID numbers(?) are different and the order
>>> has changed. Not sure if that is significant.
>>>
>>> Cold boot:
>>>
>>> 1: phy0: Wireless LAN Soft blocked: no Hard blocked: no
>>> 2: hci0: Bluetooth Soft blocked: no Hard blocked: no
>>>
>>>
>>> Warm boot:
>>>
>>> : hci0: Bluetooth Soft blocked: no Hard blocked: no
>>> 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no
>>
>> Is this a Dell 5570 (Sierra 8805)? Also, which specific Windows
>> kernel version is this machine using?
>
> I believe it is a "Dell 5808 Gobi(TM) 4G LTE Mobile Broadband" which
> appears to actually be a Sierra MC7750 from what I've found online[1]?
> The lsusb output is:
>
> Bus 002 Device 003: ID 413c:81a8 Dell Computer Corp.
>
> The string obviously isn't terribly useful in identifying it.
>
> Not sure about the Windows kernel - don't have the windows USB disk
> with me at the moment. It would be the latest patched Windows 7 Pro
> kernel though.

Actually it looks like it is identifying as a MC7355. Here is some
additional output that I was able to get via AT commands (I don't really
know much about this so I'm not sure if this is useful information):

ATI Manufacturer: Sierra Wireless, Incorporated Model: MC7355 Revision:
SWI9X15C_05.05.39.00 r22582 carmd-fwbuild1 2014/06/14 13:21:08 MEID:
35619505057226 ESN: 12802831533, 802B34AD IMEI: 356195050572260 IMEI SV:
14 FSN: ER422300060411 +GCAP: +CGSM


OK AT!CUSTOM? !CUSTOM: GPSENABLE 0x01 FASTENUMEN 0x01 GPSSEL 0x01
NMEAENABLE 0x01 UBISTENABLE 0x01 GOBIIMEN 0x01 USBSERIALENABLE 0x02


OK AT+CGREG? +CGREG: 2,0

OK AT+CPIN? +CPIN: READY

OK AT+COPS? +COPS: 0

I had set the CGREG mode to 2. The second value there seems to indicate
that the modem is not looking for a network -- but I cannot find out how
to switch it into a mode where it will actually look for the network.

IJR

>
>>
>> If it is a Sierra 8805, can you run 'minicom -D /dev/ttyUSBx' (where
>> 'x' is one of the serial ports exposed by the modem, if any) and then
>> run "at!pcinfo". Try all the ports, one of them may respond even
>> though the modem is usually driven by QMI.
>
> Here's what I get from the port that I had found before:
>
> at!pcinfo ERROR
>
> This is strange, I thought this command had worked fine in the past.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20150126/309cb24b/attachment.html>