public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] Bluetooth Setup
@ 2009-06-10 10:56 dhk
  0 siblings, 0 replies; only message in thread
From: dhk @ 2009-06-10 10:56 UTC (permalink / raw
  To: gentoo-user

I'm on an amd64 machine.  Ever since I emerged some bluetooth programs 
(from http://www.gentoo.org/doc/en/bluetooth-guide.xml) to set up a 
bluetooth dongle my /var/log/kern.log gets filled up with messages like 
the following.

Jun 10 06:26:51 host2 hci_scodata_packet: hci0 SCO packet for unknown 
connection handle 92

About 330 of these line get written to kern.log a second and eventually 
my /var partition gets filled up.

Even after stopping bluetooth (/etc/init.d/bluetooth stop) these 
messages still get written to the log.

The setup seemed to go well, but I don't have the sdpd process.

When I start bluetooth I get . . .
# /etc/init.d/bluetooth start
  * Starting Bluetooth ...
  *     Starting hcid ...     [ ok ]
  *     Starting rfcomm ...   [ ok ]

The documentation says I should get . . .
# /etc/init.d/bluetooth start
  * Starting Bluetooth ...
  *     Starting hcid ...     [ ok ]
  *     Starting sdpd ...     [ ok ]
  *     Starting rfcomm ...   [ ok ]

I can find to much about the sdpd process.  What does it do?  Is it 
needed or deprecated?

The two problems I'm having are:
   1) The kern.log filling up which should stop once the setup is 
correct, but until then I'd like to be able to stop whatever is doing it.
   2) The sdpd process, I don't know why it didn't get installed and if 
that's causing me problems.


The documentation to setup bluetooth seemed easy, I don't know why it 
didn't work.

Thanks,
--dhk






^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2009-06-10 10:56 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-10 10:56 [gentoo-user] Bluetooth Setup dhk

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox