FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 11-21-2011, 09:37 AM
Sam Morris
 
Default Bug#649365: linux-image-3.1.0-1-amd64: Broadcom USB adapter not recognised

On Mon, 2011-11-21 at 05:59 +0000, Ben Hutchings wrote:
> Please provide a kernel log covering initialisation of the btusb driver.
>
> Ben.

It's just these two lines:

Nov 21 10:35:40 durandal kernel: [73148.139130] Bluetooth: Generic Bluetooth USB driver ver 0.6
Nov 21 10:35:40 durandal kernel: [73148.139498] usbcore: registered new interface driver btusb

--
Sam Morris <sam@robots.org.uk>



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1321871874.26175.1.camel@durandal">http://lists.debian.org/1321871874.26175.1.camel@durandal
 
Old 11-25-2011, 04:17 AM
Ben Hutchings
 
Default Bug#649365: linux-image-3.1.0-1-amd64: Broadcom USB adapter not recognised

On Mon, 2011-11-21 at 10:37 +0000, Sam Morris wrote:
> On Mon, 2011-11-21 at 05:59 +0000, Ben Hutchings wrote:
> > Please provide a kernel log covering initialisation of the btusb driver.
> >
> > Ben.
>
> It's just these two lines:
>
> Nov 21 10:35:40 durandal kernel: [73148.139130] Bluetooth: Generic Bluetooth USB driver ver 0.6
> Nov 21 10:35:40 durandal kernel: [73148.139498] usbcore: registered new interface driver btusb

So you loaded it yourself - it wasn't automatically loaded?

Ben.

--
Ben Hutchings
Teamwork is essential - it allows you to blame someone else.
 
Old 11-25-2011, 10:40 AM
Sam Morris
 
Default Bug#649365: linux-image-3.1.0-1-amd64: Broadcom USB adapter not recognised

On Fri, 2011-11-25 at 05:17 +0000, Ben Hutchings wrote:
> On Mon, 2011-11-21 at 10:37 +0000, Sam Morris wrote:
> > On Mon, 2011-11-21 at 05:59 +0000, Ben Hutchings wrote:
> > > Please provide a kernel log covering initialisation of the btusb driver.
> > >
> >
> > It's just these two lines:
> >
> > Nov 21 10:35:40 durandal kernel: [73148.139130] Bluetooth: Generic Bluetooth USB driver ver 0.6
> > Nov 21 10:35:40 durandal kernel: [73148.139498] usbcore: registered new interface driver btusb
>
> So you loaded it yourself - it wasn't automatically loaded?

I unloaded it then loaded it to get those log messages, but it is also
loaded during boot. I did some more digging and there is a
device, /sys/class/bluetooth/hci0, that appears once the module is
loaded, so this may be a problem with bluez.

Bluez maintainers, hci_for_each_dev in lib/hci.c doesn't recognise my
Bluetooth adapter.

if (ioctl(sk, HCIGETDEVLIST, (void *) dl) < 0) {
err = errno;
goto free;
}

for (i = 0; i < dl->dev_num; i++, dr++) {
if (hci_test_bit(flag, &dr->dev_opt))
if (!func || func(sk, dr->dev_id, arg)) {
dev_id = dr->dev_id;
break;
}
}

While iterating through the memory filled by the HCIGETDEVLIST ioctl, it
skips over the device because the call to hci_test_bit returns 0. 'flag'
is HCI_UP. My knowledge of Bluetooth devices ends here, so I don't know
if that's a problem with the kernel, or something else in userspace not
initializing the device correctly.

--
Sam Morris <https://robots.org.uk/>
3412 EA18 1277 354B 991B C869 B219 7FDB 5EA0 1078
 

Thread Tools




All times are GMT. The time now is 12:14 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org