From: "Ryan Hutchings" <RyanHornibrook@aol.com>
To: "Speakup is a screen review system for Linux."
<speakup@linux-speakup.org>
Subject: Re: Serial ports with 32-bit vs. 64-bit processors
Date: Thu, 16 May 2013 20:06:36 +0100 [thread overview]
Message-ID: <5B95586E79D54D8EB60DBD02E788E850@RyanTosh> (raw)
In-Reply-To: <5194F445.6020807@math.wisc.edu>
Hi John,
Did your doubletalk work during wheezy installation as well?
I tried using my doubletalk lt with Wheezy 64 bit to install, and got no
speech.
I also tried the latest grml live 64 bit cd, and got no speech after doing a
modprobe speakup_ltlk.
I wonder what determines when speakup will work with hardware speech? if it
works on your 64bit system it can't be a 64bit thing.
I tried this on a laptop if that makes any differences?
Maybe a device in my laptop interferes with the speakup serial code - i.e. a
device is using the i/o address that speakup normally associates with a
serial port?
Ryan
-----Original Message-----
From: John G. Heim
Sent: Thursday, May 16, 2013 3:59 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Serial ports with 32-bit vs. 64-bit processors
Are you saying you can't get your doubletalk to work at all or only if
you load the speakup_sot module before loading the speakup_ltlk module?
I don't know if I've ever tried that. But I have a 64 bit machine
running squeeze and another running wheezy. Speakup works with my
doubletalk on either machine if I load the speakup_ltlk module
directly. On the squeeze, I'm running a kernel from squeeze-backports
and on the wheezy machine, I'm running the stock kernel. Here is what
uname -r says on each;
squeeze: 3.2.0-0.bpo.4-amd64
wheezy: 3.2.0-4-amd64
My doubletalk also works with the 64-bit grml live CD. As I said, I'm
not entirely sure I ever tried loading the speakup_ltlk module after
speakup_soft. I would have to say that I have though because I put
speakup_soft in /etc/modules so it loads during boot.
On 05/16/13 04:07, Tony Baechler wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Ah, that's what I've been wondering about. I've asked various people here
> who claim to have working hardware speech, but never got a response. My
> question is if they're running 32-bit or not. I can not only confirm that
> it won't work on 64-bit systems but if I try to unload speakup_soft and
> load speakup_ltlk, it completely locks up the system. Someone else said
> they didn't have any problem with serial speech with new kernels and a
> 32-bit processor, but I couldn't get it confirmed. Now, my question is
> what difference would a 64-bit processor make? Why does it completely
> lock up here but seems to work for at least three people on older 32-bit
> processors? I'm tempted to install 32-bit Debian Wheezy just to see if it
> makes any difference. I can say that it doesn't seem to matter on a
> 32-bit live CD here.
>
> On 5/15/2013 3:45 PM, Adam Myrow wrote:
>> Ok, I am using the kernel that ships with Debian 7.0, which is listed
>> as 3.2.0-4-686-pae. My Dectalk USB works just as it always has in
>> RS232 mode. In other words, serial support isn't broken for me. This
>> is the 32-bit version, so maybe that's the difference.
>> _______________________________________________ Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
> - --
> Have a good day,
> Tony Baechler
> tony@baechler.net
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQIcBAEBCAAGBQJRlKHnAAoJEPrAuJWnLe0yfn0P/iXnQjg7+/N8wfGHKe1+eSph
> Urwuctsw+WKw8jwgFEKcHZz8HhkOggfNzttUItcPiTDJfvD/4cg/KIAJ+XKYMCc0
> LNxXIZN85uZ2iY5r7xgBgjplbHRsAeLbXrD0UazzXQVkGLfkqC+Kp58aGPGDsY0w
> //vyg+xvAwggIuFHaSsO9SMBktYKCyGJ4kJn1UOfyZne4TbUQs0rbGG+T1S29p4f
> /gC0D4uL04Xa374qOSkG+aFso6ET99Ax/3hkPtBZsfL9JZsju3vhhwvoDQtmMONw
> OPSjNSZoSK0eov9P69HEUuK6QtZwsdE4azk6xDJp0EGftu3cpM0rXm9c0kcLa5k1
> MiZsqkM0HNgr8gF72D7f4eIdc/E9zzgK2HC9P0lKaZK5E4q7CR4ASKZKwKKlWcez
> wvZsCq6MqGmQz5dUD5K2bj2QkZT8E4gzSo8PKso7ELs/fcovca5E910Kgj2B8wnb
> uaCrsbjlxwFMBONxmc3M4FGXnNv2qzCl56asYOaPT+hAvMM7oOJ/XJHXYq0qm1WP
> A2/FkoSwM1ks/dDjkngwPP4uF473m2xplApkoEDJA+wcPfzaCS70mDS+PMcVMsZC
> SNkCPg1zl7MsUm/UED25oJ/ZJ1/HbFKFMGU/Rw5YnCZ0q0UwZtxLDfZZwWPgO1n3
> oNMRyb/34AvysFFcJ0GS
> =BDqC
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>
--
---
John G. Heim, 608-263-4189, jheim@math.wisc.edu
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
Slack 13.37 and 14.0 Mitchell D. Lynn
` Tony Baechler
` Mitchell D. Lynn
` Tony Baechler
` Mitchell D. Lynn
` 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 [this message]
` 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=5B95586E79D54D8EB60DBD02E788E850@RyanTosh \
--to=ryanhornibrook@aol.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).