Boot Parameters with Debian

[Steve Holmes]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

Well this might call for a little egg on my face:).  I didn't realize
I needed to load both modules at the same time to be able to switch
between them.  I always thought echoing the synth name would cause the
loading and unloading of respective modules.  I just now did a
'modprobe speakup_spkout start=0' while softsynth was running and then
was able to toggle back and forth with the talkwith script.  I
experimented earlier with modprobing of speakup_soft without any
special paramaters and my machine appeared to lockup entirely so at
that point I was a bit nervous about loading additional speakup
modules.  

In the past (before 2.6.22), I was used to having spkout hard coded
into the kernel and loading softsynth via modules and could always
switch between them.  Now that speakup is completely modular, I wasn't
exactly sure how things worked.

Thanks to both Chuck and Tony for the latest help here.

My one remain point of clarification then is concerning the softsynth
module.  If I wanted to load software speech first and use either
espeakup connector or speechd-up, do I need to always start the module
with start=0 and then get espeakup or speechd-up loaded as soon as
possible there after? When I had tried loading soft without specifying
that, I had experienced lock-ups as mentioned earlier.

On Sat, Oct 18, 2008 at 06:21:10PM -0400, Chuck Hallenbeck wrote:
> Hi Steve,
> 
> On Sat, Oct 18, 2008 at 03:03:28PM -0700, Steve Holmes wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: RIPEMD160
> > 
> > Hey, that is really informative.  I see where that got added to
> > /etc/modules.  I commented that line out which originally loaded
> > speakup_spkout module.  Now when I boot, I could manually load
> > speakup_soft and follow immediately with espeakup to get things
> > going.  But once I do that, I still cannot use talkwith script to switch
> > synths on the fly.  For whatever reason, echoing the new synth name
> > won't stick in the parameter variable, nor will it load the respective
> > module.  The talkwith script echos none to the synth variable and that
> > takes effect and speakup stops bu the only synth that I can echo back
> > in and successfully launch is the same one that I previously
> > unloaded.  It's like the modules aren't unloading or something.
> > 
> 
> You should not want your modules to unload. On my system, I load two
> speakup modules in /etc/modules, speakup_ltlk and speakup_soft, using
> the parameter "start=0". The talkwith script switches between the ltlk
> and the espeakup/espeak systems fine, no unloading or reloading of
> modules. 
> 
> Chuck
> 
> 
> 
> -- 
> The Moon is Waning Gibbous (78% of Full)
> 
> My web site: http://hallenbeck.ftml.net -- my telephone: 1-518-334-9022.
>                                 --------
> Sarah Palin: At last, a Beauty Queen who doesn't want World Peace.
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkj6lSwACgkQWSjv55S0LfFCBgCgnQtKChWF4B1v0S58+UbdzKxA
qFcAoJXs47l/Yv0k9Dwcg3HSYO08eMbN
=YCAE
-----END PGP SIGNATURE-----