> 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