If you don't have a mouse in Console mode do
gpm -k (To KILL the mouse driver)
gpm -h to get help
Jeremy wrote:
> James wrote:
> >
> > Nightstalker wrote:
> > :Have you looked in your /etc/X11/XF86Config file, at the Pointer section
> > :- It should look something like this:
> >
> > : Section "Pointer"
> > : Protocol "MouseManPlusPS/2"
> > : Device "/dev/psaux"
> > : BaudRate 1200
> > : ZAxisMapping 4 5
> > : EndSection
> >
> > This part is ok in my XF86Config.
> >
> > :Are your values still valid for your hardware? (ZAxisMapping only if
> > :wheel btw) Is your device still in the /dev directory? Do you have a
> > :mouse in console mode?
> >
> > When I do an "ls mou*" I get "mouse@" but I have no mouse in console mode.
> > Your next suggestion might be to see if the mouse is connected, but I've
> > done that and it's connected. Though, it is connected through a switcher
> > box so I can use the keyboard and mouse on both my NT box and my Linux
> > box. It has worked well up until today, and I am not sure what I might
> > have done to change things.
> >
> > :Running XF86Setup (as root) might help restore this file if you don't
> > :want to do it manually. Maybe make a backup (cp XF86Config
> > :XF86Config.backup) too before doing anything.
> >
> > How do I run XF86Setup? I typed XF86Setup to no avail.
> >
> > james
>
> "mouse@" is something called a symbolic link, its not actually the
> device but it points to it. Mine points to /dev/psaux 'cause its PS/2.
> if you "ls -laF /dev/mou*" it will show the device it actually points
> to. MAke sure that device is listed in /dev. Then make sure that device
> is what you're actually hooked up to. If its serial it will be
> something like ttyS0 or ttyS1 for com1/com2 respectively. I think the
> mandrake install programs usually setup XF86Config to the actual device
> and not the sym links...but I've never used 6.1 just 6.0 & 7 so I cant
> be sure.
>
> To double check the exact protocol, there is a list in the man page "man
> XF86Config" about a dozen pages into it. Make sure the
> spelling/capitalization is correct. Note that all these protocols might
> not show up in configuration tools.
>
> Did you _ever_ have a mouse in console mode? This could help narrow
> down the problem to X specific or the whole Linux box in general.
>
> XF86Setup should be in your path, but if not it is probably located in
> /usr/X11R6/bin. "locate XF86Setup |more"
> could help you find it. You could also use "xf86config", which is a
> text mode tool and less user friendly. Both have their strenghts, the
> latter is better for setting multiple resolutions and color depths. But
> for just changing mouse settings "vi /etc/XF86Config" would be my
> choice.
>
> I don't think that you would get this error if the mouse wasn't
> physically plugged in. You just wouldn't be able to move the pointer.
> You could have done something inadvertantly last time you were in X, and
> just didn't notice it until you tried to go back in. Take a good hard
> look at the /dev directory and your device line in XF86Config. It
> really won;t hurt to double check the protocol either. Let me know if
> you get it.
>
> NightStalker
