public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurence Orchard <laurence@orchards.org.uk>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Nokia 7610 phone & logitech DiNovo keyboard / MX900 mouse
Date: Sat, 11 Dec 2004 01:11:27 +0000	[thread overview]
Message-ID: <1102727487.6653.6.camel@localhost> (raw)
In-Reply-To: <1102666379.11207.2.camel@pegasus>

On Fri, 2004-12-10 at 09:12 +0100, Marcel Holtmann wrote:
> Hi Laurence,
> 
> > Yes hidd --server --search
> 
> no, only "hidd --server". The search option is only for the first
> connection.
> 
> > run at boot S26hidd in rc5.d
> > after S25bluetooth
> 
> There is a nice init script in bluez-utils that does this all for you
> and with Fedore Core 3 this should be all in place and you only need to
> activate it somewhere. Maybe /etc/default/ or so.
> 
I 
 I took out the --server option,but it still isn't working.
it displays the following message during boot:-
'Can't open RFCOMM console socket: address family not supported by
protocol'

looking back through /var/log/messages I found the following error
messages:- 

Dec 10 23:49:04 localhost rpcidmapd: rpc.idmapd startup succeeded
Dec 10 23:49:04 localhost hcid[2497]: Bluetooth HCI daemon
Dec 10 23:49:04 localhost hcid[2497]: Can't open HCI socket. Address
family not supported by protocol(97)
Dec 10 23:49:04 localhost bluetooth: hcid startup succeeded
Dec 10 23:49:04 localhost sdpd[2503]: init_server: opening L2CAP socket:
Address family not supported by protocol
Dec 10 23:49:04 localhost sdpd[2503]: main: Server initialization failed
Dec 10 23:49:04 localhost bluetooth: sdpd startup succeeded
Dec 10 23:49:05 localhost kernel: usb 1-1.2: new full speed USB device
using address 5

then a little later:-

Dec 10 23:49:06 localhost kernel: Bluetooth: Core ver 2.6
Dec 10 23:49:06 localhost kernel: NET: Registered protocol family 31
Dec 10 23:49:06 localhost kernel: Bluetooth: HCI device and connection
manager initialized
Dec 10 23:49:06 localhost kernel: Bluetooth: HCI socket layer
initialized
Dec 10 23:49:08 localhost kernel: Bluetooth: HCI USB driver ver 2.7
Dec 10 23:49:08 localhost kernel: usbcore: registered new driver hci_usb


any ideas?

-- 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-12-11  1:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-03  0:52 [Bluez-users] Nokia 7610 phone & logitech DiNovo keyboard / MX900 mouse Laurence Orchard
2004-12-03  2:59 ` Marcel Holtmann
2004-12-06  0:00   ` Laurence Orchard
2004-12-06  6:41     ` Marcel Holtmann
2004-12-10  0:51       ` Laurence Orchard
2004-12-10  0:53       ` Laurence Orchard
2004-12-10  8:12         ` Marcel Holtmann
2004-12-11  1:11           ` Laurence Orchard [this message]
2004-12-11  9:12             ` Marcel Holtmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1102727487.6653.6.camel@localhost \
    --to=laurence@orchards.org.uk \
    --cc=bluez-users@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox