Date: Sun, 10 May 2009 14:35:17 +0100 From: Mike Clarke <jmc-freebsd2@milibyte.co.uk> To: freebsd-questions@freebsd.org Subject: Re: Problems after upgrading to xorg-7.4_1 Message-ID: <200905101435.17396.jmc-freebsd2@milibyte.co.uk> In-Reply-To: <69401662@bb.ipt.ru> References: <200905072343.46922.jmc-freebsd2@milibyte.co.uk> <69401662@bb.ipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday 08 May 2009, Boris Samorodov wrote: > New xorg uses hal by default. > > You have two options: either use hal [1] (i.e. start dbus and hald > while booting) or not use it (then you should tweak xorg.conf). > Either way please read recent freebsd-x11@ mail list archieves to > understand what's up and what to do. > [1] http://lists.freebsd.org/pipermail/freebsd-x11/2009-April/008185.html Thanks for the link. I was aware that xorg now uses hal but I didn't realise I would need to make any configuration adjustments to hal. Adding the keyboard details to /usr/local/share/hal/fdi/policy/10osvendor/10-x11-input.fdi as described in the link fixed the problem. I was also able to get the keyboard working correctly without hal and dbus by adding Option "AllowEmptyInput" "off" to xorg.conf. Since hal doesn't appear to usefully do anything else for me I've gone for the AllowEmptyInput option. I still need to fix my problem with the nv and nvidia drivers but I've discovered that things work OK with the vesa driver so I'll use that for now. -- Mike Clarke
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905101435.17396.jmc-freebsd2>