I guess nobody had any ideas. ;-)
For the record, to save anyone else the trouble: After banging my head against this for a while, I went back through the BlueZ site looking for clues and it seems that the bluecard_cs driver doesn't have support for the AnyCom CF-300 until kernel version 2.6.6-rc2 and beyond. So you have to be careful with this: even if BlueZ says it's supported, you need concomitant support in your driver-kernel combo for this to work. See:
http://www.holtmann.org/linux/bluetooth/bluecard.htmlThe comment in bluetooth/bluecard_cs.c in the revision to 2.6.6-rc2 says:
# The Anycom CF-300 compact flash card contains a new Bluetooth chip and
# thus it needs some special handling for the faster UART baud rate. This
# patch detects this new card and does the different initialization.
So, not going to work in Cacko unless they patch the kernel specifically to support it.
This would explain why the card gets a certain way through the initialization process (recognized by the Z as a bluetooth card and the LED goes on) and then craps out.
So, I've got a Socket card on order which arrived today, and I'm going to have another go...
Anybody with supported hardware wanna buy an otherwise new bluetooth card? It's apparently very nice... :-(