Date: Fri, 20 Apr 2007 10:46:05 -0700 From: "Maksim Yevmenkin" <maksim.yevmenkin@gmail.com> To: "Christopher McCarley" <chrismccarley@yahoo.com> Cc: freebsd-bluetooth@freebsd.org Subject: Re: bluetooth errors on boot with dongle already attached Message-ID: <bb4a86c70704201046v6dfc1a06td6c02e5918929e0e@mail.gmail.com> In-Reply-To: <341436.85215.qm@web32804.mail.mud.yahoo.com> References: <341436.85215.qm@web32804.mail.mud.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/20/07, Christopher McCarley <chrismccarley@yahoo.com> wrote: > I have not been successful getting bluetooth to work when the dongle is already plugged in before booting up. The error I get is: > > ... could not set alternative configuration 0 for interface 1 .. hmm... never saw that one > I see this error message in the ng_ubt source code, which is consistent with the behavior. If I don't compile ng_bluetooth into the kernel, it works a little better in that I can manually kldload ng_ubt, etc. to get bluetooth to come up. However, *I still have to unplug and plug back in the dongle* before doing this. how about loading ng_ubt from the loader? i.e. add ng_ubt_load="YES" to your loader.conf and reboot. you do not really need to compile bluetooth stuff into the kernel as long as you load ng_ubt(4) early (i.e. from loader). > Is there a known issue related to this? My goal is to run bluetooth on an appliance environment so I really want to get it to work without having to physically touch it. I will continue to debug, but after trying a number of things so far, I want to make sure I am not beating my head against the wall for a known issue. I see this on FreeBSD 6.1 and 6.2 versions. like i said, i never seen it before. it could be some weird usb issue. thanks, max
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bb4a86c70704201046v6dfc1a06td6c02e5918929e0e>