public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: disabled system speaker: how to enable?
Date: Wed, 31 Dec 2003 13:33:21 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0312311325080.465@debian-box> (raw)

We recently installed Gentoo Linux on a laptop, which went successfully
for the most part.  The Gentoo install seems to run from a ramdisk Linux
version, and it includes things like the links browser so you can go
online during the install to check documentation.  We also installed an
application there that used the console beep (a chat client) to keep in
touch with someone during the install.  The system speaker/console beep on
the machine worked fine at this stage, and would beep as it was supposed
to when someone would send a message.  On the installed system, however,
the console beep/system speaker is not working.  It doesn't work in the
chat client, and issuing | echo -e "\a" | doesn't make the system speaker
beep either (no error responses or anything, just a blank line like it's
trying to ring the system bell, then a return to bash prompt).  This is
the 2.6 kernel, btw.  So, what could the problem be?  Should we have maybe
enabled console beep when we compiled the kernel or something?  Any other
things I could check/implement to get it working?

Thanks, James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

             reply	other threads:[~2003-12-31 19:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 19:33 James Miller [this message]
2004-01-01  3:33 ` disabled system speaker: how to enable? caszonyi
2004-01-01 23:44   ` Debian network reconfigure jamtat
2004-01-01 23:54     ` Ray Olszewski
2004-01-02  0:38       ` James Miller
2004-01-04 20:43       ` starting and stopping networking James Miller
2004-01-04 20:49         ` caszonyi
2004-01-04 21:07           ` James Miller
2004-01-04 21:14             ` Jacob Langley
2004-01-04 21:19             ` caszonyi
2004-01-04 21:28               ` James Miller
2004-01-04 21:41                 ` James Miller
2004-01-04 22:24                   ` Ray Olszewski
2004-01-04 21:32               ` Alan Bort
2004-01-04 23:26                 ` Ray Olszewski
2004-01-04 23:51                   ` Alan Bort
2004-01-05  0:28                     ` Ray Olszewski
2004-01-05  3:11                       ` Alan Bort
2004-01-05  3:55                         ` Juan Facundo Suárez

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=Pine.LNX.4.58.0312311325080.465@debian-box \
    --to=jamtat@mailsnare.net \
    --cc=linux-newbie@vger.kernel.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