<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=iso-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hummm, this is very interesting indeed. Maybe I was on the wrong track.<br>
<br>
Doing the find -type p yielded the result:<br>
/dev/shm/acpi_fakekey<br>
which was:<br>
ls -al /dev/shm/acpi_fakekey<br>
p-w------- 1 root root 0 2010-02-10 23:24 /dev/shm/acpi_fakekey<br>
<br>
after a chmod 222 it was:<br>
ls -al /dev/shm/acpi_fakekey<br>
p--x--x--x 1 root root 0 2010-02-10 23:24 /dev/shm/acpi_fakekey<br>
<br>
Doing that makes it so that when a normal user tries to use
acpi_fakekey I no longer get the permission denied message. Small
victory, but my volume keys still don't work.<br>
<br>
So I followed the path that Jim recommended....<br>
kawa:~# cat /usr/share/acpi-support/key-constants | grep VOL<br>
KEY_VOLUMEDOWN=114<br>
KEY_VOLUMEUP=115<br>
<br>
kawa:~# ls /dev/input<br>
by-path event10 event13 event3 event6 event9 mouse1<br>
event0 event11 event14 event4 event7 mice mouse2<br>
event1 event12 event2 event5 event8 mouse0 uinput<br>
<br>
As you can see, those events are clearly missing based on his
description. Any clues as to why those might be missing? Since my
keys are still not working, is it possible that /etc/acpi/volupbtn.sh
is not the file being used? Since my first path was not the cause of
the problem, I have also included the contents of one of those acpi
files, just in case it gives any more clues:<br>
<br>
#!/bin/sh<br>
<br>
test -f /usr/share/acpi-support/key-constants || exit 0<br>
<br>
. /usr/share/acpi-support/key-constants<br>
acpi_fakekey $KEY_VOLUMEUP<br>
<br>
Do you guys think that the flaw is because those event's in /dev/input
don't exist? If so, any ideas on why they don't exist? Thanks for all
the great already....this has helped me tons.<br>
<br>
chris fedde wrote:
<blockquote
cite="mid:7de3d64f1002110947l58a5cber4e6e2c4d2150f40b@mail.gmail.com"
type="cite">
<pre wrap="">I opened and read /etc/acpi/volupbtn.sh on my ubuntu box. I see it
uses acpi_fakekey as you say.
I then checked if acpi_fakekey has a man page to see if any clues were
buried there.
in that man page I found that it used fifos (aka named pipes) in /dev/input/
And that the event numbers are defined in /usr/share/acpi-support/key-constants
I find that
grep KEY_VOLUMEUP /usr/share/acpi-support/key-constants
KEY_VOLUMEUP=115
So the fifo in question is /dev/input/event115 in my case.
But this all begs the real question which is why are these fifos not
writable by the acpid daemon.
I suspect some boot time failure or misconfiguration when acpid is
started at boot time.
so I then started looking in /etc/init.d/acpid for more clues when my
gumption ran out.
Maybe some of this research will be helpful to you.
On Thu, Feb 11, 2010 at 9:49 AM, Jim Ockers <a class="moz-txt-link-rfc2396E" href="mailto:ockers@ockers.net"><ockers@ockers.net></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Mike,
You are going to have to do a bit of detective work. The brute force way
might be to just do "find / -type p" as root and see what comes up.
[root]# find / -type p -exec ls -l {} \;
prw------- 1 root root 0 Nov 18 15:20 /dev/initctl
...
There will be more, I don't know how long the find command will take, but it
may take a long time depending on your system. As for which process is
using it, try 'lsof -n" to see what filehandles each process has open.
Hope this helps,
Jim
Mike Jensen wrote:
That is VERY helpful. I did not know that previously.
But that does beg the question, how can I find out which file acpi_fakekey
is trying to use and does not have the proper permissions for?
Jim Ockers wrote:
Hi Mike,
FIFOs are usually unix pipe special files. Here is an example:
[root@agadez tmp]# touch this_is_a_normal_file
[root@agadez tmp]# mknod this_is_a_fifo p
[root@agadez tmp]# ls -al this*
prw-r--r-- 1 root root 0 Feb 11 07:16 this_is_a_fifo
-rw-r--r-- 1 root root 0 Feb 11 07:16 this_is_a_normal_file
As you can see the FIFO has permissions associated with it just like any
other file. Please check the permissions on your FIFO using ls -al and
see who has permission to write to it and read from it. Here is an
example of me changing the permissions on my FIFO file:
[root@agadez tmp]# chmod 666 this_is_a_fifo
[root@agadez tmp]# ls -al this_is_a_fifo
prw-rw-rw- 1 root root 0 Feb 11 07:16 this_is_a_fifo
I hope this helps,
Jim
Mike Jensen wrote:
Been lurking around for a while, but never posted before. Sorry to have
my first post be a help request.
I am trying to get the volume up/down/mute key to work on my Lenovo
T400. The distro is Debian Squeeze, fully updated, amd64. My volume
keys don't seem to work, so I traced down /etc/acpi/volupbtn.sh (and
others), and noticed that it was using acpi_fakekey....when I run it as
such in root, there is no problems, it returns fine. But when I run the
same thing as a normal user I get: fifo: Permission denied
Let me know if there is any more information I can provide. I have
searched around but have not seen this percise problem before. Thanks
in advanced.
_______________________________________________
clue-tech mailing list
<a class="moz-txt-link-abbreviated" href="mailto:clue-tech@cluedenver.org">clue-tech@cluedenver.org</a>
<a class="moz-txt-link-freetext" href="http://cluedenver.org/mailman/listinfo/clue-tech">http://cluedenver.org/mailman/listinfo/clue-tech</a>
_______________________________________________
clue-tech mailing list
<a class="moz-txt-link-abbreviated" href="mailto:clue-tech@cluedenver.org">clue-tech@cluedenver.org</a>
<a class="moz-txt-link-freetext" href="http://cluedenver.org/mailman/listinfo/clue-tech">http://cluedenver.org/mailman/listinfo/clue-tech</a>
________________________________
_______________________________________________
clue-tech mailing list
<a class="moz-txt-link-abbreviated" href="mailto:clue-tech@cluedenver.org">clue-tech@cluedenver.org</a>
<a class="moz-txt-link-freetext" href="http://cluedenver.org/mailman/listinfo/clue-tech">http://cluedenver.org/mailman/listinfo/clue-tech</a>
_______________________________________________
clue-tech mailing list
<a class="moz-txt-link-abbreviated" href="mailto:clue-tech@cluedenver.org">clue-tech@cluedenver.org</a>
<a class="moz-txt-link-freetext" href="http://cluedenver.org/mailman/listinfo/clue-tech">http://cluedenver.org/mailman/listinfo/clue-tech</a>
</pre>
</blockquote>
<pre wrap=""><!---->_______________________________________________
clue-tech mailing list
<a class="moz-txt-link-abbreviated" href="mailto:clue-tech@cluedenver.org">clue-tech@cluedenver.org</a>
<a class="moz-txt-link-freetext" href="http://cluedenver.org/mailman/listinfo/clue-tech">http://cluedenver.org/mailman/listinfo/clue-tech</a>
</pre>
</blockquote>
<br>
</body>
</html>