Comment 34 for bug 293946

Just a couple notes: the "unknown RFChipID: 0x5!!!" seems to suggest your chip might not be the same as the one the driver supports. Perhaps you can list the exact version you have (via lspci or lsusb).

I haven't tried it yet, but when you compile the new driver, perhaps it doesn't allow you to have both. Do they both exist in the appropriate /lib/modules subdirectories? (try "find /lib/modules | grep 8187" ... if they're both there and you still can't load the old one, then maybe try blacklisting the new one.)

Lastly, linux is all about experimental and use-at-your-own-risk and this-might-blow-up type stuff. Not only does this increase fun, but it also encourages more users to delve into the code -- to really get to know their machines. It just wouldn't feel right if everything was polished and Guaranteed(TM) to work without any need to tinker, IMHO :).