Skip to contentSkip to conversation

Regression: ps2mouse not working in 2.6.34

DISCUSSION Mark Lord 2 participants 7 messages Jun 28, 2010

lore
Share & tools
lore

Mark Lord

author
#0 lore raw

Okay, who broke it, and how do I re-enable it?

The PS/2 mice on my systems here don't do anything with 2.6.34. One system complains that I need to boot with i8042.nopnp to enable it, which I also tried, but still nogo. Same behaviour with or without /dev/psaux enabled. 64-bit kernel.

The other system, running older userspace, hangs at the X-server startup
because it cannot find the mouse. No i8042 warnings. 32-bit kernel.

Both systems working fine with older kernels.
Google finds lots of other people discovering the same problem.

What gives?

#1 lore raw
Quoted 7 lines · Mark Lord

Okay, who broke it, and how do I re-enable it?

The PS/2 mice on my systems here don't do anything with 2.6.34. One system complains that I need to boot with i8042.nopnp to enable it, which I also tried, but still nogo. Same behaviour with or without /dev/psaux enabled. 64-bit kernel.

Quoted 8 lines

The other system, running older userspace, hangs at the X-server startup
because it cannot find the mouse. No i8042 warnings. 32-bit kernel.

Both systems working fine with older kernels.
Google finds lots of other people discovering the same problem.

What gives?

Well, lest start small: did it work ifor you with 2.6.33? Does kernel discover AUX serio port (dmesg)? What about the mouse itself? Is it absent or is it not reporting events?

Thanks.

Signature · 1 line
Dmitry
author
#5 lore raw
In reply to Mark Lord
Quoted 7 lines · Mark Lord

Okay, who broke it, and how do I re-enable it?

The PS/2 mice on my systems here don't do anything with 2.6.34. One system complains that I need to boot with i8042.nopnp to enable it, which I also tried, but still nogo. Same behaviour with or without /dev/psaux enabled. 64-bit kernel.

Quoted 7 lines

The other system, running older userspace, hangs at the X-server startup because it cannot find the mouse. No i8042 warnings. 32-bit kernel.

Both systems working fine with older kernels.
Google finds lots of other people discovering the same problem.

What gives?

..

Mmmm.. the problem started for some people with 2.6.32:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/587134

That thread has a suggestion that perhaps
"the kernel fails to properly set the power settings for the PS2 port"

Whatever that means. :)

#6 lore raw
Quoted 14 lines · Mark Lord
Quoted 13 lines · Mark Lord

Okay, who broke it, and how do I re-enable it?

The PS/2 mice on my systems here don't do anything with 2.6.34. One system complains that I need to boot with i8042.nopnp to enable it, which I also tried, but still nogo. Same behaviour with or without /dev/psaux enabled. 64-bit kernel.

The other system, running older userspace, hangs at the X-server startup because it cannot find the mouse. No i8042 warnings. 32-bit kernel.

Both systems working fine with older kernels.
Google finds lots of other people discovering the same problem.

Quoted 6 lines
Quoted 1 line

What gives?

..

Mmmm.. the problem started for some people with 2.6.32:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/587134

When did it start for _you_? I really do not know what kernel and patches are in Lucid so I'd much more prefer knowing the vanilla kernel version - I could at least see what has been changed there.

Are you also using USB-to-PS/2 converter?

Probably if you boot with i8042.debug and post full dmesg we coudl see what is going on there...

Quoted 5 lines

That thread has a suggestion that perhaps
"the kernel fails to properly set the power settings for the PS2 port"

Whatever that means. :)

I have no idea either.

Signature · 1 line
Dmitry
author
#2 lore raw
In reply to Dmitry Torokhov
Quoted 14 lines · Dmitry Torokhov
Quoted 13 lines · Mark Lord

Okay, who broke it, and how do I re-enable it?

The PS/2 mice on my systems here don't do anything with 2.6.34. One system complains that I need to boot with i8042.nopnp to enable it, which I also tried, but still nogo. Same behaviour with or without /dev/psaux enabled. 64-bit kernel.

