From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] D-Link DWB-120M and BlueZ 2.14
Date: Sat, 29 Jan 2005 02:13:35 +0100 [thread overview]
Message-ID: <1106961215.10580.5.camel@pegasus> (raw)
In-Reply-To: <200501282151.ALQ50969@ms12.netsolmail.com>
Hi Chris,
> I installed bluez-libs-2.14 and bluez-utils-2.14 on a linux 2.4.26 system. I
> also installed the BCM2033-FW.bin and BCM2033-MD.hex files in both /
> lib/firmware and /usr/lib/hotplug/firmware. The bluez kernel module
> loads, and I can see stuff like this in the messages log when I unplug and
> plug in the device and start the hcid daemon:
>
> Jan 28 12:23:59 krank kernel: usb.c: deregistering driver hci_usb
> Jan 28 12:24:14 krank kernel: BlueZ Core ver 2.3 Copyright (C) 2000,2001
> Qualcomm Inc
> Jan 28 12:24:14 krank kernel: Written 2000,2001 by Maxim Krasnyansky
> <maxk@qualcomm.com>
> Jan 28 12:24:31 krank kernel: BlueZ HCI USB driver ver 2.5 Copyright
> (C) 2000,2001 Qualcomm Inc
> Jan 28 12:24:31 krank kernel: Written 2000,2001 by Maxim Krasnyansky
> <maxk@qualcomm.com>
> Jan 28 12:24:31 krank kernel: usb.c: registered new driver hci_usb
> Jan 28 12:25:13 krank kernel: usb.c: USB disconnect on device 00:04.2-2
> address 2
> Jan 28 12:25:17 krank kernel: hub.c: new USB device 00:04.2-2, assigned
> address 3
> Jan 28 12:36:49 krank -- MARK --
> Jan 28 12:39:06 krank hcid[1025]: Bluetooth HCI daemon
>
> However, when I do a 'hcitool dev' it doesn't see anything- it just says
> "Devices:" and then nothing. If I run lsusb it says:
>
> Bus 001 Device 001: ID 0000:0000
> Bus 001 Device 003: ID 0a5c:2033 Broadcom Corp. BCM2033 Bluetooth
>
> What'd I do wrong?
on a system with a 2.4 kernel you need the bcm203x utility. You must
enable when compiling bluez-utils.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-01-29 1:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 21:51 [Bluez-users] D-Link DWB-120M and BlueZ 2.14 Chris Taylor
2005-01-29 1:13 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-29 1:28 Chris Taylor
2005-01-29 1:36 ` Marcel Holtmann
2005-01-29 2:31 Chris Taylor
2005-01-30 19:48 Chris Taylor
2005-01-30 19:52 ` Marcel Holtmann
2005-01-30 20:46 Chris Taylor
2005-01-30 20:58 ` Marcel Holtmann
2005-01-31 8:06 Chris Taylor
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=1106961215.10580.5.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/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