LinuxQuestions.org - Mouse Problem

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Mouse Problem - rc.modules-2.6.23.1 (https://www.linuxquestions.org/questions/slackware-14/mouse-problem-rc-modules-2-6-23-1-a-593308/)

Mouse Problem - rc.modules-2.6.23.1

I note that in the 'rc.modules' file included in the 'Current' module package, the following appears:

Quote:

### Mouse support:
# PS/2 mouse support:
# The default in Slackware is to use proto=imps because that works with the
# most types of mice out of the box. For example, using proto=any will
# completely break the mouse if you change consoles with several models of KVM
# switches.
#
# This is commented out here because a better place to configure the options
# for the psmouse module is in /etc/modprobe.d/psmouse.
#
#/sbin/modprobe psmouse proto=imps

With this line commented-out, my mouse module does not load.

I certainly have '/etc/modprobe.d/psmouse'in my filesystem.

Do I need to add more to the modprobe.d directory to get the mouse module to load without calling it in rc.modules?.

Thanks,

Bill.

Many thanks - that sorted it.

It was the 'blacklist.old' file in my 'modprobe.d' directory that was still being read.

It was not obvious to me that all '*.old' files must be deleted.

Bill

There are no .old files created by anything that Slackware does.
For configuration files, the package will contain "file.new" -- it works something like this on install/upgrade:
1. If "file" does not exist on the target system, then "file.new" inside the package is renamed to "file" during postinstall.
2. If "file" exists on the target system, and "file.new" is identical, then "file.new" is deleted.
3. If "file" exists on the target system, and "file.new" is different, then "file.new" is left behind (and "file" is left untouched completely).

In other words, the .old files were created by something else. I think slackpkg does that if you allow it to overwrite the config files when it asks...