Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Cc: puggy@gentoo.org, bryan@reigndropsfall.net, puggy@bobspants.com
Subject: Re: [Bluez-users] MX900 sometimes catalepsic
Date: Mon, 07 Feb 2005 11:36:19 +0100	[thread overview]
Message-ID: <1107772579.7327.80.camel@pegasus> (raw)
In-Reply-To: <1107771690.23897.23.camel@bluez.bueche.ch>

Hi Charles,

> sorry for the long time before answering, I wanted to be sure the
> problem is really fixed.
> 
> Apart from the good remarks about the MX900 design error (lack of a
> power-switch), the best suggestion came from Marcel :
> 
> Doing this :
> 
> 	/usr/sbin/hciconfig hci0 noscan
> 	/usr/bin/hidd --killall
> 
> at shutdown time avoids the problem, not a single mouse deadlock anymore
> since one week.
> 
> Thanks for you suggestions. I shall update my MX900 web page rsn.

if this works, then this should be inside the Bluetooth init scripts or
inside the hidd with a special option like --shutdown or so.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-02-07 10:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 19:38 [Bluez-users] MX900 sometimes catalepsic Charles Bueche
2005-01-26 17:42 ` Marcel Holtmann
2005-02-07 10:21   ` Charles Bueche
2005-02-07 10:36     ` Marcel Holtmann [this message]
     [not found] <1106636710.13319.6.camel@bluez.bueche.ch>
2005-01-27  0:42 ` Douglas Russell
2005-01-27  5:59   ` Marcel Holtmann
2005-01-27 18:10     ` Bryan Forbes
2005-01-28 16:30       ` puggy

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=1107772579.7327.80.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=bryan@reigndropsfall.net \
    --cc=puggy@bobspants.com \
    --cc=puggy@gentoo.org \
    /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