public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Michael Curran <mick@jantrid.net>
To: speakup@braille.uwo.ca
Subject: Re: Speakup/Festival Config Question
Date: Fri, 11 Apr 2003 09:48:06 +1000	[thread overview]
Message-ID: <20030410234806.GB542@electric> (raw)
In-Reply-To: <20030410234216.GA542@electric>

Sorry, ignore my last email

On Fri, Apr 11, 2003 at 09:42:16AM +1000, Michael Curran wrote:
> I get exactly the same
> 
> On Thu, Apr 10, 2003 at 04:23:45PM +0200, Doug wrote:
> > Owen,
> > 
> > I am having a problem in the final steps of getting
> > your speakup mods working with festival. The patches
> > were applied with no errors and the kernel compiled
> > just fine. I created the usrdev device:
> > 
> > ls -l /dev/usrdev
> > crwxrwxrwx   1 root root 252, 0  /dev/usrdev
> > 
> > The major device number is 252, which is what is
> > hardcoded in speakup_usrdev.h
> > 
> > But then I boot I get these messages:
> > 
> > Speakup usrdev: Registered as char device major #0
> > Speakup usrdev: Minor number is 0
> > Speakup v-1.00 CVS: initialized
> > 
> > and later I get the message
> > speakup: initialized device: /dev/synth, node (MAJOR 10, MINOR 25)
> > 
> > 
> > Note that initially the usrdev is listed as major 0 minor 0.
> > Do you have any idea what might be wrong here?
> > 
> > These are my kernel config options:
> > 
> > CONFIG_SPEAKUP=y
> > CONFIG_SPEAKUP_USRDEV=y
> > CONFIG_SPEAKUP_DEFAULT="usrdev"
> > CONFIG_SPEAKUP_KEYMAP=y
> > 
> > Another issue ... can you please tell me the right commands
> > to start festival as server and start the middleware program?
> > If I run festival I get an interactive session. How do I
> > make it run as server?
> > 
> > If I start festival as usual I get the interactive session
> > and festival works. I can do (SayText "festival works")
> > and it speaks fine. If I open another tty and then start
> > the middleware program I get this message:
> > 
> > Festival server: localhost, on port: 1214 with mode: fundamental
> > festival_client: connect to server failed
> > failed to open Festival: connection refused
> > Speech Error!
> > 
> > Unix sockets and TCP/IP is installed,  and I can ping
> > localhost, in case that matters ...
> > 
> > Any ideas? I am so close ... but so far ...
> > Why would the usrdev be major #0?
> > 
> >   -- Doug
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> -- 
> Michael D. Curran
> www: http://redgum.bendigo.latrobe.edu.au/~mdcurran/
> msn: mick@jantrid.net
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 

-- 
Michael D. Curran
www: http://redgum.bendigo.latrobe.edu.au/~mdcurran/
msn: mick@jantrid.net


      reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Doug
 ` Owen Patrick Smith
   ` Doug
     ` Owen Patrick Smith
       ` Doug
     ` Michael Curran
 ` Michael Curran
   ` Michael Curran [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030410234806.GB542@electric \
    --to=mick@jantrid.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).