The other system, running older userspace, hangs at the X-server startup
because it cannot find the mouse. No i8042 warnings. 32-bit kernel.

Both systems working fine with older kernels.
Google finds lots of other people discovering the same problem.

Quoted 6 lines
Quoted 2 lines

What gives?

Well, lest start small: did it work ifor you with 2.6.33? Does kernel discover AUX serio port (dmesg)? What about the mouse itself? Is it absent or is it not reporting events?

..

I started by crawling into the wire nest under the table. :)

After a certain amount of experimentation, it appears that the newer kernel is not compatible with the USB-to-PS2 dongle on the end of the mouse. I found a different USB-to-PS2 dongle which does work, though.

Very weird. I can mail you the other dongle if are really interested in figuring out what broke and fixing it.

Otherwise, things are now working here again after the hardware change.

Cheers

#3 lore raw
Quoted 23 lines · Mark Lord
Quoted 19 lines · Dmitry Torokhov
Quoted 7 lines · Mark Lord

Okay, who broke it, and how do I re-enable it?

The PS/2 mice on my systems here don't do anything with 2.6.34. One system complains that I need to boot with i8042.nopnp to enable it, which I also tried, but still nogo. Same behaviour with or without /dev/psaux enabled. 64-bit kernel.

Quoted 7 lines

The other system, running older userspace, hangs at the X-server startup
because it cannot find the mouse. No i8042 warnings. 32-bit kernel.

Both systems working fine with older kernels.
Google finds lots of other people discovering the same problem.

What gives?

Well, lest start small: did it work ifor you with 2.6.33? Does kernel discover AUX serio port (dmesg)? What about the mouse itself? Is it absent or is it not reporting events?

..

Quoted 8 lines

I started by crawling into the wire nest under the table. :)

After a certain amount of experimentation, it appears that the newer kernel is not compatible with the USB-to-PS2 dongle on the end of the mouse. I found a different USB-to-PS2 dongle which does work, though.

Very weird. I can mail you the other dongle if are really interested in figuring out what broke and fixing it.

Hmm, let me dig out one of my dongles first and see if it is broken too... If not I might be interested in getting yours but no promises - time is tight ;(

Thanks.

Signature · 1 line
Dmitry
author
#4 lore raw
Quoted 30 lines · Dmitry Torokhov
Quoted 29 lines · Mark Lord
Quoted 11 lines · Dmitry Torokhov
Quoted 10 lines · Mark Lord

Okay, who broke it, and how do I re-enable it?

The PS/2 mice on my systems here don't do anything with 2.6.34. One system complains that I need to boot with i8042.nopnp to enable it, which I also tried, but still nogo. Same behaviour with or without /dev/psaux enabled. 64-bit kernel.

The other system, running older userspace, hangs at the X-server startup
because it cannot find the mouse. No i8042 warnings. 32-bit kernel.

Quoted 8 lines
Quoted 4 lines

Both systems working fine with older kernels.
Google finds lots of other people discovering the same problem.

What gives?

Well, lest start small: did it work ifor you with 2.6.33? Does kernel discover AUX serio port (dmesg)? What about the mouse itself? Is it absent or is it not reporting events?

..

I started by crawling into the wire nest under the table. :)

After a certain amount of experimentation, it appears that the newer kernel is not compatible with the USB-to-PS2 dongle on the end of the mouse. I found a different USB-to-PS2 dongle which does work, though.

Quoted 5 lines
Quoted 2 lines

Very weird. I can mail you the other dongle if are really interested in figuring out what broke and fixing it.

Hmm, let me dig out one of my dongles first and see if it is broken too... If not I might be interested in getting yours but no promises - time is tight ;(

..

I'm beginning to suspect the dongle I was using simply went bad
at the same time I upgraded kernels. It no longer works with older stuff either.

So.. unfortunate timing of a hardware failure with kernel upgrade.

Nothing to see here.

Thanks Dmitry!