freebsd stable - Jan 2014 - 10.0-RC4 -> 10.0-RC5: Xorg stopped using /dev/sysmouse

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

Killing all moused processes 'fixes' Xorg mouse but proper patch would
be
nice


On Thu, Jan 9, 2014 at 2:42 PM, Jan Henrik Sylvester <me at janh.de>
wrote:
> 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
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at
freebsd.org"
>

Jan,

On Thu, Jan 09, 2014 at 02:42:28PM +0100, Jan Henrik Sylvester wrote:
J> Although the announcement is still pending, I have just upgraded two
J> machines from 10.0-RC4 to 10.0-RC5. Now my mouse is not working in Xorg
J> anymore.
J> 
J> Is it necessary to rebuild all ports due to the ABI change in r260406?
J> Is there a reasonable way to find out, which ports are affected? Is
J> r260406 related at all?
J> 
J> Some details in case the cause of the problem is not simply using old
J> packages:
J> 
J> /dev/psm0 and /dev/usm0 are both picked up by moused and still work on
J> ttyvX (due to moused_enable="YES" and
devd_enable="YES" in rc.conf).
J> 
J> Before the upgrade, Xorg would use /dev/sysmouse, but now it tries to
J> open /dev/psm0 and /dev/usm0 directly, which fails, since they are
J> already in use.
J> 
J> I thought "Device" "/dev/sysmouse" as
"InputDevice" in my xorg.conf was
J> still relevant, but at least /dev/psm0 and /dev/usm0 are detected by
J> hald, since they are not listed in xorg.conf.
J> 
J> >From ps, I see hald is still recognizing sysmouse:
J> 
J> hald-addon-mouse-sysmouse: /dev/psm0 (hald-addon-mouse-sy)
J> hald-addon-mouse-sysmouse: /dev/ums0 (hald-addon-mouse-sy)
J> 
J> All ports related are up to date and have been build WITH_NEW_XORG=yes
J> but otherwise default options on 10.0-RC3 or 10.0-RC4 (amd64).

In my case after moving to newer X.org I needed to put line

        Option "AutoAddDevices" "Off"

and remove line

	Option "AllowEmptyInput" "Off"

from the Section "ServerLayout".

After that I got my mouse and keyboard working.

-- 
Totus tuus, Glebius.

On 01/09/2014 14:42, Jan Henrik Sylvester wrote:
> 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?
In case anyone else wonders, how serious "It is recommended to rebuild
and install all applications if possible" from the announcement should
be taken coming from a previous RC:

At least sysutils/hal malfunctions due to the restored ABI.

Searching for the dynamic uses of kinfo_getfile:

find /usr/local/ -type f | while read -r FILE ; do readelf -s "$FILE"
2>/dev/null | grep kinfo_getfile && echo "$(pkg which -qo
"$FILE")
$FILE" ; done

On my system, sysutils/tmux, x11/konsole, and sysutils/hal are using it.

Of course, there could be other uses of kinfo_file.

Cheers,
Jan Henrik