Broadcom 802.11g linuxant redhat 9 help
 

Hello All,

I have an emachines M5312 laptop with the Broadcom 54g 802.11g wireless card.

I have installed both Mandrake 9.2 and Redhat 9.0 on the machine with the linuxant driverloader (windows driver wrapper) and cannot get my card to connect. I am frustrated because I have seen that at least a couple other people have managed to accomplish this with what appears to be little fanfare.

My wireless card in my laptop can detect the WAP, but cannot get an IP address from DHCP, and will not work with a static address either. If I try DHCP, I get the error "Determining IP Address... Failed". If I set a static address, it loads the driver and brings up the interface, but I cannot ping my WAP.

If I do iwconfig, it returns the driver with the ESSID of my WAP and tx rate, etc.

I believe I've followed all instructions from linuxant on how to load the drivers and both Mandrake and Redhat recognize the driver.

Ok, this is the setup:

* linuxant driverloader for athlon from linuxant website
* 30 day free trial license from linuxant
* broadcom bcmwl5.inf and bcmwl5.sys windows
drivers from c:\windows\system32
* Netgear 802.11b router/WAP

Ok, first I installed the linuxant drivers. Next, I used the web configurator to configure the driver, including uploading the windows drivers and entering the license information.

After that, I went into gnome networking configurator and added a 'new' wireless interface, using the driverloader (eth1), configured to 'managed' mode with 'auto' ESSID and channel 1, 11MBS.

I also tried 'auto' mode and also tried setting the ESSID to the same as my WAP and also tried manually setting the IP address.

No luck on any of it.

Am I doing anything wrong? Am I missing something? I feel frustrated because I have this fear that its something extremely obvious, but it is escaping me if it is.

Oh, also, the card and drivers work perfect on Windows XP and also, the WAP does not have WEP enabled.

Thanks very much for ANY help!!!

George :)

Make sure you're entering a 0x before your WEP Keys if they're in hex..

ie 0xABEDEDED not ABEDEDED

Thanks, Lewt. I don't believe I have WEP enabled. At least, it's not on the WAP. Hmm, maybe Linux is trying to use WEP... That would certainly be a problem if it were. I'll check it out, at least, thanks for the help!

George :)