From: "John W. Linville" <linville@tuxdriver.com>
To: Dennis Nezic <dennisn@dennisn.dyndns.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: ipw2200 antenna selection
Date: Wed, 31 Aug 2011 09:38:39 -0400 [thread overview]
Message-ID: <20110831133838.GA2474@tuxdriver.com> (raw)
In-Reply-To: <20110830215135.db381ecf.dennisn@dennisn.dyndns.org>
On Tue, Aug 30, 2011 at 09:51:35PM -0400, Dennis Nezic wrote:
> My ipw2200 pcie wifi card has 2 antennas... "Main" and "Aux". I think
> either the firmware or the kernel/module is overriding my explicit
> antenna module setting, after a while.
>
> I mentioned about it a few days ago,
> http://marc.info/?l=linux-wireless&m=131448481319374&w=2
> although I'm still seeing the problem (even after physically
> disconnecting the Aux antenna/wire. (Even after disconnecting it, I
> think it is still able to receive the 30KB/s signal, and I think the
> card still switches to it eventually, against my wishes.))
Dennis,
I'm sorry you haven't received any replies until now. The truth
is that the ipw2200 hardware is a bit old, and has more-or-less
been abandoned by the manufacturer and the original driver authors.
Worse, no hardware specification is available and even if it were
then likely no firmware changes would be possible.
You mentioned that one of your antenna lines is cut. Is it possible
that you might repair that antenna?
Would it be possible for you to try using a much older kernel?
If you can find a point where the problem you are seeing does not
exist, then we may be able to pinpoint a change that is contributing
to the issue you are seeing. Beyond that, I'm not sure what else we
might do to help.
Thanks,
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2011-08-31 13:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 1:51 ipw2200 antenna selection Dennis Nezic
2011-08-31 13:38 ` John W. Linville [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=20110831133838.GA2474@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=dennisn@dennisn.dyndns.org \
--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 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).