10.0-RC4 -> 10.0-RC5: Xorg stopped using /dev/sysmouse
Jan Henrik Sylvester
me at janh.de
Thu Jan 9 13:42:31 UTC 2014
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
More information about the freebsd-stable
mailing list