Hi:

I have a Broadcom 4322 card and I have compiled and loaded the Broadcom 802.11 Linux STA driver. I pretty much followed what is in the "README" file with the source code and what's given in the article at

http://djkaos.wordpress.com/2008/10/...ux-sta-driver/

There was a a couple of changes I made with the part in which the article describes adding "modprobe" commands to a configuration file in order to connect at boot up:

"5)Add following Lines to /etc/rc.local (in openSuse /etc/rc/rc.d/boot.local)

modprobe wl"

One change was because there is no "/etc/rc/rc.d/boot.local" file in OpenSuSE since there is no "/etc/rc" location but there is a "/etc/rc.d/boot.local" file and that is where I added the "modprobe" commands, Probably, a typo in the article I assume.

The other was that I added another "modprobe" command for the "lib80211" module so that I ended up appending the following two lines to the "boot.local" file:

modprobe lib80211
modprobe wl

I did that the that was the only way to get the "wl" module to load at all (I believe the lib provides encryption functionality for "WEP" security that I use in my network.)

Now everything is set up using the "ifup" method along with the appropriate SSID and WEP key. The problem is, when I boot up, I do not get an immediate connection without some kind of "activity" like any one of the following actions:

1 Open "Network Settings" in YaST2.
2 Re-enable the network service via "System Services (Runlevel)" in YaST2
3 Execute "depmod -a"
4 Open "Hardware Information" in YaST2.

and probably more.

When I run "ifconfig" before I do any one of the preceding actions, the only device that shows up is "lo", the "loopback" device. After I execute one of those actions, "eth1" shows up and this is the wireless device. What's more, the machine connects, gets an IP from DHCP and everything is rosy.

When I run "iwconfig" at any time, it shows the "eth1" device is configured even when I initially boot up.

I thought at first maybe is some timing issue and that my machine would connect after some elapsed time period. But that does not appear to be true. That machine can sit for how long whatsoever and remain not connected. Trying to ping my router results in an error message saying there is available network. But once I "nudge" the machine, I am OK.

Any ideas about what might be the problem? I have been at this obsessively for the past 2 days without any luck.

Thanks in advance.

ModalLogic