On mer., 2009-11-11 at 16:49 +0100, Michael Biebl wrote: > I think only the devices named input* are relevant (9 to go). Then > test each of > them if it has a capabilities/sw file. > > What do you get if you run > cd /sys/class/input > for i in `seq 0 8`; do > cat input$i/capabilites/sw > done
cor...@hidalgo: for i in `seq 0 8`; do for> cat input$i/capabilites/sw for> done cat: input0/capabilites/sw: No such file or directory cat: input1/capabilites/sw: No such file or directory cat: input2/capabilites/sw: No such file or directory cat: input3/capabilites/sw: No such file or directory cat: input4/capabilites/sw: No such file or directory cat: input5/capabilites/sw: No such file or directory cat: input6/capabilites/sw: No such file or directory cat: input7/capabilites/sw: No such file or directory cat: input8/capabilites/sw: No such file or directory cor...@hidalgo: find /sys/class/input -name sw This is on debian 2.6.31: Linux hidalgo 2.6.31-1-amd64 #1 SMP Sat Oct 24 17:50:31 UTC 2009 x86_64 GNU/Linux So I guess “something” doesn't report the LID input. What puzzles me is that it's a ThinkPad, which is vastly used by Linux people, so I would expect that kind of stuff to be present if it's the way to go. Though, iirc, LID events are reported using event4: /dev/input/event4 bustype : BUS_HOST vendor : 0x0 product : 0x5 version : 0 name : "Lid Switch" phys : "PNP0C0D/button/input0" bits ev : EV_SYN EV_SW Cheers, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
