Date: Thu, 10 Apr 2014 12:53:04 +0100 From: Chris Whitehouse <cwhiteh@onetel.com> To: freebsd-mobile@freebsd.org Subject: Re: Can't pair FreeBSD laptop and Nokia E72 phone with bluetooth Message-ID: <53468620.6080506@onetel.com> In-Reply-To: <53417B52.50500@onetel.com> References: <532AF631.5000300@onetel.com> <53417B52.50500@onetel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Anyone? Or is bluetooth on FreeBSD dead? thanks Chris On 06/04/2014 17:05, Chris Whitehouse wrote: > Hi, > > previously posted to bluetooth@ and questions@ but no reply so this is > my last hope :) > > I'm hoping I'm just missing a bit of glue somewhere and it's not an > unsupported bluetooth device. > > thanks > > Chris > > On 20/03/2014 14:07, Chris Whitehouse wrote: >> I have a laptop with internal bluetooth module: >> ugen4.3: <Broadcom Corp> at usbus4 >> ubt0: <Broadcom Corp HP Integrated Module, class 224/1, rev 2.00/1.00, >> addr 3> on usbus4 >> >> root@nc-lap:~ # uname -a >> FreeBSD nc-lap.bikerevolution.co.uk 10.0-RELEASE FreeBSD 10.0-RELEASE #0 >> r260789: Thu Jan 16 22:34:59 UTC 2014 >> root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >> >> The devices can see each other but if I try to pair from the phone I get >> a message Unable to pair with nc-lap.bikerevolution.co.uk (ubt0). The >> phone is set to be >> visible to everybody. See below for pairing from the laptop. >> >> loader.conf: >> acpi_dsdt_load="YES" >> acpi_dsdt_name="/boot/nc6320.aml" >> loader_logo="BEASTIE" >> coretemp_load="YES" >> vboxdrv_load="YES" >> tmpfs_load="YES" >> ubtbcmfw_load="YES" >> ng_ubt_load="YES" >> acpi_hp_load="YES" >> >> >> root@nc-lap:~ # kldstat >> Id Refs Address Size Name >> 1 62 0xffffffff80200000 15f0310 kernel >> 2 1 0xffffffff817f1000 49a8 coretemp.ko >> 3 3 0xffffffff81806000 57fb8 vboxdrv.ko >> 4 1 0xffffffff8185e000 118a8 tmpfs.ko >> 5 1 0xffffffff81870000 5120 ubtbcmfw.ko >> 6 1 0xffffffff81876000 9f70 ng_ubt.ko >> 7 2 0xffffffff81880000 10ec0 ng_hci.ko >> 8 4 0xffffffff81891000 3508 ng_bluetooth.ko >> 9 8 0xffffffff81895000 17680 netgraph.ko >> 10 1 0xffffffff818ad000 83c0 acpi_hp.ko >> 11 2 0xffffffff818b6000 7e10 acpi_wmi.ko >> 12 1 0xffffffff81a12000 9bf6 linprocfs.ko >> 13 2 0xffffffff81a1c000 432d4 linux.ko >> 14 1 0xffffffff81a60000 25141 wpifw.ko >> 15 1 0xffffffff81a86000 be53 ng_l2cap.ko >> 16 1 0xffffffff81a92000 19d55 ng_btsocket.ko >> 17 1 0xffffffff81aac000 37c7 ng_socket.ko >> 18 1 0xffffffff81ab0000 34d8 ums.ko >> 19 2 0xffffffff81ab4000 28c0 vboxnetflt.ko >> 20 1 0xffffffff81ab7000 4041 ng_ether.ko >> 21 1 0xffffffff81abc000 3ec0 vboxnetadp.ko >> 22 1 0xffffffff81ac0000 1e7 linux_adobe.ko >> 23 1 0xffffffff81ac1000 c1fe i915.ko >> 24 1 0xffffffff81ace000 16efd drm.ko >> >> root@nc-lap:~ # ngctl list >> There are 10 total nodes: >> Name: ubt0 Type: ubt ID: 00000001 Num >> hooks: 1 >> Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num >> hooks: 1 >> Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num >> hooks: 1 >> Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num >> hooks: 1 >> Name: btsock_sco Type: btsock_sco ID: 00000005 Num >> hooks: 0 >> Name: ubt0hci Type: hci ID: 00000007 Num >> hooks: 3 >> Name: ubt0l2cap Type: l2cap ID: 0000000b Num >> hooks: 3 >> Name: bge0 Type: ether ID: 00000011 Num >> hooks: 0 >> Name: wlan0 Type: ether ID: 00000012 Num >> hooks: 0 >> Name: ngctl1534 Type: socket ID: 00000013 Num >> hooks: 0 >> >> I found somewhere advice to start bluetooth twice: >> >> root@nc-lap:~ # service -v bluetooth start ubt0 >> bluetooth is located in /etc/rc.d >> /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device >> ubt0 >> root@nc-lap:~ # service -v bluetooth start ubt0 >> bluetooth is located in /etc/rc.d >> >> After the first service start /var/log/messages says >> Mar 16 12:37:15 nc-lap chrisw: /etc/rc.d/bluetooth: ERROR: Unable to >> setup Bluetooth stack for device ubt0 >> >> >> root@nc-lap:~ # hccontrol -n ubt0hci inquiry >> Inquiry result, num_responses=1 >> Inquiry result #0 >> BD_ADDR: 30:38:55:8f:22:a7 >> Page Scan Rep. Mode: 0x1 >> Page Scan Period Mode: 00 >> Page Scan Mode: 00 >> Class: 5a:02:0c >> Clock offset: 0x5af2 >> Inquiry complete. Status: No error [00] >> root@nc-lap:~ # hccontrol -n ubt0hci remote_name_request >> 30:38:55:8f:22:a7 >> BD_ADDR: 30:38:55:8f:22:a7 >> Name: miPhone >> >> >> Trying to connect from the laptop: >> >> root@nc-lap:~ # hccontrol -n ubt0hci Create_Connection 30:38:55:8f:22:a7 >> BD_ADDR: 30:38:55:8f:22:a7 >> Connection handle: 11 >> Encryption mode: Disabled [0] >> >> A few seconds later this message appears in /var/log/messages >> Mar 16 13:10:33 nc-lap kernel: ng_l2cap_lp_discon_ind: ubt0l2cap - >> unexpected LP_DisconnectInd event. Connection does not exist, >> con_handle=11 >> >> root@nc-lap:~ # hccontrol -n ubt0hci read_connection_list >> Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State >> >> I've also tried with role switching turned off but it doesn't change >> anything. >> >> These warning messages appear in /var/log/messages >> WARNING: attempt to domain_add(bluetooth) after domainfinalize() >> WARNING: attempt to domain_add(netgraph) after domainfinalize() >> >> Also I don't get messages similar to what the handbook suggests should >> appear: >> ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2ubt0: Interface >> 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2ubt0: Interface 1 >> (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3, wMaxPacketSize=49, >> nframes=6, buffer size=294 > > root@nc-lap:~ # l2ping -a 30:38:55:8f:22:a7 > 0 bytes from 30:38:55:8f:22:a7 seq_no=0 time=773.300 ms result=0 > 0 bytes from 30:38:55:8f:22:a7 seq_no=1 time=43.983 ms result=0 > 0 bytes from 30:38:55:8f:22:a7 seq_no=2 time=20.430 ms result=0 > > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?53468620.6080506>