Re: [Bluez-users] Can't init device hci0 (all information included), help! Thanx a lot!!!

Marcel Holtmann
2005-01-24T12:22:09Z

Hi Andy,

> I have reinstalled Vmware (change from 5.0 beta to 4.5.2) and Red Hat
> 9 (use default bluez-lib-2.3-3 and bluez-util-2.2-3) just now, it
> WORKS now, at least everything looks fine so far, I can l2ping the
> device (Nokia 7650) properly.
>
> Below is the hciconfig -a output of my usb doggle, you can check it
> whether it's supported by lastest bluez package.
>
> hci0: Type: USB
> BD Address: 00:10:60:A3:83:0E ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:1132 acl:2 sco:0 events:44 errors:0
> TX bytes:423 acl:2 sco:0 commands:26 errors:0
> Features: 0xff 0xff 0x0f 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ (0)'
> Class: 0x000100
> Service Classes: Unspecified
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x1e7 LMP Ver: 1.1 (0x1) LMP Subver: 0x1e7
> Manufacturer: Cambridge Silicon Radio (10)
>
> I will try new kernel later, and tell you the outcome. Btw, I noticed
> that many people talked 'ep0in timed out' problem, maybe it's
> something wrong with latest usb subsystem?

the bluez-{libs|utils} can't be the problem here. It is the VMware or
maybe the USB subsystem. Keep testing and try to find the wrong part in
your puzzle.

Regards

Marcel