From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Typewriter sound
Date: Thu, 1 Sep 2011 19:58:56 +0100 [thread overview]
Message-ID: <201109011959.08448.michaelkintzios@gmail.com> (raw)
In-Reply-To: <2158365.M8HB8KvBNO@eisen>
[-- Attachment #1: Type: Text/Plain, Size: 1375 bytes --]
On Thursday 01 Sep 2011 15:22:29 Frank Steinmetzger wrote:
> Am Donnerstag, 1. September 2011, 00:57:37 schrieb Grant Edwards:
> > > I didn't reply to the OP. I only replied about xset
> > > (non-)functionality, where it sounds like we're in agreement that it
> > > just sounds the system bell (or whatever you call it).
> >
> > No, it doesn't do that for me, and I don't ever remember being able to
> > get it to do so. I just tried on a couple different systems (all of
> > which have a "pc speaker", and 'xset c' doesn't do anying.
> >
> > Does 'xset c' work for you?
>
> I haven't tested it here, but do you have the speaker enabled in the
> kernel? (CONFIG_INPUT_PCSPKR)
I have set:
$ cat /usr/src/linux/.config | grep PCSPKR
CONFIG_PCSPKR_PLATFORM=y
CONFIG_INPUT_PCSPKR=y
and can confirm that it doesn't click of beep, despite me setting it to do so:
$ xset -q | grep key
auto repeat: on key click percent: 80 LED mask: 00000000
auto repeating keys: 00ffffffdffffbbf
$ xset -q | grep bell
bell percent: 50 bell pitch: 400 bell duration: 100
Another box of mine used to beep (I like having the bell turned on to remind
me that I am typing rubbish ;) but some months ago it stopped doing so. I
never bothered looking into it and assumed that some change in Xorg caused
this.
--
Regards,
Mick
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-09-01 19:00 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-17 17:20 [gentoo-user] Typewriter sound meino.cramer
2010-08-17 17:56 ` Albert Hopkins
2010-08-17 18:13 ` Bill Longman
2010-08-17 18:43 ` meino.cramer
2010-08-17 19:34 ` Albert Hopkins
2010-08-17 21:44 ` Mick
2010-08-17 23:11 ` Bill Longman
2011-08-31 15:18 ` Space Cake
2011-08-31 15:41 ` [gentoo-user] " Grant Edwards
2011-08-31 15:54 ` [gentoo-user] " Volker Armin Hemmann
2011-08-31 16:20 ` Space Cake
2011-08-31 16:27 ` [gentoo-user] " Grant Edwards
2011-08-31 16:49 ` Paul Hartman
2011-08-31 17:46 ` Grant Edwards
2011-08-31 18:50 ` Paul Hartman
2011-08-31 20:18 ` Grant Edwards
2011-08-31 21:58 ` Paul Hartman
2011-09-01 0:57 ` Grant Edwards
2011-09-01 2:43 ` Paul Hartman
2011-09-01 13:53 ` Grant Edwards
2011-09-01 14:22 ` Frank Steinmetzger
2011-09-01 18:58 ` Mick [this message]
2011-09-01 16:36 ` Volker Armin Hemmann
2011-09-01 19:11 ` Grant Edwards
2011-09-04 12:55 ` Alex Schuster
2010-08-17 22:14 ` [gentoo-user] " Paul Hartman
2010-08-17 22:47 ` meino.cramer
2010-08-18 3:42 ` Paul Hartman
2010-08-18 3:53 ` Dale
2010-08-18 13:45 ` [gentoo-user] " Grant Edwards
2010-08-18 15:56 ` [gentoo-user] " meino.cramer
2010-08-17 23:17 ` Albert Hopkins
2010-08-17 23:41 ` Albert Hopkins
2010-08-17 23:44 ` Albert Hopkins
2010-08-18 14:14 ` Stefan G. Weichinger
2010-08-18 15:10 ` Peter Ruskin
2010-08-18 16:46 ` Stefan G. Weichinger
2010-08-18 16:20 ` meino.cramer
2010-08-18 16:43 ` Albert Hopkins
2010-08-18 16:06 ` meino.cramer
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=201109011959.08448.michaelkintzios@gmail.com \
--to=michaelkintzios@gmail.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