On Thu, Mar 22, 2012 at 6:14 AM, Ken Moffat <zarniwh...@ntlworld.com> wrote:

> On Wed, Mar 21, 2012 at 05:56:45PM +0100, Dr.-Ing. Edgar Alwers wrote:
> > On Sun, 18 Mar 2012 14:46:41 -0500
> > Bruce Dubbs <bruce.du...@gmail.com> wrote:
> >
> > > First, the problem is xorg, so take kde out of the loop.  Look at the
> > > xorg config section and change ~/.xiinitrc
> >
> > In the meantime we have some new experiences:
> >
> > 1.) There are no differences in the behaviour of the desktop and the
> laptop ( my wife's system ). After recompiling the kernel of the desktop (
> it had not been renewed since the LFS7 installation ) it does not function
> anymore, exactly the same behaviour like the laptop
> >
>
>  I'm not sure if I've parsed that correctly - you say that the
> desktop used to work, but the new kernel broke it ?  I assume you
> mean that the mouse and keyboard stopped working in xorg ?
>
>  On the desktop, did you take the working config from the old kernel
> (hopefully, you have it in /proc/config.gz), copy it to .config in
> the new kernel source, and then run 'make oldconfig' ?
>
>  If you did, what versions were the old and new kernels ?
>
> > 2.)  In my own System I do not experience any problems. The difference
> to 1.) is that I have the old Xorg and my wife the new one with  the evdef
> driver. So, it _could be_ that the problem concerns the new xorg
> >
>
>  This is what makes me think I've misunderstood you - now you seem
> to be saying that the desktop has no problems ?
>
>  Anyway, for your wife's system, have you set CONFIG_INPUT_EVDEV in
> the kernel config ?
>
> > 3.) We changed ~/xinitrc to xterm as you suggested and introduced
> xkb-defaults.conf. There are keyboard and mouse availaible on the console
> _before_ entering "startx". After startx, xterm shows up but no
> keyboard/mouse are functioning ( wired mouse/trackball )
> > After the startx command,  the directory "/etc/X11/xorg.conf.d" contains
> two new files, "10-evdev.conf" and "11-keyboard.conf" and the original
> "xkb-defaults.conf" is away.
> >
>  Surely 10-evdev.conf was installed by the xorg-server, and you
> installed 11-keyboard.conf yourself ?  These are how the server is
> able to tie events to their sources.  Actually, taking a quick look
> through the rendered book I can't see where 11-keyboard.conf is
> mentioned.  I'm sure we mention it somewhere, because I believe that
> without it xorg should still work, but with an American keyboard
> layout which is not useful for everyone.
>
>  I think 10-evdev.conf should be ok - it comes from the server, so
> it should match what everyone else has.  For 11-keyboard.conf you
> should have something similar to this:
>
> Section "InputClass"
>        Identifier "keyboard-all"
>        Driver "evdev"
>        Option "XkbLayout" "gb"
>        Option "XkbModel" "evdev"
>        Option "XkbOptions" "ctrl_alt_bksp"
>        MatchIsKeyboard "on"
> EndSection
>
>  Obviously, you will not want "gb" for the layout.  I don't know if
> there are multiple german keyboard variants, but "de" seems a
> likely value to start with.
>
>  Looking at my own Xorg log, I think all the useful information for
> debugging goes to stderr and appears on the console, not in the log.
> So, try using 'startx 2>xorg-errors'.
>
>  Do you have MagicSysRQ enabled in the kernel ?  If you do (it's
> under Kernel Hacking), you can sync with Alt-SysRq-S, wait, then
> umount with Alt-SysRq-U and boot with Alt-SysRq-B : those keys
> should, I think, still work even if Xorg doesn't find the keyboard.
> If you have that, the Sync and Umount ought to allow the xorg-errors
> file to be updated.
>
> > 5.) some final lines of Xorg.0.log:
> > -------------------
> > 9428.142] (II) GLX: Initialized DRI2 GL provider for screen 0
> > [  9428.143] (II) intel(0): Setting screen physical size to 270 x 203
> > [  9428.793] (II) No input driver/identifier specified (ignoring)
> > [  9428.794] (II) config/udev: Adding input device TPPS/2 IBM TrackPoint
> (/dev/input/mouse0)
> > [  9428.794] (II) No input driver/identifier specified (ignoring)
>
>  I think those two 'No input driver' messages are the signs that the
> input devices are not configured correctly.
>
> ĸen
> --
> das eine Mal als Tragödie, das andere Mal als Farce
> --
> http://linuxfromscratch.org/mailman/listinfo/blfs-support
> FAQ: http://www.linuxfromscratch.org/blfs/faq.html
> Unsubscribe: See the above information page
>


Might be worth checking if udev is working correctly. I have just had a
similar problem and after many hours cursing Xorg,
found that udevd had changed location from /sbin to /lib/udev and was not
being started by the boot script.

Check with

     udevadm info --export-db | grep -B 4 -A 14 /dev/input/mouse0

which should contain a E: ID_INPUT=1 line.

cheers
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to