perhaps try to switch to a runlevel that does not have X window running. it could be that the X window code is competing for these events - and when you make tests, you don't want to have that.
--guy On Tue, 2011-02-15 at 11:55 +0200, Dotan Cohen wrote: > On Tue, Feb 15, 2011 at 11:19, Yedidyah Bar-David > <linux...@didi.bardavid.org> wrote: > > I have no idea about the specific mouse or issue, but other places you > > can check are: > > > > 1. Outside of X, do > > od -tx1 /dev/input/mice > > then press various buttons and see what happens. > > > > Interesting approach. In fact, even buttons that _do_ work did not > reliably give any output. However, I could get absolutely zero output > from the buttons in question. > > > > 2. Try playing with acpi/acpid. E.g., from the examples of acpid > > - look at /usr/share/doc/acpid/examples/default{,.sh} > > (or at least that's where they are on my laptop - Debian Lenny). > > I personally managed to make "Fn F7" move between internal/external > > monitor by playing with it and an example I once found on google - > > I think it was this one: > > http://www.thinkwiki.org/wiki/Sample_Fn-F7_script > > > > I have no idea if you can get acpi events from "normal" keys (not Fn) > > and did not try this (yet?). > > > > Thanks, but I don't see how I could adapt that to a mouse. In any > case, it would have to be after I get a scancode from the device > buttons. > _______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il