* Harry Putnam ([EMAIL PROTECTED]) [020305 09:36]: > Vineet Kumar <[EMAIL PROTECTED]> writes: > > > * Harry Putnam ([EMAIL PROTECTED]) [020305 00:29]: > >> /etc/gpm.conf is set to /dev/psaux. So the X mouse cannot be > >> .. right? > > > > Right. Also, as I've said before, adding a symlink in the mix can only > > confuse things further. Forget about a /dev/mouse symlink. Tell gpm to > > use /dev/psaux and tell X to use /dev/gpmdata. See the links below. > > Not sure I see what confusion it causes but it does seem extraneous. > Are suggesting it is the problem here?
No, just that it's one more (useless) variable, and that you should "take it out of the equation" </impression who="keanu reeves" movie="speed" quality="bad"> > You say "(Start by reading Joost's message regarding mouse hardware.)" > Joost says if the hardware connector is small and round it is PS/2. > Thats what I've used. Everyone seems to agree if it is ps2 /dev/psaux > should be the device: > > My current (non-working) gpm.conf: > device=/dev/psaux > responsiveness= > repeat_type=raw > type=ps2 > append="" > sample_rate= > > My current XF86Config (in part) > > Section "InputDevice" > Identifier "gpm-mouse" > Driver "mouse" > Option "CorePointer" > Option "Device" "/dev/gpmdata" > Option "Protocol" "PS/2" > Option "Emulate3Buttons" "true" > # Option "ZAxisMapping" "4 5" (This is now commented) > EndSection > Your setup does look correct. Could it be that the PS/2 port just isn't working at all? Is this a stock debian kernel? In that case it should be enabled. Otherwise, if it's a custom build, ensure that you have CONFIG_PSMOUSE=y. To continue to diagnose this, I'd suggest tackling one of either X or gpm independently. Again, reducing the scope of your problem will help eliminate the red herrings and find the real problem. Once we get something working, we can build on it. > > 2) More important probably. You talk about both configs (gpm.conf and > XF86Config-4) Referencing the same mouse protocol but never really > say what that is. For example: The gpm.conf I posted says `raw' > for the repeat option and as you note in those posts is > alright. But you never say what the X config should say... only > that it should be the same. But don't think you mean `raw' in > the X config. No, not raw in XF86Config. I mean that if you tell gpm to use repeat_type=ms3, then you should tell X to listen in ms3. If you tell gpm to use repeat_type=raw, then you need to tell X to listen in whatever protocol gpm is listening in. (PS/2 in this case). > > From your post:Message-ID: <[EMAIL PROTECTED]> > > Alternatively, you can specify any protocol you > > like in your gpm repeater config, as long as you tell X to use the > > same protocol. As someone else suggested, you can tell gpm to repeat > > as type 'raw' in which case you should configure X to use the actual > > protocol that your mouse is speaking. > > By `actual protocol' you mean PS/2 .. right? Yup. > > Can you say point blank what you see as wrong with the above? It > seems to conform to your outline. But, I've been staring at it too > long and probably missing some important difference. It does look right. I didn't mean to brush you off before by sending you to the archives; just thought you might find the answer you were looking for. I guess not. =/ > > The final piece of the puzzle: > > Section "ServerLayout" > Identifier "Default Layout" > Screen "Default Screen" > InputDevice "Generic Keyboard" > InputDevice "gpm-mouse" "CorePointer" > # InputDevice "Generic Mouse" > EndSection > > Note Generic Mouse is commented out along with that entire section That looks fine. Also (you probably know, but should be said for the record) > > With that setup, and in console mode running this command: > # /etc/init.d/gpm force-reload > Stopping mouse interface server: gpm. > Starting mouse interface server: gpm. > # ps wuax|grep gpm > > Appears as if gpm is started but nothing shows in ps output and mouse > doesn't work. This seems to be the heart of the problem. With X listening on /dev/gpmdata, the mouse will not work without gpm running. I'd suggest leaving X out of it for now and getting gpm running (or the other way around, your call). Incidentally, anyone know what happened to mev? It was the mouse event viewer, sort of a la xev, but for console mouse events. It was very handy in situations like this. I thought it was in the gpm package, but it's nowhere on my system. Just now looking through the changelog for mev it sounds like there have been various problems with the init sequence and starting up gpm. Maybe that's a place to start looking. Also, if you're having troubles with the init scripts (they look like it started fine, but not really) you should check to see if there are any messages in the logs, and maybe just try starting gpm manually on the command line (at least for diagnostic purposes): /usr/sbin/gpm -D -m /dev/psaux -t ps2 -Rraw The -D should be very helpful here; it should keep gpm running in the foreground and log messages to stderr. Leave that going on a console to see what's going wrong. If gpm just won't start at all, that's a problem. good times, Vineet -- Currently seeking opportunities in the SF Bay Area Please see http://www.doorstop.net/resume/
pgp1LQtTOcOBN.pgp
Description: PGP signature
