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: Sat, 10 Jul 2004 10:48:03 +0200 [thread overview]
Message-ID: <1089449283.13519.35.camel@pegasus> (raw)
In-Reply-To: <40EFABCE.7000503@gmx.de>
Hi Holger,
> > did hid2hci showed any error messages. Is there anything in the logfiles
> > or visible through dmesg. What kind of machine do you use? Do you have
> > the hiddevX devices nodes?
> hid2hci tells this:
> Switching device 046d:c704 to HCI mode was successful.
this sound good.
> But this immediately results in my keyboard, mouse and MediaPad not
> working anymore, or rather they get disconnected, I suppose. So I press
> the connect button on the keyboard and then the one on the hub, just the
> hub does not react (does not start blinking) and so nothing happens. Ok,
> so I've got my old PS/2 keyboard and attached this one additionally so I
> can keep typing. I then tried 'hcitool dev' which now (after hid2hci)
> shows me the logitech hub as hci0. I then typed 'hcitool scan', it does
> not complain about missing devices, the hub starts blinking and it
> finally lists all my diNovo devices. So far, so good. Then I try to
> manually connect one of my devices (doesn't matter, which) via 'hcitool
> cc [address]', and the hub again starts blinking, but all I get in
> result is: 'Can't create connection: Input/Output error'. 'hidd
> --search' returns a similar error: 'Can't create HID control channel:
> Invalid exchange'...
Don't use "hcitool cc ...", because this is only for development. What
does "hciconfig -a" show?
Run "hcidump -x" as root while connecting with hidd.
> Interestingly, the HIDP protocol still identifies as mh1, though I
> meanwhile did supply the mh2 patch. So is this correct, or should I
> investigate more here?
These are two different version numbers. What "modinfo hidp" shows means
that you use the HIDP version 1.0 with an additional patch for the
report protocol mode. I only put -mh1 after it to identify it, because
the HIDP with boot protocol mode is submitted for kernel inclusion.
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
next prev parent reply other threads:[~2004-07-10 8:48 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
[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 [this message]
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=1089449283.13519.35.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