Prev: vhost-net: add dhclient work-around from userspace
Next: 2.6.35-rc2-git5 -- [drm:drm_mode_getfb] *ERROR* invalid framebuffer id
From: Mark Lord on 28 Jun 2010 12:10 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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Dmitry Torokhov on 28 Jun 2010 12:40 On Mon, Jun 28, 2010 at 12:04:46PM -0400, Mark Lord wrote: > 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? > 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. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Mark Lord on 28 Jun 2010 12:40 On 28/06/10 12:04 PM, Mark Lord wrote: > 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? ... 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. :) -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Dmitry Torokhov on 28 Jun 2010 13:00 On Mon, Jun 28, 2010 at 12:34:30PM -0400, Mark Lord wrote: > On 28/06/10 12:04 PM, Mark Lord wrote: > >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? > .. > > 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... > > 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. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Mark Lord on 28 Jun 2010 13:20
On 28/06/10 12:33 PM, Dmitry Torokhov wrote: > On Mon, Jun 28, 2010 at 12:04:46PM -0400, Mark Lord wrote: >> 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? >> > > 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |