[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Apple built-in Bluetooth not appearing in /dev



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Jun 18, 2004, at 1:11 PM, Alain Perry wrote:

Alain,
	Thanks for the reply.  By sid installation I meant the unstable

Sorry, I missed that in your first mail...

branch.  I forgot to include the error from hid2hci; here it is:

$ hid2hci
No devices in HCI mode found

That is a strange error...
You indeed shouldn't have any device in HCI mode before hid2hci
completes its execution. If anything, the error message should be:
No devices in HID mode found

Or am I completely mistaken ?
Anyway, I think your question would find an answer more easily on the
bluez project mailing lists, since this is supposed to be supported by
their software.

	By the way, where did you get your 2.6.7 kernel/sources?

Took them from kernel.org, and compiled the debian way. No noticeable
problem so far (BTW, people using the prism54 driver, the cvs-snapshot
version from prism54.org works way better than the one in the kernel for
the moment. There have been problems committing the patches, and the
prism54 team is trying to solve that issue).

Hope this helps.

--
Alain Perry

Alain,
Thanks again. The default mode for hid2hci is to switch to HCI mode as you mention, so perhaps the message is returned after the switch is supposed to have been made, as a confirmation of sorts. That would make sense, since hid2hci returns the following:

$ hid2hci
No devices in HCI mode found

$ hid2hci --tohci
No devices in HCI mode found

$ hid2hci --tohid
No devices in HID mode found

I have subscribed to bluez-users and searched their archive as well. So far, it looks like the Apple Bluetooth Firmware Update may be giving me this grief by causing issues with hci_usb. I had compiled all of the Bluetooth device drivers as modules in the event I had overlooked the correct driver in my kernel configuration, and since then I noticed several lines in dmesg that I had not seen before:

(Begin dmesg excerpts)
...
Bluetooth: HCI USB driver ver 2.5
drivers/usb/core/usb.c: registered new driver hci_usb
Bluetooth: VHCI driver ver 1.1
...
usbfs: USBDEVFS_CONTROL failed cmd hid2hci dev 2 rqt 64 rq 0 len 0 ret - -110
usb 1-1: USB disconnect, address 2
drivers/usb/input/hid-core.c: can't resubmit intr, 0001:01:1a.0-1/input0, status -19 drivers/usb/input/hid-core.c: can't resubmit intr. 0001:01:1a.0-1/input1, status -19
usb 1-1: new full speed USB device using address 3
Oops: kernel access of bad area, sig: 11 [#1]
NIP: C01C4690 LR: C01C4934 SP: EFDEFD00 REGS: efdefc50 TRAP: 0301 Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 00000004, DSISR: 40000000
TASK = c19d2000[5] 'khubd' Last syscall: -1
GPR00: C01C4934 EFDEFD00 C19D2000 D7BE0800 EFCEA8C0 C1ACDF50 00000000 C037FE3C
GPR08: 0000001E 0000001D EFFFE810 00000074 82008022
Call trace:
 [c01c4934] usb_set_interface+0x94/0x164
 [f24aaab4] hci_usb_probe+0x21c/0x48c [hci_usb]
 [c01be0c4] usb_probe_interface+0x80/0x98
 [c011ffc8] bus_match+0x50/0x8c
 [c012005c] device_attach+0x58/0xbc
 [c01202dc] bus_add_device+0x7c/0xd8
 [c011eb7c] device_add+0xb0/0x184
 [c01c4d20] usb_set_configuration+0x20c/0x25c
 [c01bf400] usb_new_device+0x20c/0x25c
 [c01c0e60] hub_port_connect_change+0x1a0/0x298
 [c01c122c] hub_events+0x2d4/0x354
 [c01c12e8] hub_thread+0x3c/0xf4
 [c000afd4] kernel_thread+0x44/0x60
...

(End dmesg excerpts)

Does that look anything like the kernel oops you mentioned earlier that you had with 2.6.5? Because I don't have the internal modem (or GPRS, obviously) working yet, I am having to transcribe this stuff into MOL and then reboot in OSX while I am at work. Sorry for any errors.

Regards,
- -- Barry C. Hawkins
All Things Computed
site: www.allthingscomputed.com
weblog: www.yepthatsme.com


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFA0z7j7bZ6kUftWZwRAtS4AJwIEYEA66QawUhLKRuAQzkW4/+GygCeNwDU
MiBSu6jaVBve0DxCGn4fqaY=
=YBdv
-----END PGP SIGNATURE-----



Reply to: