ltlk issue again

ltlk issue again

[Cheryl Homiak]

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."

Re: ltlk issue again

[William Hubbs]

Hi Cheryl,

I downloaded kernel version 2.6.29 from kernel.org and installed speakup
into it.  Speakup is built in without modules, and I use the ltlk also.
grub is set up with speakup.synth=ltlk on the boot line.

I rebooted the computer and let speakup talk all the way through the
reboot until the login prompt came up, and it did not shut down.  Then,
I rebooted again, and hit numpad enter as soon as speakup started
talking.  Still, the login prompt came up with no issues.

Can you please give a very detailed, step by step explanation of what
you are doing to make this happen?  Also, you say that speakup stops and
you are unable to turn it on again.  Have you tried pressing print
screen?  When it stops, do you know if the computer is locked up or if
speakup is just not talking?

Thanks,

William

Re: ltlk issue again

[Cheryl Homiak]

The step-by-step is as you described it in your email; i've tried it both 
ways. Yes, I've tried printscreen. No, the computer doesn't lock up, just 
speakup stops (I see something about too many timeout from ltlk, 
deactivating). I wondered if maybe I need to set the baudrate to 9600 
somewhere. Other than that I can't think what could be causing the 
problem.

Thanks.


-- 
Cheryl

"Where your treasure is, there will your heart be also."

Re: Re: ltlk issue again

[Michael Whapples]

This sounds very much like my problems with the apollo. I haven't tried 
just letting speakup speak all the boot messages, I normaly use numpad 
enter to shut it up. I find that if I keep speakup active by using the 
screen review keys it seems to be reasonably OK (not sure if it is 100% 
of the time but certainly it seems to improve the situation). I have 
occasionally found speakup stops working with my apollo at other times 
than booting, but booting seems to be a fairly sure way of creating the 
situation which leads to the "too many timeouts" message.

Other than the synth being used, the other difference is I am using GRML 
(kernel 2.6.28) with debian unstable providing the extra packages on my 
system.

Michael Whapples
On 23/12/42 19:59, Cheryl Homiak wrote:
> <div class="moz-text-flowed" style="font-family: -moz-fixed">The 
> step-by-step is as you described it in your email; i've tried it both 
> ways. Yes, I've tried printscreen. No, the computer doesn't lock up, 
> just speakup stops (I see something about too many timeout from ltlk, 
> deactivating). I wondered if maybe I need to set the baudrate to 9600 
> somewhere. Other than that I can't think what could be causing the 
> problem.
>
> Thanks.
>
>
>

Re: Re: ltlk issue again

[Cheryl Homiak]

Hmm, wonder if there's some common ground there. i'm running debian 
unstable. It wouldn't be so terrible except that there doesn't seem to be 
any way that I can start it (speakup) up again once it deactivates. I 
actually 
probably get to hear most of the boot messages because even though there 
are the "too many timeouts" errors it actually keeps talking for quite a 
while. also, would it make any difference that Im also using a braillelite 
40 on ttyUSB0? That shouldn't make a difference but I'm just looking for 
some cause.



-- 
Cheryl

"Where your treasure is, there will your heart be also."

Re: Re: Re: ltlk issue again

[Michael Whapples]

I have speakup as modules and I find if I remove the speakup_apollo 
module using rmmod and then load it back in again with modprobe speakup 
starts working again. Does speakup start working again if you switch to 
another synth (may be soft or none) and then switch back to the 
doubletalk? It isn't a solution to the problem but at least it may mean 
you might be able to recover speakup when it is deactivated.

Michael Whapples
On 23/12/42 19:59, Cheryl Homiak wrote:
> <div class="moz-text-flowed" style="font-family: -moz-fixed">Hmm, 
> wonder if there's some common ground there. i'm running debian 
> unstable. It wouldn't be so terrible except that there doesn't seem to 
> be any way that I can start it (speakup) up again once it deactivates. 
> I actually probably get to hear most of the boot messages because even 
> though there are the "too many timeouts" errors it actually keeps 
> talking for quite a while. also, would it make any difference that Im 
> also using a braillelite 40 on ttyUSB0? That shouldn't make a 
> difference but I'm just looking for some cause.
>
>
>
>

Re: Re: Re: ltlk issue again

[Cheryl Homiak]

I'm not using modules but have speakup built into the kernel. I do have 
speakup with debian modules in a 2.6.26 kernel and that loads fine in 
/etc/modules using espeakup but then of course speakup doesn't start up as 
early. I wonder:  would it make any difference if i tried to build a 
kernel without an initrd?



-- 
Cheryl

"Where your treasure is, there will your heart be also."

Re: Re: Re: ltlk issue again

[Gregory Nowak]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Apr 24, 2009 at 12:27:00PM -0500, Cheryl Homiak wrote:
> I'm not using modules but have speakup built into the kernel.

You should still be able to switch synths via echoing the synth name
to /sys/module/speakup/parameters/synth.

Greg


- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknyDMMACgkQ7s9z/XlyUyBabwCgwwqYLkgoxeSMDEpZjx6m9hUg
Y7kAnA7Are9b2dgZkHHXbgr09kTf1YNr
=hU5V
-----END PGP SIGNATURE-----

Re: Re: Re: ltlk issue again

[Cheryl Homiak]

Ok, thanks Greg; will try that.



-- 
Cheryl

"Where your treasure is, there will your heart be also."

Re: Re: Re: ltlk issue again

[Cheryl Homiak]

I know this is going to sound really strange, but after speakup dies and I 
log in there doesn't appear to be a /proc/speakup.


--
Cheryl

"Where your treasure is, there will your heart be also."

Re: Re: Re: ltlk issue again

[William Hubbs]

Hi Cheryl,

On Sat, Apr 25, 2009 at 09:28:56AM -0500, Cheryl Homiak wrote:
> I know this is going to sound really strange, but after speakup dies and I 
> log in there doesn't appear to be a /proc/speakup.

/proc/speakup hasn't existed since we migrated over to /sys a while
back, so do you mean /sys/module/speakup/parameters?

Thanks,

William

Re: Re: Re: ltlk issue again

[Cheryl Homiak]

Ooops, sorry about that.
I forgot to save the email with the path yesterday and couldn't bring up 
the archives site last night so googled and got the 2.0 Users guide. 
Didn't use speakup for a while at all so keep forgetting some of the 
changes.

I can restart speakup with doubletalk lt by switching synths or even just 
echoing none and then when it releases ltlk echoing ltlk again.

I may have found the problem but not the source of the problem. In 
/sys/module I have both a speakup_ltlk and a speakup. speakup_ltlk has 
ser and start under it; speakup has parameters. Should the speakup_ltlk 
not be there or is this normal? I did try at one point to run ltlk with 
the debian modules and had it in /etc/modules but I removed it.






-- 
Cheryl

"Where your treasure is, there will your heart be also."

Re: Re: Re: ltlk issue again

[William Hubbs]

Hi Cheryl,

On Sat, Apr 25, 2009 at 01:28:27PM -0500, Cheryl Homiak wrote:
> I may have found the problem but not the source of the problem. In 
> /sys/module I have both a speakup_ltlk and a speakup. speakup_ltlk has ser 
> and start under it; speakup has parameters. Should the speakup_ltlk not be 
> there or is this normal? I did try at one point to run ltlk with the debian 
> modules and had it in /etc/modules but I removed it.

There will be a directory in /sys/module for each module in the kernel,
so having the directories for speakup and speakup_ltlk in there is
normal.

William