> > no output indeed. so do i understand you correctly? because of that, > some > > other application "steals" the events which therefor cannot be processed > by > > mouseemu? any ideas which applications that might be? > > No, that's not what I said. Usually mouseemu 'steals' the events. mouseemu > not getting any events at all does point to the kernel as likely culprit, > IMHO.
so what should be activated in the kernel in addition to CONFIG_INPUT_UINPUT=[y|m] (the only option i found that was necessary). > Regarding other apps receiving events, see my suggestion to search /proc > for any occurrences of 'event' files. Any process opening some event > device will have a file /proc/<pid>/fd/event%d showing in /proc. ls /proc/*/fd does not show any event%d files only symlinks in earlier postings in debian-powerpc, i have found something like /proc/input/devices. the input directory does not exist on my mac. > To see which events are processed by the kernel, load the evbug module and > watch /var/log/debug ok, moving the mouse produces something like ... event. dev: adb3:3.01/input, type: 2, code: 1, value -1 mouse-click ... event. dev: adb3:3.01/input, type: 1, code: 272, value 0 event. dev: adb3:3.01/input, type: 0, code: 0, value 0 pressing ctrl ... event. dev: adb2:2.c4/input, type: 1, code: 29, value 0 event. dev: adb3:3.01/input, type: 0, code: 0, value 0 michael -- Telefonieren Sie schon oder sparen Sie noch? NEU: GMX Phone_Flat http://www.gmx.net/de/go/telefonie -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
