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 14:27:04 +0530 [thread overview]
Message-ID: <402C9160.3060907@sancharnet.in> (raw)
In-Reply-To: 5.1.0.14.1.20040212202502.01faeaa0@celine
Ray Olszewski wrote:
>>
>> I have a USB mouse , but it used to work fine froom the same usb port
>> before the reinstall.....
>
>
> Do you mean it previously worked with Debian-Woody, or that it worked
> with Slackware? Or something else? Were you using a stock kernel or
> one you compiled? I don't use a USB mouse here, but I wouldn't count
> on a stock Debian kernel supporting one ... though someone else here,
> someone who uses a USB mouse with Debian, would be a better source of
> advice at this point.
used to use a 2.6.1 now 2.6.2.
> I haven't used a stock Linux kernel (aside from the early stage of an
> install) for years, so I don't recall what they include either
> compiled in or as modules ... both USB mouse support and Input Core
> mouse support appear to be available as modules, so modprobe'ing them
> (or adding them to /etc/modules) may be the prior fix you've
> forgotten. Just a guess, though, as I say.
The clincher so to say. after reading this I saw my previous kernel
conf, and voila, HID support was configured as a module (was built into
my older kernel). just added a modprobe into my startup scripts
and the mouse is working fine!!!
also Ray, about that trick I tried (cat /dev/psaux ..... ), I tried it
again. the mouse is not unresponsive, I get a newline for a right click
and scroll wheel click, ie , it is writing whitespaces atleast......
>
>
>
>
>
>
> -
> 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 8:57 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
2004-02-13 4:37 ` Ray Olszewski
2004-02-13 8:57 ` joy [this message]
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=402C9160.3060907@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