I just couldn't sleep tonight, so I took care of a project that I've been putting off for about a month or so, which is getting my Belkin USB wireless thingy to work with Linux (CentOS 4.4 running on a Dell Inspiron 2650). The project received a bit higher priority due to my Lombard Powerbook finally starting to completely flake out (now it will only boot once in a blue moon.) I think the ole' PowerBook's PMU battery is shot.
The model I have is an F5D7050, which corresponds to version 4.000 of this particular Belkin model. It is based on a ZyDas 1211B chipset. There are a couple of drivers for this unit, and I suppose that ndiswrapper can be used as well, but the good news is that this module is now included in the vanilla Linux kernel source as of 126.96.36.199. The bad news is that this module doesn't include too many supported USB id codes, so if you just compile it and go, your usb stick stands a good chance of just plain not working (it happened to me).
If this is the case for you, check and see if your usb id is included in the "zd_usb.c" file. (from your /usr/src/linux-version directory, run a "find ./ -name zd_usb.c" to find it.) Take a look at that file, and compare the usb id's listed within it to what you have (you can figure out what you have by plugging in your USB adapter and running "lsusb" as root).
If you made changes, rebuild the module and reload if neccessary. Run an iwconfig and you should probably see something. The bundled in kernel module likes to confiure itself as an ethernet device (i.e. eth1 as opposed to the semi-standard wlan0 or wlan1 type device alias). I just rolled with it, and set up my device alias appropriately in /etc/modprobe.conf.
I have noticed one "gotcha" so far; if you have the adapter plugged in, and you're booting up, kudzu (automatic hardware detection) will hang until you unplug it.
Be sure to do a "iwconfig eth1 up" before you use the device....otherwise no subsequent iwconfig commands will work and you'll be left confused.
Later, I'll set up config files, so that CentOS knows how to bring up the device correctly.