public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: keyboard interupt
Date: Sat, 19 Aug 2006 20:16:51 -0700	[thread overview]
Message-ID: <20060820031651.GA16117@localhost.localdomain> (raw)
In-Reply-To: <20060820030025.GA23639@lava-net.com>

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

This isn't a direct answer to your question, however, putting

speakup_quiet=1

in the boot loader to pass to the kernel, should shut speakup up,
until you use review commands, type something, ETC. Hth.

Greg


On Sat, Aug 19, 2006 at 11:00:25PM -0400, Igor Gueths wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
> 
> Hi all. I recently needed to modify a RIP (Recovery Is Possible) disk and put Speakup into a 2.6.17.1 kernel I compiled for it. However, I am noticing that I am only able to interupt speech 
> very late in the boot process. As a result, this adds about 5 minutes to what I would say should be about a 30-45 second boot, since my Dectalk is stuck reading most of the kernel messages. 
> Does anyone know how I can make sure I get keyboard support loaded earlier on instead of wherever it gets loaded now? 
> Or am I pretty much stuck with the way things are now? Thanks in advance.
> - -- 
> For an IRC experience without all the clutter, check out BOFHNet at irc.bofhnet.us.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.2.2 (GNU/Linux)
> 
> iQIVAwUBROfQSae2pgKIdGq4AQqN0g//ZkR/Ena7ciFjsREI0rvxDj48JFrl23KZ
> gdyhoRa8Vyky7pOeQkICpcXIrlDWRu6hFizvs8/iHVKS5ni32Y28gJym2iFyYY5n
> +06Ad7aJNDFl40TZDLcgy834oq//nFEWo0HvdTBZMY2Oc/pOmoCDFPrtV6ue9sB+
> H1ldRmfNgfR3bSLGeTbrYRYyN+ADyPjYil6mWHH6PmDdqrUmKmDJSP7L3y5fIjwm
> eMb2iXd5w+v+QKMWdPspJKfq41WwmHwQbKMrUhUZaWE7p/8uyie29d441P0rQbxH
> 89MT8c4L3AbSh+Db2B14QhIGnqH52z15kMasUISoPz3Z7fBvbv8K+mvTUMhIhCF7
> yLgB5LhVWsHzQCsw/HZUxeRtpbbzhzQ8Pa+7sEf7mGIqfObVQREYhPr8x4nZRfya
> cwAAryDn3irOs3qaBi/7exLdd3d54zFN3WD4l4ZlUy04xlEqU/pzObPtFEA/B8D2
> eb2E//pdGKTREx/vcnx7UlYCyPt4wYb4b5Jd5803wF1fcPh55IBpesFm7ug613iL
> 117/dy2QiPPabbLPdG4BP2X3YMoDEvOG0ZN1kLciERe1+M/y0Ea4nGLqydI5fMYe
> s6S4667kN7uXEG94rZN/s0v/9N9QQYZqPPgJaxOBucdGzAnapt0yNNqIgpCLqagU
> P8sagUtEWP4=
> =nuyC
> -----END PGP SIGNATURE-----
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
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.3 (GNU/Linux)

iD8DBQFE59Qj7s9z/XlyUyARAitsAKDQvmACPawJ1bEfjTfz0k69CEgQAQCeO+hm
6yh1axs7vQD7WNe4JpgKsUc=
=cwCs
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Igor Gueths
 ` Gregory Nowak [this message]
   ` Igor Gueths
 ` John covici
   ` Igor Gueths

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=20060820031651.GA16117@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --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).