Boot Parameters with Debian

[Steve Holmes]

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

I have things working pretty well now.  I was just trying to do one
thing at a time.  I'll probably go and build speakup from latest git
and install the modules.  I now have spkout and soft both loaded as
modules from /etc/modules and in this configuration, speakout comes up
first but I can always switch after I login.  Interesting about 2.6.27
kernel; I thought 2.6.26 was supposed to be just as easy to
integrate.  I realize that the Lenny testing image has an older
version of speakup thus causing some of my grief.  But in any case,
speakup is much more seemless now than it used to be, back a year or
more ago.

On Sat, Oct 18, 2008 at 11:41:42PM -0400, John covici wrote:
> 
> I think you would bet better results with the git sources, this way
> you can either build in the speakout module (you will still need the
> boot parameter), or modprobe the softsynth module in /etc/modules and
> it will work much better.  Also, 2.6.27 kernel will integrate better
> -- at least this is what I understand -- in Ubuntu it seems as though
> speakup can be installed in 2.6.27 and it is seamless.
> 
> Hope this helps.
> 
> on Saturday 10/18/2008 Steve Holmes(steve at holmesgrown.com) wrote
>  > -----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.
>  > 
> 
> -- 
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
> 
>          John Covici
>          covici at ccs.covici.com
> _______________________________________________
> 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)

iEYEAREDAAYFAkj7s4kACgkQWSjv55S0LfGnSQCcCXdvH64min5FbRudKcfdYcSo
ZCQAnR78wOtUu99VCF7EiGV4ke3XG74M
=n4Dw
-----END PGP SIGNATURE-----