All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Messer <andi@bastelmap.de>
To: linux-wireless@vger.kernel.org
Subject: Re: rt73usb not working since linux 3.4
Date: Tue, 24 Jul 2012 19:33:34 +0200	[thread overview]
Message-ID: <1994279.EoVfTdb8RL@hermes> (raw)
In-Reply-To: <20120626171835.GB32503@tuxdriver.com>

[-- Attachment #1: Type: text/plain, Size: 1768 bytes --]

Hello Again,

Am Dienstag, 26. Juni 2012, 13:18:35 schrieb John W. Linville:
> On Tue, Jun 26, 2012 at 06:03:56PM +0200, Andreas Messer wrote:
> > Dear all,
> > 
> > updating my pc from linux kernel 3.3 to linux kernel 3.4 broke my wlan.
> > I'm
> > using rt2571 based wlan module from qcom: LR802UKG, which is wired to an
> > internal usb port of my media center pc. The rfkill switch is hardwired to
> > make wlan active all the time. This setup is (almost) properly working
> > since about three years now. (If i ignore the occasional
> > vendor_request_error things)
> > The wlan device now refuses to go
> > online, saying that the kill switch is active, which of course can not be
> > as it is working with linux kernel 3.3.
> > [...]
> > So, what can I do to track down the problem?
> 
> Andreas,
> 
> Hmmm...well, perhaps you can start by doing a git bisect to narrow-down
> the commit that started this problem for you?  It may take serveral
> iterations, if you can only narrow it down to 3.3 working and 3.4 not
> working.  But, at least that should point us in the right direction.
> 
> John

first of all, sorry for the long delay. After some hours of compiling and 
checking, I have found the following things: The problem is introduced 
somewhere between v3.3.8 and v3.4, actually the commit 7e29629 already shows 
the problem. So range is v3.3.8...7e29629. I thing there is something wrong 
with initialization of the chip because of the following behaviour: If I boot 
from power-off into 7e29629 the kill switch reports to be in state 1 
(/sys/../hard = 1). If I first boot into 3.3.8 and afterwards re-boot into 
7e29629, the kill switch reports to be in state 0 and the WLAN connection 
builds up properly.
Hope that helps somehow.

Cheers,
Andreas

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2012-07-24 17:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 16:03 rt73usb not working since linux 3.4 Andreas Messer
2012-06-26 17:18 ` John W. Linville
2012-07-24 17:33   ` Andreas Messer [this message]
2012-08-23 18:51     ` Andreas Messer
2012-08-26 18:22       ` Gertjan van Wingerde
2012-08-27 16:33         ` Andreas Messer
2012-08-27 17:26           ` Gertjan van Wingerde
2012-07-11 16:50 ` Olive
2012-07-14 20:28   ` Olive

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=1994279.EoVfTdb8RL@hermes \
    --to=andi@bastelmap.de \
    --cc=linux-wireless@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.