A history report:
For anyone who doesn't know, the Texas Instruments acx100 chipset, primarily present in the D-Link 520+, 650+, and other D-Link cards - pcmcia or pci - with the '+' designation. This chipset is notoriously unsupported by Texas Instruments on the Linux platform. D-Link isn't helping this all that much either.
There is a binary driver that was leaked near the initial release of the chipset, but it's slow and breaks easily.
There is also the acx100 project. This is an open source project to design a fully functioning driver (modules) for the chipset via reverse-engineering and I/O testing.
I tried the leaked binary driver when I first installed RH9 and it did NOT work. The card would initialize and activate as eth1, but it wouldn't associate with the wireless network with some kind of I/O error...basically the computer registered the hardware with the kernel but the communication's layer was distorted.
I tried to compile and install my own acx100 modules per instructions from houseofcraig.com. It displayed no errors with the hardware or the association, but there still was no talking to the internet.
After a few months of just using a hardwire connection, I came across the DAG apt-rpm repository and saw the acx100 kernel-module precompiled, ready to go...so I gave it a shot and it worked.
Now, I decided to switch to Fedora - redhat discontinuing their GPL distro and all, decided it was time to move on, as everyone else has. I'm very happy with the OS. Some priviledge diff's need some getting used to, but altogether a very comfortable OS.
I got apt-rpm installed and running, at least as fine as synaptic will let it, installed the acx100 modules, depmod -a. Everything's fine. I plug the card in...nothing. modprobe acx100, insmod error. I'm doing a little more investigation, but, anyone have any idea why this would work in RedHat and not Fedora?