On Thu, Jun 11, 2009 at 1:54 PM, Tino Keiteltino.keitel+x...@tikei.de wrote:
Hi,
as the Intel driver is very fragile recently, I want to test it in a
chroot environment, and keep the stable 2.4 driver in the normal
system. This implies that I also keep an old version of the X server in
the
On Sat, Jun 13, 2009 at 01:35:19PM +0200, Maarten Maathuis wrote:
They can never be replaced by evdev, because evdev is linux-only. But
yes, evdev is often used on linux platforms, but it does need a
working hal.
HAL and evdev are independent. HAL is a replacement for xorg.conf and most
On Fri, Jun 12, 2009 at 07:17:56 +0800, Li, Yan wrote:
[...]
Have you tried X -configure to generate a usable xorg.conf (inside
chroot). And if necessary, adding your own Keyboard and Mouse section
like this:
Section InputDevice
Identifier Generic Keyboard
Driver
They can never be replaced by evdev, because evdev is linux-only. But
yes, evdev is often used on linux platforms, but it does need a
working hal.
Maarten.
___
xorg mailing list
xorg@lists.freedesktop.org
Hi,
for the records: stopping HAL outside the chroot and starting it inside
the chroot works, and now I can use X inside a chroot.
Regards,
Tino
___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
On Thu, Jun 11, 2009 at 10:54:52PM +0200, Tino Keitel wrote:
(II) Cannot locate a core pointer device.
(II) Cannot locate a core keyboard device.
(II) The server relies on HAL to provide the list of input devices.
If no devices become available, reconfigure HAL or disable
Hi,
as the Intel driver is very fragile recently, I want to test it in a
chroot environment, and keep the stable 2.4 driver in the normal
system. This implies that I also keep an old version of the X server in
the normal system. So I installed a chroot system. But HAL can not be
used in a chroot,
On Thu, 11 Jun 2009 22:54:52 +0200
Tino Keitel tino.keitel+x...@tikei.de wrote:
Hi,
as the Intel driver is very fragile recently, I want to test it in a
chroot environment, and keep the stable 2.4 driver in the normal
system. This implies that I also keep an old version of the X server
in