Re: Mouse/X
On Thu, Mar 13, 2003 at 10:06:16AM +, Olivier wrote: > Quoting "Paul M Foster" : > > -- was [EMAIL PROTECTED] on Mar 12, 2003 at 10:59:50 -- > > > I'll give you the solution someone gave me on my system. I'm using a > > Trident Cyberblade i/1 video card, so YMMV. > > That's quite interesting because my video card is a > Trident Cyberblade i/7 ... Same here ... > > > Go to your XF86Config-4 file (in /etc/X11) and find the section > > pertaining to your video card. Within that section, add the following: > > > > Option "SWCursor" "on" > > > > What I was told is that this causes X to position the cursor, rather > > than the video card (which apparently gets it wrong). Naturally, restart > > X afterward. > > I will investigate this way and test a little (since the problem > only appears from time to time) before reporting the results. I missed the start of this thread, but if it's "X thinks I'm clicking Zcm to the $LEFT_OR_RIGHT of where my mouse cursor actually is" (where Z=1.5 and LEFT_OR_RIGHT=left for me), then this advice is correct. I used to see the problem at least once a day (only solution was a reboot, though I learned to mentally adjust the cursor position and carry on regardless :-) but haven't seen it at all since adding the SWCursor line (as detailed above) to my X config file about 1 month ago. HTH, jc -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mouse/X
Quoting "Paul M Foster" : > -- was [EMAIL PROTECTED] on Mar 12, 2003 at 10:59:50 -- > I'll give you the solution someone gave me on my system. I'm using a > Trident Cyberblade i/1 video card, so YMMV. That's quite interesting because my video card is a Trident Cyberblade i/7 ... > Go to your XF86Config-4 file (in /etc/X11) and find the section > pertaining to your video card. Within that section, add the following: > > Option"SWCursor" "on" > > What I was told is that this causes X to position the cursor, rather > than the video card (which apparently gets it wrong). Naturally, restart > X afterward. I will investigate this way and test a little (since the problem only appears from time to time) before reporting the results. Many, many thanks Paul ! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mouse / X problems UPDATE
Hey, thanks Kent that's great. (I have been following the list, honest! Guess I missed that post though...) :-) Chris Kent West wrote: Chris Owen wrote: I have now found a solution for this mouse problem in X: it seems gpm was the problem. After uninstalling gpm, the PS/2 mouse now works correctly in X. If anyone can tell me why this is, or whether there's a workaround which lets me keep gpm, that would be interesting (although to be honest I'm not that bothered about needing gpm...). Thanks Chris From a posting earlier in the day (subj: MOUSE won't function): gpm is a mouse driver for the text-only virtual console. For example, if you are not running X, and you only have text-only virtual consoles (hereafter referred to as VTs, for Virtual Terminals), and you need a mouse in your VTs, then you'd need to be running gpm. Or even if you are running X, but you occasionally need to pop out to a VT and need a mouse while there, you'd need gpm running. Now, if you have X running, X needs a mouse. It has its own mouse driver built-in. This mouse driver conflicts with gpm, and having gpm running as well as X can cause the mouse to behave erratically, etc. For example, the mouse might generate some events, such as "I've moved left", followed by "I've moved up". If both gpm and the X mouse driver are reading the mouse port, it may be that gpm reads the "left" event, removing that event from the incoming data stream, and then it comes X's turn to read the mouse events, and it reads "up", never getting a chance to read the "left" event because gpm "took" it. So the mouse behaviour in X was supposed to be left, then up, but turns out to be only up. Doh! Thankfully, these two mouse drivers can be convinced to play nicely together. The way this is done is to tell gpm to not keep the incoming data to itself, but to repeat that incoming data, in a "raw" format. Both gpm and X normally read from the "incoming mouse data port" (whatever that is, perhaps /dev/psaux, perhaps /dev/ttyS0, etc). gpm can't repeat the data it reads back to that port, or next time it goes to read that port it'll just re-read what it read earlier, and loopity-loop. So instead it repeats the data to a special "virtual" port, called /dev/gpmdata. Then X needs to be configured to read its incoming mouse data, not from the normal port, but from the /dev/gpmdata "port". Voila! gpm and X now get along just dandy. So, you have two options. 1) Remove gpm, and just get the mouse working in X 2) Configure gpm to repeat the raw data (run gpmconfig and answer the questions), and configure X to read its mouse data from /dev/gpmdata. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mouse / X problems UPDATE
Chris Owen wrote: I have now found a solution for this mouse problem in X: it seems gpm was the problem. After uninstalling gpm, the PS/2 mouse now works correctly in X. If anyone can tell me why this is, or whether there's a workaround which lets me keep gpm, that would be interesting (although to be honest I'm not that bothered about needing gpm...). Thanks Chris From a posting earlier in the day (subj: MOUSE won't function): gpm is a mouse driver for the text-only virtual console. For example, if you are not running X, and you only have text-only virtual consoles (hereafter referred to as VTs, for Virtual Terminals), and you need a mouse in your VTs, then you'd need to be running gpm. Or even if you are running X, but you occasionally need to pop out to a VT and need a mouse while there, you'd need gpm running. Now, if you have X running, X needs a mouse. It has its own mouse driver built-in. This mouse driver conflicts with gpm, and having gpm running as well as X can cause the mouse to behave erratically, etc. For example, the mouse might generate some events, such as "I've moved left", followed by "I've moved up". If both gpm and the X mouse driver are reading the mouse port, it may be that gpm reads the "left" event, removing that event from the incoming data stream, and then it comes X's turn to read the mouse events, and it reads "up", never getting a chance to read the "left" event because gpm "took" it. So the mouse behaviour in X was supposed to be left, then up, but turns out to be only up. Doh! Thankfully, these two mouse drivers can be convinced to play nicely together. The way this is done is to tell gpm to not keep the incoming data to itself, but to repeat that incoming data, in a "raw" format. Both gpm and X normally read from the "incoming mouse data port" (whatever that is, perhaps /dev/psaux, perhaps /dev/ttyS0, etc). gpm can't repeat the data it reads back to that port, or next time it goes to read that port it'll just re-read what it read earlier, and loopity-loop. So instead it repeats the data to a special "virtual" port, called /dev/gpmdata. Then X needs to be configured to read its incoming mouse data, not from the normal port, but from the /dev/gpmdata "port". Voila! gpm and X now get along just dandy. So, you have two options. 1) Remove gpm, and just get the mouse working in X 2) Configure gpm to repeat the raw data (run gpmconfig and answer the questions), and configure X to read its mouse data from /dev/gpmdata. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Mouse / X problems UPDATE
I have now found a solution for this mouse problem in X: it seems gpm was the problem. After uninstalling gpm, the PS/2 mouse now works correctly in X. If anyone can tell me why this is, or whether there's a workaround which lets me keep gpm, that would be interesting (although to be honest I'm not that bothered about needing gpm...). Thanks Chris Chris Owen wrote: Hi, if someone could help me get my X server + mouse running I'd be very grateful. Hardware details: Old AJP 5400 laptop (you won't have heard of it), 75MHz Pentium, 16MB RAM Trackpad PS/2 mouse Cirrus Logic 754x display chipset 800x600 LCD display Debian 3.0r0 The story so far: I used to have RetHat 6.0 going on this machine and X was fine, so I know it's possible. 1. Started with XFree86-v4, as installed by default. Chose the "cirrus" driver. Debconf configuration didn't start X, error in log file about "No screens found". 2. Ran XFree86 -configure, this came up with an XF86Config.new which used the "vesa" driver. With this, X comes up but mouse not working. 3. After some unsuccessful mucking about, decided to try the XFree86-v3 server, so uninstalled xserver-xfree86 and installed xserver-svga. 4. dpkg-reconfigure xserver-svga produces an XF86Config which allows X to start, but still mouse problems. The cursur does respond to mouse movements, but goes haywire, sticking, jumping and opening menus. 5. xf86config-v3 produces an XF86Config which doesn't work at all, complains about lines such as Modes (null). 6. I had saved off my old XF86Config which used to work under RH6.0, tried this but it chokes on the very first line; complains about Section "Files", saying "File section keyword expected". Don't understand this at all, as the syntax here seems to be that same as the XF86Config files which do work, I even tried copying the Files section over but get the same error? 7. Went back to dpkg-reconfigure xserver-svga, tried every one of the PS/2 protocols but they all behave the same way. I'm quite sure the mouse is PS/2. Also tried an external mouse plugged into the PS/2 port, and get same result. I'm attaching XF86Config-RH6 (the old RH6.0 one which used to work), and the current XF86Config produced by dpkg-reconfigure. Thanks a lot for any help Chris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: mouse/X compatibility problem
Which revision of the serial mouse is it? If it is a 2.1a MS Mouse, there is a problem with it and the newest versions of X. They are incompatible. I had to send back 15 MS mice and have my hardware supplier dig up 2.0 revisions of the mouse. I believe there is more info about it over at xfree86.org Timm Gleason Hardware Engineer On Wed, 29 Oct 1997 15:49:45 -0500 (EST), [EMAIL PROTECTED] (Larry Gariepy) wrote: >Hello. > I am mailing a message that I posted earlier on the newsgroup because a >friend of mine informed me that many people subscribe to the list but do >not check the newsgroup that often. >- >I am a new Debian user. With a great deal of help from a friend (read: >he installed and debugged it for me), I now have Debian Linux 1.3.1 on >my Pentium 233. It is set up as a dual boot machine, with Win95. > >My problem is that X Windows doesn't seem to recognize my mouse, though >it works under Win95, and you even get a mouse cursor when logged in to >a vt100 terminal. The mouse is just a standard Microsoft serial mouse. > >If anyone has had this problem, or even if you haven't and know how to >fix it, any advice would be greatly appreciated. > >Thanks, >Larry Gariepy >[EMAIL PROTECTED] > >ps. I have two friends who are Debian gurus, and they were unable to >diagnose the problem (other than to recommend buying a new mouse!), so >it leads me to believe this problem is non-trivial. > > > >-- >TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to >[EMAIL PROTECTED] . >Trouble? e-mail to [EMAIL PROTECTED] . > > ** "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning." - Rich Cook ** Timm Gleason -- [EMAIL PROTECTED] -- [EMAIL PROTECTED] -- http://n2h2.com/ N2H2, Creators of Bess -- 1301 Fifth Avenue, Suite 1501--Seattle, WA 98101 ** -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mouse/X compatibility problem
On Thu, 30 Oct 1997, Larry Gariepy wrote: > Hi. Ok, I have sat down and done a little research. The mouse is on > Com 1, sort of. When I boot in Windows 95, it does not seem to recognize > the mouse as being on Com 1, it is just "there". In Linux, the device > /dev/mouse is linked to /dev/ttyS0. The mouse is a Microsoft Serial > Mouse, version 2.1A. Is this too new for the driver to work correctly? > Is it possible that the mouse is not connected to Com1 or Com2? Hmm. How's it plug into the machine? If it's plugged into a serial port, it's probably got to be on a com port. But if you have a recent motherboard, it could be on com3 or com4 -- try the other /dev/ttys[2..4] entries as the Device "/dev/ttywhatever" entry, and see if that helps. Also, you might want to check your kernel messages on boot and see if the serial driver is installed -- try "more < /var/log/messages" to check this, and you should see something about tty00--tty03. It's also possible that your serial port is by default configured for the wrong IRQ, in which case you'll need to use setserial. Will -- | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | | http://www.cis.udel.edu/~lowe/ | -- | You say "Love is a temple. Love the higher law."| | You ask me to enter, but then you make me crawl.| | And I can't be holding on to what you got | | When all you got is hurt. | -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mouse/X compatibility problem
> > On Thu, 30 Oct 1997, Larry Gariepy wrote: > > > Section "Pointer" > > Protocol"Microsoft" > > Device "/dev/mouse" > > You say it's a two-button microsoft serial mouse? Which com port is it > on? If it's com A, then it should be < Device "/dev/ttys0" >. Com B is > < Device "/dev/ttys1" >, etc... > > You might want to make /dev/mouse point to the correct com port by > making a link from /dev/mouse to /dev/ttys[0...4], in which case you can > leave the "Device" line alone. > > If that's not your problem, let me know and we'll see what else > to try. > > Will Hi. Ok, I have sat down and done a little research. The mouse is on Com 1, sort of. When I boot in Windows 95, it does not seem to recognize the mouse as being on Com 1, it is just "there". In Linux, the device /dev/mouse is linked to /dev/ttyS0. The mouse is a Microsoft Serial Mouse, version 2.1A. Is this too new for the driver to work correctly? Is it possible that the mouse is not connected to Com1 or Com2? Confused... Larry -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mouse/X compatibility problem
On Thu, 30 Oct 1997, Larry Gariepy wrote: > Section "Pointer" > Protocol"Microsoft" > Device "/dev/mouse" You say it's a two-button microsoft serial mouse? Which com port is it on? If it's com A, then it should be < Device "/dev/ttys0" >. Com B is < Device "/dev/ttys1" >, etc... You might want to make /dev/mouse point to the correct com port by making a link from /dev/mouse to /dev/ttys[0...4], in which case you can leave the "Device" line alone. If that's not your problem, let me know and we'll see what else to try. Will -- | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | | http://www.cis.udel.edu/~lowe/ | -- | You say "Love is a temple. Love the higher law."| | You ask me to enter, but then you make me crawl.| | And I can't be holding on to what you got | | When all you got is hurt. | -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mouse/X compatibility problem
> > On Wed, 29 Oct 1997, Larry Gariepy wrote: > > > My problem is that X Windows doesn't seem to recognize my mouse, though > > it works under Win95, and you even get a mouse cursor when logged in to > > a vt100 terminal. The mouse is just a standard Microsoft serial mouse. > > 1) What sort of mouse is it? > 2) find the file /etc/X11/XF86Config and send us the lines which contain > the "pointer" stanza. > Will Here is the data that you requested from /etc/X11/XF86Config # ** # Pointer section # ** Section "Pointer" Protocol"Microsoft" Device "/dev/mouse" Emulate3Buttons Emulate3Timeout50 EndSection Larry -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mouse/X compatibility problem
If it works in win95 and you see mouse cursor like you say, I suspect whoever configured you X picked the wrong mouse device. Check your X86config file. I belive it's in /etc/X11 . Also make sure you indeed have a serial mouse. Win95 is capable of detecting PS2, BUS and serial mice. LINUX X must be told what you have. And what device to use to access it. Chuma Larry Gariepy wrote: > Hello. >I am mailing a message that I posted earlier on the newsgroup because a > friend of mine informed me that many people subscribe to the list but do > not check the newsgroup that often. > - > I am a new Debian user. With a great deal of help from a friend (read: > he installed and debugged it for me), I now have Debian Linux 1.3.1 on > my Pentium 233. It is set up as a dual boot machine, with Win95. > > My problem is that X Windows doesn't seem to recognize my mouse, though > it works under Win95, and you even get a mouse cursor when logged in to > a vt100 terminal. The mouse is just a standard Microsoft serial mouse. > > If anyone has had this problem, or even if you haven't and know how to > fix it, any advice would be greatly appreciated. > > Thanks, > Larry Gariepy > [EMAIL PROTECTED] > > ps. I have two friends who are Debian gurus, and they were unable to > diagnose the problem (other than to recommend buying a new mouse!), so > it leads me to believe this problem is non-trivial. > > > -- > TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to > [EMAIL PROTECTED] . > Trouble? e-mail to [EMAIL PROTECTED] . -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mouse/X compatibility problem
On Wed, 29 Oct 1997, Larry Gariepy wrote: > Hello. >I am mailing a message that I posted earlier on the newsgroup because a > friend of mine informed me that many people subscribe to the list but do > not check the newsgroup that often. > - > I am a new Debian user. With a great deal of help from a friend (read: > he installed and debugged it for me), I now have Debian Linux 1.3.1 on > my Pentium 233. It is set up as a dual boot machine, with Win95. > > My problem is that X Windows doesn't seem to recognize my mouse, though > it works under Win95, and you even get a mouse cursor when logged in to > a vt100 terminal. The mouse is just a standard Microsoft serial mouse. > > If anyone has had this problem, or even if you haven't and know how to > fix it, any advice would be greatly appreciated. I had a similar problem: a three-button mouse that was recognised by X as a two-button mouse, though it worked correctly in text mode (with gpm). The trick here is, that gpm can export the mouse device so that X can use it. To do this, add the '-R' option to then 'append' line in /etc/gpm.conf, like this: append="-R" You can do this manually or with the 'gpmconfig' program. Then you will have to make the /dev/gpmdata fifo, like this: # cd /dev # mkfifo gpmdata Then, configure X to use a Mouse Systems mouse attatched to /dev/gpmdata. Restart gpm and X and see if it works. Remco -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mouse/X compatibility problem
On Wed, 29 Oct 1997, Larry Gariepy wrote: [snip] > I am a new Debian user. With a great deal of help from a friend (read: > he installed and debugged it for me), I now have Debian Linux 1.3.1 on > my Pentium 233. It is set up as a dual boot machine, with Win95. > > My problem is that X Windows doesn't seem to recognize my mouse, though > it works under Win95, and you even get a mouse cursor when logged in to > a vt100 terminal. The mouse is just a standard Microsoft serial mouse. [snip] Under Win '95, can you go to the system resouce control pannel and check to see which port the mouse is attached to? This should probably be com1 or com2. This will confirm the hardware port for the device (/dev/ttyS0 is for com1, and /dev/ttyS1 is for com2). If by some chance, your mouse is a MS ps2 port mouse, you will need to use a kernel that is compiled with ps2 mouse support. Syrus. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept. -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: mouse/X compatibility problem
On Wed, 29 Oct 1997, Larry Gariepy wrote: > My problem is that X Windows doesn't seem to recognize my mouse, though > it works under Win95, and you even get a mouse cursor when logged in to > a vt100 terminal. The mouse is just a standard Microsoft serial mouse. 1) What sort of mouse is it? 2) find the file /etc/X11/XF86Config and send us the lines which contain the "pointer" stanza. Will -- | [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] | | http://www.cis.udel.edu/~lowe/ | -- -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
