Date: Thu, 16 Jan 2014 09:21:55 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: Rainer Hurling <rhurlin@gwdg.de> Cc: clutton <clutton@zoho.com>, FreeBSD Current <freebsd-current@freebsd.org> Subject: Re: mouse pointer has gone. Message-ID: <CAN6yY1szJd7_MFtaVcicK1FVQGhYmcFW--F4EE6BewowA5-acw@mail.gmail.com> In-Reply-To: <52D80DC8.7010202@gwdg.de> References: <1389881241.2088.68.camel@eva02.mbsd> <52D80DC8.7010202@gwdg.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jan 16, 2014 at 8:50 AM, Rainer Hurling <rhurlin@gwdg.de> wrote: > Am 16.01.2014 15:07, schrieb clutton: > > Using X, I have a frozen mouse pointer. > > Mouse works fine from syscons but not from X. Booting from kernel.old > > resolves the problem. > > > > Here is my X log with current kernel. > > > > 158:[ 34.043] (==) NVIDIA(0): Silken mouse enabled > > 208:[ 34.232] (II) config/hal: Adding input device PS/2 Mouse > > 209:[ 34.232] (II) LoadModule: "mouse" > > 210:[ 34.233] (II) > > Loading /usr/local/lib/xorg/modules/input/mouse_drv.so > > 211:[ 34.236] (II) Module mouse: vendor="X.Org Foundation" > > 215:[ 34.237] (II) Using input driver 'mouse' for 'PS/2 Mouse' > > 216:[ 34.237] (**) PS/2 Mouse: always reports core events > > 218:[ 34.237] (==) PS/2 Mouse: Protocol: "Auto" > > 219:[ 34.237] (**) PS/2 Mouse: always reports core events > > 222:[ 34.238] (EE) PS/2 Mouse: cannot open input device > > 223:[ 34.238] (EE) PreInit returned 2 for "PS/2 Mouse" > > 224:[ 34.238] (II) UnloadModule: "mouse" > > > > > > And with kernel.old > > > > 158:[ 30.743] (==) NVIDIA(0): Silken mouse enabled > > 208:[ 30.941] (II) config/hal: Adding input device PS/2 Mouse > > 209:[ 30.941] (II) LoadModule: "mouse" > > 210:[ 30.942] (II) > > Loading /usr/local/lib/xorg/modules/input/mouse_drv.so > > 211:[ 30.945] (II) Module mouse: vendor="X.Org Foundation" > > 215:[ 30.946] (II) Using input driver 'mouse' for 'PS/2 Mouse' > > 216:[ 30.946] (**) PS/2 Mouse: always reports core events > > 217:[ 30.946] (**) Option "Device" "/dev/sysmouse" > > 218:[ 30.946] (==) PS/2 Mouse: Protocol: "Auto" > > 219:[ 30.946] (**) PS/2 Mouse: always reports core events > > 220:[ 30.947] (==) PS/2 Mouse: Emulate3Buttons, Emulate3Timeout: 50 > > 221:[ 30.947] (**) PS/2 Mouse: ZAxisMapping: buttons 4 and 5 > > 222:[ 30.947] (**) PS/2 Mouse: Buttons: 5 > > 224:[ 30.947] (II) XINPUT: Adding extended input device "PS/2 > > Mouse" (type: MOUSE, id 7) > > 225:[ 30.948] (**) PS/2 Mouse: (accel) keeping acceleration scheme 1 > > 226:[ 30.948] (**) PS/2 Mouse: (accel) acceleration profile 0 > > 227:[ 30.948] (**) PS/2 Mouse: (accel) acceleration factor: 2.000 > > 228:[ 30.948] (**) PS/2 Mouse: (accel) acceleration threshold: 4 > > 229:[ 30.948] (II) PS/2 Mouse: SetupAuto: hw.iftype is 4, hw.model is > > 0 > > 230:[ 30.948] (II) PS/2 Mouse: SetupAuto: protocol is SysMouse > > > > For me, it helped to rebuild devel/dbus and sysutils/hal and restart > that services again. > > HTH, > Rainer > sysutils/hal needs rebuilding due to a change in the kernel ABI. It is NOT the only port affected by the change and rebuilding all ports is recommended, but to get the pointer to work only requires a re-built hald. devel/dbus has no problems. I can tell you that you need to also rebuild sysutils/tmux, if you use it. I'll admit to being lazy and have not rebuilt all ports to this point. Only the two ports mentioned have caused any problems, so far. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1szJd7_MFtaVcicK1FVQGhYmcFW--F4EE6BewowA5-acw>