There is Debian bug 354694 for this, http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=354694
Problem is that pc-speaker event device is not on event0. It may change
depending other event devices.
So easy way to fix problem is to use beep command:
beep -e /dev/input/by-path/platform-pcspkr-event-spkr <other parameters>
I hope beep package maintainer will change default device from /dev/tty0 to
this /dev/input/by-path/platform-pcspkr-event-spkr
I don't know if alsamixer has anything to do with this. I have understood that
alsamixer and pc-speaker is only when internal speaker is connected to
audio-card input.
Problem can be reproduced when /dev/input/by-path/platform-pcspkr-event-spkr is
not pointing to /dev/input/event0 and then run command beep.
Running: strace beep you'll find errors something like this:
open("/dev/tty0", O_WRONLY) = 3
ioctl(3, 0x8000451a, 0x2ace0bbef0f8) = -1 EINVAL (Invalid argument)
** Also affects: beep (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=354694
Importance: Unknown
Status: Unknown
--
The command 'beep' does not produce a sound
https://bugs.launchpad.net/bugs/144022
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
