I've just built LFS7.9 in a virtual machine. I also built a number of
additional packages, including most of 'X Window System Environment',
while still in the VM.
I've since transferred the build to a physical drive and continued to
run it natively. All packages are building/running fine etc., except X.
The keyboard (and mouse through GPM) works just fine in the console, but
becomes completely unresponsive after launching X (with startx). Even
switching TTY's doesnt' work. At this point I have to ssh in from
another machine and kill the X server to get control. This happens with
both a PS/2 and a USB keyboard.
Initially I installed th xf86-input-evdev driver as suggested. I also
tried the (what I now understand to be legacy) xf86-input-keyboard
driver but not luck.
I tried to inspect and compare config files from the initial host system
(running debian jessie) with the new LFS system. There are no obvious
omissions (missing udev rules), but because the debian system is systemd
based I might be missing something.
I also install dbus as per BLFS instructions, but that didn't help
either (and to my knowledge wasn't required on any previous system
anyway).
The same hardware is running fine in debian (and in the console for that
matter) so hardware failure is not an issue.
My last assumption is that building in a VM affected the build process
somehow (or maybe the default kernel configuration?), but not knowing
what I'm looking for I haven't been able to find anything.
To note: I am using ratpoison as my window manager, but I don't really
see how that could be having an effect.
Any Ideas?
Many Thanks
Max
--
http://lists.linuxfromscratch.org/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
