From: caszonyi@rdslink.ro
To: James Miller <jamtat@mailsnare.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: 2.6.0 kernel compile overview-the unfolding saga
Date: Tue, 6 Jan 2004 22:56:53 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.53.0401062255170.528@grinch.ro> (raw)
In-Reply-To: <Pine.LNX.4.58.0401060834140.3636@localhost>
On Tue, 6 Jan 2004, James Miller wrote:
> On Tue, 6 Jan 2004, Theo. Sean Schulze wrote:
>
> > Just a shot in the dark here, but do you have the volume turned up? I am using the ALSA sound modules, and they, as default, start up with the sound muted. I haven't gotten around to fixing it yet, so every time I reboot that machine, I have to reset the sound levels to something higher than zero.
> >
>
> And a brilliant shot in the dark it was! I ran across, somewhere on the
> web, the "alsamixer" command and even ran it (that's my kind of app -
> colors and shapes in a console). I saw "PCSpeaker" there, and even turned
> up the volume, but that didn't get me any console beep. Well, I just had
> a look at it again after reading your post. This time, I noted that
> certain of the items listed there had an "off" flag by them - among these
> the PCSpeaker. I toggled that flag and - voila! - system speaker! So, it
> woiks, it woiks! I just would never have guessed that alsa was something
> that governs the PC's speaker - I thought that was a separate "low level"
> (however that parses out in my benighted understanding of these things)
> item. Can anyone help clarify this for me? Anyway, thanks to all for
> input on this - it's now fixed (provided the settings I did stick).
>
It seems that some on-board sound controllers seem to be able to control
the pc speaker. At least at my work we have some windoz machines which
have this "feature"
> Thanks, James
> -
Calin
--
"A mouse is a device used to point at
the xterm you want to type in".
Kim Alm on a.s.r.
-
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
prev parent reply other threads:[~2004-01-06 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-05 19:39 2.6.0 kernel compile overview EXT-Reimer, Jim D
2004-01-05 20:09 ` James Miller
2004-01-05 22:08 ` 2.6.0 kernel compile overview-the unfolding saga James Miller
2004-01-05 22:19 ` caszonyi
2004-01-05 22:49 ` James Miller
2004-01-05 23:12 ` caszonyi
2004-01-06 6:05 ` Theo. Sean Schulze
2004-01-06 14:42 ` James Miller
2004-01-06 20:56 ` caszonyi [this message]
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.53.0401062255170.528@grinch.ro \
--to=caszonyi@rdslink.ro \
--cc=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