(CCing bcm43xx-dev.)
Could you post the dmesg output when this happens? (Enable debugging
in b43 before taking the log.)
2009/9/2 Brian J. Mc Hugh bjmch...@aya.yale.edu:
Hi Gábor,
I seem to remember you explaining there was a bluetooth problem and it
couldn't coexist. Is that right?
Brian
On Wed, Sep 2, 2009 at 11:57 PM, Brian J. Mc Hughbjmch...@aya.yale.edu wrote:
Hi Gábor and Broadcom,
In essense, my card seems to be receiving signal but transmitting none.
I was appreciate your help,
Thanks,
Brian
Here are the diagnostics;
#uname -r
2.6.26-2-686
#dmesg | grep b43
2009/9/3 Brian J. Mc Hugh bjmch...@aya.yale.edu:
I went in the file /var/log/dmesg and didn't find dhclient.
Does that signify failure?
You don't need to find dhclient in dmesg - the question is, what shows
up in dmesg after ifup calls dhclient?
About the Windows machine problem - try the
Brian J. Mc Hugh wrote:
Hi Larry,
I just did a clean install and have the same problem you help me solve
before.
DIdn't you recommend that I issue:
sudo modprobe b43?
I don't remember the circumstances; however, your driver b43 is
already loaded and this command would do nothing.
On Thu, Sep 3, 2009 at 1:55 AM, Alex Elsayedeternal...@gmail.com wrote:
I just recently got a new laptop with an Intel 5350, which means my
4328 [PCI-ID] (4321 official Broadcom designation) is not in use any
longer. I am in the Seattle area, but can send it by post if needed.
I just recently got a new laptop with an Intel 5350, which means my
4328 [PCI-ID] (4321 official Broadcom designation) is not in use any
longer. I am in the Seattle area, but can send it by post if needed.
___
Bcm43xx-dev mailing list
On Thu, Sep 3, 2009 at 2:37 AM, Brian J. Mc Hughbjmch...@aya.yale.edu wrote:
Hi Larry and Gabor,
Here is the file. Sorry about contacting both of you independently
Brian
Hmm, this SPROM has the BT coexistence bit unset - in that case, BT is
not the reason behind the bug.
Do you know the
2009/9/3 Brian J. Mc Hugh bjmch...@aya.yale.edu:
I use Debian. Etch was 2.18. Lenny is 2.26.
But I did already issue the commands to disable the bluetooth, i.e.,
#sudo modprobe -rv b43
#sudo modprobe -v b43 btcoex=0
#sudo /etc/init.d/networking restart
Unfortunately,
Brian J. Mc Hugh wrote:
I use Debian. Etch was 2.18. Lenny is 2.26.
But I did already issue the commands to disable the bluetooth, i.e.,
#sudo modprobe -rv b43
#sudo modprobe -v b43 btcoex=0
#sudo /etc/init.d/networking restart
Unfortunately, I still don't have
