[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Kernel 2.6.20 and bcm43xx driver

Mr Alk3 wrote:

Here is the output of 'lspci -v' for the NIC
=====================
0b:00.0 Network controller: Broadcom Corporation Dell Wireless 1390 WLAN
Mini-PCI Card (rev 01)
       Subsystem: Dell Unknown device 0007
       Flags: bus master, fast devsel, latency 0, IRQ 169
       Memory at efdfc000 (32-bit, non-prefetchable) [size=16K]
       Capabilities: [40] Power Management version 2
       Capabilities: [58] Message Signalled Interrupts: Mask- 64bit-
Queue=0/0 Enable-
       Capabilities: [d0] Express Legacy Endpoint IRQ 0
       Capabilities: [100] Advanced Error Reporting
       Capabilities: [13c] Virtual Channel
=====================
I have never used the bcm43xx module to run a broadcom chipset wireless card 
and have a few quick questions:

If I do a 'modprobe bcm43xx' as root, is that all I need to do to get my
'ethX' interface to show up?

Is there anymore configuration needed?

At boot up I get this when the wireless card is found:
=====================

bcm43xx driver
bcm43xx: Chip ID 0x4311, rev 0x1
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243
bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243
bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243
bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: set security called, .active_key = 0, .level = 1, .enabled = 1,
.encrypt = 1, .auth_mode = 0
bcm43xx: PHY connected
bcm43xx driver
bcm43xx driver
bcm43xx driver
bcm43xx: Chip ID 0x4311, rev 0x1
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0x11, vendor 0x4243
bcm43xx: Core 1: ID 0x812, rev 0xa, vendor 0x4243
bcm43xx: Core 2: ID 0x817, rev 0x3, vendor 0x4243
bcm43xx: Core 3: ID 0x820, rev 0x1, vendor 0x4243
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 4, Type 2, Revision 8
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: set security called, .active_key = 0, .level = 1, .enabled = 1,
.encrypt = 1, .auth_mode = 0
bcm43xx: PHY connected
bcm43xx: Microcode rev 0x13f, pl 0x66 (2005-10-15  22:46:19)
bcm43xx: set security called, .active_key = 0, .level = 1, .enabled = 1,
.encrypt = 1, .auth_mode = 0
bcm43xx: Microcode rev 0x13f, pl 0x66 (2005-10-15  22:46:19)
bcm43xx: Microcode rev 0x13f, pl 0x66 (2005-10-15  22:46:19)
bcm43xx: Microcode rev 0x13f, pl 0x66 (2005-10-15  22:46:19)
bcm43xx: Microcode rev 0x13f, pl 0x66 (2005-10-15  22:46:19)


Does 'Radio turned off' mean I need to do something more to get the card
active?

I have the firmware, the NIC doesn't show up as 'ethX'.  'wlan0 shows up
even without ndiswrapper installed. So, I tried to connect to an AP and I try to enter the essid and its a no go, with wlan0. My AP name is "ByteMe" 
and I can only enter in lowercase and up to 5 characters, so: "bytem"

What is my problem? The driver is loaded and the hardware is recognized,
what else is there?
I just joined this mailing list and do not have the time to search for this 
topic, sorry if this has already been answered.

Thanks in advance!

Alk3
I've seen the "radio off" message in dmesg on my system too when I was playing with the bcm43xx module. For some reason that module starts, then stops, and then restarts the radio. If you used fwcutter-bcm43xx to extract the software it should have placed the firmware in the correct location. As to your problem entering the ssid I'm not sure where you are doing this. I always configure my network connections in /etc/network/interfaces, and if I am going to use a secured AP, in /etc/wpa_supplicant/wpa_supplicant.conf.
You can find the documentation for configuring wpa_supplicant in /usr/share/doc/wpasupplicant. There are example configurations given there.
Reply to: