OK.

[frustrated]
I'm at my witts end. I have spent most of the day today trying to get the 2.6.0 kernel to work. It compiles fine, only every single time, no matter what I try I am unable to use my mouse in either console or X. I have tried using the old .config file from slack 9.1 and making the necessary changes to get framebuffer support, I have tried makeing a .config file from scratch. I have done everything I can think of, and still, every time I boot up I am left mouseless. XFree86.0.log shows no errors on X start-up, and nothing in my XF86config file has changed. I can even get the NVIDIA drivers working fine, but still no mouse. It's like it's not even there. Funny thing is, I have used 3 of the frickin' 2.6 test kernels (2.6 test 3, test 7, and test 9) and ALL OF THEM HAVE WORKED FINE. Idiot me erased all my source trees when I DL'ed 2.6.0, and I'd like to get 2.6.0 working anyway. I have searched the forums and found no mention of anyone having a problem like this. I mean, come on. It's a frickin' PS2 wheel mouse, what the heck am I missing???!!!

my .config (well, the last one I tried at least, just the stuff pertaining to mouse):

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=m
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_PS2_SYNAPTICS is not set
CONFIG_MOUSE_SERIAL=m
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
[/frustrated]

slight

do u have mouse when in console only?

Nope.... and I have tried enabling and disabling gdm as well.

slight

Take and disable the modules for serial mouse you are loading it as a module. That my cause some issues?

Walt

Compiling it as a module won't harm anything. It's not loaded in any of the scripts.

slight

What does your

dmesg | grep PS/2
more /var/log/XFree86.0.log |grep mouse

say?

It's maybe something changed in the stable 2.6.0 kernel. Maybe someone could help you if he/she has the same hardware as yours.

And, last thing... ALWAYS SAVE YOUR KERNEL CONFIGS either in your /boot/ and/or somewhere else...

Just my 2 €/cents.

dmesg | grep PS/2 says:

Mice: PS/2 mouse device common for all mice

My XFree86.0.log shows no errors. I've already been over it with a fine toothed comb, even comparing it to the log from my 2.4.22 kernel install (which is what I am typing this post on). Gpm doesn't work either, which seems to me would point to a module or option that needs to be loaded/compiled into the kernel.

slight

Very strange... anyway if X starts without errors that means that your PS/2 mouse is being successfully found and use as your corepointer.

What about:

dmesg | grep input

And, what does gpm exactly complains about? Something like mousedev?
If you can, please post the exact error message.

Hope this could help.

That's the strange thing... according to dmesg, gpm (or is it gdm, I always forget) loads fine. No error messages, nothing that shows up in any of the logs. It's as if the kernel is recognizing the mouse, and everything loads fine, but for some reason it just doesn't accept any input. As you said, X starts fine, so it at least knows that a mouse is attached to the system. This is a stock Slackware 9.1 install, with only a few minor modifications in the way of installed dependencies. What am I missing?

slight

Using normal device-nodes, devfs or udev for devices? Maybe you should try a different one than the one you currently use?

Ummm.... I'm not sure, honestly. How would I go about changing between devfs and udev, and how do I know which one is loaded to begin with? Are they modules? Is their a config file?

slight

You include support for it when building the kernel and can enable disable them before boot by passing various settings to the kernel.

Example:

devfs=mount or devfs=nomount

I haven't used udev so I don't know about that though. Normal device-nodes should be the default.

I'll have to give it a shot when I get home. I'm at work right now, and my company blocks SSH, so I can't try it now.

slight

Closer yet farther away....

I noticed that in all my previous compiles that I neglected to select devfs, so I gave it a shot. I installed the NVIDIA driver for the 2.6 kernel and tried to startx, only to be kicked back to CLI with X complaining that the core pointer could not be contacted. This did not happen before. Previously I was able to startx and have X come up as if it detected the mouse, however the mouse would not move. Interesting......

I will continue screwing with my kernel .config. In the meantime if someone with a working 2.6 kernel would like to e-mail the contents of their .config file to me for comparison I would be very gratefull

slightcrazed@linuxquestions.net

slight

I'm having the same problem. PS/2 Mouse (Logitech Cordless Wheel Mouse - keyboard is running on the same cordless controller without isssues) no workie on 2.6. I'm running a brand new build of Fedora core 1 and just installed the RH RPMs for 2.6 (2.6.0-1.109). With both the stock kernel, and rolling my own, I get the same symptom. However, if I boot back to 2.4 mouse works fine.

Further this is the only discussion of this issue I have been able to find. If I were having problems with a USB mouse everyone and their brother would have the answer, but it seems slight and I are the only people running into trouble with PS2.

# dmesg | grep mouse
mice: PS/2 mouse device common for all mice
# dmesg | grep input
input: ImPS/2 Generic Wheel Mouse on isa0060/serio1
input: AT Translated Set 2 keyboard on isa0060/serio0

I can see the mouse being properly identified by X, but it won't move or do anything. Basically exactly as slight is describing.

Machine:
Asus A7V
Duron 600@750
512MB PC133
NVidia TNT2
Turtle Beach Montego II (au8830)
Linksys NIC (tulip)
Aver TV98 (bt848)

So... slight if you figure it out, please post! Thanks.