public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] No motherboard beep since kernel upgrade
Date: Sun, 23 Mar 2014 04:13:30 +0100	[thread overview]
Message-ID: <532E515A.2040205@googlemail.com> (raw)
In-Reply-To: <20140322234510.GA3511@gmx.de>

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" <rhannek@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.


  parent reply	other threads:[~2014-03-23  3:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-21 17:51 [gentoo-user] No motherboard beep since kernel upgrade null_ptr
2014-03-21 18:54 ` Francesco Turco
2014-03-21 19:39   ` Dat G
2014-03-21 21:41     ` Lee
2014-03-22  1:08       ` null_ptr
2014-03-22  7:20         ` David Haller
2014-03-22 22:40         ` Volker Armin Hemmann
2014-03-22 23:45           ` null_ptr
2014-03-23  0:42             ` David Haller
2014-03-23  3:13             ` Volker Armin Hemmann [this message]
2014-03-23 10:27               ` wraeth
2014-03-23 10:28               ` Matti Nykyri
2014-03-22  1:36 ` Tom Wijsman
2014-03-22 11:29   ` null_ptr
2014-03-23 10:06     ` Tom Wijsman
2014-03-23 17:35       ` null_ptr
2014-03-23 18:26         ` Tom Wijsman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=532E515A.2040205@googlemail.com \
    --to=volkerarmin@googlemail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox