Silencing Boot Messages / missing quiet parameter?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I have a file called /etc/modprobe.d/local.conf, which contains:

options speakup synth=soft

I have tried:

options speakup synth=soft quiet=1

and:

options speakup synth=soft
options speakup_soft quiet=1

Am I doing something wrong here with the first version?

The first word I hear on boot is "failed!".  I think it is part of this 
sequence:

"
Setting up ALSA...done.
Starting Speakup/espeak connector : espeakup failed!
Cannot connect to server socket err = No such file or directory
Cannot connect to server socket
jack server is not running or cannot be started
Setting console screen modes.
Skipping font and keymap setup (handled by console-setup).
Setting up console font and keymap...done.
Setting kernel variables ...done.
Setting sensors limits.
startpar: service(s) returned failure: espeakup ... failed!
INIT: Entering runlevel: 2
"

Haven't tried to diagnose the espeak thing yet--speakup is working, so I'm 
not sure what's up with that.

Luke


On Sat, 17 Dec 2011, Gregory Nowak wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> I'm not aware of the quiet parameter being dropped, so I guess it's
> still there. You need to pass it when loading the speakup module. On a
> debian squeeze system, I have a file called speakup.conf in
> /etc/modprobe.d, which reads in part:
> 
> # options for speakup
> 
> options speakup quiet=1
> 
> This is the speakup that comes with squeeze, not the latest one, and it
> works for me as expected.
> 
> Greg
> 
> 
> On Sat, Dec 17, 2011 at 03:49:00PM -0500, luke wrote:
> > Hello
> > 
> > I have been attempting to find a way to keep my laptop from speaking the 
> > boot messages, on a new Debian Squeeze install.
> > 
> > The screen quickly switches to GDM, so speakup goes on speaking boot 
> > messages unless you switch back and silence it, or catch it before the 
> > switch to the gnome console.
> > 
> > I thought I could use the quiet boot parameter as has been done in the 
> > past.  However, adding it to the line in the modprobe.d file for local 
> > configurations, does not seem effective.
> > 
> > In addition, it is not listed as a boot parameter in the version of the 
> > manual which comes with speakup-doc under Debian, which makes me think 
> > that the parameter has been dropped for some reason when I wasn't paying 
> > attention.
> > 
> > Is there some other way to do this now, or was it thought to be useless 
> > functionality?  Or am I just doing it wrong?
> > 
> > Luke
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> - -- 
> web site: http://www.romuald.net.eu.org
> gpg public key: http://www.romuald.net.eu.org/pubkey.asc
> skype: gregn1
> (authorization required, add me to your contacts list first)
> 
> - --
> Free domains: http://www.eu.org/ or mail dns-manager at EU.org
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> 
> iEYEARECAAYFAk7tIl4ACgkQ7s9z/XlyUyCPfwCgrMjcdvaayIrEPHO+y4G2CYxT
> 7pQAn3ILVeHcq0/CZujZt4N5xFL67oSC
> =muJQ
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 



[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]
  Powered by Linux