[Pkg-bluetooth-maintainers] Bug#631620: there may be things you could help with

Mark Fletcher mark27q1 at gmail.com
Sun Jul 24 11:36:18 UTC 2011


On Sat, Jul 23, 2011 at 5:57 PM, Cristian Ionescu-Idbohrn <
cristian.ionescu-idbohrn at axis.com> wrote:

> Bug #626975 may give you some ideas.
>
> The result from 'lsusb' paired with the rules in
> /lib/udev/rules.d/*hid2hci.rules may be a start point.
>
>
Well the first thing I notice is that the rules in that file in
/lib/udev/rules.d are expressed completely differently between the two
package versions. This is looking more like it was back in the 4.61 days
(when nothing worked for this keyboard combo either). 4.66-3 (which works)
specifies the path to the hid2hci executable, in /usr/sbin. Meanwhile,
4.94-2 doesn't specify the path to the hid2hci executable, and puts the
executable in /lib/udev by the look of it. Any chance the hid2hci executable
is not being found?

I also notice the hid2hci executable has changed between the two versions,
not just its path. The command line options etc are different. Any chance
the new one just doesn't work properly?

Overall I'm inclined to think the rule is firing but is either not able to
find the hid2hci executable it is supposed to be running, or else that
executable is not doing its job properly.

I looked over the bug you pointed me at but I'm quickly getting out of my
depth. I'll take a more detailed look later if I have time later this
evening (in Japan, Sunday evening here).

I'd like to be able to see some evidence of what's happening in the logs but
I am not sure which logs I should be looking in -- I don't know my way
around the debian logging arrangements well enough at the moment. If you can
give me a pointer on that I can maybe gather some more useful information.

And finally -- lsusb output (when 4.66-3 is installed -- ie working. Are you
thinking it would be different when 4.94-2 is installed? No, right?)

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 004: ID 0d8c:000c C-Media Electronics, Inc. Audio Adapter
Bus 008 Device 002: ID 046d:0b06 Logitech, Inc.
Bus 008 Device 003: ID 046d:c71b Logitech, Inc.
Bus 008 Device 004: ID 046d:c71c Logitech, Inc.


You can see the keyboard / mouse are using c71b and c71c which are both
covered in the udev rules. 0b06 is not, but that's also true in the working
4.66-3 version so I don't think that matters.

C-Media is a USB headset I am using, which is not bluetooth and works fine.

Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-bluetooth-maintainers/attachments/20110724/aa969e49/attachment.html>


More information about the Pkg-bluetooth-maintainers mailing list