From: "Mumia W.." <paduille.4061.mumia.w+nospam@earthlink.net>
To: Bluez-Users-List <bluez-users@lists.sourceforge.net>
Subject: [Bluez-users] Anycom USB-250 won't enter discoverable mode
Date: Fri, 23 May 2008 23:46:38 -0500 [thread overview]
Message-ID: <48379DAE.7000603@earthlink.net> (raw)
I have an Anycom USB-250 that won't enter discoverable mode with bluez
3.7. I'm pretty sure that I've followed the instructions properly from
here: http://howto.pilot-link.org/bluesync/index.html
However, it doesn't work. When I try to get my Palm T|X to scan for
Bluetooth devices, it sees nothing. This is under Debian Etch (i386)
with bluez-utils 3.7-1. I'm running kernel 2.6.24.6.
I'm looking at two possible sources of the problem: 1) a bluez software
failure (probably in sdpd) or 2) a firmware requirement for the Anycom.
Sdpd seems to enable SDP by default; however, I wouldn't begin to know
how to evaluate if SDP actually working.
For the firmware requirement, I've installed bluez-firmware, but the
package seems to do nothing. The /usr/share/doc/bluez-firmware/README
file only discusses compilation and installation, and README.Debian only
says that hotplug is requires, but hotplug is not compatible with Etch.
I need to find out how to use the binary firmware files in
/usr/lib/firmware (which are evidently intended for my adapter). The
Anycom USB-250 has a Broadcomm chipset, and I've heard that Broadcomm
needs firmware to work.
Someone please tell me how to get either sdpd to work properly or the
firmware installed. Thanks.
(I also asked a similar question in debian-user.)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
reply other threads:[~2008-05-24 4:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=48379DAE.7000603@earthlink.net \
--to=paduille.4061.mumia.w+nospam@earthlink.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.