On 07 Oct 2005, Jan T. Kim wrote: > On Fri, Oct 07, 2005 at 08:33:04AM +0000, Florian Dorpmueller wrote: > > > Section "InputDevice" > > > Identifier "Configured Mouse" > > > Driver "mouse" > > > Option "CorePointer" > > > Option "Device" "/dev/ttyS0" > > > Option "Protocol" "Microsoft" > > > Option "Emulate3Buttons" "true" > > >EndSection > > > > Sure that your mouse is plugged at /dev/ttySx ? Have you tried > > "/dev/input/mice", "/dev/psaux" or simply "/dev/mouse"? > > An easy way to find out whether a device indeed gets the mouse input > is to use hexdump: If running > > hexdump /dev/ttyS0 > > and then moving the mouse gives you a stream of hex digits, then you've > got the right device. If nothing happens, then there's little reason to > expect any response by X's mouse cursor... > > Best regards, Jan > -- > +- Jan T. Kim -------------------------------------------------------+ > | *NEW* email: [EMAIL PROTECTED] | > | *NEW* WWW: http://www.cmp.uea.ac.uk/people/jtk | > *-----=< hierarchical systems are for files, not for humans >=-----* >
Thanks to both for replies. I'll look into it further. Meanwhile I got hold of a PS2 mouse and that is working so the immediate problem is solved. Anthony -- Anthony Campbell - [EMAIL PROTECTED] Microsoft-free zone - Using Linux Gnu-Debian http://www.acampbell.org.uk (blog, book reviews, on-line books and sceptical articles) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
