From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mta11.charter.net (mta11.charter.net [216.33.127.80]) by speech.braille.uwo.ca (Postfix) with ESMTP id 4B6D910A0E for ; Sun, 19 Apr 2009 18:25:54 -0400 (EDT) Received: from imp11 ([10.20.200.11]) by mta11.charter.net (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090419222553.NSUG22327.mta11.charter.net@imp11> for ; Sun, 19 Apr 2009 18:25:53 -0400 Received: from maranatha.local ([66.191.124.47]) by imp11 with charter.net id haRt1b00611USpe05aRtia; Sun, 19 Apr 2009 18:25:53 -0400 Date: Sun, 19 Apr 2009 17:25:52 -0500 (CDT) From: Cheryl Homiak To: speakup List Subject: ltlk issue again Message-ID: User-Agent: Alpine 2.00 (DEB 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.12 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Apr 2009 22:25:54 -0000 Hi all. I used git to get speakup and installed it in the kernel source for the 2.6.29 downloaded from debian. I compiled using make-kpkg and installed the .deb package. I do have an initrd in case that makes a difference. The ltlk (for my doubletalk lt) parameter was added to my kernel line in the menu.lst. It boots fine but unfortunately i still get the error about too many timeouts and even if I manage to turn speakup off while booting speakup is deactivated; i have no speech and can't turn it back on again once I am booted. My full_time setting does show 40000. Is there any more I can do about this? I suppose I can just go back to using speakup with espeakup as a module but then I don't hear boot information from the beginning and besides, laugh if you like, but i have a fondness for the old doubletalk lt. I know it always did have some problems with stopping during boot at some point but I always used to be able to start it up again. Any suggestions would be appreciated both for solving this problem and any way of reactivating it. I compiled into the kernel rather than using modules. Tia. -- Cheryl "Where your treasure is, there will your heart be also."