Re: logitech cordless mouse w/ freebsd 5.3 stable
I removed above this to save some bandwidth, as bandwidth is not free every where in the world :) Chuck Robey wrote: I then edit the pointer section of /etc/X11/xorg.conf to: Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/bpsm0 I am running FreeBSD-6.0-current, but I bet it works for you like it works (just fine) for me. Try it, what have you got to lose? However, if it works, you owe us a usage report, Sirrah! Anyhow, FreeBSD is not terribly willing to share the mouse. When it boots, the stupid thing will start 'moused' processes on both mouses. Check this with: ps -ax | grep mouse if it's like I think it is, one of the lines that come back will report a device filename of ums0. You need this process dead, dead, dead. You *could*, I suppose, edit /etc/usbd.conf ... After you do that, the stuff you have above for Xorg isn't enough either, cause you left out the wheel. take those lines out and replace them with Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/ums0 Option Buttons 5 Option ZAxisMapping 4 5 EndSection Don't forget, at the top: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Try this, tell me how it works. Chuck, Setting my mouse driver to ums0, will make X crash before loading. My box never reported the ums0 device/the usb mouse. The usbd is running. There is no moused processes running on this box, as it is disabled in /etc/rc.conf. I get the scroll wheel to work as a middle button, but you are right, the scroll feature does not work. Option Buttons 5 Option ZAxisMapping 4 5 Setting those two options does not enable the scroll wheel. I think that is due to the generic PS/2 driver reported in dmesg. Having a working scroll wheel was never a issue for me :) Also note, I never tried FreeBSD 6.x . I am not sure if the following info matters or not: This is included as it may give you some hints for fixing the wheel feature. This mouse config was a combination of some google hints that led me to look at, 'man psm', 'man device.hints', and my experience with Freebsd 4.x. FreeBSD 4.x taught me that using /dev/bpsm0 in the X config would work, with this mouse and this kvm. I didn't try setting up the moused in /etc/rc.conf with FreeBSD 5.x. In FreeBSD 4.x adding the bpsm0 config to /etc/rc.conf just lead to error messages getting reported to my shells every so often. Here is some additional info: %ls /dev acd0ata fidopsm0ttyv3 acpiatkbd0 geom.ctlptyp0 ttyv4 ad0 audio0.0io ptyp1 ttyv5 ad0s1 audio0.1kbd0ptyp2 ttyv6 ad0s10 bpf0klogptyp3 ttyv7 ad0s1a bpsm0 kmemrandom ttyv8 ad0s1b console log sndstat ttyv9 ad0s1c consolectl lpt0stderr ttyva ad0s1d cttylpt0.ctlstdin ttyvb ad0s1e cuaa0 mdctl stdout ttyvc ad0s1f cuaia0 mem sysmousettyvd ad0s2 cuala0 mixer0 ttyd0 ttyve ad0s3 devctl net ttyid0 ttyvf ad0s4 devstat net1ttyld0 urandom ad0s5 dsp0.0 net2ttyp0 usb ad0s6 dsp0.1 net3ttyp1 usb0 ad0s7 dspW0.0 network ttyp2 usb1 ad0s8 dspW0.1 nfs4ttyp3 usb2 ad0s9 dspr0.1 nullttyv0 xpt0 agpgart fd pci ttyv1 zero apm fd0 ppi0ttyv2 %cat /etc/rc.conf # -- sysinstall generated deltas -- # Mon Jan 3 05:51:08 2005 # Created: Mon Jan 3 05:51:08 2005 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=demon-spawn.bsdunix.us ifconfig_rl0=DHCP linux_enable=YES usbd_enable=YES moused_port=/dev/psm0 moused_type=auto moused_enable=NO % %ps auxw | grep usbd root362 0.0 0.2 1240 780 ?? Ss5:51AM 0:00.01 /usr/sbin/usbd eric871 0.0 0.1 348 232 p3 R+7:38AM 0:00.00 grep usbd %ps auxw | grep mouse eric 1240 0.0 0.5 2276 1760 p1 RV9:18AM 0:00.00 grep mouse (csh) this seems like a waste of bandwidth but... %dmesg Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980,
Re: logitech cordless mouse w/ freebsd 5.3 stable
On Mon, 14 Mar 2005, Eric wrote: I removed above this to save some bandwidth, as bandwidth is not free every where in the world :) Chuck Robey wrote: I then edit the pointer section of /etc/X11/xorg.conf to: Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/bpsm0 I am running FreeBSD-6.0-current, but I bet it works for you like it works (just fine) for me. Try it, what have you got to lose? However, if it works, you owe us a usage report, Sirrah! Anyhow, FreeBSD is not terribly willing to share the mouse. When it boots, the stupid thing will start 'moused' processes on both mouses. Check this with: ps -ax | grep mouse if it's like I think it is, one of the lines that come back will report a device filename of ums0. You need this process dead, dead, dead. You *could*, I suppose, edit /etc/usbd.conf ... After you do that, the stuff you have above for Xorg isn't enough either, cause you left out the wheel. take those lines out and replace them with Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/ums0 Option Buttons 5 Option ZAxisMapping 4 5 EndSection Don't forget, at the top: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Try this, tell me how it works. Chuck, Setting my mouse driver to ums0, will make X crash before loading. My box never reported the ums0 device/the usb mouse. The usbd is running. There is no moused processes running on this box, as it is disabled in /etc/rc.conf. I get the scroll wheel to work as a middle button, but you are right, the scroll feature does not work. Just 1 thing I need to confirm: did you kill the moused process BEFORE starting X? Because if you didn't, that's exactly what happens to me. I need to kill the moused process that is tying up ums0, then I can start up X. Option Buttons 5 Option ZAxisMapping 4 5 Setting those two options does not enable the scroll wheel. I think that is due to the generic PS/2 driver reported in dmesg. Having a working scroll wheel was never a issue for me :) Also note, I never tried FreeBSD 6.x . No, let's fix the mouse first, then we worry about the mouse wheel. I am not sure if the following info matters or not: This is included as it may give you some hints for fixing the wheel feature. This mouse config was a combination of some google hints that led me to look at, 'man psm', 'man device.hints', and my experience with Freebsd 4.x. FreeBSD 4.x taught me that using /dev/bpsm0 in the X config would work, with this mouse and this kvm. I didn't try setting up the moused in /etc/rc.conf with FreeBSD 5.x. In FreeBSD 4.x adding the bpsm0 config to /etc/rc.conf just lead to error messages getting reported to my shells every so often. Here is some additional info: %ls /dev acd0ata fidopsm0ttyv3 acpiatkbd0 geom.ctlptyp0 ttyv4 ad0 audio0.0io ptyp1 ttyv5 ad0s1 audio0.1kbd0ptyp2 ttyv6 ad0s10 bpf0klogptyp3 ttyv7 ad0s1a bpsm0 kmemrandom ttyv8 ad0s1b console log sndstat ttyv9 ad0s1c consolectl lpt0stderr ttyva ad0s1d cttylpt0.ctlstdin ttyvb ad0s1e cuaa0 mdctl stdout ttyvc ad0s1f cuaia0 mem sysmousettyvd ad0s2 cuala0 mixer0 ttyd0 ttyve ad0s3 devctl net ttyid0 ttyvf ad0s4 devstat net1ttyld0 urandom ad0s5 dsp0.0 net2ttyp0 usb ad0s6 dsp0.1 net3ttyp1 usb0 ad0s7 dspW0.0 network ttyp2 usb1 ad0s8 dspW0.1 nfs4ttyp3 usb2 ad0s9 dspr0.1 nullttyv0 xpt0 agpgart fd pci ttyv1 zero apm fd0 ppi0ttyv2 %cat /etc/rc.conf # -- sysinstall generated deltas -- # Mon Jan 3 05:51:08 2005 # Created: Mon Jan 3 05:51:08 2005 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=demon-spawn.bsdunix.us ifconfig_rl0=DHCP linux_enable=YES usbd_enable=YES
Re: logitech cordless mouse w/ freebsd 5.3 stable
Chuck Robey wrote: On Mon, 14 Mar 2005, Eric wrote: I removed above this to save some bandwidth, as bandwidth is not free every where in the world :) Chuck Robey wrote: I then edit the pointer section of /etc/X11/xorg.conf to: Identifier Mouse1 Driver mouse Option ProtocolAuto Option Device /dev/bpsm0 I am running FreeBSD-6.0-current, but I bet it works for you like it works (just fine) for me. Try it, what have you got to lose? However, if it works, you owe us a usage report, Sirrah! Anyhow, FreeBSD is not terribly willing to share the mouse. When it boots, the stupid thing will start 'moused' processes on both mouses. Check this with: ps -ax | grep mouse if it's like I think it is, one of the lines that come back will report a device filename of ums0. You need this process dead, dead, dead. You *could*, I suppose, edit /etc/usbd.conf ... After you do that, the stuff you have above for Xorg isn't enough either, cause you left out the wheel. take those lines out and replace them with Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/ums0 Option Buttons 5 Option ZAxisMapping 4 5 EndSection Don't forget, at the top: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Try this, tell me how it works. Chuck, Setting my mouse driver to ums0, will make X crash before loading. My box never reported the ums0 device/the usb mouse. The usbd is running. There is no moused processes running on this box, as it is disabled in /etc/rc.conf. I get the scroll wheel to work as a middle button, but you are right, the scroll feature does not work. Just 1 thing I need to confirm: did you kill the moused process BEFORE starting X? Because if you didn't, that's exactly what happens to me. I need to kill the moused process that is tying up ums0, then I can start up X. I do not have any problem with the moused running at all (after doing the steps in the original email). Also as far as my os is concerned there is no USB mouse attached to the workstation. We are using different versions of FreeBSD :) By editing /etc/rc.conf and adding this line at the end: moused_enable=NO , and then rebooting, keeps my moused from starting. I suppose I could have done #killall -9 moused *and* edited /etc/rc.conf with no immediate reboot. When I appended the line to /boot/device.hints, I rebooted for that too. This box is a workstation with one user, me, so uptime is not a issue. As far as the order of the steps, please see the original email. I did start X last after doing everything in the original email, as the mouse did not work at all until all steps were complete. Option Buttons 5 Option ZAxisMapping 4 5 Setting those two options does not enable the scroll wheel. I think that is due to the generic PS/2 driver reported in dmesg. Having a working scroll wheel was never a issue for me :) Also note, I never tried FreeBSD 6.x . No, let's fix the mouse first, then we worry about the mouse wheel. I re-read man psm and I believe the flags i set (/boot/device.hints) keep the mouse driver at level 0. A level 1 driver would make the scroll wheel work. When I boot with a level 1 driver, my mouse is completly dead in X. It is beyond my skills and desire, to code a custom driver :) I am not sure if the following info matters or not: This is included as it may give you some hints for fixing the wheel feature. This mouse config was a combination of some google hints that led me to look at, 'man psm', 'man device.hints', and my experience with Freebsd 4.x. FreeBSD 4.x taught me that using /dev/bpsm0 in the X config would work, with this mouse and this kvm. I didn't try setting up the moused in /etc/rc.conf with FreeBSD 5.x. In FreeBSD 4.x adding the bpsm0 config to /etc/rc.conf just lead to error messages getting reported to my shells every so often. Here is some additional info: %ls /dev acd0ata fidopsm0ttyv3 acpiatkbd0 geom.ctlptyp0 ttyv4 ad0 audio0.0io ptyp1 ttyv5 ad0s1 audio0.1kbd0ptyp2 ttyv6 ad0s10 bpf0klogptyp3 ttyv7 ad0s1a bpsm0 kmemrandom ttyv8 ad0s1b console log sndstat ttyv9 ad0s1c consolectl lpt0stderr ttyva ad0s1d cttylpt0.ctlstdin ttyvb ad0s1e cuaa0 mdctl stdout ttyvc ad0s1f cuaia0 mem sysmousettyvd ad0s2 cuala0 mixer0 ttyd0 ttyve ad0s3
Re: logitech cordless mouse w/ freebsd 5.3 stable
My ugly mouse hack: I am sure this question has already been answered, although I couldn't find the answer via google. Hardware and Software: Logitech USB cordless mouse M/N:M-RN67 P/N:851390- 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 cel Using the ps/2 adapter with my mouse, was required to use the kvm. 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 ProtocolAuto 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 hope this helps someone else :) YMMV, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: logitech cordless mouse w/ freebsd 5.3 stable
On Sun, 13 Mar 2005, Eric wrote: My ugly mouse hack: I am sure this question has already been answered, although I couldn't find the answer via google. Hardware and Software: Logitech USB cordless mouse M/N:M-RN67 P/N:851390- 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 cel Using the ps/2 adapter with my mouse, was required to use the kvm. 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 ProtocolAuto Option Device /dev/bpsm0 I am running FreeBSD-6.0-current, but I bet it works for you like it works (just fine) for me. Try it, what have you got to lose? However, if it works, you owe us a usage report, Sirrah! Anyhow, FreeBSD is not terribly willing to share the mouse. When it boots, the stupid thing will start 'moused' processes on both mouses. Check this with: ps -ax | grep mouse if it's like I think it is, one of the lines that come back will report a device filename of ums0. You need this process dead, dead, dead. You *could*, I suppose, edit /etc/usbd.conf ... After you do that, the stuff you have above for Xorg isn't enough either, cause you left out the wheel. take those lines out and replace them with Section InputDevice Identifier Mouse0 Driver mouse Option Protocol auto Option Device /dev/ums0 Option Buttons 5 Option ZAxisMapping 4 5 EndSection Don't forget, at the top: Section ServerLayout Identifier X.org Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Try this, tell me how it works. 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 hope this helps someone else :) YMMV, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] Chuck Robey | Interests include C Java programming, FreeBSD, [EMAIL PROTECTED] | electronics, communications, and SF/Fantasy. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary (on the wall at my old fraternity, Signa Phi Nothing). ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: logitech cordless mouse w/ freebsd 5.3 stable
Eric, Please submit this via the send-pr mechanism so that it will get fixed in the next version of FreeBSD. thanks, Ted [EMAIL PROTECTED] wrote: My ugly mouse hack: I am sure this question has already been answered, although I couldn't find the answer via google. Hardware and Software: Logitech USB cordless mouse M/N:M-RN67 P/N:851390- 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 cel Using the ps/2 adapter with my mouse, was required to use the kvm. 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 ProtocolAuto 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 hope this helps someone else :) YMMV, Eric ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
