Hi, On Mon, May 16, 2011 at 6:36 AM, Eponymous - <the.epon@xxxxxxxxx> wrote: > OK guys, > > I had a theory that my l2test test was not working due to the fact > that the chip wasn't configured to work with upperlayers. After > enabling this however, the devices disappear (in hciconfig) so I > can't really test any L2CAP stuff (which I assume is what l2test is > doing). > > Are there any other things I can try to help debug this issue I've seen? What is the chipset of your USB dongles ? A "lsusb -d <vid>:<pid>" and relevant output from dmesg might help here. What do you mean by "the chip wasn't configured to work with upperlayers" ? Was the chipset in a mode which was not HCI compliant? Keep in mind that there are development/prototype USB dongles which are in fact serial/FTDI devices, and thus require using hciattach to be able to use them in BlueZ. Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- 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