Here's a puzzle for someone who has a little free time... I've got a manual switchbox to switch my mouse, keyboard, and monitor between to computers. It's a manual switchbox, so it doesn't send a constant signal to both systems (like those fancy - and expensive - automatic ones). Here's the problem: When my mouse (actully a trackball, a PS/2 Logitech TrackMan Marble) is unplugged from the system, it ceases to remember how to send a signal to the system (I assume some initialization is being done by moused when it starts up). So, when I switch over to my second system and back over to the FreeBSD one, the cursor doesn't respond to any mouse movement. To fix it I have to kill moused and start it back up. Sort of a pain, albeit not completely unbearable. Anyone have any theories on how we could get moused to a) detect the mouse being unplugged and reinserted and b) reinitialize the mouse after this happens? Here's some fun info type stuff (in case it'll help)... I'm running FreeBSD 4.2-BETA #10 (although I believe the problem existed under FreeBSD 4.1-RELEASE too. >From dmesg (after a verbose boot): psm0: current command byte:0065 psm: status 00 02 64 psm: status 09 03 c8 psm: status 09 03 c8 psm: status 09 03 c8 psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 >From rc.conf: moused_flags="" moused_port="/dev/psm0" moused_type="auto" moused_enable="YES" I'd greatly appreciate any help anyone can give me! If you need any more info about my system setup, just give me a yell... Thanks a million.... Dave Howland [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
