Linux bluetooth development
 help / color / mirror / Atom feed
From: Charles Bueche <charles@bueche.ch>
To: Olivier Bornet <Olivier.Bornet@smartdata.ch>
Cc: BlueZ Developers List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600
Date: Sat, 13 Dec 2003 16:56:35 +0100	[thread overview]
Message-ID: <1071330995.4307.27.camel@bluez.bueche.ch> (raw)
In-Reply-To: <20031210083002.GG26896@smartdata.ch>

Hi Olivier,

Thanks for your answer. I don't run GPM, so the problem isn't from
there. But you gave me another idea : I loaded my modules, started the
patched bthid, exited X, and tried gpm in console. I got the same
problem !!! The mouse is jumpy as well. I think I can now exclude Xfree
from the potential problem.

I guess bthid is producing the jumpy mouse. I tried to checkout the CVS
version, but I'm lost with autoconf and friends. I guess I will have to
wait for Marcel's new snapshot.

What frustrate me is that I got it working twice last week, after
unloading/loading stopping/starting it several times, but I lost the
order and options I had.

Well, we it works, we all have to get a good beer :-)

Charles

On Wed, 2003-12-10 at 09:30, Olivier Bornet wrote:
> Hi Charles,
> 
> > I tried your config, the wheel now works OK. Thanks a lot.
> 
> Great. :-)
> 
> > Another problem appeared after my initial email : the mouse movements
> > are showing sudden accelerations. Makes it difficult to use. I tried
> > several protocols in XF86Config-4, no difference.
> 
> I have add this kind of problem with my USB mouse long time ago. This
> was because I have also gpm working (mouse usage in non grphical
> session). I you need to use gpm at the same time of XFree, you need to
> search on the web, as there is some special config to do. A quick search
> on google give lot of tips for this config. For example
> http://linuxfromscratch.org/pipermail/blfs-dev/2003-April/002637.html
> 
> > I find this strange, as yesterday evening, the mouse suddenly worked
> > fine... I'm getting confused.
> 
> Maybe you have installed gpm ?
> 
> > Could you provide your setup ? hciconfig command, loaded modules, bthid
> > command line, etc ?
> 
> I think as you have it working (maybe bad, but working), your bluetooth
> config is OK (hciconfig command, loaded modules). For the bthid command
> line, I have modified the /etc/init.d/bluetooth-hid file for having the
> command line:
> 
> 	bthid -m -l -s
> 
> > Another question : do I need MOUSEDEV in my kernel ? I have 
> > 
> > CONFIG_INPUT_MOUSEDEV=y
> > CONFIG_INPUT_MOUSEDEV_PSAUX=y
> > CONFIG_INPUT_MOUSEDEV_SCREEN_X=1920
> > CONFIG_INPUT_MOUSEDEV_SCREEN_Y=1200
> 
> I think you need CONFIG_INPUT_MOUSEDEV, but I'm not sure. I have it in
> module. (but as I also have a USB mouse, I really need it).
> 
> > should I remove this ?
> 
> Because XF86Config-4 use /dev/input/mice, I think you really need it.
> 
> Good day.
> 
> 		Olivier
-- 
Charles Bueche <charles@bueche.ch>
sand, snow, wave, wind and net -surfer



-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive?  Does it
help you create better code?  SHARE THE LOVE, and help us help
YOU!  Click Here: http://sourceforge.net/donate/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2003-12-13 15:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-30 14:12 [Bluez-devel] Logitech MX900 mouse with Dell Inspiron 8600 Charles Bueche
2003-11-30 18:51 ` Charles Bueche
2003-12-01 15:38   ` Peter Klausler
2003-12-02 15:55     ` Edd Dumbill
2003-12-02 16:01       ` Edd Dumbill
2003-12-03 20:18         ` Charles Bueche
2003-12-03 20:35           ` Marcel Holtmann
2003-12-04  8:53             ` Olivier Bornet
2003-12-04 13:52               ` Marcel Holtmann
2003-12-04 13:57                 ` Olivier Bornet
2003-12-04 14:10                   ` Marcel Holtmann
2003-12-04 16:35                     ` Olivier Bornet
2003-12-04 17:03                       ` Marcel Holtmann
2003-12-09 20:31               ` Charles Bueche
2003-12-09 22:42                 ` Olivier Bornet
2003-12-10  8:12                   ` Charles Bueche
2003-12-10  8:30                     ` Olivier Bornet
2003-12-13 15:56                       ` Charles Bueche [this message]
2003-12-13 16:39                         ` Marcel Holtmann
2003-12-13 18:51                           ` Charles Bueche
2003-12-13 19:04                             ` Marcel Holtmann
2003-12-14 13:55                               ` Charles Bueche
2003-12-14 14:22                                 ` Marcel Holtmann
2003-12-14 20:01                                   ` Charles Bueche
2003-12-14 20:09                                     ` Marcel Holtmann
2003-12-10  1:41                 ` Marcel Holtmann
2003-12-02 17:39       ` Marcel Holtmann
2003-12-02 17:42         ` Peter Klausler
2003-12-02 17:56           ` Marcel Holtmann
2003-12-03 10:10         ` Stephen Crane
2003-12-03 13:06           ` 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=1071330995.4307.27.camel@bluez.bueche.ch \
    --to=charles@bueche.ch \
    --cc=Olivier.Bornet@smartdata.ch \
    --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