Fwd: Kernel 2.6.20 and bcm43xx driver
- To: debian-laptop <debian-laptop@lists.debian.org>
- Subject: Fwd: Kernel 2.6.20 and bcm43xx driver
- From: "Mr Alk3" <mr.alk3@gmail.com>
- Date: Thu, 1 Mar 2007 01:02:07 -0600
- Message-id: <[🔎] bf0bf82d0702282302s7c0c1445u2d22c4930ba690e1@mail.gmail.com>
- In-reply-to: <bf0bf82d0702282041t24e3d96ayd4e1c4851bda0814@mail.gmail.com>
- References: <bf0bf82d0702281408i476ff93cw585e3121bf4e86c8@mail.gmail.com> <20070228221220.GA19714@bnl.gov> <bf0bf82d0702281415p4b013205p7e9d201c34e3bbdc@mail.gmail.com> <bf0bf82d0702281436t627e22b9p2bc9090091e3d32e@mail.gmail.com> <bf0bf82d0702282041t24e3d96ayd4e1c4851bda0814@mail.gmail.com>
---------- Forwarded message ----------
From: Mr Alk3 <mr.alk3@gmail.com>
Date: Feb 28, 2007 10:41 PM
Subject: Re: Kernel 2.6.20 and bcm43xx driver
To: Tim Sailer <sailer@bnl.gov>
Does anyone have any idea on how to solve my problem? I really dont want to have to rename my AP essid... Once this is worked out I will have a fully functional Broadcom Nic!
On 2/28/07,
Mr Alk3 <mr.alk3@gmail.com> wrote:
I did what was suggested and checked out my BIOS and my WiFI was already enabled. BTW. I have a Dell Inspiron E1505 running Debian Etch. I have a 2.6.20 custom kernel with the bcm43xx module support. As far as I can tell, when I boot the module is loaded and the output of iwconfig only shows eth0 and lo interfaces with now wireless extensions. When I do a 'modporbe bcm43xx' the wlan0 interfaces appears and seems to work. I am confused though, because when I do and 'iwconfig wlan0 essid <ap name>' it doesn't work. Here is the output when I tried to configure iwconfig essid:
+++++++++++++++++
# iwconfig wlan0 essid "byteme"
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11b/g ESSID:"b" Nickname:"Broadcom 4311"
Mode:Managed Access Point: Invalid
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
+++++++++++++++++
It only lets me use 5 characters and lowercase for my AP name. My ap essid is actually "ByteMe"
+++++++++++++++++
# iwconfig wlan0 essid "bytem"
# iwconfig
lo no wireless extensions.
eth0 no wireless extensions.
wlan0 IEEE 802.11b/g ESSID:"bytem" Nickname:"Broadcom 4311"
Mode:Managed Access Point: Invalid
RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=0/100 Signal level=-256 dBm Noise level=-256 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
+++++++++++++++++
I dont understand. do I need to rename my AP essid to lesser/lowercase characters?
Thanks again!
Alk3
On 2/28/07, Mr Alk3 <mr.alk3@gmail.com> wrote:
It works fine with ndiswrapper and I don't have to reboot to the BIOS to turn it on. I also don't have Windows on this laptop... I will check out the BIOS, though.
On 2/28/07,
Tim Sailer <sailer@bnl.gov> wrote:
On Wed, Feb 28, 2007 at 04:08:56PM -0600, Mr Alk3 wrote:
> If I do a 'modprobe bcm43xx' as root, is that all I need to do to get my
> 'ethX' interface to show up?
It should load the needed modules upon boot.
> bcm43xx: Radio turned off
> bcm43xx: Radio turned off
Either boot into windows and hit ctrl-alt-f2 (I think, or f1) to
turn it on, or go into the BIOS and turn it on. Reboot back into
Linux, you should see it, or other errors in dmesg that would help
explain the problem.
Tim
--
Tim Sailer <sailer@bnl.gov>
DoE Intelligence and Counterintelligence - Cyber Division
Northeast Regional Counterintelligence Office
Brookhaven National Laboratory (631) 344-3001
Reply to: