lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d2nezoob.fsf@nemi.mork.no>
Date:	Wed, 09 Oct 2013 13:09:08 +0200
From:	Bjørn Mork <bjorn@...k.no>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Dan Williams <dcbw@...hat.com>, netdev@...r.kernel.org
Subject: Re: MBIM device refusing to be enabled

Bjørn Mork <bjorn@...k.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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