From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lowblow.svc.tds.net ([204.246.1.39]) by speech.braille.uwo.ca with esmtp (Exim 3.32 #1 (Debian)) id 16WV47-0004k3-00 for ; Thu, 31 Jan 2002 23:12:43 -0500 Received: from snoopy ([216.170.197.79]) by lowblow.svc.tds.net with SMTP id <20020201041252.ESXT27436.lowblow@snoopy> for ; Thu, 31 Jan 2002 22:12:52 -0600 Message-Id: <3.0.5.32.20020131231254.007cb350@somtel.com> X-Sender: talmage@somtel.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 31 Jan 2002 23:12:54 -0500 To: speakup@braille.uwo.ca From: TALMAGE@SOMTEL.COM Subject: Re: Redhat 7.2 and Speakup In-Reply-To: References: <3.0.5.32.20020130230207.007c73d0@somtel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.7 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: Thanks to all who replied to my question. For those interested in the lessons of the school of hard knocks, and the problems we can cause ourselves the solution was: Don't boot your system from a serial terminal and expect speech to work on the actual linux box. I was using Grub's serial terminal feature to load and boot my kernel to test it and that was a bad thing. I think I'll find when I go back and do it again, for curiosity sake, I'll find that it wasn't Speakup that was dead but instead my keyboard. Thanks especially to Bill who answered the question I didn't even know I had at the time. When I finally loaded the kernel from my linux box's keyboard it was the standard key map that was coming up, and his suggestion fixed that problem. As to why my LiteTalk wasn't working, I think it may be to old and peculiar. It has a ROM revision of 2.02 and that is the newest it is capable of taking. It has an AMD processor and was one of the last ones MicroTalk put out before changing to an Intel processor. No biggie though, I just swapped with the Doubletalk LT I have on my kid's Windows box, and all works fine now. Dave Talmage