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

[Isaac Raway]

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.

>
> 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.

IJR

[1]https://lists.ubuntu.com/archives/kernel-team/2014-June/043358.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/libqmi-devel/attachments/20150126/2cf20621/attachment.html>