Date: Thu, 16 Jun 2011 10:22:15 -0700 From: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> To: Da Rock <freebsd-bluetooth@herveybayaustralia.com.au> Cc: bluetooth@freebsd.org Subject: Re: Asus bluetooth device - 0x1712 Message-ID: <BANLkTimkagoZ3zvkRKYtDmCyDqt3dKacOA@mail.gmail.com> In-Reply-To: <4DF8430C.3010104@herveybayaustralia.com.au> References: <4DF46049.6080206@herveybayaustralia.com.au> <alpine.NEB.2.00.1106120817050.472@galant.ukfsn.org> <4DF53A6F.9080701@herveybayaustralia.com.au> <alpine.NEB.2.00.1106130738010.14646@galant.ukfsn.org> <BANLkTikGH9nsqgj_ELOM=PakD=4_h-C4Yw@mail.gmail.com> <4DF705C9.7020606@herveybayaustralia.com.au> <alpine.NEB.2.00.1106142057270.1687@galant.ukfsn.org> <4DF7F13C.6090208@herveybayaustralia.com.au> <BANLkTi=5rhWfo38T2x-33OB2y47xQasU9A@mail.gmail.com> <4DF8430C.3010104@herveybayaustralia.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
[...] >>> Probably would if it recognised the product then. What is the correct way >>> to >>> do this then? I know about usbdevs, and the awk script to run, but does >>> anything then need to be added to the driver to pick it up, or should >>> that >>> be all thats needed? >> >> it does not look at the product. it looks at interface class, subclass >> and protocol. are you sure you are loading ng_ubt(4) from loader.conf? >> are there any error messages from ng_ubt(4) in /var/log/messages? > > devd.conf problem then? I haven't got it in loader.conf, but I did kldload- > dmesg output (although the last 2 lines disappear when unloaded/loaded: > > ubt0: <vendor 0x0b05 product 0x1712, class 224/1, rev 2.00/19.15, addr 2> on > usbus5 > WARNING: attempt to domain_add(bluetooth) after domainfinalize() > WARNING: attempt to domain_add(netgraph) after domainfinalize() if you get ubt0 line then device was recognized and attached. those two WARNING messages are harmless > But ls dev shows no devices, and I can't start bluetooth services: ng_ubt(4) does NOT create device nodes in /dev. this question pops up very often. handbook should really be updated to mention this. > /etc/rc.d/bluetooth: ERROR: Unable to setup Bluetooth stack for device ubt0 > > If it should work, then what am I doing wrong? devd(8) will start/stop stack for you automatically. please check devd.conf (look at ubt secion). there is no need to start stack by hand any more. the error is because you are trying to start the stack when its already been started. again, handbook should be updated to reflect that. max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTimkagoZ3zvkRKYtDmCyDqt3dKacOA>