HAL, xserver 1.5.3 and AllowEmptyInput

I still haven’t really traced the source of my scrambled Crux graphical systems — I’m hoping the Crux 2.5 release candidate sorts it out for me — but one thing that was mentioned to me in IRC was that an xorg-server 1.5.3 “bug” (“feature”?) causes both the keyboard and mouse to go dead if HAL isn’t running on the machine.

Of course, I run without HAL as a course of habit, so it didn’t surprise me when an Intrepid system I build up from nada had nada coming from the mouse and keyboard. A quick double-check of my personal desktop wiki, a sharp three-finger salute to regain control of my system, and with this line added to the “ServerLayout” option in my xorg.conf file,

Option "AllowEmptyInput" "false"

everything was right as rain. If, for some reason, you find yourself in the same boat, that might be what fixes it.

It’s worth mentioning that this didn’t solve my mangled X systems in Crux though. The solution to that problem is still out there somewhere. I want to believe.

Tilman’s note to the Crux faithful is here, and the Xorg mailing list discussion is here.

10 Responses to “HAL, xserver 1.5.3 and AllowEmptyInput”


  1. 1 Dapper Dan 2008/12/29 at 10:43 PM

    Missed this. It deals exactly with the issues I’m having! Sorry I didn’t see it sooner and thanks! :)

  2. 2 K.Mandla 2008/12/29 at 11:22 PM

    No problem! :D For what it’s worth I’ve been needing this tweak for both Arch and Ubuntu systems, mostly because I prefer to run without HAL and dbus. Ubuntu is a little less hamfisted about it because it will more or less automagically configure things, but Arch needs the option or you definitely get the dead X. Progress, we call it. … :roll:

  3. 3 johnraff 2009/02/05 at 1:53 AM

    How much do HAL and dbus slow things down?
    Conversely, what functionality do you lose by not having them, beyond automounting of plugin usb sticks?

    • 4 K.Mandla 2009/02/05 at 7:09 AM

      Ech, that’s a matter of personal experience really. I wouldn’t even consider using either HAL or dbus on that 100Mhz laptop, but my 1Ghz machine doesn’t flinch at them. I suppose it’s part of my reluctance to use daemons or subsystems that aren’t truly essential, and on a modern machine, it’s hardly noticed at all.

  4. 5 kone80 2009/10/06 at 3:53 AM

    menuconfig -> device drivers -> input device supports -> event interface
    is the real solution for this

    kone80


  1. 1 Playing whack-a-mole « Motho ke motho ka botho Trackback on 2008/12/04 at 7:17 PM
  2. 2 Stupid mistake, drastic solution « Motho ke motho ka botho Trackback on 2009/01/21 at 11:38 PM
  3. 3 One week at 100Mhz: X-less and not a hiccup « Motho ke motho ka botho Trackback on 2009/02/26 at 11:11 PM
  4. 4 What’s to like? « Motho ke motho ka botho Trackback on 2009/07/12 at 10:43 PM
  5. 5 Oliver Herold (olhe) 's status on Tuesday, 28-Jul-09 09:12:28 UTC - Identi.ca Trackback on 2009/07/28 at 6:12 PM

Leave a Reply




Welcome!

Some recent desktops


Sept. 24, 2009
screen-vs on Crux Linux
550Mhz Celeron 192Mb PC100


Aug. 21, 2009
Crux 2.4 with Xorg 7.3
and Musca 0.9.23
120Mhz Pentium 16Mb PC66 40Gb

Be counted!

License

This work is licensed under the GNU Free Documentation License. Please see the About page for details.

Downloads

Blog Stats

  • 1,402,153 hits

Categories

Archives

Calendar

November 2008
S M T W T F S
« Oct   Dec »
 1
2345678
9101112131415
16171819202122
23242526272829
30