Return-Path: <cyrus@holtmann.org>
Message-ID: <BAY176-W40E12E1C2F620AB0D38605D3000@phx.gbl>
From: Ssagarr Patil <hugarsagar@outlook.com>
To: Szymon Janc <szymon.janc@tieto.com>,
	Marcel Holtmann <marcel@holtmann.org>
CC: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: RE: bluez5 pairing devices
Date: Wed, 18 Mar 2015 17:39:26 +0530
In-Reply-To: <12627750.IG3ACNRtuD@leonov>
References: <BAY176-W679B1127159C091585D3AD3030@phx.gbl>
 <46068BD2-CF33-4617-80DB-5AE5C1FCA364@holtmann.org>,<12627750.IG3ACNRtuD@leonov>
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

Hi Szymon/Marcel,

> On Tuesday 17 of March 2015 09:42:44 Marcel Holtmann wrote:
>> Hi Sagar,
>>
[Snip]
> Just an note that recent backports dropped support for kernels older than 3.0.
> So some older release might be needed for 2.6.37.
>
I have managed to backport it thanks.


But bluetoothctl doesnt detect it, It says the following:

# bluetoothctl 
[bluetooth]# power on
No default controller available
[bluetooth]# 

Here is output of hciconfig:

$ hciconfig? -a
hci0:?? Type: BR/EDR? Bus: UART
??????? BD Address: 34:B1:F7:E2:DE:CB? ACL MTU: 1021:6? SCO MTU: 180:4
??????? UP RUNNING PSCAN ISCAN 
??????? RX bytes:12525 acl:56 sco:0 events:262 errors:0
??????? TX bytes:2948 acl:52 sco:0 commands:108 errors:0
??????? Features: 0xff 0xfe 0x2d 0xfe 0xdb 0xff 0x7b 0x87
??????? Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
??????? Link policy: RSWITCH HOLD SNIFF 
??????? Link mode: SLAVE ACCEPT 
??????? Name: 'bt_hw'
??????? Class: 0x001f00
??????? Service Classes: Unspecified
??????? Device Class: Invalid Device Class!
??????? HCI Version: 4.1 (0x7)? Revision: 0x0
??????? LMP Version: 4.1 (0x7)? Subversion: 0xac7c
??????? Manufacturer: Texas Instruments Inc. (13)

# 

And I scan devices using hcitool as well.

Any pointers why bluetoothctl fails ?

Regards,
Sagar