From owner-freebsd-stable@FreeBSD.ORG Thu Jan 9 13:42:31 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 76F38BB9 for ; Thu, 9 Jan 2014 13:42:31 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 126B11519 for ; Thu, 9 Jan 2014 13:42:30 +0000 (UTC) Received: from nb981.math (nb981.math.uni-hamburg.de [134.100.222.111]) by mrelayeu.kundenserver.de (node=mrbap1) with ESMTP (Nemesis) id 0LosHL-1VTrrK392J-00g6Mk; Thu, 09 Jan 2014 14:42:21 +0100 Message-ID: <52CEA744.8050105@janh.de> Date: Thu, 09 Jan 2014 14:42:28 +0100 From: Jan Henrik Sylvester User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: stable-list freebsd Subject: 10.0-RC4 -> 10.0-RC5: Xorg stopped using /dev/sysmouse Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:45H2LkDRGi6I3MC/uU007YhIFPumUM4Os6JNH6ssQC7 JyYJwDgRM8UJ6a/bzbFFDJshbZdylIQ9nG2pG/t79uXgd303jN FoNxATi0UbKlW25eIbKuBrrl2MTOSDpZWCTAEWhnpXyiFE1VsB RJcLasP4giRm9HrBTJF6v6xwVRn02QzMK1MguBZC8DwF1gytEt kLd3SCA2rsfTWH6CgF94KHZGI068sxySTZYxd8c7RC0b83DqgI OciqCrrA1BiP5ClmNl9JKy2m1zG0q9ddl1u4ZP7eHPr9mvwH2W 5tA6Vo/UT0kXg3jP36vtPt2z66i8vnK4FugZEzX6PMI4SWhiw= = X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Jan 2014 13:42:31 -0000 Although the announcement is still pending, I have just upgraded two machines from 10.0-RC4 to 10.0-RC5. Now my mouse is not working in Xorg anymore. Is it necessary to rebuild all ports due to the ABI change in r260406? Is there a reasonable way to find out, which ports are affected? Is r260406 related at all? Some details in case the cause of the problem is not simply using old packages: /dev/psm0 and /dev/usm0 are both picked up by moused and still work on ttyvX (due to moused_enable="YES" and devd_enable="YES" in rc.conf). Before the upgrade, Xorg would use /dev/sysmouse, but now it tries to open /dev/psm0 and /dev/usm0 directly, which fails, since they are already in use. I thought "Device" "/dev/sysmouse" as "InputDevice" in my xorg.conf was still relevant, but at least /dev/psm0 and /dev/usm0 are detected by hald, since they are not listed in xorg.conf. >From ps, I see hald is still recognizing sysmouse: hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy) hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy) All ports related are up to date and have been build WITH_NEW_XORG=yes but otherwise default options on 10.0-RC3 or 10.0-RC4 (amd64). Cheers, Jan Henrik