Simple modprobe pcspkr worked great for me in 12.04. Add to
/etc/modules and good to go. No -e required - much thanks for the tip.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/144022
Title:
The
This now works for me using the solution from post #18.
Thanks Alexander (& Mannex
(https://answers.launchpad.net/ubuntu/+source/beep/+question/130004) for
pointing out that this solution now works)!
I tried this in 10.10 without success, but retrying now in 11.04 fixes the
problem.
Currently
Same problem (no beep) here using kubuntu 10.10 (Linux golem
2.6.35-28-generic #50-Ubuntu SMP Fri Mar 18 18:42:20 UTC 2011 x86_64
GNU/Linux).
Everything worked fine in 10.04. I fixed the blacklist issue noted by That Bum
(https://answers.launchpad.net/ubuntu/+source/beep/+question/130004) and
re
For me the problem was in ALSA, snd-hda-intel module.
$ modinfo snd-hda-intel | grep beep
parm: beep_mode:Select HDA Beep registration mode (0=off, 1=on,
2=mute switch on/off) (default=1). (array of int)
So, "modinfo" says that "beep" sound can be manipulated through "beep_mode"
modul
Faced same problem with 10.10 and bobemoe solution also works 11.04
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/144022
Title:
The command 'beep' does not produce a sound
--
ubuntu-bugs mailing l
I thought I was experiencing this problem, but all I had to do was
modprobe pcspkr and then beep works without specifying device or any
other arguments.
Ubuntu 10.04 64bit
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
Stil present in Ubuntu 10.10.
--
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.u
I can confirm Magnentius's comment (#13). Recently, I have written some
scripts which need Ubuntu's beeping feature. Neither Ubuntu's beep
package nor Perl's Audio::Beep works. The workaround from Henri's
comment (#5) did not work. I'm using Ubuntu 10.04
--
The command 'beep' does not produce
I wish to state that this problem persists in Ubuntu 10.04. "beep -e
/dev/input/by-path/platform-pcspkr-event-spkr" doesn't work, even when I
added "rmmod pcspkr || true / modprobe pcspkr || true" to /etc/rc.local
and rebooted. (See
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/398161). It's
Hi Gerfried,
Regarding something you had said earlier:
> Maybe switching from probing /dev/input/event0 to /dev/input/by-path
/platform-pcspkr-event-spkr might be someting to think about, though
that would limit its usage to udev using systems, which I would like to
avoid.and would propably turn
I don't understand what you mean with respect to "This isn't Debian.
This is Ubuntu." That response somehow doesn't make much sense to me.
About the configuration into a working state - please read the linked
bugreport in Debian about that the other approach also was giving quite
some people tro
This isn't Debian. This is Ubuntu. If the configuration isn't expected
to configure it into a working state for Ubuntu, then the documentation
should tell the user how to solve that. And I do hope this will be
configurable once, instead of figuring out what device to use every time
we want a beep.
I'm marking this bug "Invalid" at the request of the Debian Maintainer.
This behaviour is the expected behaviour of beep when in an envronment
which requires access to event0, and -e should be used in that case.
** Changed in: beep (Ubuntu)
Status: Confirmed => Invalid
--
The command 'bee
Detlef, I've written the description of the package myself, so no need
to tell me reading it :)
The description doesn't claim that it will work without using of any
commandline option on all systems - that was the main purpose for
introducing the -e switch. It's not a "workaround" like Henri likes
The problem persists in Ubuntu 8.04.
"[EMAIL PROTECTED]:~$ uname -a; Linux MD97600 2.6.24-19-generic #1 SMP Wed Jun
4 16:35:01 UTC 2008 i686 GNU/Linux."
'apropos platform-pcspkr-event-spkr' does not produce any output.
@Gerfried: Please read the description which Synaptic provides. This
descri
Is this bugreport assigned to the wrong package? It speaks about
softbeep which is a completely different thing?
Anyway, if it is about beep it should be closed with the usage of the
-e switch. The program is not meant to be that unversal and guessing
everything on its own, that would just bloat
** Changed in: beep (Debian)
Status: Unknown => Fix Released
--
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
Problem still exists if pc-spkr is not on /dev/input/event0.
Workaround is to run command: beep -e
/dev/input/by-path/platform-pcspkr-event-spkr
** Changed in: beep (Ubuntu)
Status: Invalid => Confirmed
--
The command 'beep' does not produce a sound
https://bugs.launchpad.net/bugs/14402
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-even
The problem persists in Ubuntu 7.10.
--
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 the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
ht
alsamixer does not show an entry 'PC speaker'.
--
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 the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
This is more than likely a hardware configuration issue. You should
check your mixer settings to ensure that the volume for PC speaker is
not muted, and is turned up, if possible.
** Changed in: beep (Ubuntu)
Status: New => Invalid
--
The command 'beep' does not produce a sound
https://bu
22 matches
Mail list logo
