I had this working last trip, but I can't get the wireless to link up now.
I get the correct driver installed, it will search for a wireless network, come up with an address, but will not connect. I am running over the same computer now with Windows using the wireless connection. Is there a step by step setup for wirless around? I tried to search the forum but didn't find anything I could use.

Linux distro = Puppy 3.01
Wireless adaptor/driver BCM43XX
after getting an OK from setup to get an IP id ckick Auto DHCP and it fails.
Do a TEST ETH1 and it passes, go to Auto DHCP and it fails, everytime.

Go back to find another network (Scan) and I get "no network avaiable". Relaod the previously saved network and it will pass to get IP. Then fail.

It's like I'm forgetting a step. I feel like there is something simple I am missing.

with the bcm43xx drivers your mileage may vary, or rather some cards will work fine and others just wont. I have the 43xx drivers on a 4318 broadcom card and with my current kernel version (2.6.22.8) the wireless works great, but on an older kernel version (2.6.18) i could only connect using no encrytion and when i was very close to the access point. So which kernel are you using? and is your access point encrypted? (wep sometimes worked depending on distance to ap, but wpa just wouldn't work)

When I had the older kernel version I used ndiswrapper to connect to encrypted access points, thats something to consider.

<edit> if you post the output of "dmesg | grep bcm" (without the quotes) it may help someone to determine what the actual problem is.

I remember my problem with the older card having these symptoms though and in dmesg it would just keep trying to associate (or authenticate - i forget) but would never get an address.

Thanks for answering, here's the output of dmesg | grep bcm

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: Analog: 4, Type 2, Revision 8
bcm43xx: Detected Radio: ID: 2205017f (Manuf: 17f Ver: 2050 Rev: 2)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
unionfs: do delay copyup of "bcm43xx.ko"

Hope you can see something ("Radio turned off"?)

I'll have to reboot to find the Kernel version.

Do you have the firmware installed for your card? If not then the readio will not turn on. Google bcm43xx-fwcutter for a tool to extract the firmware from windows drivers. Unfortunately i've never used puppy so I don't know if it comes with bcm firmware, it's relatively easy to extract though when i'm missing firmware it tells me in dmesg cant load XXX.fw. Thats the only thing I can think of, though I'm a relative newbie

OK, I give up. I am at a new location so, just for grins, I tired to log on in Puppy. Guess what, I'm not only on but it's a great connection.

I did exactly what I did at the last site, it just worked here??? You tell me!

So I have everything I need to get the connection, it just works in some places and not in others. OK, I'll live with it.