Hi Zenja, I thought this problem was fixed already... guess not. Sounds like a race condition between the input_server device traversing the available keyboards and setting up node monitoring for these folders. Ie, the device is added by the driver after the input device searched for it, but before the node monitoring is effective. I have not looked at the code if this is really a possible cause. IIRC, the console mode uses the same driver, so it is probably not the drivers fault, as you also suggest. Maybe you can edit your boot script, so that input_server start is delayed. If this fixes the problem, and no other interference prevents this trick from working, then my assumption is likely correct. Best regards, -Stephan