Date: Fri, 19 Nov 2004 10:29:09 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Chuck Robey <chuckr@chuckr.org> Cc: FreeBSD-current@freebsd.org Subject: Re: mouse problems Message-ID: <20041119182909.GB14789@odin.ac.hmc.edu> In-Reply-To: <20041119130644.G38351@april.chuckr.org> References: <20041118222536.R38351@april.chuckr.org> <20041119105620.J38351@april.chuckr.org> <20041119162454.GA14789@odin.ac.hmc.edu> <20041119122917.V38351@april.chuckr.org> <20041119130644.G38351@april.chuckr.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--CUfgB8w4ZwR/yMy5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Nov 19, 2004 at 01:14:52PM -0500, Chuck Robey wrote: > On Fri, 19 Nov 2004, Chuck Robey wrote: >=20 > > > The PS/2 mouse is configured in /etc/rc.conf with the lines: > > > > > > moused_enable=3D"YES" > > > moused_flags=3D"" > > > > > > and the USB mouse is handled by the default entrly in usbd.conf which= is > > > enabled in rc.conf with: > > > > > > usbd_enable=3D"YES" > > > > VERY good, thanks for the response, please work with me here. First, I= 'm > > working with a brand new amd64 install, so my etc is hopefully (and more > > properly, my rc.conf) up to date, it has a mouse_ports, but not a > > moused_flags at all, so you may be working witha customized etc ... no = big > > surprise. I interpolated, tried your settings, on reboot I have no > > /dev/psm0 device. I looked at the psm man page, and I dolled up the > > /boot/loader.conf as instructed. on reboot, kenv reports what I would > > want to see, but still no /dev/psm0 (which is why, I suppose, I have on= ly > > a single moused process running, the usbd.conf inspired one. That one, > > the mouse cursor still disappears the moment I touch the keyboard.. > > > > That info I did, I tried both with and without the atkbdc hint in the m= ail > > archives. > > > > I notice, btw, that the usb (ums0) gets probed by the kernel well, well > > before rc.conf gets asked about psm0 ... I bet that timing is something > > that, if I could change, might help things. I would like the psm to get > > started before the usb one. >=20 > Bad etiquete to reply to myself, but I had more ideas, and I tried them. > I'm again at an end, but I have this to add: I went in and deleted the > ums0 entry from usbd.conf, so that it won't get attached; if I use the > serial converter so that my keyboard and mouse are serial, then /dev/psm0 > does get created; if ums0 is being cteaed first, then /dev/psm0 is > unavailble to the system for some reason, I can't get it created later on. > I need some method to delay the usb processing for the keyboard and mouse > combo UNTIL all of the PS/2 processing is finished. >=20 > Obviously, /dev/psm0 and /dev/ums0 get along poorly. >=20 > BTW, yes, I tried adding the ums0 back after I had the good (?) > /dev/psm0, again, the mouse cursor disappears the moment I touch the > keyboard. It flickers to life, and is immediately gone. I don't > understand abou that, your notion about running two moused processes was > aluring. >=20 > Funny point? for the PS/2 case, rc.conf is NOT making a moused process. > That's not working. OK, that's something I can investigate. >=20 > Again, if anyone thinks they know all of the steps to completely delete > the ps/2 mouse an dkeyboard from the system (leaving me the usb ones) let > me know, I'll try anything that looks like a complete task list. Does your BIOS have a legacy mode setting? If so, please try disabling it. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --CUfgB8w4ZwR/yMy5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBnjt1XY6L6fI4GtQRAgYyAJ98AWYoHPcj9NZnJvDDhAq4xfBgywCfVQ6m a2/6BJhqg5nol6DXN5nzwBg= =XRIN -----END PGP SIGNATURE----- --CUfgB8w4ZwR/yMy5--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041119182909.GB14789>