misc/78812: logitech cordless mouse with ps/2 adapter will not work

eric eric at bsdunix.us
Mon Mar 14 03:00:12 PST 2005

>Number:         78812
>Category:       misc
>Synopsis:       logitech cordless mouse with ps/2 adapter will not work
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 14 11:00:11 GMT 2005
>Originator:     eric kistler <eric at bsdunix.us>
>Release:        FreeBSD 5.3-STABLE i386
System: FreeBSD demon-spawn.bsdunix.us 5.3-STABLE FreeBSD 5.3-STABLE #0: Sun Mar 13 08:53:16 CST 2005 root at demon-spawn.bsdunix.us:/usr/obj/usr/src/sys/CUSTOM i386


logitech USB cordless mouse will not work with ps/2 adapter
use a logitech USB cordless mouse with ps/2 adapter
see work around
 >Logitech USB cordless mouse M/N:M-RN67 P/N:851390-0000 w/ ps/2 adapter
 > Auravision slimseries ps/2 keyboard /w wire
 > a starband kvm switch, 4 port PS/2 for both keyboard and mouse
 > w/ extern
 > power source.
 > FreeBSD 5.3 stable cpu=2.8 celeroN
 >Work around:
 > dmesg reports this for my mouse by default:
 > psm0: <PS/2 Mouse> flags 0x24 irq 12 on atkbdc0
 > psm0: [GIANT-LOCKED]
 > psm0: model IntelliMouse Explorer, device ID 4
 > the mouse will not work.
 > appending: hint.psm.0.flags="0x204"
 > to /boot/device.hints
 > I now get this via dmesg:
 > psm0: <PS/2 Mouse> flags 0x204 irq 12 on atkbdc0
 > psm0: [GIANT-LOCKED]
 > psm0: model Generic PS/2 mouse, device ID 0
 > I then edited /etc/rc.conf and disabled my console mouse (moused)
 > (which I would prefere worked)
 > moused_enable="NO"
 > I then edit the pointer section of  /etc/X11/xorg.conf to:
 >     Identifier  "Mouse1"
 >     Driver      "mouse"
 >     Option "Protocol"    "Auto"
 >     Option "Device"      "/dev/bpsm0"
 > notice that is the "b" psm device that i am using which is for
 > blocking mode or bpsm
 > At any rate, the mouse now works in X, through the kvm, and
 > through usb
 > to ps/2 adapter.
 >I posted this workaround to freebsd-questions at freebsd.org, and recieved a suggestion to use the send-pr to help get it fixed in future versions. This is my first use of send-pr, so if it is done wrong, i apologise in advance.

More information about the freebsd-bugs mailing list