From: David Gibson <hermes@gibson.dropbear.id.au>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jt@hpl.hp.com, Linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: Orinoco Wireless driver bugs in 2.5.17
Date: Thu, 23 May 2002 11:25:17 +1000 [thread overview]
Message-ID: <20020523012517.GM1001@zax> (raw)
In-Reply-To: <20020522103834.B10921@bougret.hpl.hp.com> <E17Aams-0002Ue-00@the-village.bc.nu>
On Wed, May 22, 2002 at 07:24:37PM +0100, Alan Cox wrote:
> > Alan,
> > Could you be more precise and point out which kernel start
> > failing ?
>
> Certainly in 2.4.18 (and I've seen a pile of other similar reports).
Ah, bugger.
> > If I remember properly my debug session with Alan (that was a
> > long while ago), the COR reset was screwing up the firmware (well, how
> > many time did I told you to not make it mandatory ?).
>
> Long time ago -its been behaving well until fairly recently
>
> > Alan has an old Compaq card (the Intersil PrismII variety, not
> > the new Lucent one) and his firmware is probably not very fresh.
>
> Oldish firmware definitely. The newer driver finds the card registers
> it but fails on all tx/rx and reports no signal and noise of
> 130/150 or so (as opposed to db). Flipping back to the older kernel it
> works happily.
The signal/noise bit is probably a red herring. We have problems with
the reporting of this, but it's mostly cosmetic. I seem to have
confusing and contradictory information about how to interpret the
values the firmware reports.
> Any specific info/debug/traces that would help ?
Specific error messages on Tx/Rx and also the firmware version as
reported on module load would be very helpful.
--
David Gibson | For every complex problem there is a
david@gibson.dropbear.id.au | solution which is simple, neat and
| wrong. -- H.L. Mencken
http://www.ozlabs.org/people/dgibson
next prev parent reply other threads:[~2002-05-23 1:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 17:38 Orinoco Wireless driver bugs in 2.5.17 Jean Tourrilhes
2002-05-22 18:24 ` Alan Cox
2002-05-22 18:17 ` Jean Tourrilhes
2002-05-23 1:27 ` David Gibson
2002-05-23 1:25 ` David Gibson [this message]
2002-05-29 18:40 ` Alan Cox
2002-05-29 17:42 ` Jean Tourrilhes
2002-06-02 23:38 ` David Gibson
2002-06-03 1:08 ` Alan Cox
[not found] <385229951@toto.iv>
2002-05-27 9:27 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2002-05-23 3:21 Erik McKee
2002-05-22 0:06 Peter Chubb
2002-05-22 1:53 ` David Gibson
2002-05-22 13:16 ` Alan Cox
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=20020523012517.GM1001@zax \
--to=hermes@gibson.dropbear.id.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@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.