From: Vojtech Pavlik <vojtech@suse.cz>
To: Sean Callanan <spyffe@cs.sunysb.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [MOUSE] "Virtual PC" mouse no longer works
Date: Sun, 30 Nov 2003 10:07:40 +0100 [thread overview]
Message-ID: <20031130090740.GA17190@ucw.cz> (raw)
In-Reply-To: <3FC99B0B.6010701@cs.sunysb.edu>
On Sun, Nov 30, 2003 at 02:23:55AM -0500, Sean Callanan wrote:
> Dear mailing list,
>
> I'm running Debian inside Connectix Virtual PC 6.0.1. This software
> simulates Pentium-based hardware on a Macintosh. It lets the guest OS
> "captue" the Macintosh mouse - when the guest OS wants to use the mouse,
> the Macintosh pointer disappears and the guest OS receives mouse events.
> This is done using a virtual PS/2 device.
>
> This functionality works with the following kernels (with relevant
> configuration options). They are stock Debian kernels.
>
> 2.2.20:
> CONFIG_MOUSE=y
> CONFIG_PSMOUSE=y
> 2.4.18:
> CONFIG_PSMOUSE=y
>
> The mouse is free until X starts up (getting mouse events from
> /dev/psaux) and is then "captured" and usable in X. But with
> 2.6.0-test11, this functionality is broken. The relevant parameters in
> my .config are:
>
> CONFIG_INPUT=y
> CONFIG_INPUT_MOUSEDEV=y
> CONFIG_INPUT_MOUSEDEV_PSAUX=y
> CONFIG_INPUT_MOUSE=y
> CONFIG_MOUSE_PS2=y
> CONFIG_BUSMOUSE=y
>
> I have tried:
> 1) Using /dev/input/mice and /dev/psaux in my XF86Config
> 2) Passing psmouse_noext=1 to the kernel
> Neither gave any success.
>
> Please cc: me on any replies as I am not subscribed. Thank you for your
> time.
Enable DEBUG in drivers/input/serio/i8042.c and look at dmesg output
(and send it to me, too). There one can see what went wrong, what's
not being emulated correctly.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
prev parent reply other threads:[~2003-11-30 9:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-30 7:23 [MOUSE] "Virtual PC" mouse no longer works Sean Callanan
2003-11-30 9:07 ` Vojtech Pavlik [this message]
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=20031130090740.GA17190@ucw.cz \
--to=vojtech@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=spyffe@cs.sunysb.edu \
/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;
as well as URLs for NNTP newsgroup(s).