I believe I have finally narrowed down the problem. It lies in the 'libmtp-runtime' package with the command 'mtp-probe' (only present in wheezy or newer). I'm not sure what this is doing to my system, but when the package mentioned is installed, it "messes" up my atheros bluetooth device so that the kernel/udev cannot load the firmware into it. As soon as I uninstalled this package and thus caused the boot process to throw some errors about missing mtp-probe command, my bluetooth module was correctly loaded and the led turned on. >> Inexplicably yesterday's (and the day before) Debian testing snapshot >> seems to have the problem fixed! I guess this snapshot that I tested earlier didn't have that package installed I found out about this completely by chance. For whatever reason, on my second upgrade to wheezy 'apt-get dist-upgrade' didn't pull 'libmtp-runtime' and my bluetooth module just worked. I tried to get the bootlog messages so I can send this info, but even with bootlogd enabled these messages happen too early on the boot process to be logged in /var/log/boot. I feel this is not necessarily a kernel bug anymore (all kernels tested work fine 3.0.x, 3.1.x, 3.2.x and even 3.3.0-rc3). But the experts will know better. This is definitely progress! Cheers Andres PS: please forward the info to other bug reports I don't have access to, like Red Hat / Fedora and Ubuntu. Additional testing is needed. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
