broadcom air force x86_64

Lenard · 01-04-2006, 02:39 PM

It's not the permissions, it's the file sizes;

480256 Dec 02 2004 BCMWL564.SYS
467456 May 12 2005 BCMWL564.SYS

superbnerb · 01-04-2006, 07:22 PM

Quote:

Originally Posted by drj000

I had previously tried the driver that Lenard suggest, and with it ndiswrapper -l gave me

Code:

bcmwl5 driver present

but it didn't say hardware present. I found another generic 64-bit Broadcom driver at Linuxant, called netbc564, which included the same BCMWL564.SYS.
Anyway, ndiswrapper -l with that one gave me both driver present, and hardware present.

if it says hardware present, then you got something man.

go back to the driver that gave you this message (hardware present) and type this for me

Code:

iwlist wlan0 scan

you should see your AP... if it says NO (i forget the error, paste what

Code:

iwconfig

says please.

lastly if all else fails, try this driver, it worked on my compaq, and i know it sounds weird but try it.here

drj000 · 02-05-2006, 12:48 AM

In case anyone else is still having this problem, I figured I'd tell about how I finally got it working, sort of.

It turns out that it mostly works, but not entirely. I disabled WEP on my AP, and lo and behold, it works. This, of course, creates a security problem, but I solved that by enabling MAC filtering on my AP. Now, it works just fine, and hopefully, the Open Source Broadcom Linux driver at http://bcm43xx.berlios.de/ will have a stable release soon (I think they've got WEP working), and I won't have to use proprietary Windows drivers anymore.