From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Ronald <ronald645@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: [BUG?] b43: Wireless signal lowers when increasing sound
Date: Mon, 18 Feb 2008 20:07:19 +0100 [thread overview]
Message-ID: <200802182007.19859.mb@bu3sch.de> (raw)
In-Reply-To: <20080218153511.GB3098@tuxdriver.com>
On Monday 18 February 2008 16:35:11 John W. Linville wrote:
> On Mon, Feb 18, 2008 at 08:23:35AM +0100, Ronald wrote:
> > hey,
> >
> > I'm currently using the b43 driver for my BCM4311 chipset. The driver works
> > extremely well. It is the only option under Linux that supports WPA-AES
> > with wpa_supplicant :) (and it's more stable than wpa_supplicant). However,
> > I'm seeing some unexpected behaviour with the card and another chipset.
> > When I enable my soundcard (setting volume from 0 to > 0) the wireless
> > signal seems to drop completely (really funny to see my downloadspeeds go
> > up and down :) ). My question is, is this normal?
> >
> > However, I'm not sure if this is related to the b43 driver so don't flame
> > me ;)
>
> Very strange...my only guess would be EMI generated from your audio
> chipset and/or the speakers in your laptop.
>
> Is it really just the volume setting? I.E. if you "play" the audio
> but with the volume turned down does everything work fine? Does the
> performance continue to degrade as you increase the volume?
>
> Wierd...I'm not sure what we can do about this...
Heh, yeah. I guess you should buy an FCC rules compliant soundcard instead. ;)
This sounds like EMI.
--
Greetings Michael.
prev parent reply other threads:[~2008-02-18 19:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-18 7:23 [BUG?] b43: Wireless signal lowers when increasing sound Ronald
2008-02-18 7:25 ` Ronald
2008-02-18 15:35 ` John W. Linville
2008-02-18 19:07 ` Michael Buesch [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=200802182007.19859.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=ronald645@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).