linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: David Smith <sidicas2@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Bug#684352: phy0/hp-wifi problems after kernel update from 2.6 to 3.2
Date: Tue, 02 Oct 2012 20:41:34 +0200	[thread overview]
Message-ID: <1349203294.10698.25.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <CA+7qwUksJykOMW1gOq4g+9kyv6R0Tb_fx9Lkuikss37V1-EPTg@mail.gmail.com> (sfid-20121002_203720_153266_D0AF5DDE)

On Wed, 2012-10-03 at 02:37 +0800, David Smith wrote:
> Trying again to send this to  linux-wireless@vger.kernel.org.
> Previously blocked because gmail put some html in there.
> 
> Please CC:  Anssi Hannula <anssi.hannula@iki.fi>,
> 684352@bugs.debian.org, sidicas2@gmail.com  on replies.

> Hello, I'm having a problem with my Intel 2200 wireless on my Compaq
> Presario V4000T (made by HP) that has started happening after I
> upgraded my kernel from 2.6 to 3.2.
> 
> Problem: phy0 wireless state is incorrect.

> After many many hours of searching, I discovered that running "rfkill
> unblock all" is able to remove the "Hard Block" from phy0 and put the
> wireless into this state:

Since you can fix it that way, it must be a bug with the HP platform
driver, so there's nothing we can do about it on the linux-wireless
list, sorry. You might want to bisect the platform drivers to see which
change caused this.

johannes


      reply	other threads:[~2012-10-02 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+7qwUkZiysOF-ocV+wyTGfnFyiGH6G=TiEB+ts89Pb=NvgpxA@mail.gmail.com>
2012-10-02 18:20 ` phy0/hp-wifi problems after kernel update from 2.6 to 3.2 Anssi Hannula
2012-10-02 18:37 ` Bug#684352: " David Smith
2012-10-02 18:41   ` Johannes Berg [this message]

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=1349203294.10698.25.camel@jlt4.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sidicas2@gmail.com \
    /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).