[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: understanding/troubleshooting gnokii
|
From: |
Raphaël |
|
Subject: |
Re: understanding/troubleshooting gnokii |
|
Date: |
Fri, 12 Jun 2015 11:52:02 -0300 |
|
User-agent: |
Mutt/1.5.23 (2014-03-12) |
On Fri, Jun 12, 2015 at 11:53:14AM +0200, Pawel Kot wrote:
> On Fri, Jun 12, 2015 at 10:20 AM, Roberto Verzola <address@hidden> wrote:
> > address@hidden:~/HotlineSMS$ sudo l2ping hci1
> > Can't connect: Host is down
>
> Looks like something's wrong with the device. Perhaps there is some
> hint in dmesg?
Indeed...
And ensure the bluez is installed and running, eg:
# ps faux|grep bluez
# service bluetooth start
There is /var/log/syslog to look at too.
(well I would say it runs if hcitool output a valid device)
What outputs:
# hcitool scan
What says hciconfig about the BT address of your dongle?
Can you l2ping yourself at that address ?
More generally than binding your device to hci1 and then pinging hci1,
try to directly l2ping the mac-address of the device.
BTW why hci1 and not hci0 ?
--
GPG id: 0xF41572CEBD4218F4