Bug#584203: acpi-fakekey: fails to start at boot
On Fri, Jul 2, 2010 at 12:14, Michael Meskes mes...@debian.org wrote: Sure, if we sleep for 5 seconds. Anyway, thanks I think I will try with one second in the new package. Please tell me if it does not work. Yes one second was enough as it starts fine now. Thank You, Michel
Bug#584203: acpi-fakekey: fails to start at boot
On Thu, Jul 01, 2010 at 10:24:35AM -0400, Michel wrote: Yes it starts fine now at boot, no errors messages. Just thought I mention that it does lengthen the boot time a bit. Sure, if we sleep for 5 seconds. Anyway, thanks I think I will try with one second in the new package. Please tell me if it does not work. If you have any clues as to why that is happening, I'm open to suggestions to try to figure it out. I have not, sorry, it might be the kernel or your bios, but with no events generated there is nothing the acpi* packages can work with. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
On Wed, Jun 30, 2010 at 05:25:19PM -0400, Michel wrote: Ok, that fixed it :) So it does start now? None that was the output from kacpimon. Yes, but to be meaningful the output of kacpimon when pressing volume -/+ or mute keys is needed. Could you please also try one of the volume keys or the mute key with acpi_listen running? The volume -/+ or mute key, did not give any output. So no events seem to be generated. This hardly looks like a problem in any of the acpi* packages. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
On Thu, Jul 1, 2010 at 02:32, Michael Meskes mes...@debian.org wrote: So it does start now? Yes it starts fine now at boot, no errors messages. Just thought I mention that it does lengthen the boot time a bit. Yes, but to be meaningful the output of kacpimon when pressing volume -/+ or mute keys is needed. Sorry, I thought I had mentioned that I get no output from kacpimon either, when pressing the volume -/+ or mute key. Just what I showed you from before. So no events seem to be generated. This hardly looks like a problem in any of the acpi* packages. Ok, all I know it was working fine before. I'm not sure when this started happening, I just noticed the volumes keys stopped controlling alsamixer around the same time as acpi-fakekey was failing at boot. And thought there might be some correlation. If you have any clues as to why that is happening, I'm open to suggestions to try to figure it out. Thanks, Mike
Bug#584203: acpi-fakekey: fails to start at boot
On Tue, Jun 29, 2010 at 02:40:29PM -0400, Michel wrote: Sorry should have being clearer, like this: 'if ! modprobe -q uinput; then sleep 5' I changed it to: 'if ! modprobe -q uinput; sleep 5; then' What I meant was: if ! modprobe -q uinput; then ... fi sleep 5 With the above it does start at boot now: ... Doesn't mean a lot since you changed the if command. Please put the sleep below the fi. Input Layer: Type: 4 Code: 4 Value: 28 Input Layer: Type: 1 Code: 28 Value: 0 Input Layer: Sync Which key did you press here? Could you please also try one of the volume keys or the mute key with acpi_listen running? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
On Wed, Jun 30, 2010 at 05:48, Michael Meskes mes...@debian.org wrote: What I meant was: if ! modprobe -q uinput; then ... fi sleep 5 Ok, that fixed it :) To be clear this is what I did: . fi sleep 5 .. Input Layer: Type: 4 Code: 4 Value: 28 Input Layer: Type: 1 Code: 28 Value: 0 Input Layer: Sync Which key did you press here? None that was the output from kacpimon. Could you please also try one of the volume keys or the mute key with acpi_listen running? The volume -/+ or mute key, did not give any output. Thanks, Michel
Bug#584203: acpi-fakekey: fails to start at boot
On Mon, Jun 28, 2010 at 04:11:35PM -0400, Michel wrote: I did what you suggested and added 'sleep 5' right after: 'if ! modprobe -q uinput; then' to /etc/init.d/acpi-fakekey. It still fails at boot, but can start manually, like I stated before. Just to clarify this, you added the line after the fi and not inside the then branch right? It wouldn't get run inside the then. issue. All I know is that it was working fine with alsamixer before With which version of acpi-support? Does it work again if you install an older version ? http://snapshot.debian.org/binary/acpi-support/ This is on a Thinkpad T23. xev does not report anything with vol -/+ Ah, just saw you mentioned this before, sorry, missed it. Some Thinkpad stuff got removed by upstream but was re-added to the Debian package later on because the kernel key handling failed on some systems. Not sure what's going on on yours. Could you please run kacpimon and report which events get generated? Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
After installing 0.136-4, it still fails at boot with the same message. But I now see this message above, which did not show before: 'Starting acpi_fakekey daemon...open device: No such file or directory' The initscript makes sure the module is included before starting acpi_fakekeyd, so the device should be there. Strange. Can now manually start with: /usr/sbin/acpi_fakekeyd, acpi_fakekeyd and invoke acpi_fakekeyd start. Eh? Does that mean it only doesn't start in the boot process but works correctly if run later on? Could you go into /etc/init.d/acpi-fakekey and add a sleep 5 after the modprobe and before the start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/acpi_fakekeyd and retry? But still does not control alsamixer like it did before. This seems to be a different problem. Which hardware do you have? What keycodes are produced? Please note that acpi-support only translates key events and you might still need some other software like a mixer to react on these. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
Eh? Does that mean it only doesn't start in the boot process but works correctly if run later on? Could you go into /etc/init.d/acpi-fakekey and add a sleep 5 after the modprobe and before the start-stop-daemon --start --quiet --oknodo --exec /usr/sbin/acpi_fakekeyd and retry? That is what I'm seeing here. I did what you suggested and added 'sleep 5' right after: 'if ! modprobe -q uinput; then' to /etc/init.d/acpi-fakekey. It still fails at boot, but can start manually, like I stated before. This seems to be a different problem. Which hardware do you have? What keycodes are produced? Please note that acpi-support only translates key events and you might still need some other software like a mixer to react on these. It maybe a different issue, but I did notice this at the same time as the acpi-fakekey issue. All I know is that it was working fine with alsamixer before and I had not done anything for the keys to work with alsamixer. This is on a Thinkpad T23. xev does not report anything with vol -/+ or mute keys. I forgot to mention this before, I had tried xev to find out what was the cause. But thought nothing of it as it was working fine before. Thanks, Michel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
On Thu, Jun 24, 2010 at 08:26, Michael Meskes mes...@debian.org wrote: On Wed, Jun 02, 2010 at 04:57:20AM -0400, Michel wrote: At boot time I get the following message: 'failed (Could not start /usr/sbin/acpi_fakekeyd).' The keys for volume up/down and mute work, but does not control the volume up/down and mute on alsamixer like before. Seems similar to #577603, but I have no messages like that in /var/log/Xorg.0.log, from #577603: 'ACPI Virtual Keyboard Device: Dropping event due to full que' Even after manually stopping and starting with 'invoke-rc.d acpi-fakekey' the same thing still happens. This is on a Thinkpad T23. Do you still see the problem with 0.136-4 in unstable? If so could you please start /usr/sbin/acpi_fakekeyd manually under strace to see what happens? It might also be helpful to compile acpi-fakekey with debugging enabled and run it under gdb. I haven't seen this problem before. Michael After installing 0.136-4, it still fails at boot with the same message. But I now see this message above, which did not show before: 'Starting acpi_fakekey daemon...open device: No such file or directory' Can now manually start with: /usr/sbin/acpi_fakekeyd, acpi_fakekeyd and invoke acpi_fakekeyd start. 'Starting acpi_fakekey daemon...[time] input: ACPI Virtual Keyboard Device as /devices/virtual/input/input8 done.' But still does not control alsamixer like it did before. Thanks, Michel -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: [Pkg-acpi-devel] Bug#584203: acpi-fakekey: fails to start at boot
On Thu, Jun 24, 2010 at 11:48:41PM +0200, Petter Reinholdtsen wrote: Could this be a boot ordering problem? Should acpi-fakekey start before acpi-support? This is the ordering of the acpi scripts in a recent Squeeze installation: ... No, they should be independant. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
On Wed, Jun 02, 2010 at 04:57:20AM -0400, Michel wrote: At boot time I get the following message: 'failed (Could not start /usr/sbin/acpi_fakekeyd).' The keys for volume up/down and mute work, but does not control the volume up/down and mute on alsamixer like before. Seems similar to #577603, but I have no messages like that in /var/log/Xorg.0.log, from #577603: 'ACPI Virtual Keyboard Device: Dropping event due to full que' Even after manually stopping and starting with 'invoke-rc.d acpi-fakekey' the same thing still happens. This is on a Thinkpad T23. Do you still see the problem with 0.136-4 in unstable? If so could you please start /usr/sbin/acpi_fakekeyd manually under strace to see what happens? It might also be helpful to compile acpi-fakekey with debugging enabled and run it under gdb. I haven't seen this problem before. Michael -- Michael Meskes Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org) Michael at BorussiaFan dot De, Meskes at (Debian|Postgresql) dot Org ICQ 179140304, AIM/Yahoo/Skype michaelmeskes, Jabber mes...@jabber.org VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
[Michael Meskes] Do you still see the problem with 0.136-4 in unstable? If so could you please start /usr/sbin/acpi_fakekeyd manually under strace to see what happens? It might also be helpful to compile acpi-fakekey with debugging enabled and run it under gdb. I haven't seen this problem before. I've seen it too, but was not sure if it was hardware dependent or not. Could this be a boot ordering problem? Should acpi-fakekey start before acpi-support? This is the ordering of the acpi scripts in a recent Squeeze installation: r...@localhost:/# ls /etc/rc2.d/*acpi* /etc/rc2.d/S20acpi-fakekey /etc/rc2.d/S22acpid /etc/rc2.d/S22acpi-support r...@localhost:/# If they need some specific ordering, the script dependencies are incomplete. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#584203: acpi-fakekey: fails to start at boot
Package: acpi-fakekey Version: 0.136-3 Severity: important At boot time I get the following message: 'failed (Could not start /usr/sbin/acpi_fakekeyd).' The keys for volume up/down and mute work, but does not control the volume up/down and mute on alsamixer like before. Seems similar to #577603, but I have no messages like that in /var/log/Xorg.0.log, from #577603: 'ACPI Virtual Keyboard Device: Dropping event due to full que' Even after manually stopping and starting with 'invoke-rc.d acpi-fakekey' the same thing still happens. This is on a Thinkpad T23. Thanks, Michel -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages acpi-fakekey depends on: ii libc6 2.10.2-9 Embedded GNU C Library: Shared lib acpi-fakekey recommends no packages. acpi-fakekey suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
