From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754950Ab0F1QEy (ORCPT ); Mon, 28 Jun 2010 12:04:54 -0400 Received: from ironport2-out.teksavvy.com ([206.248.154.183]:57131 "EHLO ironport2-out.pppoe.ca" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1754879Ab0F1QEw (ORCPT ); Mon, 28 Jun 2010 12:04:52 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq4BAM5kKExLd/sX/2dsb2JhbAAHgxaXC7VskGqBKYMJcgQ X-IronPort-AV: E=Sophos;i="4.53,498,1272859200"; d="scan'208";a="69041703" Message-ID: <4C28C81E.4010909@teksavvy.com> Date: Mon, 28 Jun 2010 12:04:46 -0400 From: Mark Lord User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-GB; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Dmitry Torokhov , Dmitry Torokhov , Linux Kernel Subject: Regression: ps2mouse not working in 2.6.34 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?