-current and psmouse module?

abrouwers · 03-26-2008, 11:55 AM

Hi all,

I know -current now loads psmouse slightly differently than in 12.0. I've reproduced this bug a couple times, and can't find what I'm missing. Everytime I reboot the system, I have to load psmouse manually to have my mouse work in xorg.

I have installed a fresh copy of 12.0; generated a working xorg.conf, and tested the mouse, which loads and functions fine. I then rsync all of -current, update (properly :-) ), merge *.new files in /etc, and ensure rc.modules points to the new kernel (currently vmlinuz-generic-smp-2.6.24.3-smp). Yet, upon rebooting, the module does not load.

Am I missing a step? I can't quite seem to figure out why udev won't load this properly. The correct files seem to be in place in /etc/modprobe.d/, as well.

Franklin · 03-26-2008, 12:12 PM

Take a look a /ect/rc.d/rc.modules-2.6.24.3-smp

Code:

### 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

You could uncomment the line above that loads the psmouse module or try configuring the options in /etc/modprobe.d/psmouse as the comment suggests.

HTH

abrouwers · 03-26-2008, 12:26 PM

Hi Franklin,

Yes, I can certainly get it going by editing a few configs, but was curious if I'm the only one experiencing this requirement to get it going "out of the box."

Franklin · 03-26-2008, 01:51 PM

I would have to "guess" then that what your are seeing is an artifact of the/your upgrade process. I'm running current here installed clean over nfs and the psmouse module is loading fine with no intervention.

I would recheck for any .new files you might have missed. Also, I should probably say that I am running current with updates as of 3/22. I have not installed today's changes, but will be momentarily.

truthfatal · 03-26-2008, 04:03 PM

I also think that this is a symptom of the upgrade process. I was having the same issue until I took some time to clear out my residual 12.0 files, now I have no issues at all with psmouse.

abrouwers · 03-26-2008, 06:39 PM

I just tried a fresh 12.0 -> -current, and get the same symptoms. Not sure what else to check :-(

Code:

home# find /etc -iname "*.new*"
/etc/shadow.new
/etc/group.new
/etc/passwd.new

I have the rc.modules-2.6.21.5, and my config's are stored as "*.bak;" if I ignore those, here is what I have in /etc -

Code:

home# grep psmouse /etc/*/* | grep -v 2.6.21.5 | grep -v bak  
/etc/modprobe.d/isapnp:alias pnp:dPNP0F13 psmouse
/etc/modprobe.d/psmouse:# The default options when the psmouse module is loaded will completely
/etc/modprobe.d/psmouse:options psmouse proto=imps
/etc/rc.d/rc.modules:# for the psmouse module is in /etc/modprobe.d/psmouse.
/etc/rc.d/rc.modules:#/sbin/modprobe psmouse proto=imps
/etc/rc.d/rc.modules-2.6.24.3:# for the psmouse module is in /etc/modprobe.d/psmouse.
/etc/rc.d/rc.modules-2.6.24.3:#/sbin/modprobe psmouse proto=imps
/etc/rc.d/rc.modules-2.6.24.3-smp:# for the psmouse module is in /etc/modprobe.d/psmouse.
/etc/rc.d/rc.modules-2.6.24.3-smp:#/sbin/modprobe psmouse proto=imps

Franklin · 03-27-2008, 07:03 AM

Is it possible to just do a fresh install of current not use the upgrade path? For example, create an iso for cd 1 and 2 (or one dvd-iso) and install that. Since I do not have this problem I can't tell you exactly what to look for as far as old files are concerned.

This will not tell us what file(s) is responsible for the issue though.
Maybe truthfatal can add something here?

abrouwers · 03-27-2008, 07:42 AM

I figured out the cause. When I updated (and confirmed this yet with another fresh 12.0 -> -current), I scripted *.new files in /etc to be merged over, and the file in which they replaced to be file.bak (similar to the script in UPGRADE.txt). Unknowingly, anything in /etc/modprobe.d/* gets executed; so, the file /etc/modprobe.d/blacklist.bak blacklisted my psmouse module, even though /etc/modprobe.d/psmouse was present :-)

Thanks again to Rob for helping out

shadowsnipes · 04-04-2008, 07:09 PM

Quote:

Originally Posted by Franklin

Is it possible to just do a fresh install of current not use the upgrade path? For example, create an iso for cd 1 and 2 (or one dvd-iso) and install that. Since I do not have this problem I can't tell you exactly what to look for as far as old files are concerned.

This will not tell us what file(s) is responsible for the issue though.
Maybe truthfatal can add something here?

Eric Hameleers (Alien) has a nice script that will mirror any of the slackware versions (default is -current) and it will allow you to automatically create install cds or an install dvd. It can even check for updates to itself.

Check out Alien's mirror-slackware-current.sh script

rworkman · 04-04-2008, 08:31 PM

Quote:

Originally Posted by abrouwers

I figured out the cause.

Oh, *you* did? ;-) Just kidding, really.

Quote:

Unknowingly, anything in /etc/modprobe.d/* gets executed; so, the file /etc/modprobe.d/blacklist.bak blacklisted my psmouse module, even though /etc/modprobe.d/psmouse was present :-)

Well, "executed" isn't the correct term to use here, really, but it gets the point across.

For the record, those of you who use slackpkg also need to watch out for this -- slackpkg's new-config routine (the one that offers to compare and then keep or overwrite .new files) will, when overwriting, save the original files with a .orig extension. This will also bite you in the butt with module-init-tools.

Quote:

Thanks again to Rob for helping out

febriansasi · 04-05-2008, 01:16 AM

finally, an answer of my problem.
At first i guess the problem was xorg.conf