* [Bluez-users] VB: Problem with 2nd second dongle
@ 2006-11-13 20:39 Håkan Lager
2006-11-16 10:32 ` Marcel Holtmann
0 siblings, 1 reply; 9+ messages in thread
From: Håkan Lager @ 2006-11-13 20:39 UTC (permalink / raw)
To: Bluez-users
I begin to suspect this is a dbus error. Is there any simple way to check
this suspicion?
-----Ursprungligt meddelande-----
Fr=E5n: H=E5kan Lager [mailto:hakan@digiloo.net] =
Skickat: den 13 november 2006 19:23
Till: 'BlueZ users'
=C4mne: SV: [Bluez-users] Problem with 2nd second dongle
Hi,
After mounted the /proc/bus/usb filesystem the result is this:
Nov 13 18:18:12 ts7200 daemon.info hcid[145]: HCI dev 0 down
Nov 13 18:18:12 ts7200 daemon.info hcid[145]: Stoping security manager 0
Nov 13 18:18:12 ts7200 daemon.info hcid[145]: HCI dev 0 unregistered
Nov 13 18:18:16 ts7200 daemon.info hcid[145]: HCI dev 0 registered
Nov 13 18:18:16 ts7200 daemon.info hcid[145]: HCI dev 0 up
Nov 13 18:18:16 ts7200 daemon.info hcid[145]: Starting security manager 0
Nov 13 18:18:53 ts7200 daemon.info hcid[145]: HCI dev 1 registered
Nov 13 18:18:53 ts7200 daemon.err hcid[186]: Can't init device hci1: No such
device (19)
Nov 13 18:18:53 ts7200 daemon.info hcid[145]: HCI dev 1 unregistered
Nov 13 18:18:53 ts7200 daemon.info hcid[145]: HCI dev 1 registered
Nov 13 18:19:03 ts7200 daemon.err hcid[195]: Can't init device hci1:
Connection timed out (110)
cat /proc/bus/usb/devices gives:
$ cat /proc/bus/usb/devices
T: Bus=3D01 Lev=3D00 Prnt=3D00 Port=3D00 Cnt=3D00 Dev#=3D 1 Spd=3D12 MxC=
h=3D 3
B: Alloc=3D 38/900 us ( 4%), #Int=3D 2, #Iso=3D 2
D: Ver=3D 1.10 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D 8 #Cfgs=3D 1
P: Vendor=3D0000 ProdID=3D0000 Rev=3D 0.00
S: Product=3DUSB OHCI Root Hub
S: SerialNumber=3De0020000
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3D40 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 2 Ivl=3D255ms
T: Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D00 Cnt=3D01 Dev#=3D 2 Spd=3D12 MxC=
h=3D 2
D: Ver=3D 2.00 Cls=3D09(hub ) Sub=3D00 Prot=3D00 MxPS=3D64 #Cfgs=3D 1
P: Vendor=3D0409 ProdID=3D005a Rev=3D 1.00
C:* #Ifs=3D 1 Cfg#=3D 1 Atr=3De0 MxPwr=3D100mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 1 Cls=3D09(hub ) Sub=3D00 Prot=3D00 Driver=
=3Dhub
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 1 Ivl=3D255ms
T: Bus=3D01 Lev=3D02 Prnt=3D02 Port=3D00 Cnt=3D01 Dev#=3D 9 Spd=3D12 MxC=
h=3D 0
D: Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 MxPS=3D64 #Cfgs=3D 1
P: Vendor=3D050d ProdID=3D0084 Rev=3D 5.25
C:* #Ifs=3D 3 Cfg#=3D 1 Atr=3Dc0 MxPwr=3D 0mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 16 Ivl=3D1ms
E: Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
E: Ad=3D82(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
I: If#=3D 1 Alt=3D 0 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
I: If#=3D 1 Alt=3D 1 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
I: If#=3D 1 Alt=3D 2 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
I: If#=3D 1 Alt=3D 3 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
I: If#=3D 1 Alt=3D 4 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
I: If#=3D 1 Alt=3D 5 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
I: If#=3D 2 Alt=3D 0 #EPs=3D 0 Cls=3Dfe(app. ) Sub=3D01 Prot=3D00 Driver=
=3D(none)
T: Bus=3D01 Lev=3D01 Prnt=3D01 Port=3D02 Cnt=3D02 Dev#=3D 7 Spd=3D12 MxC=
h=3D 0
D: Ver=3D 1.10 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 MxPS=3D64 #Cfgs=3D 1
P: Vendor=3D0db0 ProdID=3D6970 Rev=3D 5.25
C:* #Ifs=3D 3 Cfg#=3D 1 Atr=3D80 MxPwr=3D100mA
I: If#=3D 0 Alt=3D 0 #EPs=3D 3 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D81(I) Atr=3D03(Int.) MxPS=3D 16 Ivl=3D1ms
E: Ad=3D02(O) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
E: Ad=3D82(I) Atr=3D02(Bulk) MxPS=3D 64 Ivl=3D0ms
I: If#=3D 1 Alt=3D 0 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 0 Ivl=3D1ms
I: If#=3D 1 Alt=3D 1 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 9 Ivl=3D1ms
I: If#=3D 1 Alt=3D 2 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 17 Ivl=3D1ms
I: If#=3D 1 Alt=3D 3 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 25 Ivl=3D1ms
I: If#=3D 1 Alt=3D 4 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 33 Ivl=3D1ms
I: If#=3D 1 Alt=3D 5 #EPs=3D 2 Cls=3De0(unk. ) Sub=3D01 Prot=3D01 Driver=
=3Dhci_usb
E: Ad=3D03(O) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
E: Ad=3D83(I) Atr=3D01(Isoc) MxPS=3D 49 Ivl=3D1ms
I: If#=3D 2 Alt=3D 0 #EPs=3D 0 Cls=3Dfe(app. ) Sub=3D01 Prot=3D00 Driver=
=3D(none)
/ Hakan
-----Ursprungligt meddelande-----
Fr=E5n: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Marcel Holtmann
Skickat: den 13 november 2006 18:44
Till: BlueZ users
=C4mne: Re: [Bluez-users] Problem with 2nd second dongle
Hi,
> OK; But it work with one dongle...
it can be a bug (however I have multiple dongles working without any
problems) or simply a bad dongle or even a USB bus issue.
Regards
Marcel
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job
easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easi=
er
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D120709&bid=3D263057&dat=3D1=
21642
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bluez-users] VB: Problem with 2nd second dongle
2006-11-13 20:39 [Bluez-users] VB: Problem with 2nd second dongle Håkan Lager
@ 2006-11-16 10:32 ` Marcel Holtmann
2006-11-18 15:08 ` Håkan Lager
0 siblings, 1 reply; 9+ messages in thread
From: Marcel Holtmann @ 2006-11-16 10:32 UTC (permalink / raw)
To: BlueZ users
Hi Hakan,
> I begin to suspect this is a dbus error. Is there any simple way to check
> this suspicion?
it can't be a D-Bus error. Please try to load the hci_usb driver with
isoc=0. What does "lsusb" actually tell you?
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bluez-users] VB: Problem with 2nd second dongle
2006-11-16 10:32 ` Marcel Holtmann
@ 2006-11-18 15:08 ` Håkan Lager
2006-11-18 18:31 ` Andres Vargas - zodman
0 siblings, 1 reply; 9+ messages in thread
From: Håkan Lager @ 2006-11-18 15:08 UTC (permalink / raw)
To: 'BlueZ users'
[-- Attachment #1: Type: text/plain, Size: 1435 bytes --]
Hi,
Here is the result:
0)
$ ./hcid -n
hcid[205]: Bluetooth HCI daemon
Failed to open connection to system message bus: Failed to connect to socket
/var/run/dbus/system_bus_socket: No such file or directory
hcid[205]: Unable to get on D-BUS
1) $ insmod hci_usb.o isoc=0
Using /bluetooth/mod/hci_usb.o
insmod: invalid parameter isoc
2) See appended file
-----Ursprungligt meddelande-----
Från: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] För Marcel Holtmann
Skickat: den 16 november 2006 11:32
Till: BlueZ users
Ämne: Re: [Bluez-users] VB: Problem with 2nd second dongle
Hi Hakan,
> I begin to suspect this is a dbus error. Is there any simple way to check
> this suspicion?
it can't be a D-Bus error. Please try to load the hci_usb driver with
isoc=0. What does "lsusb" actually tell you?
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
[-- Attachment #2: lsusb --]
[-- Type: application/octet-stream, Size: 20977 bytes --]
Bus 001 Device 001: ID 0000:0000 Virtual Hub
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000 Virtual
idProduct 0x0000 Hub
bcdDevice 0.00
iManufacturer 0
iProduct 2 USB OHCI Root Hub
iSerial 1 e0020000
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x40
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 255
Language IDs: (length=4)
0000 (null)((null))
Bus 001 Device 002: ID 0409:005a NEC Systems
Language IDs: none (cannot get min. string descriptor; got len=-1, error=32:Broken pipe)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x0409 NEC Systems
idProduct 0x005a
bcdDevice 1.00
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 1
bInterval 255
Language IDs: none (cannot get min. string descriptor; got len=-1, error=32:Broken pipe)
Bus 001 Device 009: ID 0a5c:200a Broadcom Corp.
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 224
bDeviceSubClass 1
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0a5c Broadcom Corp.
idProduct 0x200a
bcdDevice 0.01
iManufacturer 1 Broadcom
iProduct 2 BCM92035DGROM
iSerial 3 000EA13427B6
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 200
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 16
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 0
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 0
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 9
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 9
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 17
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 17
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 32
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 32
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 64
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 64
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 64
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 64
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 255 Vendor Specific Protocol
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 32
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 32
bInterval 1
Language IDs: (length=4)
0409 English(US)
Bus 001 Device 010: ID 0db0:6970
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 224
bDeviceSubClass 1
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x0db0
idProduct 0x6970
bcdDevice 5.25
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 193
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 16
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 0
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 0
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 9
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 9
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 17
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 17
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 25
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 25
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 33
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 33
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224
bInterfaceSubClass 1
bInterfaceProtocol 1
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 49
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 49
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254
bInterfaceSubClass 1
bInterfaceProtocol 0
iInterface 0
unknown descriptor type: 07 21 07 88 13 ff 03
Language IDs: (length=4)
0409 English(US)
[-- Attachment #3: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #4: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [Bluez-users] VB: Problem with 2nd second dongle
2006-11-18 15:08 ` Håkan Lager
@ 2006-11-18 18:31 ` Andres Vargas - zodman
2006-11-18 17:02 ` Håkan Lager
0 siblings, 1 reply; 9+ messages in thread
From: Andres Vargas - zodman @ 2006-11-18 18:31 UTC (permalink / raw)
To: bluez-users
you need start the dbus daemon
/etc/init.d/dbus start
On Sat, 18 Nov 2006 16:08:04 +0100
H=E5kan Lager <hakan@digiloo.net> wrote:
> =
> Hi,
> =
> Here is the result:
> =
> 0)
> =
> $ ./hcid -n
> hcid[205]: Bluetooth HCI daemon
> Failed to open connection to system message bus: Failed to connect to soc=
ket
> /var/run/dbus/system_bus_socket: No such file or directory
> =
> hcid[205]: Unable to get on D-BUS
> =
> 1) $ insmod hci_usb.o isoc=3D0
> Using /bluetooth/mod/hci_usb.o
> insmod: invalid parameter isoc
> =
> 2) See appended file =
> =
> =
> -----Ursprungligt meddelande-----
> Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Marcel Holtmann
> Skickat: den 16 november 2006 11:32
> Till: BlueZ users
> =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> =
> Hi Hakan,
> =
> > I begin to suspect this is a dbus error. Is there any simple way to che=
ck
> > this suspicion?
> =
> it can't be a D-Bus error. Please try to load the hci_usb driver with
> isoc=3D0. What does "lsusb" actually tell you?
> =
> Regards
> =
> Marcel
> =
> =
> =
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share y=
our
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-- =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bluez-users] VB: Problem with 2nd second dongle
2006-11-18 18:31 ` Andres Vargas - zodman
@ 2006-11-18 17:02 ` Håkan Lager
2006-11-18 21:40 ` Andres Vargas - zodman
0 siblings, 1 reply; 9+ messages in thread
From: Håkan Lager @ 2006-11-18 17:02 UTC (permalink / raw)
To: 'BlueZ users'
Do I need dbus if I only use BT for sending?
/ Hakan
-----Ursprungligt meddelande-----
Fr=E5n: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
zodman
Skickat: den 18 november 2006 19:32
Till: bluez-users@lists.sourceforge.net
=C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
you need start the dbus daemon
/etc/init.d/dbus start
On Sat, 18 Nov 2006 16:08:04 +0100
H=E5kan Lager <hakan@digiloo.net> wrote:
> =
> Hi,
> =
> Here is the result:
> =
> 0)
> =
> $ ./hcid -n
> hcid[205]: Bluetooth HCI daemon
> Failed to open connection to system message bus: Failed to connect to
socket
> /var/run/dbus/system_bus_socket: No such file or directory
> =
> hcid[205]: Unable to get on D-BUS
> =
> 1) $ insmod hci_usb.o isoc=3D0
> Using /bluetooth/mod/hci_usb.o
> insmod: invalid parameter isoc
> =
> 2) See appended file =
> =
> =
> -----Ursprungligt meddelande-----
> Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Marcel Holtmann
> Skickat: den 16 november 2006 11:32
> Till: BlueZ users
> =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> =
> Hi Hakan,
> =
> > I begin to suspect this is a dbus error. Is there any simple way to
check
> > this suspicion?
> =
> it can't be a D-Bus error. Please try to load the hci_usb driver with
> isoc=3D0. What does "lsusb" actually tell you?
> =
> Regards
> =
> Marcel
> =
> =
> =
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-- =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bluez-users] VB: Problem with 2nd second dongle
2006-11-18 17:02 ` Håkan Lager
@ 2006-11-18 21:40 ` Andres Vargas - zodman
2006-11-18 20:04 ` Håkan Lager
0 siblings, 1 reply; 9+ messages in thread
From: Andres Vargas - zodman @ 2006-11-18 21:40 UTC (permalink / raw)
To: bluez-users
yeap because hcid function with dbus
lagrutadelzod:/home/andy# /etc/init.d/dbus stop
Stopping system message bus: dbus.
lagrutadelzod:/home/andy# pkill hcid
lagrutadelzod:/home/andy# hcid -n -f /etc/bluetooth/hcid.conf
hcid[18150]: Bluetooth HCI daemon
hcid[18150]: Unknown option 'piscan' line 12
hcid[18150]: Can't open system message bus connection: Failed to
connect to socket /var/run/dbus/system_bus_socket: No such file or
directory hcid[18150]: Unable to get on D-Bus
:'(
lagrutadelzod:/home/andy# /etc/init.d/dbus start
Starting system message bus: dbus.
lagrutadelzod:/home/andy# hcid -n -f /etc/bluetooth/hcid.conf
hcid[18161]: Bluetooth HCI daemon
hcid[18161]: Unknown option 'piscan' line 12
hcid[18161]: Register path:/org/bluez fallback:1
hcid[18161]: HCI dev 0 registered
hcid[18161]: Register path:/org/bluez/hci0 fallback:0
hcid[18161]: HCI dev 0 already up
hcid[18161]: Device hci0 has been added
hcid[18161]: Starting security manager 0
hcid[18161]: Device hci0 has been activated
:PPPPPPPPPPPPPPPPPP
the hcid needs dbus .... =
On Sat, 18 Nov 2006 18:02:14 +0100
H=E5kan Lager <hakan@digiloo.net> wrote:
> Do I need dbus if I only use BT for sending?
> =
> / Hakan
> =
> =
> -----Ursprungligt meddelande-----
> Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
> zodman
> Skickat: den 18 november 2006 19:32
> Till: bluez-users@lists.sourceforge.net
> =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> =
> you need start the dbus daemon
> =
> /etc/init.d/dbus start
> =
> On Sat, 18 Nov 2006 16:08:04 +0100
> H=E5kan Lager <hakan@digiloo.net> wrote:
> =
> > =
> > Hi,
> > =
> > Here is the result:
> > =
> > 0)
> > =
> > $ ./hcid -n
> > hcid[205]: Bluetooth HCI daemon
> > Failed to open connection to system message bus: Failed to connect to
> socket
> > /var/run/dbus/system_bus_socket: No such file or directory
> > =
> > hcid[205]: Unable to get on D-BUS
> > =
> > 1) $ insmod hci_usb.o isoc=3D0
> > Using /bluetooth/mod/hci_usb.o
> > insmod: invalid parameter isoc
> > =
> > 2) See appended file =
> > =
> > =
> > -----Ursprungligt meddelande-----
> > Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> > [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Marcel Holtmann
> > Skickat: den 16 november 2006 11:32
> > Till: BlueZ users
> > =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> > =
> > Hi Hakan,
> > =
> > > I begin to suspect this is a dbus error. Is there any simple way to
> check
> > > this suspicion?
> > =
> > it can't be a D-Bus error. Please try to load the hci_usb driver with
> > isoc=3D0. What does "lsusb" actually tell you?
> > =
> > Regards
> > =
> > Marcel
> > =
> > =
> > =
> > -----------------------------------------------------------------------=
--
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> > http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=
=3DDEVDEV
> > _______________________________________________
> > Bluez-users mailing list
> > Bluez-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-users
> =
> =
-- =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bluez-users] VB: Problem with 2nd second dongle
2006-11-18 21:40 ` Andres Vargas - zodman
@ 2006-11-18 20:04 ` Håkan Lager
2006-11-18 23:01 ` Andres Vargas - zodman
0 siblings, 1 reply; 9+ messages in thread
From: Håkan Lager @ 2006-11-18 20:04 UTC (permalink / raw)
To: 'BlueZ users'
Also if the pin asking thing is commented in hcid.conf?
/ Hakan
-----Ursprungligt meddelande-----
Fr=E5n: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
zodman
Skickat: den 18 november 2006 22:41
Till: bluez-users@lists.sourceforge.net
=C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
yeap because hcid function with dbus
lagrutadelzod:/home/andy# /etc/init.d/dbus stop
Stopping system message bus: dbus.
lagrutadelzod:/home/andy# pkill hcid
lagrutadelzod:/home/andy# hcid -n -f /etc/bluetooth/hcid.conf
hcid[18150]: Bluetooth HCI daemon
hcid[18150]: Unknown option 'piscan' line 12
hcid[18150]: Can't open system message bus connection: Failed to
connect to socket /var/run/dbus/system_bus_socket: No such file or
directory hcid[18150]: Unable to get on D-Bus
:'(
lagrutadelzod:/home/andy# /etc/init.d/dbus start
Starting system message bus: dbus.
lagrutadelzod:/home/andy# hcid -n -f /etc/bluetooth/hcid.conf
hcid[18161]: Bluetooth HCI daemon
hcid[18161]: Unknown option 'piscan' line 12
hcid[18161]: Register path:/org/bluez fallback:1
hcid[18161]: HCI dev 0 registered
hcid[18161]: Register path:/org/bluez/hci0 fallback:0
hcid[18161]: HCI dev 0 already up
hcid[18161]: Device hci0 has been added
hcid[18161]: Starting security manager 0
hcid[18161]: Device hci0 has been activated
:PPPPPPPPPPPPPPPPPP
the hcid needs dbus .... =
On Sat, 18 Nov 2006 18:02:14 +0100
H=E5kan Lager <hakan@digiloo.net> wrote:
> Do I need dbus if I only use BT for sending?
> =
> / Hakan
> =
> =
> -----Ursprungligt meddelande-----
> Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
> zodman
> Skickat: den 18 november 2006 19:32
> Till: bluez-users@lists.sourceforge.net
> =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> =
> you need start the dbus daemon
> =
> /etc/init.d/dbus start
> =
> On Sat, 18 Nov 2006 16:08:04 +0100
> H=E5kan Lager <hakan@digiloo.net> wrote:
> =
> > =
> > Hi,
> > =
> > Here is the result:
> > =
> > 0)
> > =
> > $ ./hcid -n
> > hcid[205]: Bluetooth HCI daemon
> > Failed to open connection to system message bus: Failed to connect to
> socket
> > /var/run/dbus/system_bus_socket: No such file or directory
> > =
> > hcid[205]: Unable to get on D-BUS
> > =
> > 1) $ insmod hci_usb.o isoc=3D0
> > Using /bluetooth/mod/hci_usb.o
> > insmod: invalid parameter isoc
> > =
> > 2) See appended file =
> > =
> > =
> > -----Ursprungligt meddelande-----
> > Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> > [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Marcel Holtmann
> > Skickat: den 16 november 2006 11:32
> > Till: BlueZ users
> > =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> > =
> > Hi Hakan,
> > =
> > > I begin to suspect this is a dbus error. Is there any simple way to
> check
> > > this suspicion?
> > =
> > it can't be a D-Bus error. Please try to load the hci_usb driver with
> > isoc=3D0. What does "lsusb" actually tell you?
> > =
> > Regards
> > =
> > Marcel
> > =
> > =
> > =
> >
-------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> > opinions on IT & business topics through brief surveys - and earn cash
> >
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
> > _______________________________________________
> > Bluez-users mailing list
> > Bluez-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/bluez-users
> =
> =
-- =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bluez-users] VB: Problem with 2nd second dongle
2006-11-18 20:04 ` Håkan Lager
@ 2006-11-18 23:01 ` Andres Vargas - zodman
2006-11-19 1:45 ` Håkan Lager
0 siblings, 1 reply; 9+ messages in thread
From: Andres Vargas - zodman @ 2006-11-18 23:01 UTC (permalink / raw)
To: bluez-users
yeap search on your hcid.conf file for the pin ..... in debian default is 1=
234
On Sat, 18 Nov 2006 21:04:29 +0100
H=E5kan Lager <hakan@digiloo.net> wrote:
> Also if the pin asking thing is commented in hcid.conf?
> =
> / Hakan
> =
> -----Ursprungligt meddelande-----
> Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
> zodman
> Skickat: den 18 november 2006 22:41
> Till: bluez-users@lists.sourceforge.net
> =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> =
> yeap because hcid function with dbus
> =
> lagrutadelzod:/home/andy# /etc/init.d/dbus stop
> Stopping system message bus: dbus.
> lagrutadelzod:/home/andy# pkill hcid
> lagrutadelzod:/home/andy# hcid -n -f /etc/bluetooth/hcid.conf
> hcid[18150]: Bluetooth HCI daemon
> hcid[18150]: Unknown option 'piscan' line 12
> hcid[18150]: Can't open system message bus connection: Failed to
> connect to socket /var/run/dbus/system_bus_socket: No such file or
> directory hcid[18150]: Unable to get on D-Bus
> =
> :'(
> =
> lagrutadelzod:/home/andy# /etc/init.d/dbus start
> Starting system message bus: dbus.
> lagrutadelzod:/home/andy# hcid -n -f /etc/bluetooth/hcid.conf
> hcid[18161]: Bluetooth HCI daemon
> hcid[18161]: Unknown option 'piscan' line 12
> hcid[18161]: Register path:/org/bluez fallback:1
> hcid[18161]: HCI dev 0 registered
> hcid[18161]: Register path:/org/bluez/hci0 fallback:0
> hcid[18161]: HCI dev 0 already up
> hcid[18161]: Device hci0 has been added
> hcid[18161]: Starting security manager 0
> hcid[18161]: Device hci0 has been activated
> =
> :PPPPPPPPPPPPPPPPPP
> =
> the hcid needs dbus .... =
> =
> On Sat, 18 Nov 2006 18:02:14 +0100
> H=E5kan Lager <hakan@digiloo.net> wrote:
> =
> > Do I need dbus if I only use BT for sending?
> > =
> > / Hakan
> > =
> > =
> > -----Ursprungligt meddelande-----
> > Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> > [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
> > zodman
> > Skickat: den 18 november 2006 19:32
> > Till: bluez-users@lists.sourceforge.net
> > =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> > =
> > you need start the dbus daemon
> > =
> > /etc/init.d/dbus start
> > =
> > On Sat, 18 Nov 2006 16:08:04 +0100
> > H=E5kan Lager <hakan@digiloo.net> wrote:
> > =
> > > =
> > > Hi,
> > > =
> > > Here is the result:
> > > =
> > > 0)
> > > =
> > > $ ./hcid -n
> > > hcid[205]: Bluetooth HCI daemon
> > > Failed to open connection to system message bus: Failed to connect to
> > socket
> > > /var/run/dbus/system_bus_socket: No such file or directory
> > > =
> > > hcid[205]: Unable to get on D-BUS
> > > =
> > > 1) $ insmod hci_usb.o isoc=3D0
> > > Using /bluetooth/mod/hci_usb.o
> > > insmod: invalid parameter isoc
> > > =
> > > 2) See appended file =
> > > =
> > > =
> > > -----Ursprungligt meddelande-----
> > > Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> > > [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Marcel Holtm=
ann
> > > Skickat: den 16 november 2006 11:32
> > > Till: BlueZ users
> > > =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> > > =
> > > Hi Hakan,
> > > =
> > > > I begin to suspect this is a dbus error. Is there any simple way to
> > check
> > > > this suspicion?
> > > =
> > > it can't be a D-Bus error. Please try to load the hci_usb driver with
> > > isoc=3D0. What does "lsusb" actually tell you?
> > > =
> > > Regards
> > > =
> > > Marcel
> > > =
> > > =
> > > =
> > >
> -------------------------------------------------------------------------
> > > Take Surveys. Earn Cash. Influence the Future of IT
> > > Join SourceForge.net's Techsay panel and you'll get the chance to sha=
re
> > your
> > > opinions on IT & business topics through brief surveys - and earn cash
> > >
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> > > _______________________________________________
> > > Bluez-users mailing list
> > > Bluez-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bluez-users
> > =
> > =
> =
> =
-- =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [Bluez-users] VB: Problem with 2nd second dongle
2006-11-18 23:01 ` Andres Vargas - zodman
@ 2006-11-19 1:45 ` Håkan Lager
0 siblings, 0 replies; 9+ messages in thread
From: Håkan Lager @ 2006-11-19 1:45 UTC (permalink / raw)
To: 'BlueZ users'
Hi,
My question was if dbus really was needed if the =
pin_helper /usr/bin/cw_pin.pl;
is removed from hcid.conf
/ Hakan
-----Ursprungligt meddelande-----
Fr=E5n: bluez-users-bounces@lists.sourceforge.net
[mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
zodman
Skickat: den 19 november 2006 00:02
Till: bluez-users@lists.sourceforge.net
=C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
yeap search on your hcid.conf file for the pin ..... in debian default is
1234
On Sat, 18 Nov 2006 21:04:29 +0100
H=E5kan Lager <hakan@digiloo.net> wrote:
> Also if the pin asking thing is commented in hcid.conf?
> =
> / Hakan
> =
> -----Ursprungligt meddelande-----
> Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
> zodman
> Skickat: den 18 november 2006 22:41
> Till: bluez-users@lists.sourceforge.net
> =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> =
> yeap because hcid function with dbus
> =
> lagrutadelzod:/home/andy# /etc/init.d/dbus stop
> Stopping system message bus: dbus.
> lagrutadelzod:/home/andy# pkill hcid
> lagrutadelzod:/home/andy# hcid -n -f /etc/bluetooth/hcid.conf
> hcid[18150]: Bluetooth HCI daemon
> hcid[18150]: Unknown option 'piscan' line 12
> hcid[18150]: Can't open system message bus connection: Failed to
> connect to socket /var/run/dbus/system_bus_socket: No such file or
> directory hcid[18150]: Unable to get on D-Bus
> =
> :'(
> =
> lagrutadelzod:/home/andy# /etc/init.d/dbus start
> Starting system message bus: dbus.
> lagrutadelzod:/home/andy# hcid -n -f /etc/bluetooth/hcid.conf
> hcid[18161]: Bluetooth HCI daemon
> hcid[18161]: Unknown option 'piscan' line 12
> hcid[18161]: Register path:/org/bluez fallback:1
> hcid[18161]: HCI dev 0 registered
> hcid[18161]: Register path:/org/bluez/hci0 fallback:0
> hcid[18161]: HCI dev 0 already up
> hcid[18161]: Device hci0 has been added
> hcid[18161]: Starting security manager 0
> hcid[18161]: Device hci0 has been activated
> =
> :PPPPPPPPPPPPPPPPPP
> =
> the hcid needs dbus .... =
> =
> On Sat, 18 Nov 2006 18:02:14 +0100
> H=E5kan Lager <hakan@digiloo.net> wrote:
> =
> > Do I need dbus if I only use BT for sending?
> > =
> > / Hakan
> > =
> > =
> > -----Ursprungligt meddelande-----
> > Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> > [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Andres Vargas -
> > zodman
> > Skickat: den 18 november 2006 19:32
> > Till: bluez-users@lists.sourceforge.net
> > =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> > =
> > you need start the dbus daemon
> > =
> > /etc/init.d/dbus start
> > =
> > On Sat, 18 Nov 2006 16:08:04 +0100
> > H=E5kan Lager <hakan@digiloo.net> wrote:
> > =
> > > =
> > > Hi,
> > > =
> > > Here is the result:
> > > =
> > > 0)
> > > =
> > > $ ./hcid -n
> > > hcid[205]: Bluetooth HCI daemon
> > > Failed to open connection to system message bus: Failed to connect to
> > socket
> > > /var/run/dbus/system_bus_socket: No such file or directory
> > > =
> > > hcid[205]: Unable to get on D-BUS
> > > =
> > > 1) $ insmod hci_usb.o isoc=3D0
> > > Using /bluetooth/mod/hci_usb.o
> > > insmod: invalid parameter isoc
> > > =
> > > 2) See appended file =
> > > =
> > > =
> > > -----Ursprungligt meddelande-----
> > > Fr=E5n: bluez-users-bounces@lists.sourceforge.net
> > > [mailto:bluez-users-bounces@lists.sourceforge.net] F=F6r Marcel Holtm=
ann
> > > Skickat: den 16 november 2006 11:32
> > > Till: BlueZ users
> > > =C4mne: Re: [Bluez-users] VB: Problem with 2nd second dongle
> > > =
> > > Hi Hakan,
> > > =
> > > > I begin to suspect this is a dbus error. Is there any simple way to
> > check
> > > > this suspicion?
> > > =
> > > it can't be a D-Bus error. Please try to load the hci_usb driver with
> > > isoc=3D0. What does "lsusb" actually tell you?
> > > =
> > > Regards
> > > =
> > > Marcel
> > > =
> > > =
> > > =
> > >
> -------------------------------------------------------------------------
> > > Take Surveys. Earn Cash. Influence the Future of IT
> > > Join SourceForge.net's Techsay panel and you'll get the chance to
share
> > your
> > > opinions on IT & business topics through brief surveys - and earn cash
> > >
> http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3D=
DEVDEV
> > > _______________________________________________
> > > Bluez-users mailing list
> > > Bluez-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/bluez-users
> > =
> > =
> =
> =
-- =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2006-11-19 1:45 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-11-13 20:39 [Bluez-users] VB: Problem with 2nd second dongle Håkan Lager
2006-11-16 10:32 ` Marcel Holtmann
2006-11-18 15:08 ` Håkan Lager
2006-11-18 18:31 ` Andres Vargas - zodman
2006-11-18 17:02 ` Håkan Lager
2006-11-18 21:40 ` Andres Vargas - zodman
2006-11-18 20:04 ` Håkan Lager
2006-11-18 23:01 ` Andres Vargas - zodman
2006-11-19 1:45 ` Håkan Lager
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox