From: joy <gracecott@sancharnet.in>
To: James Miller <jamtat@mailsnare.net>, linux-newbie@vger.kernel.org
Subject: Re: mouse not writing to device file.....
Date: Fri, 13 Feb 2004 14:47:44 +0530 [thread overview]
Message-ID: <402C9638.60704@sancharnet.in> (raw)
In-Reply-To: Pine.LNX.4.58.0402130706310.13970@debian-emach
James Miller wrote:
>On Thu, 12 Feb 2004, Ray Olszewski wrote:
>
>
>
>>At 09:37 AM 2/13/2004 +0530, joy wrote:
>>[...]
>>
>>
>>>>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..........
>>>
>>>
>>Sorry; that was a typo. I meant to write gpm (gdm is an X login manager,
>>like xdm, and not what I meant to refer to).
>>
>>
>
>This sounds a little like a problem I had recently (and never solved) that
>was somehow related to the 2.6.x kernel. Does your install perhaps use a
>2.6.x kernel? When I tried adding the 2.6.x kernel from Debian as a boot
>
>
a brand new ,top of the line 2.6.2!!
>option, each time I would boot using that kernel, I would not be able to
>control the mouse in X. The cursor would appear on the screen, but moving
>the mouse would have no effect on it. I did get error messages though -
>something to the effect of "pointing device not found" (don't recall
>precisely, since my resolution was to put the matter on the back burner
>
>
No no no, after checking out the speed of the 2.6, with KDE loading in
quarte the time,how did you ever get the heart to go back?
I suggest you do the same as I did -- check the config .If yours too is
a USB mouse, then with the HID support built in or as a module
the mouse will still use psaux. Also disable support for anything called
APIC in the kernel.
according to NVIDIA 's helpfile this affects performance on the X
server (mine used to hang every 3.5 (approx.,) minutes)
>and go back to a 2.4.x kernel, under which the mouse works fine). Don't
>know if these comments will aid the discussion or help in troubleshooting.
>
>
>James
>-
>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 9:17 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
2004-02-13 13:12 ` James Miller
2004-02-13 9:17 ` joy [this message]
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=402C9638.60704@sancharnet.in \
--to=gracecott@sancharnet.in \
--cc=jamtat@mailsnare.net \
--cc=linux-newbie@vger.kernel.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