From: "Bjørn Mork" <bjorn@mork.no>
To: Oliver Neukum <oliver@neukum.org>
Cc: Dan Williams <dcbw@redhat.com>, netdev@vger.kernel.org
Subject: Re: MBIM device refusing to be enabled
Date: Wed, 09 Oct 2013 13:09:08 +0200 [thread overview]
Message-ID: <87d2nezoob.fsf@nemi.mork.no> (raw)
In-Reply-To: <87hacqzqi0.fsf@nemi.mork.no> ("Bjørn Mork"'s message of "Wed, 09 Oct 2013 12:29:43 +0200")
Bjørn Mork <bjorn@mork.no> writes:
> Sorry, that was nonsense. rfkill would only affect the HwRadioState.
Turns out I wasn't completely off anyway... by pure luck ;-)
> Looking at the commands following this message, it appears that MM
> correctly attempts to enable the SwRadioState but fails. I don't know
> why.
Is the device by any chance a Sierra Wireless device?
I was able to recreate the behaviour you see after experimenting a bit
with my MC7710. This device (and I assume most other MBIM capable
Sierra Wireless minicards) can be configured to enter low power mode on
rfkill (W_DISABLE asserted), instead of powering off. Sony for example
are known to configure the built-in Sierra devices in this mode.
When low power mode is forced by rfkill this way, the firmware
erroneously[1] claims
HwRadioState: on
SwRadioState: off
Any attempt to change this software state using MBIM will fail with
MBIM_STATUS_FAILURE. Exactly like your log shows. The modem must be
enabled using rfkill before MM can use it. Changing the firmware
behaviour will not do any good - it will just cause the modem to power
off and disappear instead.
So I would start looking at rfkill after all. There are often problems
with these platform drivers and newer laptops, due to the lack of
documentation from the vendors. Here's one (now fixed) example:
https://bugzilla.kernel.org/show_bug.cgi?id=47751
[1] Section 10.5.3.6 of the MBIM v1.0 spec says
"HwRadioState: The state of the W_DISABLE switch [..]
SwRadioState: Software configured radio state."
Bjørn
next prev parent reply other threads:[~2013-10-09 11:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 8:59 MBIM device refusing to be enabled Oliver Neukum
2013-10-09 10:05 ` Bjørn Mork
2013-10-09 10:29 ` Bjørn Mork
2013-10-09 11:09 ` Bjørn Mork [this message]
2013-10-09 11:22 ` Oliver Neukum
2013-10-09 13:31 ` Dan Williams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d2nezoob.fsf@nemi.mork.no \
--to=bjorn@mork.no \
--cc=dcbw@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=oliver@neukum.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).