alain.didierj...@free.fr schrieb: > Definitly, an update shouldn't break an existing working configuration! This > happens these days only too often with the Xorg + hal mess. > I happen to use linux as a working tool and 3 days without being able to > launch > a working X is a source of problems! This is the second time. As for hal > config, > the author should remember that ol'saying:KISS for Keep It Simple, Stupid. > Now, with or without /etc/X11/xorg.conf, my machine (amd64), updated to > libxcb-1.4, xorg-1.6 and hal last version launches X all right, only mouse and > keyboard are not working ! > A line in /var/log/Xorg.0.log says: > (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' > will be disabled. > Where is that b..... AllowEmptyOption ? certainly not in xorg.conf. > How do I get back some input on X screen ? > I also get (with xorg.conf) > (EE) Failed to load module "type1" (module doesn't exist, 0) > (EE) Failed to load module "evdev" (module doesn't exist, 0) > Please help before I turn crazy (it might be too late) >
With 'launches X' do you mean your desktop environment (login -> startx) or xdm/kdm/gdm? In any case, try to add Option "AllowEmptyInput" "false" to your xorg.conf Section "ServerLayout" However, for me this has tripled any key press and also messed up some other things. You (and anyone else, actually) might also want to add Option "XkbOptions" "terminate:ctrl_alt_bksp" to the Section "InputDevice" of your keyboard. This will reenable Ctrl+Alt+Backspace for killing X. For me, X started to work again after removing ~/.Xauthority.
signature.asc
Description: OpenPGP digital signature
