You've so far done everything right; ath3k is the correct device-specific driver for the USB gizmo in question and /lib/firmware/ath3k-1.fw is the correct firmware file, in the proper location, and the USB infrastructure even noticed the device and reported some generic info about it.
Unfortunately, you're likely enjoying a known bug in the handling of that device: https://duckduckgo.com/?q=0cf3%3A3000+firmware ...so backports may be the path of least resistance. _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/
