public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Mitchell D. Lynn" <mlynn@kc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@linux-speakup.org>
Subject: RE: Slack 13.37 and 14.0
Date: Wed, 15 May 2013 09:15:12 -0500	[thread overview]
Message-ID: <72708A629D1C40508DEB3147F83238DA@mdlynn> (raw)
In-Reply-To: <51933C1C.9070201@baechler.net>

Thanks for the info on the 3.2 kernels. That, then, is the issue. 

RE Debian: Looks like there has been a new release since I last looked.
Grabbed the Wheezy release and installed on a test system last night.
Software synth works fine on that machine. No serial port on this system to
test with DEC. I will see how it does on the main server later this week
when I can have it down for an extended period. I can live with a software
synth as long as I can get boot messages, and serial ports are getting
harder to find on modern mainboards.   


-----Original Message-----
From: Speakup [mailto:speakup-bounces@linux-speakup.org] On Behalf Of Tony
Baechler
Sent: Wednesday, May 15, 2013 2:41 AM
To: Speakup is a screen review system for Linux.
Subject: Re: Slack 13.37 and 14.0

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

The 3.2 kernel with Speakup has the broken serial support, so no hardware
speech for you with kernels after 2.6.37 which is why I suggested installing
Debian Squeeze.  What Speakup parameter are you passing to the installer?  I
agree that I don't think it's a keyboard issue, but that's very weird.  I'm
wondering if you're passing the wrong synthesizer parameter.  If you try
64-bit Wheezy with software speech, do you have the same problem?  That's
very strange.  You might want to join the debian-accessibility list,
especially if you found a bug in D-I.  I'm trying to isolate whether it's a
Speakup or a Debian issue.

I could be wrong here, but I don't think 32-bit kernels can support drives
larger than 2 TB.  I'm sure I'll be corrected if that's wrong, but I did
quite a bit of research before upgrading my server to 3 TB drives.  The
problem seems to have to do with very large partitions.  You really need GPT
for drives larger than 2 TB because the standard X86 architecture can't
access sectors past the 2 TB boundary.  It's not an OS issue, but a BIOS
design issue.  I think you'll have problems with any 32-bit OS you try.  If
your processor isn't 64-bit, you're either out of luck or you'll need a new
processor.

On 5/14/2013 7:03 AM, Mitchell D. Lynn wrote:
> Thanks for the response.
> 
> My rate change blues are post-install for Debian and while the Speakup 
> keys announce incremental rate changes, they don't actually change the 
> rate. It stays at 180 something . I'd have to go check to see. Now, if 
> memory serves me, the rate does change in the rate file for the synth.
> Changes in the rate file have no affect on the rate whatsoever. I 
> don't think it is a keyboard issue because I have tried multiple
keyboards:
> one was a PS2 connector and the other two were USB. Same result with 
> all, and all seem to work fine on other systems. I will give 64-bit 
> Wheezy a shot.
> 
> RE The Slackware Issue According to the Slackware docs on the DVD, 
> those issues were back with version 12.x FWIW, Slack 14 uses 3.2.29 
> kernel.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJRkzwcAAoJEPrAuJWnLe0yBjMP/2JJgIc2EulMOMPeyRffefTQ
eGQYBy+3dzzW0aveekebRUWLrsQ3zGQJCqWoqwt9H5JB4mbHqXgS+lMXtfPIvUbK
x9pMVcB8NBz6q3W3rkpgVZSInTWVcHt3FXMbE3cHNptSJjXq9mOpDg6RF36AUxSo
s0x+pZG1NLn9FuT6jnUE7WY/dqATzAJ7FtEIhzOBZrW1BFJNV5wbguAsbIQgzhQz
/XNXhRqK7dNT0NfLWQGbPC8Nh/EdeMt9dMmhNdaSS5GFh3wbRWrpOMjnSlVKRXOm
KLAEVRuB/Udjzdu6/wOHY1B5hqID5X8Ox0hxvDae8Yd9n3PatEltznAtab5tTk6x
DG5OP3JN9tpRiJQSh9VIB06yBah9kH4mnMjYqRLHF0jLYpHZYdZfPTYNsecyqrHu
mL6mdw1jGc71JLOw28+Jli1my0KA/ZmtKrVy5jZ2OEXPst+7EEkVPxcm1VEHs5yR
Ri44ijwe2x7itdbZRABKuGHVrbBsVXHmW0qMz6cFU2fGrxreDZwrs17ezChqKzJY
JSYHW9OSwSPidyveDjYtpFWsxZja2cMNYHOBjGwYujlSLQA54uhVjcs5HKR8tqkd
gZtYsyHFS7pSxeU4xqhsi5jTagWhhNhQ7MlC2Lny6051ucXpwTPzPMyoXzhBNZbx
sM5pj6OSIu+zwFtJQZUQ
=rvPy
-----END PGP SIGNATURE-----
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Mitchell D. Lynn
 ` Tony Baechler
   ` Mitchell D. Lynn
     ` Tony Baechler
       ` Mitchell D. Lynn [this message]
         ` Tony Baechler
           ` Mitchell D. Lynn
           ` covici
             ` Mitchell D. Lynn
               ` covici
                 ` Mitchell D. Lynn
                   ` Onboard serial ports Tony Baechler
                     ` John G. Heim
                       ` Mitchell D. Lynn
                       ` Jason White
                   ` Slack 13.37 and 14.0 John G. Heim
             ` Adam Myrow
               ` Mitchell D. Lynn
               ` Serial ports with 32-bit vs. 64-bit processors Tony Baechler
                 ` Kitty Litter
                 ` John G. Heim
                   ` Ryan Hutchings
                     ` John G. Heim
                   ` Tony Baechler
                 ` covici
                   ` Keith Wessel
           ` Slack 13.37 and 14.0 Gregory Nowak
             ` Tony Baechler
   ` Ryan Hutchings
     ` Debian Squeeze CDs Tony Baechler
       ` Ryan Hutchings
   ` Slack 13.37 and 14.0 Alex Snow
     ` Mitchell D. Lynn

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=72708A629D1C40508DEB3147F83238DA@mdlynn \
    --to=mlynn@kc.rr.com \
    --cc=speakup@linux-speakup.org \
    /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).