From: joy <gracecott@sancharnet.in>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: mouse not writing to device file.....
Date: Fri, 13 Feb 2004 09:37:05 +0530 [thread overview]
Message-ID: <402C4D69.8050504@sancharnet.in> (raw)
In-Reply-To: 5.1.0.14.1.20040212091018.01f91780@celine
Ray Olszewski wrote:
>
> The problem may be with your test rather than your mouse. I tried to
> duplicate it here -- testing my mouse on a Debian-Sid system -- and
> could not. That is, my mouse works fine in X, accessed through
> /dev/psaux ... but if I try either "cat /dev/psaux" or "cat
> </dev/psaux" and "click away", I too get nothing on the screen (I
> assume that's what you meant by "there is no change in the file").
>
> I don't know *why* Debian and Slack seem to act differently with
> respect to this test, but apparently they do.
>
> So ... you might do better by focusing directly on the X problem.
>
> Are there any messages of interest in X's output to STDERR?
No, there are none, the mouse detection and initialization is fine. the
mouse pointer appears too, but does not move ( got the server o/p using
the man page command startx >$HOME/log 2>&1)
>
> In X, what exactly does "my mouse not working" mean ... does the mouse
> pointer simply not show up at all, or does it show up but move
> erratically in response to mouse movement? Or something else?
>
> Do you possibly have gdm (the mouse app for consoles) running? If so,
> kill it ... it often interferes with access to the mouse by X.
never used gdm..........
>
>
> What happens if you eliminate the reference to /dev/input/mouse in (I
> suppose) /etc/X11/XF86Config-4? Leave just the one to /dev/psaux .
tried that too, changing both to /input/mice and both to /psaux . but
didn't work.
>
> Am I correct in assuming that you have a PS/2 mouse? It normally uses
> the /dev/psaux device ... I'm not sure if /dev/input/mouse also
> accesses this physical device. If you have a different type of mouse
> (serial, USB), please tell us what it is. All my earlier suggestions
> assume you are using a PS/2 mouse.
I have a USB mouse , but it used to work fine froom the same usb port
before the reinstall.....
I do have a PS/2 adapter for the mouse, but I really would like to know
what went wrong before I chicken out and use that....
Thanks,
Joy.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-newbie" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.linux-learn.org/faqs
>
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2004-02-13 4:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 3:45 mouse not writing to device file joy
2004-02-12 17:23 ` Ray Olszewski
2004-02-13 4:07 ` joy [this message]
2004-02-13 4:37 ` Ray Olszewski
2004-02-13 8:57 ` joy
2004-02-13 13:12 ` James Miller
2004-02-13 9:17 ` joy
2004-02-13 15:32 ` James Miller
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=402C4D69.8050504@sancharnet.in \
--to=gracecott@sancharnet.in \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/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