Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 238
  • Last Modified:

mouse problem at xwindows in slakware 3.5

i use slakware 3.5 but cannot use mouse in x windows. help me please
0
mujdat
Asked:
mujdat
  • 4
  • 2
  • 2
  • +2
1 Solution
 
pestilenceCommented:
Thats propably because you haven't setup correctlyyour mouse...try running xf86config and in the mouse area decalre your mouse...if it is a com1 mouse use /dev/cua0 if it is a PS/2 then add the PS2 support...
If the problem is more complicated please send the whole part of it :)
For instance do you have a mouse in command line???
 
0
 
mujdatAuthor Commented:
thanx . i will try and inform u about the situation

0
 
mujdatAuthor Commented:
my mouse is not PS/2. and use com1 (/dev/tty00) it is still not working.is it have to be /dec/cua0 ?
0
NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

 
ahoffmannCommented:
do you have a link  /dev/mouse  to /dev/tty00 ?
/dev/cua0  is not the right one.

Also check if you have gpm running, if so, kill it before starting X.
0
 
mujdatAuthor Commented:
there is link but
gpm is running. why do i have to kill it before starting X ?
if i kill it will it work ?

0
 
tunctCommented:
normally, gpm should cause no problem... does a text cursor appear when you move the mouse in console mode? does /dev/mouse really point to /dev/ttyS0? do you have a (pnp) modem that might interfere?
0
 
tunctCommented:
normally, gpm should cause no problem... does a text cursor appear when you move the mouse in console mode? does /dev/mouse really point to /dev/ttyS0? do you have a (pnp) modem that might interfere?
0
 
mujdatAuthor Commented:
when i killed gpm mouse worked in X Windows. but i can not write anything at xterm windows this time. what shold i do?
0
 
ahoffmannCommented:
killing gpm solved the problem.

Xterm is a new one. Give more details, best in a new question :-)
0
 
plush98Commented:
I'd suggest modifying /etc/rc.d/rc.local (or whatever the path is) removing one of the parameters for gpm does the trick... I guess it was -R

0

Featured Post

Ask an Anonymous Question!

Don't feel intimidated by what you don't know. Ask your question anonymously. It's easy! Learn more and upgrade.

  • 4
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now