Date: Mon, 26 Aug 2019 07:23:03 -0500 From: Antonio Olivares <olivares14031@gmail.com> To: Polytropon <freebsd@edvax.de> Cc: "Kevin P. Neal" <kpn@neutralgood.org>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: PS mouse/USB mouse no response Message-ID: <CAJ5UdcNWWfZuQ3fVQTYm7SiPa09WmfLH_jNB9dHveqw5cnbsgw@mail.gmail.com> In-Reply-To: <20190825073425.40f308fc.freebsd@edvax.de> References: <CAJ5UdcMzJVTeGDkfPxWst83FZ4KYrYv3bzqvWwm3WT8qa%2BfQzQ@mail.gmail.com> <20190824075357.a091c2d6.freebsd@edvax.de> <20190825012112.GA38082@neutralgood.org> <20190825073425.40f308fc.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Aug 25, 2019 at 12:34 AM Polytropon <freebsd@edvax.de> wrote: > > On Sat, 24 Aug 2019 21:21:12 -0400, Kevin P. Neal wrote: > > On Sat, Aug 24, 2019 at 07:53:57AM +0200, Polytropon wrote: > > > On Fri, 23 Aug 2019 18:16:14 -0500, Antonio Olivares wrote: > > > > I have and old HP machine which ran windows 7 home premium and I > > > > sucessfully loaded FreeBSD 12.0-RELEASE-p10 updated successfully both > > > > freebsd-update and through pkg. The machine boots and loads X but the mouse > > > > does not respond. I have tried a PS2 mouse and corresponding > > > > moused_enable="YES" in /etc/rc.conf [...] > > > > > > That's not sufficient. First, check for the psm (PS/2 mouse) > > > device to exist: > > > > > > # dmesg | grep psm > > > psm0: <PS/2 Mouse> irq 12 on atkbdc0 > > > psm0: [GIANT-LOCKED] > > > psm0: model MouseMan+, device ID 0 > > > > I seem to remember that PS/2 devices only work if attached before boot. > > Is that correct? > > That is correct, expected, and logical. > > The PS/2 connector is _not_ capable of hot-plug operations. You can > even destroy it when you plug / unplug a PS/2 keyboard or mouse when > the system is already powered on. The specification of that port is > from a time where hot-plugging was not common, so don't take the risk. > > > > > And, if so, is that how the OP is trying the experiment? > > By rebooting. The PS/2 mouse will be connected when the system is > powered off. If possible, it should be _really_ powered off with > the switch on the back of the power supply. If there is no such > switch, remove the power cable, just to be sure. After reboot, > the dmesg output should contain the PS/2 mouse entry. Without that > entry, any experiments on PS/2 mouse support are futile. > > With USB, it's a lot easier: It can be plugged in during system > operation, and kernel messages (or dmesg output, or system log > file) will immediately (!) tell you what has been attached. Further- > more, devd will, in case a ums-type device has been recognized, > start moused with the appropriate parameters. > > This should all work in "text mode" (console), and of course in X. > > > > > -- > Polytropon > Magdeburg, Germany > Happy FreeBSD user since 4.0 > Andra moi ennepe, Mousa, ... Dear kind folks, I have great news. I plugged in a usb to ps2 converter and stuck in the usb mouse and it works! root@f104-2:~ # dmesg | grep psm psm0: <PS/2 Mouse> irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model IntelliMouse Explorer, device ID 4 root@f104-2:~ # Thanks for all your help. The usb mouse worked by plugging it in to the front usb drives but not the back ones when starting the machine. olivares@f104-2$ uname -a FreeBSD f104-2 12.0-RELEASE-p10 FreeBSD 12.0-RELEASE-p10 GENERIC amd64 olivares@f104-2$ Best Regards, Antonio
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ5UdcNWWfZuQ3fVQTYm7SiPa09WmfLH_jNB9dHveqw5cnbsgw>