From: Mahaboob Nazeer SK <nazeer.m@phytec.in>
To: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: No default controller available error
Date: Mon, 29 Jul 2019 15:56:12 +0200 [thread overview]
Message-ID: <OF16744CA5.5F3760DC-ONC1258446.004C8E8D-C1258446.004C8E8E@phytec.de> (raw)
In-Reply-To:
Hi,
I just cloned the latest Bluez and tried to install it with mesh enabled. The installation was
successful. But when i run the mesh control and try to do discover-unprovisioned,i am facing below error.I also get same error when i tried with bluetoothctl.
$ meshctl
Waiting to connect to bluetoothd...Reading prov_db.json and local_node.json from /home/nazeer/.config/meshctl directory
[meshctl]# discover-unprovisioned on
No default controller available
[meshctl]#
I checked weather the service was running. And found it was running fine
sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2019-07-29 19:06:39 IST; 1min 18s ago
Docs: man:bluetoothd(8)
Main PID: 18612 (bluetoothd)
Tasks: 1 (limit: 4489)
Memory: 708.0K
CGroup: /system.slice/bluetooth.service
└─18612 /usr/libexec/bluetooth/bluetoothd
Jul 29 19:06:39 nazeer systemd[1]: Starting Bluetooth service...
Jul 29 19:06:39 nazeer bluetoothd[18612]: Bluetooth daemon 5.50
Jul 29 19:06:39 nazeer systemd[1]: Started Bluetooth service.
Jul 29 19:06:39 nazeer bluetoothd[18612]: Starting SDP server
Jul 29 19:06:39 nazeer bluetoothd[18612]: Bluetooth management interface 1.14 initialized
I request to please provide me a solution.
Regards,
Nazeer.
next reply other threads:[~2019-07-29 13:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-29 13:56 Mahaboob Nazeer SK [this message]
2019-07-30 7:00 ` No default controller available error Michał Lowas-Rzechonek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=OF16744CA5.5F3760DC-ONC1258446.004C8E8D-C1258446.004C8E8E@phytec.de \
--to=nazeer.m@phytec.in \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).