Logitech Bluetooth adapter not going into HCI mode

kenny · 2007-11-10 14:19:02

Hi.
I just installed Arch-Linux on a HP Compaq T5000, and is actually quite pleased with it.
It runs much faster than Ubuntu server, and uses much less resources than ubuntu did (it's a thin client, it only got 128 MB ram and 800 MHz cpu, though i use it as a server ).
Now, apart from serving my iTunes library, playing music on remote speakers, backing up my data, and doing a billion other things, i wanted it to serve a Bluetooth PAN network. So, i plugged my Logitech Bluetooth adapter (From a keyboard/mouse combo) in, and it was registered as a HID device. I then ran hid2hci to make it run in HCI mode, and it said it succeded. But, hcitool dev didn't give any devices, and dmesg said this:

usb 1-1: new full speed USB device using uhci_hcd and address 8
usb 1-1: configuration #1 chosen from 1 choice
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 3 ports detected
usb 1-1.2: new full speed USB device using uhci_hcd and address 9
usb 1-1.2: configuration #1 chosen from 1 choice
input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:10.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input7
input: USB HID v1.11 Keyboard [Logitech Logitech BT Mini-Receiver] on usb-0000:00:10.0-1.2
usb 1-1.3: new full speed USB device using uhci_hcd and address 10
usb 1-1.3: configuration #1 chosen from 1 choice
input: Logitech Logitech BT Mini-Receiver as /devices/pci0000:00/0000:00:10.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input8
input,hiddev0: USB HID v1.11 Mouse [Logitech Logitech BT Mini-Receiver] on usb-0000:00:10.0-1.3
WARNING: at drivers/hid/hid-core.c:784 implement()
 [<c78634a0>] hid_output_report+0x130/0x310 [hid]
 [<c0194603>] mntput_no_expire+0x13/0x70
 [<c78984d8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [<c015dd35>] filemap_fault+0x215/0x470
 [<c78987cc>] usbhid_submit_report+0x14c/0x1b0 [usbhid]
 [<c789b076>] hiddev_ioctl+0x3f6/0xb40 [usbhid]
 [<c016a03d>] handle_mm_fault+0x11d/0x760
 [<c017c885>] nameidata_to_filp+0x35/0x40
 [<c0139507>] __atomic_notifier_call_chain+0x27/0x50
 [<c018a508>] do_ioctl+0x78/0x90
 [<c018a74e>] vfs_ioctl+0x22e/0x2b0
 [<c017c9ac>] do_sys_open+0xbc/0xe0
 [<c018a82d>] sys_ioctl+0x5d/0x70
 [<c01044fa>] syscall_call+0x7/0xb
 =======================
WARNING: at drivers/hid/hid-core.c:784 implement()
 [<c78634a0>] hid_output_report+0x130/0x310 [hid]
 [<c0194603>] mntput_no_expire+0x13/0x70
 [<c78984d8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [<c015dd35>] filemap_fault+0x215/0x470
 [<c78987cc>] usbhid_submit_report+0x14c/0x1b0 [usbhid]
 [<c789b076>] hiddev_ioctl+0x3f6/0xb40 [usbhid]
 [<c016a03d>] handle_mm_fault+0x11d/0x760
 [<c017c885>] nameidata_to_filp+0x35/0x40
 [<c0139507>] __atomic_notifier_call_chain+0x27/0x50
 [<c018a508>] do_ioctl+0x78/0x90
 [<c018a74e>] vfs_ioctl+0x22e/0x2b0
 [<c017c9ac>] do_sys_open+0xbc/0xe0
 [<c018a82d>] sys_ioctl+0x5d/0x70
 [<c01044fa>] syscall_call+0x7/0xb
 =======================
WARNING: at drivers/hid/hid-core.c:784 implement()
 [<c78634a0>] hid_output_report+0x130/0x310 [hid]
 [<c0194603>] mntput_no_expire+0x13/0x70
 [<c78984d8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [<c015dd35>] filemap_fault+0x215/0x470
 [<c78987cc>] usbhid_submit_report+0x14c/0x1b0 [usbhid]
 [<c789b076>] hiddev_ioctl+0x3f6/0xb40 [usbhid]
 [<c016a03d>] handle_mm_fault+0x11d/0x760
 [<c017c885>] nameidata_to_filp+0x35/0x40
 [<c0139507>] __atomic_notifier_call_chain+0x27/0x50
 [<c018a508>] do_ioctl+0x78/0x90
 [<c018a74e>] vfs_ioctl+0x22e/0x2b0
 [<c017c9ac>] do_sys_open+0xbc/0xe0
 [<c018a82d>] sys_ioctl+0x5d/0x70
 [<c01044fa>] syscall_call+0x7/0xb
 =======================
WARNING: at drivers/hid/hid-core.c:784 implement()
 [<c78634a0>] hid_output_report+0x130/0x310 [hid]
 [<c0123a8c>] update_stats_wait_end+0x9c/0xd0
 [<c78984d8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [<c78987cc>] usbhid_submit_report+0x14c/0x1b0 [usbhid]
 [<c789b076>] hiddev_ioctl+0x3f6/0xb40 [usbhid]
 [<c016a03d>] handle_mm_fault+0x11d/0x760
 [<c017c885>] nameidata_to_filp+0x35/0x40
 [<c0139507>] __atomic_notifier_call_chain+0x27/0x50
 [<c018a508>] do_ioctl+0x78/0x90
 [<c018a74e>] vfs_ioctl+0x22e/0x2b0
 [<c017c9ac>] do_sys_open+0xbc/0xe0
 [<c018a82d>] sys_ioctl+0x5d/0x70
 [<c01044fa>] syscall_call+0x7/0xb
 =======================
WARNING: at drivers/hid/hid-core.c:784 implement()
 [<c78634a0>] hid_output_report+0x130/0x310 [hid]
 [<c78984d8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [<c78987cc>] usbhid_submit_report+0x14c/0x1b0 [usbhid]
 [<c789b076>] hiddev_ioctl+0x3f6/0xb40 [usbhid]
 [<c016a03d>] handle_mm_fault+0x11d/0x760
 [<c017c885>] nameidata_to_filp+0x35/0x40
 [<c0139507>] __atomic_notifier_call_chain+0x27/0x50
 [<c018a508>] do_ioctl+0x78/0x90
 [<c018a74e>] vfs_ioctl+0x22e/0x2b0
 [<c017c9ac>] do_sys_open+0xbc/0xe0
 [<c018a82d>] sys_ioctl+0x5d/0x70
 [<c01044fa>] syscall_call+0x7/0xb
 =======================
WARNING: at drivers/hid/hid-core.c:784 implement()
 [<c78634a0>] hid_output_report+0x130/0x310 [hid]
 [<c0123a8c>] update_stats_wait_end+0x9c/0xd0
 [<c78984d8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [<c78987cc>] usbhid_submit_report+0x14c/0x1b0 [usbhid]
 [<c789b076>] hiddev_ioctl+0x3f6/0xb40 [usbhid]
 [<c016a03d>] handle_mm_fault+0x11d/0x760
 [<c017c885>] nameidata_to_filp+0x35/0x40
 [<c0139507>] __atomic_notifier_call_chain+0x27/0x50
 [<c018a508>] do_ioctl+0x78/0x90
 [<c018a74e>] vfs_ioctl+0x22e/0x2b0
 [<c017c9ac>] do_sys_open+0xbc/0xe0
 [<c018a82d>] sys_ioctl+0x5d/0x70
 [<c01044fa>] syscall_call+0x7/0xb
 =======================
WARNING: at drivers/hid/hid-core.c:784 implement()
 [<c78634a0>] hid_output_report+0x130/0x310 [hid]
 [<c78984d8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [<c78987cc>] usbhid_submit_report+0x14c/0x1b0 [usbhid]
 [<c789b076>] hiddev_ioctl+0x3f6/0xb40 [usbhid]
 [<c016a03d>] handle_mm_fault+0x11d/0x760
 [<c017c885>] nameidata_to_filp+0x35/0x40
 [<c0139507>] __atomic_notifier_call_chain+0x27/0x50
 [<c018a508>] do_ioctl+0x78/0x90
 [<c018a74e>] vfs_ioctl+0x22e/0x2b0
 [<c017c9ac>] do_sys_open+0xbc/0xe0
 [<c018a82d>] sys_ioctl+0x5d/0x70
 [<c01044fa>] syscall_call+0x7/0xb
 =======================
WARNING: at drivers/hid/hid-core.c:784 implement()
 [<c78634a0>] hid_output_report+0x130/0x310 [hid]
 [<c78984d8>] hid_submit_ctrl+0x58/0x200 [usbhid]
 [<c78987cc>] usbhid_submit_report+0x14c/0x1b0 [usbhid]
 [<c789b076>] hiddev_ioctl+0x3f6/0xb40 [usbhid]
 [<c016a03d>] handle_mm_fault+0x11d/0x760
 [<c017c885>] nameidata_to_filp+0x35/0x40
 [<c0139507>] __atomic_notifier_call_chain+0x27/0x50
 [<c018a508>] do_ioctl+0x78/0x90
 [<c018a74e>] vfs_ioctl+0x22e/0x2b0
 [<c017c9ac>] do_sys_open+0xbc/0xe0
 [<c018a82d>] sys_ioctl+0x5d/0x70
 [<c01044fa>] syscall_call+0x7/0xb
 =======================
usb 1-1.1: new full speed USB device using uhci_hcd and address 11
usb 1-1.1: configuration #1 chosen from 1 choice

hid2hci says this:

Switching device 046d:c70a to HCI mode was successful
Switching device 046d:c70e to HCI mode was successful

I believe hid2hci doesn't do the job correctly (even though it think it does).
I'm running "Core Dump", and using linux version 2.6.23-ARCH.

Any help would be appreciated.

kenny · 2007-11-15 21:19:54

Hmm... anyone willing to help?
It's not like i'm gonna die of it's not gonna work, but a little response would be nice, even a "That's impossible to fix" would be nice, because then i would know i shouldn't spend a lifetime on this

.:B:. · 2007-11-16 07:08:20

Well I'll throw one in then. The stack errors (I think that's what those messages are) look a bit horrible, so I don't think there's an easy way to fix it, looks like something's wrong with the code.

kenny · 2007-11-16 21:19:35

Ah...
Well, then i'll just dump the idea, i didn't need that network anyway

Arch Linux

#1 2007-11-10 14:19:02

Logitech Bluetooth adapter not going into HCI mode

#2 2007-11-15 21:19:54

Re: Logitech Bluetooth adapter not going into HCI mode

#3 2007-11-16 07:08:20

Re: Logitech Bluetooth adapter not going into HCI mode

#4 2007-11-16 21:19:35

Re: Logitech Bluetooth adapter not going into HCI mode

Board footer