From: "Rafał Miłecki" <zajec5@gmail.com>
To: b43-dev@lists.infradead.org
Subject: Degradation on b43 14e4:4315 ?
Date: Thu, 16 Jun 2011 11:22:00 +0200 [thread overview]
Message-ID: <BANLkTinurxCysuDOFp7WMbC488hVAvBiag@mail.gmail.com> (raw)
In-Reply-To: <4DF9BBCE.10702@snafu.de>
Hey,
2011/6/16 Oncaphillis <oncaphillis@snafu.de>:
> ?I'm using my b43 14e4:4315 on my acer notebook for quite a while now.
> I've started to use a wireless git-kernel and helped a bit in debugging
> initial problems with this device. Since the early Fedora 14 it seemed to
> work out of the box, but now when Fedora 14 moved to 2.6.35.12+ kernels
> I loose connections on heavy transfer.
Do you get something interesting from "dmesg | grep b43"?
> Where there developments during the 2.6.35.x developments which could
> explain such behaviour ?
Do you mean 2.6.35 was working fine and 2.6.35.12 already contains
regression? Were you using clean 2.6.35 earlier with success?
Did you/Fedora update firmware in /lib/firmware/b43 meanwhile?
--
Rafa?
next prev parent reply other threads:[~2011-06-16 9:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-16 8:16 Degradation on b43 14e4:4315 ? Oncaphillis
2011-06-16 9:22 ` Rafał Miłecki [this message]
2011-06-16 21:23 ` Oncaphillis
2011-06-16 22:08 ` Rafał Miłecki
2011-08-26 19:09 ` Rafał Miłecki
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=BANLkTinurxCysuDOFp7WMbC488hVAvBiag@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=b43-dev@lists.infradead.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).