PDA

View Full Version : Mouse configuration on FreeBSD 4.8


tarballed
April 30th, 2003, 15:58
Morning everyone.

Just a real quick question. I installed FreeBSD 4.8 on my workstation (looks nice) however, I am having a few problems with the mouse. It goes crazy when I try and move it on the desktop. :(

Anyways, I remember awhile back, I was working with my FreeBSD box at home and was having to go in and manually edit the configuration file for my mouse. The only problem is, I do not recall the file (Im thinking XF86Config.new) and what I need to enter.

I also remember there was a link I had that had a pretty good description on how to troubleshoot mouse issues.

Anyone happen to have a link offhand, or some suggestions?

I should mention, the mouse is a PS/2 mouse, logitech 2 button with a wheel.

I appreciate it.

Tarballed

tarballed
April 30th, 2003, 17:52
I should mention that I have my two machines setup between a little two port KVM switch. Nothing fancy.

I have tried booting up to the FreeBSD box while the KVM is on it, but no luck.

When I first boot to the box, if I move the mouse, I get some errors. Like so:

FreeBSD /kernel: psmintr: out of sync (008 != 0000).

Possibly the KVM? Or is my mouse just not synced right?

Tarballed

soup4you2
April 30th, 2003, 18:42
have you tried booting up w/ out using the KVM? see if the same error is generated...

tarballed
May 1st, 2003, 01:31
Yep. That was it. The little KVM bastard was causing the problem.

No worries. Nothing like having a couple of mice running around on the desk. hehehe


Tarballed

Kernel_Killer
May 1st, 2003, 02:53
Had the same issue b4. Pain in the arse. You can slways run it w/o the daemon, or run with daemon (use auto protocol, and PS./2 on the port), and then set your XF86Config to Auto Protocol (or MouseSystems), and then use /dev/sysmouse.

If you don't any luck out of using the daemon, just completely disable it, and run with just XF86 (best bet most likely). The only reason I point this out is that even through, or not through my KVM, I've had this problem with various non-M$ mice in 4.5 4.7 4.8 and 5.0.