From: Willem van der Walt <wvdwalt@csir.co.za>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: How to unmute multiple controls at once
Date: Fri, 20 Mar 2009 10:14:39 +0200 (SAST) [thread overview]
Message-ID: <Pine.LNX.4.64.0903201013040.2100@localhost.localdomain> (raw)
In-Reply-To: <4af646bf0903190916i5b8c019ck1c4ac4076756f178@mail.gmail.com>
Not quite solving the problem, but:
amixer|fgrep -i simp
should give you the names of all controls and adding another |fgrep -i
speak
might limmit it further.
Regards, Willem
On Thu, 19 Mar 2009, Keith Hinton wrote:
> Hi to all on the Speakup mailing list,
> This is a very general question. How do you unmute all the audio
> controls? One problem that I will have with my laptop is this.
> The sound card has a PC Speaker control that generates a PC speaker
> tone through it. I use this generally for knowing if I'm at the left
> hand margin of the BASH shell. While other people find it annoying, I
> find it useful for this personally. Only previous versions of Udev
> detect it, beginning with Linux kernel 2.6.26. The GRML-kernel, used
> in GRML-2008.11, uses 2.6.26. In that case, my laptop sound card works
> great. However, I still don't know how to successfully unmute all the
> necessary controls. The PCM and master volumes should work, however I
> will require my PC speaker control to work. I don't know what
> Alsa-mixer calls that type Of control, as many laptops do not have an
> onboard PC speaker. Therefore, I'm not sure what I'm going to do. Is
> there a rappid command I could send to alsamixer? I.e. Alsamixer
> Control1; control2; control3; control4; contro.l5; control 6; control
> seven; control 8; control 9; control 10; unmute /dev/audio? Or
> something.
> Well, on second thought, maybe not all the audio controls, but I don't
> want to go changing volume levels, I just want them unmuted. What
> should I do? If I can quickly do this on the LiveCD before really
> using it, I don't care about the glaring defect. The card in my
> laptop, according to Windows, is an Realtek HD Audio card. Would the
> PCM and master volumes be enough to provide audio output? I guess that
> testing is the only way to determan this, but I'd like a more
> practical for sure to work solution. I won't go hunting around the
> Internet to get this working, I really don't have any time to do this.
> Thanks again. Regards, --Keith
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
--
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard.
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.
This message has been scanned for viruses and dangerous content by MailScanner,
and is believed to be clean. MailScanner thanks Transtec Computers for their support.
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Hinton
` Willem van der Walt [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.64.0903201013040.2100@localhost.localdomain \
--to=wvdwalt@csir.co.za \
--cc=speakup@braille.uwo.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).