Duh, uh! Sometimes I feel pretty dumb. On 23 Mar 2001, Kirk Reiser wrote: ... snip ... > If you give the string "none" instead of a synth the kernel will turn > speakup off and not probe for a synth. > I confess I didn't do that. Maybe because I had experienced these later versions of speakup continuing to boot even if my synth was off, I never thought to actually specify "speakup_synth=none." Like I say, sometimes I feel dumb! <grin> I post this in the interest of full disclosure. I would test this, but I simply overwrote the kernel I had before, so can't without compiling again. I would assume, though, that this was my ignorance, and not the fault of the speakup code. So, please forget what I wrote yesterday, and please pardon the noise. If there's anything that would have cleared this up for me, it might be the way the prompt comes up in the .config. I admit that the way it is now, Enter the four to six character synth string from above or none. is grammatical. I have, however, seen much poor grammar in technical documents, so I was simply not certain that this prompt meant that I was actually to type 'none' as opposed to entering nothing at all and pressing enter on an empty field. That's why I posted my question yesterday. I'm glad I did, of course, because I resolved my problem and I learned something I should have known. However, it might have been clearer to me with one additional word in the prompt as follows: Enter the four to six character synth string from above or enter none. Just a small suggestion.
