On Mar 23, 2014, at 5:13, Volker Armin Hemmann <volkerar...@googlemail.com> wrote:
> Am 23.03.2014 00:45, schrieb null_ptr: >> On 22/03/14 23:40, Volker Armin Hemmann wrote: >>> Am 22.03.2014 02:08, schrieb null_ptr: >>>> On 21/03/14 14:41, Lee wrote: >>>>> I can't think of the name of the module, pcspkr IIRC or some such, >>>>> but it >>>>> prolly isn't loaded. Modprobe can tell you if it's available & load >>>>> it. >>>>> On Mar 21, 2014 12:41 PM, "Dat G" <rhan...@gmx.de> wrote: >>>>> >>>>>> On 21/03/14 19:54, Francesco Turco wrote: >>>>>> >>>>>>> On Fri, Mar 21, 2014, at 18:51, null_ptr wrote: >>>>>>> >>>>>>>> Module for my sound card is running and SND_HDA_INPUT_BEEP is >>>>>>>> activated >>>>>>>> in kernel config. Am I missing something else? >>>>>>>> >>>>>>> >>>>>>> Perhaps you need CONFIG_INPUT_PCSPKR. >>>>>>> >>>>>> I tried building with that and it didn't fix it. >>>> >>>> "modprobe pcspkr" doesn't change anything. It is still silent. I also >>>> tried >>>> building it in the kernel. >>>> >>>> On the other hand from what I understand the snd_hda_intel should be >>>> doing the beeps when the mainboard does not have a physical speaker on >>>> the mainboard and instead beeps through the regular sound device. At >>>> least on 3.10.25 I had not build the pcspkr module and the system >>>> beeped >>>> happily. >>>> >>>> >>> >>> Now, are we talking about the motherboard beeping through a little >>> builtin speaker that does not work >>> or >>> Are we talking about your onboard sound not beeping in your >>> headphones/your attached speakers when there is a motherboard 'beep'? >>> >>> Either way, I don't see any problem at all. A non-beeping computer is a >>> correctly working one. >> >> I'm talking about the onboard sound not beeping in the attached >> headphones/speakers when there is a motherboard 'beep'. The problem is >> that I used that for some events as a status (e.g. battery running low) >> and I like the annoying nature of the beep for these events. >> >> > > so it is not a 'speaker' problem but a sound card problem. You should > have stated that from the beginning. > > Probably something muted that should not be muted. > Check that you can play sounds from different sources to see that there is no process blocking your alsa driver. If there is a program that is blocking alsa you can find out which process it is by: fuser -v /dev/snd/*
