From: Markus Kohli <kohli@webdeko.com>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] DiNovo in Bluetooth-Mode
Date: Sat, 12 Feb 2005 08:58:46 +0100 [thread overview]
Message-ID: <200502120858.46323.kohli@webdeko.com> (raw)
Hi
I read some posts in the archives, because I was trying to get my DiNovo
working under SuSE 9.2, and found this here:
> > I tested it with SuSE 9.2, Fedora Core 3 and Ubuntu. The only thing you
have
> > to do, is to call
> >
> > hid2hci
> >
> > Then you should see a message, like
> >
> > Switching device XXXX:XXXX to HCI mode was successful
> >
> > Now check with
> >
> > hcitool dev
> >
> > if it sees the bluetooth hub.
> >
>
> yes it did that, said it was successful,
> BUT the keyboard & mouse stopped responding!
> The only way to get them working again was to reboot.
>
> Laurence
Now, I found out how to get this working... Only enable the following
bluetooth-services:
HCI
SDP
HID
HID2HCI
If you have any others, like obex stuff enabled, that'll block the keyboard
and the mouse. With SuSE you can easily configure that by help of yast2, or
by hand in /etc/sysconfig/bluetooth.
Then additionaly, once I had this working, the F-keys had gone missing, but an
update to the latest kernel-of-the-day also fixed that (I'm running on
2.6.11rc3 now, that's probably got the -mh patch included).
Hope this helps anyone.
Kind regards
Markus
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
reply other threads:[~2005-02-12 7:58 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=200502120858.46323.kohli@webdeko.com \
--to=kohli@webdeko.com \
--cc=bluez-devel@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