Hi Ben, I'm not confident it's related, but I believe that error is triggered by AutoAddDevices false in xorg.conf, but perhaps that's essential for your setup (if you don't hit solution, try posting xorg.conf here and a few more details on what your setup is). In xorg.conf, you could also try AllowEmptyInput true. I'm suspicious that it might be some kind of X recovery loop -- with multiple X servers, it's easy for X to mistakenly thinks things are miscofigured. Beyond Greg's question, it'd be nice to know if any traffic is making it to the displaylink X server or kernel driver - I don't have a good recommendation on how to watch that other than debugger. When you do get to the root cause, it'd be great to post back here or comment on the wiki. Thanks! Bernie <a href="http://plugable.com/">http://plugable.com/</a> <div class="gmail_quote">On Wed, Oct 14, 2009 at 10:18 AM, Ben Hardill <<a href="mailto:b.hardill@gmail.com">b.hardill@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> <div text="#000000" bgcolor="#ffffff"> Hi, Yep, just retested and the cpu usage ramps up straight away when I start Xorg and before everything else. There is nothing obvious in the log files, but I do get the following written out to stderr by the process: (EE) config/hal: NewInputDeviceRequest failed (8) (EE) config/hal: NewInputDeviceRequest failed (8) (EE) config/hal: NewInputDeviceRequest failed (8) Ben Hardill </div></blockquote></div>