public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Holger Frydrych <h.frydrych@gmx.de>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Logitech diNovo hub not recognized?
Date: Fri, 09 Jul 2004 20:15:42 +0200	[thread overview]
Message-ID: <1089396942.22528.10.camel@pegasus> (raw)
In-Reply-To: <40EEC9CD.8030003@gmx.de>

Hi Holger,

> I've bought a Logitech diNovo set some time ago which I have used in 
> non-bluetooth mode so far (because I do not have any other bluetooth 
> devices anyway, and the procedure to switch into bluetooth mode seemed 
> to complicated to me to be worth the time). But now that I've read that 
> with the latest tools and kernel patches and the use of the HIDP 
> protocol the process should have become quite the easy task, I decided 
> to give it a try.
> Well, so I downloaded the 2.6.7 kernel, applied the mh1 patch (and 
> additionally the ck5 patch, if that matters) and configured it along 
> with the bluetooth options. Then I rebooted with the new kernel and 
> executed the bluetooth start script, which should have been about all to 
> do, at least so far that I've read in this mailing list here. But, well, 
> nothing at all happens... The hub does not switch to Bluetooth mode, and 
> any attempt to use hcitool to search for bluetooth devices just reports 
> me a "device not found" error.

use 2.6.7-mh2 and bluez-libs-2.8 and bluez-utils-2.8 to get this really
working. To use hid2hci you must enable CONFIG_USB_HIDDEV in your kernel
config and it is a good idea to use udev for creation of the hiddev
device nodes.

> I've since tried to compile the bluetooth parts both as modules and as 
> built-in and compiled virtually everything in there, but so far no 
> success. I can still use this 'hid2hci' tool, which obviously switches 
> the hub to HCI mode, but that results in my keyboard and mouse not 
> working anymore, and I didn't succeed in reconnecting them.

Show us the content of /proc/bus/usb/devices.

Regards

Marcel




-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-07-09 18:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 16:37 [Bluez-users] Logitech diNovo hub not recognized? Holger Frydrych
2004-07-09 18:15 ` Marcel Holtmann [this message]
     [not found]   ` <40EF0F10.8050302@gmx.de>
2004-07-09 22:51     ` Marcel Holtmann
2004-07-10  8:41       ` Holger Frydrych
2004-07-10  8:48         ` Marcel Holtmann
2004-07-10  9:20           ` Holger Frydrych
2004-07-10  9:25             ` Marcel Holtmann
2004-07-10 12:32               ` Holger Frydrych
2004-07-10 17:34                 ` 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=1089396942.22528.10.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=h.frydrych@gmx.de \
    /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