Acx111 Driver Not Working, How To Remove?

I'm trying to set up a Linksys WPC54Gv2 PCMCIA wireless card on suse 10, kernel 2.6.13-15.8-default. It was working beautifully on suse 9.3 but since switching to 10 I haven't been able to make it work. When I insert the card and do a "dmesg" I get this:
----------------------
PCI: Enabling device 0000:07:00.0 (0000 -> 0002)
ACPI: PCI Interrupt 0000:07:00.0[A] -> Link [LNKD] -> GSI 11 (level, low) -> IRQ 11
PCI: Setting latency timer of device 0000:07:00.0 to 64
ACPI: PCI interrupt for device 0000:07:00.0 disabled
acx_pci: probe of 0000:07:00.0 failed with error -5
----------------------
Much googling has suggested that the acx_pci driver is somehow “locking” the card so that no other drivers can claim it. There is no package with the word acx in the name or description so it's not as simple as just uninstalling an rpm. I have found acx_pci.ko in /lib/modules/2.6.13-15.8-default/source/net and references to it in modules.alias, modules.dep and modules.pcimap, so I'm assuming that it was included in the kernel. I've tried removing all references to the driver in these files and doing an rmmod acx_pci but when I reboot, the module is loaded again and the references have been magically rewritten into those files.

My question is how do I disable the acx driver?

I had a similar problem with some early versions of this driver, on a US Robotics 5410 card. If you do indeed have a TI ACX111 chipset in your card, it should work fine with ndiswrapper. To disable the driver, there are 2 steps (that I can think of). If you do it this way it will be easy to undo if you ever need to.

1. Look for a file called 'acx_pci' in /etc/modprobe.d and look in /etc/modprobe.conf and /etc/modprobe.conf.local for a line that's something like

alias wlan0 acx_pci

"comment out" any lines you find like that by inserting a '#' at the begining.

2. Rename /lib/modules/2.6.13-15.8-default/source/net/acx_pci.ko to acx_pci.ko.bkup or something like that.

After that the module shouldn't load. If you ever need to undo it, just reverse those two steps ~Loki