Your message dated Sun, 9 Mar 2025 18:24:05 +0100
with message-id <[email protected]>
and subject line bluez-utils: hid2hci --tohid does not work
has caused the Debian Bug report #355497,
regarding bluez: make hid2hci --tohid work (with certain logitech dongles)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
355497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=355497
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bluez-utils
Version: 2.25-1
Severity: normal
Hi,
according to the manpage, hid2hci is used to switch HID proxy bluetooth dongle
into the HCI mode and back. The bluetooth initscript tries to make use of it
on stop/shutdown.
However, it doesn't seem to work for me: my symptom is that I have no way of
typing on my system, when I reboot after booting first in Debian. The BIOS or
the GRUB menu are inaccessible if I last booted in Debian.
When I try to execute hid2hci --tohid manually, I get the following error
message:
# hid2hci --tohid
No devices in HID mode found
# lsusb
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 046d:c707 Logitech, Inc.
Bus 001 Device 004: ID 046d:c704 Logitech, Inc.
Bus 001 Device 003: ID 0451:2036 Texas Instruments, Inc. TUSB2036 Hub
Bus 001 Device 001: ID 0000:0000
So bottom line is: switching from HID to HCI works, switching back doesn't
(and never has I might add). For the record: my keyboard is a Logitech DiNovo
Media Desktop with an MX900 BT mouse.
Thanks,
-- Mourad DC
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages bluez-utils depends on:
ii libbluetooth1 2.25-1 Library to use the BlueZ Linux Blu
ii libc6 2.3.6-3 GNU C Library: Shared libraries an
ii libdbus-1-2 0.61-3 simple interprocess messaging syst
ii libusb-0.1-4 2:0.1.11-5 userspace USB programming library
ii lsb-base 3.0-15 Linux Standard Base 3.0 init scrip
ii makedev 2.3.1-80 creates device files in /dev
ii module-init-tools 3.2.2-2 tools for managing Linux kernel mo
ii modutils 2.4.27.0-4 Linux module utilities
ii sysvinit 2.86.ds1-12 System-V-like init utilities
bluez-utils recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Okay, this bug is ancient.
I really doubt the hardware is still out there being used.
Kind regards,
-- Mourad De Clerck
--- End Message ---
