Linux bluetooth development
 help / color / mirror / Atom feed
From: nicolas <n1c0l4s.l3@wanadoo.fr>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Re: inactivity of my Bt
Date: Thu, 24 Jun 2004 00:47:38 +0200	[thread overview]
Message-ID: <200406240047.38462.n1c0l4s.l3@wanadoo.fr> (raw)
In-Reply-To: <1088029418.4296.9.camel@pegasus>

Le jeudi 24 Juin 2004 00:23, Marcel Holtmann a =E9crit=A0:
> Hi Nicolas,
>
> > > > i have with your advices installed my bluetooth  but i have a big
> > > > problem, if i let my bluetooth alone a time too long 10-15 min   i
> > > > lost my bluetooth and i have to use a ps/2 or usb keyboard/ mouse to
> > > > reinstall ( hcitool inq  scan and hidd -c )
> > > >
> > > > there is a way to keep it alive ?
> > >
> > > mostly every HID will disconnect after some time. Start "hidd --serve=
r"
> > > at boot time and your mouse or keyboard will reconnect after a
> > > keypress.
> >
> > and how can i start "hidd --server" at boot time?
>
> the bluez-utils-2.7 (and also the Debian package) contains an init
> script that will do this for you.

i have all installed this rpm from my distrib

bluez-bluefw-1.0-1mdk
bluez-utils-2.7-4mdk
bluez-hciemu-1.0-2mdk
libbluez1-2.7-1mdk
bluez-hcidump-1.8-1mdk
libbluez1-devel-2.7-1mdk

and there is no bluetooth service in my mcc but service bluetooth start   w=
ork

so  what have i to do?
there is a packaging bug?  ( in this case i will mail the packager rapidly)



thanks
>
> Regards
>
> Marcel
>
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-devel

=2D-=20
Ce mail a =E9t=E9 =E9crit sous linux mandrake cooker (www.linux-mandrake.co=
m/fr)
avec KMail 1.6.2 (www.kde.org)

Kernel: 2.6.7-2mdk
Kde 3.2.3


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2004-06-23 22:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200406232055.06709.n1c0l4s.l3@wanadoo.fr>
     [not found] ` <1088028819.4296.7.camel@pegasus>
2004-06-23 22:28   ` inactivity of my Bt nicolas
2004-06-23 22:23     ` [Bluez-devel] " Marcel Holtmann
2004-06-23 22:47       ` nicolas [this message]
2004-06-23 22:50       ` nicolas
2004-06-23 22:46         ` Marcel Holtmann
2004-06-24 17:32           ` nicolas
2004-06-24 17:32             ` Marcel Holtmann
2004-06-24 18:15               ` nicolas
2004-06-24 19:56                 ` Marcel Holtmann
2004-06-24 20:35                   ` nicolas
2004-06-24 20:35                     ` Marcel Holtmann
     [not found]                       ` <200406242245.43321.n1c0l4s.l3@wanadoo.fr>
2004-06-24 20:54                         ` 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=200406240047.38462.n1c0l4s.l3@wanadoo.fr \
    --to=n1c0l4s.l3@wanadoo.fr \
    --cc=bluez-devel@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