I think you should ask for support from your distribution.

If you're running the "stable" release of it, then there almost certainly aren't any new xorg packages to upgrade (meaning you screwed up).

If you're running the development version of it, then there are probably some important notes in the ChangeLog or elsewhere that you've neglected to read, and/or you didn't upgrade the other packages associated with it (IOW, you upgraded *only* xorg packages from the development version, leaving everything else with the packages from -stable). If that's the case, then yeah, it means you've screwed up.

Talk to arny.

i tried to update x.org server becouse i want to use
that aquarius plugin in compiz-fusion
and i get an error on compiz-fusion.
for transparant desktop u need to update x.org server
and for compiz-fusion to work on kde i solved this error message updating x.org server it's working i saw but now mouse is gone,,

yes i did all the 180 packages.

http://www.linuxquestions.org/questions/slackware-14/compiz-core-fatal-no-composite-extension-636704/
this is why i updated my x.org
i i realy did lose that specific message.

Is there anything interesting in /var/log/Xorg.0.log ?
Search for both "mouse" and "Mouse".

Or use `grep -i mouse /var/log/Xorg.0.log` to cover all your bases.

I'm also having the exact same issue. I went through the upgrade procedure that Pat outlines in CHANGES_AND_HINTS and UPGRADE.TXT from Slackware 12.0 to 12.1. Everything went smoothly with the exception of the loss of the mouse. I'm interested in the "/proc/dev/input/devices" resulting in Macintosh mouse button emulation. That seems to be the closest thing listed for a mouse. I also stopped getting the floating cursor on the console in user level 4. I don't know if that is a result of the upgrade, or if that could indicate that I have no mouse for xorg.conf to connect to.

I have to add that I use a Belkin KVM switch and I noticed that kvm's were mentioned in some of the comments as I looked for configuration options.

Everything in this post seems to be exactly the same as what I am experiencing.

What does "lsmod | grep psmouse" show?

-RW

I don't get anything at all. After insmod .../psmouse.ko, everything started to work. I should have known that it would be that easy. What would be the convention to get that thing inserted at bootup?

ryerke, what kernel are you using (vmlinuz-generic-smp-2.6.24.5-smp, vmlinuz-huge-smp-2.6.24.5-smp, vmlinuz-generic-2.6.24.5, vmlinuz-huge-2.6.24.5)? That's not the most relevant question since psmouse is built as a module in all kernels, but I just want to make sure you're using the right kernel. Have you tried `/sbin/modprobe psmouse proto=imps` as root? In /etc/modprobe.d/blacklist there's an explanation of psmouse stuff, and therefore the module is blacklisted and loaded manually by /etc/rc.d/rc.modules*, at least in Slackware 12.0 -- but this may have changed in 12.1. I think there's now a /etc/modprobe.d/psmouse file that dictates how the module gets loaded instead of blacklisting and manually loading in rc.modules*. The fact that it's still not loading properly may be because of an improper upgrade -- if it's still blacklisted in /etc/modprobe.d/blacklist (ie you didn't update that file [is there a .new file for that?]) and now is not getting loaded in /etc/rc.d/rc.modules*, it'll never get loaded. Try loading it manually (using the command above). If it works, try changing the blacklist file and making sure /etc/modprobe.d/psmouse exists and specifies the correct options -- or manually loading the module using /etc/rc.d/rc.modules*.

That's probably it there. Make sure you deleted the old blacklist file or it'll still get blacklisted.

First, ignore anyone who suggests editing rc.modules for now, as that's a last resort.

Second, look around in /etc/modprobe.d/ - what's happened is one of the following scenarios:
1. You still have both a 'blacklist' and a 'blacklist.new' file in there.
2. You have a 'blacklist' and a 'blacklist.orig' OR 'blacklist.bak'

If (1) is the case, then 'mv blacklist.new blacklist'
If (2) is the case, then 'rm blacklist.orig' or 'rm blacklist.bak'

If (1) is the case, then you need to search for more .new files in /etc (use 'find /etc -name "*.new"') to check and handle them accordingly.
If (2) is the case, then you probably used slackpkg to upgrade, and while that's fine, you need to be aware of this for future reference.

Either way, CHANGES_AND_HINTS.TXT documents this situation and what to do about it.

Thank you so much. I moved all of the old info into the .new files and cp'd them to the original configs, and yet I forgot that blacklist will look for any file that says blacklist (.bak, .new, etc.) Anyway, I thought I would wait until I was graphical to do the cleanup. Just like me to put off the chores 'til later.

I don't have time to make sure this works, but I've got a good idea that you're right. Right now it's time for bed.

Thanks again,
Bert

I removed the extra files in modprobe.d and that did the trick. I think I was looking for something more complicated and overlooked the obvious...especially when Pat V had included it in the CHANGES_AND_HINTS file. I still have some .new's to get rid of. I think there may be some from the 12.0 upgrade from 11.0. I was wondering if it will be necessary to merge the group, passwd, and shadow files as it seems the script for dealing with the .new's leaves them out. Is it safe to just delete the new ones that were installed?

Thanks again, and thanks, Robby, for all the work you do on the Slackware project.
Bert

Don't overwrite the group, passwd and shadow files -- that'll destroy your user setup. You should be fine leaving them alone. If you did merge them you may have some difficulty logging in or your group assignments may change.

Okay, I left them alone. Diff showed some changes but they seem inconsequential (an "x" in one of the fields) so I should be alright just to delete the .new files.

Much appreciated.