Re: Bluetooth Questions Using wheezy

2016-07-19 Thread Martin McCormick
David Wright writes: > ... because wheezy's hciconfig is in /usr/sbin. I probably should have used locate or which and it would have reported the path. In this case, /usr/sbin is one of the paths in my $pATH and there is no bluetooth interface as running hciconfig with the correct path si

Re: Bluetooth Questions Using wheezy

2016-07-19 Thread David Wright
On Tue 19 Jul 2016 at 12:36:22 (-0500), Martin McCormick wrote: > Reco writes: > > No, it does not. These messages mean that assorted bluetooth modules > > are loaded. > > > > > > > Another old Dell optiplex running wheezy also produces > > > exactly the same messages when running dmesg. >

Re: Bluetooth Questions Using wheezy

2016-07-19 Thread Martin McCormick
Reco writes: > No, it does not. These messages mean that assorted bluetooth modules > are loaded. > > > > Another old Dell optiplex running wheezy also produces > > exactly the same messages when running dmesg. > > > > Is there any utility I can run to see if they are alive > > and u

Re: Bluetooth Questions Using wheezy

2016-07-19 Thread Reco
Hi. On Tue, 19 Jul 2016 11:08:08 -0500 "Martin McCormick" wrote: > I see the following messages in dmesg: > > Bluetooth: Core ver 2.16 > Bluetooth: HCI device and connection manager initialized > Bluetooth: HCI socket layer initialized > Bluetooth: L2CAP socket layer initializ