Mouse not working after upgrading to 12.1

Swift&Smart · 03-14-2009, 12:27 AM

Hello,everyone!

I upgraded my Slackware from 12 to 12.1 recently. However,the mouse is not working after that.

I am using xfce as the Window Manager, but the mouse is not working. That mouse is plugged in the PS/2 socket.

I hope you guys would give me some suggestions on this if you have. :-)

gegechris99 · 03-14-2009, 03:56 PM

Hello,

According to the CHANGES_AND_HINTS.TXT of Slackware 12.1, the psmouse module is loaded automatically and may be causing your problem:

Quote:

The psmouse module is no longer blacklisted by default; instead, it is loaded
with the imps protocol per /etc/modprobe.d/psmouse -- if you need/want a
different protocol, edit that file. Note that options declarations have
no bearing on *if* a module is loaded - they only affect *how* it is loaded.
In other words, the module should now be loaded automatically (since it's no
longer blacklisted), and the options in /etc/modprobe.d/psmouse are the ones
applied when loading it.

Try to blacklist it back again and see if it solves your mouse issue.

Swift&Smart · 03-14-2009, 10:10 PM

gegechris99,thanks for your reply.

I have read the file psmouse and see that is enabled by default because it will rule out the problem of using mouse in KVM. I'm using KVM now. So,it's okay to let it enable by default. However,I have to comment out that line since "uncomment" makes my mouse not functioning. After I reboot it,the mouse still doesn't work.

I really don't know what's happening since I don't have any problem in previous version.

Thanks.

rworkman · 03-15-2009, 01:20 AM

Depending on how you upgraded, it's highly likely that you have a backup file of the old /etc/modprobe.d/blacklist file still in the /etc/modprobe.d directory. See the next paragraph of CHANGES_AND_HINTS.TXT for details on why that matters:

Code:

The /etc/modprobe.d/blacklist file has been changed significantly; be sure to
  move/merge the /etc/modprobe.d/blacklist.new file in its place.  Also, you
  must NOT leave a backup of the old blacklist file (such as blacklist.orig)
  in /etc/modprobe.d/ -- ALL files in that directory are checked, so if a 
  module is blacklisted in *any* of them, it won't be loaded.

Swift&Smart · 03-16-2009, 02:43 PM

rworkman,thanks for your reply,it works!!!!!!!!!!!

Sorry for asking that dumb question as I forget the thing about upgrading.There are many ***.old or ***.bak file didn't merge with the new configuration file.As a result,some of the program didn't work.

Thanks again.