Karanbir Singh wrote:
> Neal Becker wrote:
>
>> Jan 24 08:47:42 localhost kernel: "bcm43xx": Chip ID 0x4318, rev 0x2
>> Jan 24 08:47:42 localhost kernel: "bcm43xx": Number of cores: 4
>> Jan 24 08:47:42 localhost kernel: "bcm43xx": Core 0: ID 0x800, rev
0xd,
>> vendor 0x4243, enabled Jan 24 08:47:42 localhost kernel: "bcm43xx":
Core
>> 1: ID 0x812, rev 0x9, vendor 0x4243, disabled Jan 24 08:47:42 localhost
>> kernel: "bcm43xx": Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
Jan
>> 24 08:47:42 localhost kernel: "bcm43xx": Core 3: ID 0x80d, rev 0x7,
>> vendor 0x4243, enabled Jan 24 08:47:42 localhost kernel: "bcm43xx":
PHY
>> connected Jan 24 08:47:42 localhost kernel: "bcm43xx": Detected PHY:
>> Version: 3, Type 2, Revision 7
>> Jan 24 08:47:42 localhost kernel: "bcm43xx": Detected Radio: ID:
>> 8205017f (Manuf: 17f Ver: 2050 Rev: 8) Jan 24 08:47:42 localhost kernel:
>> "bcm43xx": Radio turned off Jan 24 08:47:42 localhost kernel:
"bcm43xx":
>> Radio turned off
>>
>>
>> WoW!!! Support for my bcm43xx!!! How do I turn it on?
>>
>>
> Support has been there for a few weeks now...
>
> take a look at
http://bcm43xx.berlios.de/ for details on how to get the
> device setup, you need to extract firmware, get it in the right place,
> setup the network config's and you *should* be good to go. I've had
> mixed results
>
>
Cool, but not ready for primetime. No encryption support.
I need to use ndiswrapper still. How do I prevent activation of bcm43xx? I
tried removing it from modprobe.conf, but it is still getting loaded, and
then ndiswrapper won't work.
WPA doesn't work but they are getting close. But WEP does work, if you
can call it encryption ;)
Bart
--
Bart Vanbrabant <bart.vanbrabant(a)zoeloelip.be>
PGP fingerprint: 093C BB84 17F6 3AA6 6D5E FC4F 84E1 FED1 E426 64D1