Okay, so I went ahead and installed Slackware 11 (current) a few hours ago and everything is working nicely. Wait, scratch that, everything except for this damn mouse! Sorry, I'm just a little frustrated. Now where was I, oh yeah, this mouse is your run of the mill wired optical 2 button scroll wheel mouse from Logitech. It works fine out of the box under WinXP and FreeBSD 6.1, but under Slack it craps out. The optical light is on but the pointer on screen will not move. I've tried every option available when using the "mouseconfig" app, but when the system loads the "gpm" app at boot time I get no pointer nor does it work under X. This also happened with Slack 10.2, any ideas???

try stopping the 'gpm' on CLi

#killall gpm
then rush to GUI
#startx

If it works then you can stop the gpm script pemanently issuing the command:
#chmod -x /etc/rc.d/rc.gpm

regards

I have exactly the same problem.

Disabling gpm does nothing for me.

what protocols have you tried?

`modprobe psmouse` fixed it for me.

The new rc.modules did not have the line `/sbin/modprobe psmouse` that was in my original.

Okay, unfortunately neither of your suggestions happened to work . However, I did happen to figure out what part of the problem was . In my original post I forgot to mention that upon this and previous installations of Slackware I got into the habit of choosing the 2.6 series kernel as opposed to the default 2.4. What lead me to suspect the kernel were some dmesg error's while booting up, which read something along the lines "2.6.17.xx /lib/modules/blah/blah error whil trying to load". So I thought hmmm, why not try falling back to the default bareacpi.i kernel image that I used to install the system originally . So I did that and when it I got to "mouseconfig" I chose "PS/2" since the mouse I'm dealing with is in fact a PS/2 (Duh!), and viola, it works .

For those of you who are experiencing this same problem, I guess could use this as a temporarily solution. Even though this does not specifically solve the problem I do still plan to use the 2.6 series kernel, when I have a little more time to weed out the actual problem of course. Until then I'll be looking forward to test driving this "current version" of what appears to be a very promising Slackware release.

Is it possible that you forgot to install the kernel modules for the 2.6.17 kernel? They would be in /testing/packages/linux-2.6.17.8.

I wasn't aware that you had to do that right after you finish installing Slackware with a 2.6 series kernel . If so how come I don't have these issues after installing Slack with the 2.4 series kernel, is this something which is only exclusive to the 2.6 series??? ???

Slackware uses the 2.4 kernel by default. If you did a full install the 2.4 modules are already installed. (They are in the "A" disk set.)

If you choose a 2.6 kernel, you have to install the matching modules. You know where the 2.6.17.8 modules are now. I've been using huge26.s. The modules for that kernel are in /extra/linux-2.6.16.27.

Ahhh, so I see... Is there a seperate how to for this or would I just use pkgtool for that???