Redhat6.1 boot disks with Speakup don't seem to work withDoubleTalkLT

Victor Tsaran vtsaran at nimbus.ocis.temple.edu
Sun May 14 05:00:47 EDT 2000


Actually, I once succedded to have LILO talk on a Redhat system. is that the
trestriction you speak of?
Regards,
Vic

----- Original Message -----
From: <frankiec at unforgettable.com>
To: <speakup at braille.uwo.ca>
Sent: Friday, May 12, 2000 3:58 AM
Subject: Re: Redhat6.1 boot disks with Speakup don't seem to work
withDoubleTalkLT


> Vic
> I think I know what your problem is.  It won't be fixed by the
> speakup_ser variable.  If it would be fixed by the speakup_ser kernel
> parameter you would type "text speakup_ser=0" because you are using com1,
> which is ttyS0.
>
> I am going to guess that you have the problem with these machines that I
> have with lots of machines that I get my hands on.  If you can wait until
> later on this weekend sometime I will try to build some speakup slackware
> bootdisks with the talking lilo prompt.  I have found that on at least one
> system this has solved the detection of serial synths problem.
>
> The issue is that the uarts aren't awake until data gets sent through
> them.  Don't ask me why because I have no freekin idea.  All I can tell
> you is that this baffled me for about four months until I started really
> understanding there behavior.  This took that long for me to really see
> what was going on.  I couldn't narrow it down because of all of the
> variables.  I think that we are going to need to come up with a fix for
> these problems at the speakup level but for now this is a fix.
>
> I can't make redhat do this because it uses syslinux and I don't think
> that you can use the serial port terminal with this boot loader.  Someone
> please correct me if I am in error on this one.
>
> Hope this helps.
>
> FC
>
>
> On Fri, 12 May 2000, Janina Sajka wrote:
>
> > Date: Fri, 12 May 2000 07:27:34 -0400 (EDT)
> > From: Janina Sajka <janina at afb.net>
> > Reply-To: speakup at braille.uwo.ca
> > To: speakup at braille.uwo.ca
> > Subject: Re: Redhat6.1 boot disks with Speakup don't seem to work
> >     withDoubleTalk LT
> >
> >
> > Hi, Voictor:
> >
> > At the boot prompt, when you're booting from the ltlkb floppy image you
> > need to type all of the following on one line before pressing enter:
> >
> > text speakup_ser=1
> >
> > At least, that's what uncorked the genie in my bottle. Your mileage may
> > vary, but it sounds like you didn't give the speakup variable a go.
> >
> > Janina
> >
> > On Thu, 11 May 2000, Victor Tsaran wrote:
> >
> > > Janina, I did what you suggested, but nothing works still. Here is
what I
> > > did:
> > >
> > > downloaded ltlkb.bin
> > >
> > > with rawrite copied it onto an empty floppy.
> > > Connected Doubletalk LT to com1, both machines are desktops, BTW.
> > > Reboot computer, prompt comes up. I type
> > >
> > > text <ENTER>
> > >
> > > The booting process proceeds as if there is no speakup built-in.
> > > Do you have any other suggestions?
> > > Vic
> > >
> > > ----- Original Message -----
> > > From: "Janina Sajka" <janina at afb.net>
> > > To: <speakup at braille.uwo.ca>
> > > Cc: <speakup at speech.braille.uwo.ca>
> > > Sent: Thursday, May 11, 2000 1:13 PM
> > > Subject: Re: Redhat6.1 boot disks with Speakup don't seem to work
> > > withDoubleTalk LT
> > >
> > >
> > > > Vic:
> > > >
> > > > I had the same problem with my IBM Thinkpad 560Z.
> > > >
> > > > The issue turned out to be that the serial port on  the backplane of
the
> > > > Thinkpad was being seen by Linux as ttyS1. Seems the irda port on
the
> > > > front plane is ttyS0. So, the fix was to add the following at the
boot
> > > > prompt:
> > > >
> > > > speakup_ser=1
> > > >
> > > > so my boot prompt response became:
> > > >
> > > > text speakup_ser=1
> > > >
> > > > That did it.
> > > >  On Thu, 11 May 2000, Victor Tsaran
> > > > wrote:
> > > >
> > > > > I downloaded the boot disk for RedHat6.1, ltlkb.bin, and copied it
onto
> > > a
> > > > > floppy. I tried it on two machines and in both cases the machines
> > > booted, but
> > > > > no speech ever came up. Anyone have an idea why this behavior?
> > > > > Vic
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Speakup mailing list
> > > > > Speakup at braille.uwo.ca
> > > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > > >
> > > >
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup at braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup at braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup





More information about the Speakup mailing list