Stop Microsoft

Operating Systems => Linux and UNIX => Topic started by: RudeCat7 on 17 November 2002, 21:56

Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 17 November 2002, 21:56
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 ]

Title: I fucked up my Slackware!!!
Post by: Master of Reality on 17 November 2002, 10:04
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 ]

Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 17 November 2002, 10:13
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 ]

Title: I fucked up my Slackware!!!
Post by: voidmain on 17 November 2002, 10:39
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.  (http://smile.gif)
Title: I fucked up my Slackware!!!
Post by: Master of Reality on 17 November 2002, 10:42
redhat 7.2 uses PS/2
Title: I fucked up my Slackware!!!
Post by: voidmain on 17 November 2002, 10:44
No, I meant the device, not the protocol. Do an "ls -l /dev/mouse" and you should see it linked to "/dev/psaux" if you have a PS2 mouse (in RedHat).
Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 17 November 2002, 10:46
I will get back to you in about 10 hours, right now I only have enough energy to post some moronic jabs at Mr. Doomass.
Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 17 November 2002, 21:41
O.k., I did the ls, and yes /dev/mouse =/dev/psaux.

and the core pointer section says:

Identifier  "Mouse1"
Driver      "mouse"
Option "Protocol" "Microsoft"
Option  "Device" "/dev/mouse"

and it is an M$ 2 button ps/2 mouse.

What do you think?
Title: I fucked up my Slackware!!!
Post by: voidmain on 17 November 2002, 23:18
Try this for a mouse section:
Code: [Select]

Then in your "ServerLayout" section make sure you have the line:

Code: [Select]

But if you post your XF86Config I could look for any other problems.

Oh, and what version of XFree86 are you running? 4.2.0?

[ November 17, 2002: Message edited by: void main ]

Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 18 November 2002, 02:37
I tried it and it had no effect.

Can I just delete my XF86Config and start over?

At least the serial mouse worked before.

I would post my config file, but I can barely navigate as is.

Though I will try to use the command line and copy to a floppy.
Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 18 November 2002, 04:38
I REALLY fucked it up now...

Oh well, time to reinstall, LOL!
Title: I fucked up my Slackware!!!
Post by: voidmain on 18 November 2002, 05:01
Huh? You don't have to reinstall for a messed up XF86Config. And once you get it working the way you like back it up before making changes. Did you run the "XF86Setup" or "xf86config" commands (case sensitive)?
Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 18 November 2002, 05:17
Uhhhhhhhhh....I...erm...../*gasp*/ deleted it. So as you can probably guess, X11 can't start up with the XF86config file.

'Nother lesson learned the hard way....but I am figuring out this Linux shit bit by bit.


Back up my xf86config? Damn it! I broke my own rule!!! I hate it when people don't back up their shit!!!

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

Title: I fucked up my Slackware!!!
Post by: voidmain on 18 November 2002, 05:20
It doesn't matter if X doesn't start. You can't run those commands with X running anyway. And you wouldn't want to back up xf86config, but you would want to back up XF86Config (two different files).
Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 18 November 2002, 05:26
....but I mean, Slackware wouldn't boot up, because it would hang at the part that X11 loads.

I tried to edit inittab so it would default to runlevel 3, but it said it was write-protected (this was using Knoppix)

I probably could've saved myself a lot of trouble if I had remembered how to boot slackware into runlevel 3, but I didn't.
Title: I fucked up my Slackware!!!
Post by: voidmain on 18 November 2002, 05:28
At the LILO or GRUB prompt, just add "single" to the boot line which will boot your system in single user mode.

If you use LILO do this:

LILO: linux single

If GRUB, press "a" at the GRUB boot menu. Move to the end of the kernel line and add "single" and press ENTER.

[ November 17, 2002: Message edited by: void main ]

Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 18 November 2002, 05:35
O.k.-thanks! I know I will need that again...probably sooner than later.  :D
Title: I fucked up my Slackware!!!
Post by: RudeCat7 on 19 November 2002, 05:06
Void Main,

Thanks!!! As you can see, I actually needed that much sooner than you might of thought....

....curiosity killed the Cat, again...

In a default Slackware install, I used, vmlinuz single.

and that saved my ass!!!  :D