From: David Haller <gentoo@dhaller.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] No motherboard beep since kernel upgrade
Date: Sun, 23 Mar 2014 01:42:07 +0100 [thread overview]
Message-ID: <20140323004207.GA24511@grusum.endjinn.de> (raw)
In-Reply-To: <20140322234510.GA3511@gmx.de>
Hello,
On Sun, 23 Mar 2014, null_ptr wrote:
>On 22/03/14 23:40, Volker Armin Hemmann wrote:
>>Am 22.03.2014 02:08, schrieb null_ptr:
>>>"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'?
[..]
>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.
Wait. What now? You have (at least) two sound-devices that can beep:
a) the beeper on your motherboard
in this case, use what I wrote, i.e.
pcsp=enable=1
in your kernel commandline and make sure
modprobe pcspkr
works. The module is not needed in the initrd.
b) the onboard-sound-chip via attached speakers/headphones
in this case, disable the mobo-beeper (might be default)
blacklist pcspkr
explicitly, possibly along with with the kernel-parameter
pcsp=enable=0
and your normal alsa-driver should take over the task of "beeping"
(snd-pcsp is a different beast).
If it does not, your alsa-driver might be buggy as it should take
over the beeping.
HTH,
-dnh, I wanted case a), beeping completely independent from any other
audio stuff. And with the program 'beep'
(http://www.johnath.com/beep) and/or the snd-pcsp driver, you can
use the beeper to do more than the standard beep.
--
There is a green, multi-legged creature crawling on your shoulder.
next prev parent reply other threads:[~2014-03-23 3:17 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 [this message]
2014-03-23 3:13 ` Volker Armin Hemmann
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=20140323004207.GA24511@grusum.endjinn.de \
--to=gentoo@dhaller.de \
--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