From: Alex Holland <ah160@student.cs.york.ac.uk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Compile bluez-bluefw-1.0 fails
Date: Mon, 19 Apr 2004 14:19:58 +0100 [thread overview]
Message-ID: <200404191419.59021.ah160@student.cs.york.ac.uk> (raw)
In-Reply-To: <1082370224.4403.33.camel@pegasus>
On Monday 19 Apr 2004 11:23, Marcel Holtmann wrote:
> you can find it at http://www.bluez.org/drivers.html
Ah, thanks! Could you put that URL in the Kernel help page for the
blutonium driver? It's a bit of an enigma at present.
While it doesn't seem to oops on Gentoo anymore, neither does it seem to
actually work - hciconfig can't see any devices. I've enclosed
information which will hopefully help find out why.
Thanks.
Alex Holland
------------------------------------------------
The dongle's a Belkin F8T001, the original model. Bluefw works very
temprementally; sometimes it just doesn't, for no apparent reason, with
the dongle timing out. Blue-fw was uninstalled before trying out the
Blutonium kernel module, and BCM-LEGAL.txt, BCM2033-FW.bin and
BCM2033-MD.hex placed in /usr/lib/hotplug/firmware/
Athlon T-Bird 900Mhz
Gentoo stable, gentoo-dev-sources-2.6.5-r2.
bluez-hcidump-1.8
bluez-libs-2.5
bluez-sdp-1.5
bluez-utils-2.5
latest CVS KDE Bluetooth
dmesg excerpts:
---------------------------------------------
...blah...
Bluetooth: Broadcom Blutonium firmware driver ver 1.0
Bluetooth: Core ver 2.4
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: HCI USB driver ver 2.5
...blah...
bcm203x_probe: Mini driver request failed
bcm203x: probe of 1-2:1.0 failed with error -5
drivers/usb/core/usb.c: registered new driver bcm203x
drivers/usb/core/usb.c: registered new driver hci_usb
...blah...
Bluetooth: L2CAP ver 2.1
Bluetooth: L2CAP socket layer initialized
-----------------------------------------------
lsusb gives the following:
Bus 001 Device 003: ID 0a5c:2033 Broadcom Corp. BCM2033 Bluetooth
---------------------------------------------
lsmod provides the following:
l2cap 21380 2
hci_usb 9664 0
bluetooth 43812 4 l2cap,hci_usb
bcm203x 4416 0
firmware_class 7616 1 bcm203x
kernel config:
------------------------------------------------
# Bluetooth support
#
CONFIG_BT=m
CONFIG_BT_L2CAP=m
# CONFIG_BT_SCO is not set
CONFIG_BT_RFCOMM=m
CONFIG_BT_RFCOMM_TTY=y
# CONFIG_BT_BNEP is not set
#
# Bluetooth device drivers
#
CONFIG_BT_HCIUSB=m
# CONFIG_BT_HCIUSB_SCO is not set
# CONFIG_BT_HCIUART is not set
CONFIG_BT_HCIBCM203X=m
# CONFIG_BT_HCIBFUSB is not set
# CONFIG_BT_HCIVHCI is not set
# CONFIG_NETPOLL is not set
# CONFIG_NET_POLL_CONTROLLER is not set
-------------------------------------------------------------
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-04-19 13:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-18 21:21 [Bluez-users] Compile bluez-bluefw-1.0 fails Dirk Vornheder
2004-04-18 21:55 ` Marcel Holtmann
2004-04-19 8:35 ` Alex Holland
2004-04-19 10:23 ` Marcel Holtmann
2004-04-19 13:19 ` Alex Holland [this message]
2004-04-19 13:30 ` Marcel Holtmann
2004-04-19 13:41 ` Alex Holland
2004-04-19 13:54 ` Marcel Holtmann
2004-04-19 15:39 ` Alex Holland
2004-04-19 16:12 ` Marcel Holtmann
2004-04-19 17:22 ` Alex Holland
2004-04-19 17:52 ` Simone Gotti
2004-04-19 20:21 ` Alex Holland
2004-04-20 9:28 ` Alex Holland
2004-04-20 11:56 ` Marcel Holtmann
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=200404191419.59021.ah160@student.cs.york.ac.uk \
--to=ah160@student.cs.york.ac.uk \
--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