usb dongle
I have a Broadcom BCM92035DGROM dongle, and this is what I'm seeing. I'm assuming it's not supported, (from the handbook: The Broadcom BCM2033 chip based Bluetooth devices are supported via the ubtbcmfw(4) and ng_ubt(4) drivers) Is there anyone that's gotten this model to work, or is it an exercise in futility? FreeBSD 6.2-STABLE #0: Mon May 14 15:21:30 EDT 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/FORTYTWO kldstat: 61 0xc60ed000 3000 ubtbcmfw.ko 71 0xc9e1f000 7000 ng_ubt.ko Nov 8 15:01:03 fortytwo kernel: ubt0: Broadcom BCM92035DGROM, rev 1.10/1.09, addr 2 Nov 8 15:01:03 fortytwo kernel: ubt0: Broadcom BCM92035DGROM, rev 1.10/1.09, addr 2 Nov 8 15:01:03 fortytwo kernel: ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 Nov 8 15:01:03 fortytwo kernel: ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 Nov 8 15:01:03 fortytwo root: /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 -- If you can't beat your computer at chess, try kickboxing. --- --- --- Solving Today's Problems Tomorrow ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb dongle
On 11/8/07, Jimmie James [EMAIL PROTECTED] wrote: Maksim Yevmenkin wrote: On 11/8/07, Jimmie James [EMAIL PROTECTED] wrote: I have a Broadcom BCM92035DGROM dongle, and this is what I'm seeing. I'm assuming it's not supported, (from the handbook: The Broadcom BCM2033 chip based Bluetooth devices are supported via the ubtbcmfw(4) and ng_ubt(4) drivers) Is there anyone that's gotten this model to work, or is it an exercise in futility? first of all, i doubt that BCM92035 is using 2033 chip. i think it is uses different (2035?) chip. it also appears that this particular dongle may need to use special non-standard initialization sequence. can you please check vendor id/product id pair for your dongle (use usbdevs(8)). 1) if it is (0x0a5c, 0x200a) then you could try to comment out reset command in /etc/rc.d/bluetooth 2) if it is (x0a5c, 0x2009) then you out of luck - this device needs special non-standard initialization sequence. ng_ubt(4) currently does not support that. if i can get this dongle into my hands i can fix ng_ubt(4) thanks, max I was searching google and came across these two threads, http://lists.freebsd.org/pipermail/freebsd-bluetooth/2006-September/000788.html http://www.nabble.com/j2me-bluetooth-app-using-freebsd-bluetooth-stack-t2356546.html So it looked like it was possible... usbdevs -dv shows: port 1 addr 2: full speed, power 100 mA, config 1, BCM92035DGROM(0x0850), Broadcom(0x22b8), rev 1.09 ubt0 huh?? very strange. not sure why your dongle says its broadcom, where is vendor id 0x22b8 is for motorola. the product is 0850 seems to be for motorola pc850 dongle. 1) please check /var/log/messages to see if there are any errors from ng_ubt(4) driver 2) please install hcidump from ports (comms/hcidump) and then as root make sure device is not connected # kldload ng_btsocket -- this may fail if ng_btsocket module was already loaded, ignore it. # hcidump -w init.dump -- this will block now attach the device and wait for it to fail terminate hcidump with ^c and send me the init.dump file thanks, max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb dongle
Maksim Yevmenkin wrote: On 11/8/07, Jimmie James [EMAIL PROTECTED] wrote: I have a Broadcom BCM92035DGROM dongle, and this is what I'm seeing. I'm assuming it's not supported, (from the handbook: The Broadcom BCM2033 chip based Bluetooth devices are supported via the ubtbcmfw(4) and ng_ubt(4) drivers) Is there anyone that's gotten this model to work, or is it an exercise in futility? first of all, i doubt that BCM92035 is using 2033 chip. i think it is uses different (2035?) chip. it also appears that this particular dongle may need to use special non-standard initialization sequence. can you please check vendor id/product id pair for your dongle (use usbdevs(8)). 1) if it is (0x0a5c, 0x200a) then you could try to comment out reset command in /etc/rc.d/bluetooth 2) if it is (x0a5c, 0x2009) then you out of luck - this device needs special non-standard initialization sequence. ng_ubt(4) currently does not support that. if i can get this dongle into my hands i can fix ng_ubt(4) thanks, max I was searching google and came across these two threads, http://lists.freebsd.org/pipermail/freebsd-bluetooth/2006-September/000788.html http://www.nabble.com/j2me-bluetooth-app-using-freebsd-bluetooth-stack-t2356546.html So it looked like it was possible... usbdevs -dv shows: port 1 addr 2: full speed, power 100 mA, config 1, BCM92035DGROM(0x0850), Broadcom(0x22b8), rev 1.09 ubt0 If you need anything else, I'll do what I can. Thanks Jimmie -- If you can't beat your computer at chess, try kickboxing. --- --- --- Solving Today's Problems Tomorrow ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb dongle
On 11/8/07, Jimmie James [EMAIL PROTECTED] wrote: I have a Broadcom BCM92035DGROM dongle, and this is what I'm seeing. I'm assuming it's not supported, (from the handbook: The Broadcom BCM2033 chip based Bluetooth devices are supported via the ubtbcmfw(4) and ng_ubt(4) drivers) Is there anyone that's gotten this model to work, or is it an exercise in futility? first of all, i doubt that BCM92035 is using 2033 chip. i think it is uses different (2035?) chip. it also appears that this particular dongle may need to use special non-standard initialization sequence. can you please check vendor id/product id pair for your dongle (use usbdevs(8)). 1) if it is (0x0a5c, 0x200a) then you could try to comment out reset command in /etc/rc.d/bluetooth 2) if it is (x0a5c, 0x2009) then you out of luck - this device needs special non-standard initialization sequence. ng_ubt(4) currently does not support that. if i can get this dongle into my hands i can fix ng_ubt(4) thanks, max ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: usb dongle [solved]]
Maksim Yevmenkin wrote: On 11/8/07, Jimmie James [EMAIL PROTECTED] wrote: Maksim Yevmenkin wrote: On 11/8/07, Jimmie James [EMAIL PROTECTED] wrote: I have a Broadcom BCM92035DGROM dongle, and this is what I'm seeing. I'm assuming it's not supported, (from the handbook: The Broadcom BCM2033 chip based Bluetooth devices are supported via the ubtbcmfw(4) and ng_ubt(4) drivers) Is there anyone that's gotten this model to work, or is it an exercise in futility? first of all, i doubt that BCM92035 is using 2033 chip. i think it is uses different (2035?) chip. it also appears that this particular dongle may need to use special non-standard initialization sequence. can you please check vendor id/product id pair for your dongle (use usbdevs(8)). 1) if it is (0x0a5c, 0x200a) then you could try to comment out reset command in /etc/rc.d/bluetooth 2) if it is (x0a5c, 0x2009) then you out of luck - this device needs special non-standard initialization sequence. ng_ubt(4) currently does not support that. if i can get this dongle into my hands i can fix ng_ubt(4) thanks, max I was searching google and came across these two threads, http://lists.freebsd.org/pipermail/freebsd-bluetooth/2006-September/000788.html http://www.nabble.com/j2me-bluetooth-app-using-freebsd-bluetooth-stack-t2356546.html So it looked like it was possible... usbdevs -dv shows: port 1 addr 2: full speed, power 100 mA, config 1, BCM92035DGROM(0x0850), Broadcom(0x22b8), rev 1.09 ubt0 huh?? very strange. not sure why your dongle says its broadcom, where is vendor id 0x22b8 is for motorola. the product is 0850 seems to be for motorola pc850 dongle. 1) please check /var/log/messages to see if there are any errors from ng_ubt(4) driver 2) please install hcidump from ports (comms/hcidump) and then as root make sure device is not connected # kldload ng_btsocket -- this may fail if ng_btsocket module was already loaded, ignore it. # hcidump -w init.dump -- this will block now attach the device and wait for it to fail terminate hcidump with ^c and send me the init.dump file thanks, max Well, after fighting with ng_btsocket, trying to get it to load, and after loading every bluetooth module I could find, it has decided to start working. Messages still things it's a Broadcom, but I can send and receive files. I'm leaning towards a module that wasn't loaded, or an old version (rebuild them all) This helped in finding the applications to transfert he files, and setting up the hosts file. http://lopisaur.blogspot.com/2006/03/bluetooth-freebsd-siemens-s5x-blues.html If there's anything more you need, let me know. Thank you Maksim!! usbdevs -v port 2 addr 2: full speed, power 100 mA, config 1, BCM92035DGROM(0x0850), Broadcom(0x22b8), rev 1.09 104 0xc60ed000 2000 ng_bluetooth.ko 111 0xca458000 19000ng_btsocket.ko 121 0xc9e1f000 7000 ng_ubt.ko 131 0xc9ebb000 d000 ng_hci.ko 141 0xca1e5000 f000 ng_l2cap.ko Nov 8 20:23:19 fortytwo kernel: ubt0: Broadcom BCM92035DGROM, rev 1.10/1.09, addr 2 Nov 8 20:23:19 fortytwo kernel: ubt0: Broadcom BCM92035DGROM, rev 1.10/1.09, addr 2 Nov 8 20:23:19 fortytwo kernel: ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2 Nov 8 20:23:19 fortytwo kernel: ubt0: Interface 1 (alt.config 4) endpoints: isoc-in=0x83, isoc-out=0x3; wMaxPacketSize=64; nframes=5, buffer size=320 Nov 8 20:21:20 fortytwo hcsecd[93960]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr xx:xx:xx:xx:xx:xx Nov 8 20:21:20 fortytwo hcsecd[93960]: Found matching entry, remote bdaddr xx:xx:xx:xx:xx:xx name 'JJ', link key exists Nov 8 20:21:20 fortytwo hcsecd[93960]: Sending Link_Key_Reply to 'ubt0hci' for remote bdaddr xx:xx:xx:xx:xx:xx hccontrol -n ubt0hci inquiry Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: jimmiejaz Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 0x2 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x7b90 Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: jimmiejaz Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 0x2 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x7b90 Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: jimmiejaz Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 0x2 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x7b90 Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: jimmiejaz Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 0x2 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x7b91 Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: jimmiejaz Page Scan Rep. Mode: 0x1 Page Scan Period Mode: 0x2 Page Scan Mode: 00 Class: 52:02:04 Clock offset: 0x7b90 Inquiry result, num_responses=1 Inquiry result #0 BD_ADDR: jimmiejaz Page
