Operating Systems > Linux and UNIX

I fucked up my Slackware!!!

(1/4) > >>

RudeCat7:
All I did was replace the serial mouse with a PS/2 mouse. I did the /mouseconfig as root....and that didn't work. So I resorted to /xf86config all over again...no good.

Short story...neither mouse works now, I just want to clean the slate so I can reconfig and my mouse works...

..........what would Void Main do?   :confused:  


EDIT: Yeah, "Void Main" would make more sense than "Void Man" LOL

[ November 17, 2002: Message edited by: Black & White Cat ]

Master of Reality:
does X work?
or does it give an error saying that it cant find the mouse?

you can edit /etc/X11/XF86Config and under the "Mouse" (it might be "pointer") portion change the protocol to "PS/2 for the PS/2 mouse.
Check the device the mouse is supposedly on, it should be /dev/mouse0 in slackware i think.

[ November 17, 2002: Message edited by: The Master of Reality / B0B ]

RudeCat7:
Yeah, X works fine, KDE starts up, but the mouse has crapped out, so I have to navigate with the virtual pointer (shift+numlock---> keypad)

I have set it as /dev/mouse0 but it doesn't do anything. Which is why I am confused...xf86config or mouseconfig should have fixed the problem, but instead it seems that all my configuring has fucked it up. And I did try 2 different ps/2 mice plus the original serial mouse, and now none of them do anything.

[ November 17, 2002: Message edited by: Black & White Cat ]

voidmain:
Does /dev/mouse0 exist? Do this:

# ls -l /dev/mouse0

and let me know what it says, that is, is it a symbolic link to a real device? Could you post your XF86Config? Most linux distros use /dev/psaux for the PS2 mouse device. I haven't used Slackware since v3 though.  

Master of Reality:
redhat 7.2 uses PS/2

Navigation

[0] Message Index

[#] Next page