What is .WITH. the Debian amd64 kernel and SpeakUP?

[Igor Gueths]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello Kirk. Now that you mention it, I remember awhile back discussing this very
issue with William a while back; of course presumably, at that time the problem
was assumed to be within Espeakup as far as I know. I was just curious if you
were referring to the same problem or something else similar?
On Thu, Sep 16, 2010 at 01:43:44PM -0400, Kirk Reiser wrote:
> There seems to be a bug in speakup running on quad core processors
> which produces garbled speech output occasionally.  I have not been
> able to nailed down an exact situation which will consistantly produce
> the effect but it happens regularly.  There must be some lock which is
> not set and therefore the text gets into the output buffer in a
> disordered fashion.  Reviewing the screen will of course read it
> correctly.
>
>   Kirk
>
>
> On Thu, 16 Sep 2010, Gaijin wrote:
>
>> On Thu, Sep 16, 2010 at 07:38:10AM -0500, Christopher Brannon wrote:
>>> 1. Which synth are you using?
>>
>> 	Both the speakup_ltlk, loaded from /etc/modules, and
>> speakup_soft, loaded from /etc/rc.local with the commands:
>>
>> rmmod speakup_ltlk
>> modprobe speakup_soft
>> espeakup
>> speakupconf load
>>
>>
>>> 2. Which version of the kernel are you using?  (uname -a)
>>
>> Linux rivensight 2.6.32-5-686 #1 SMP Wed Aug 25 14:28:12 UTC 2010 i686
>> GNU/Linux
>>
>> 	It's the unaltered Debian Squeeze kernel that came from the
>> amd64 installation disk, and I'm told, includes the speakup modules
>> compiled into the kernel, and running on a I7-930 Quad-Core CPU on a
>> SuperMicro X8STE motherboard with 24G's of Kingston memory.  I use the
>> Orca screen reader for the GUI.  I'm surprized that it's a 686 kernel,
>> but that's what Debian gave us for the 64-bit, Core-2 platforms, so I
>> gather that it's the correct one.
>>
>>
>>> 3. Which version of the Speakup package are you using?>
>>
>>> From /var/log/dmesg Sorry for not word-wrapping):
>>
>> [    6.214497] speakup: module is from the staging directory, the quality is unknown, you have been warned.
>> [    6.217153] speakup 3.1.3: initialized
>> [    6.217157] synth name on entry is: ltlk
>> [    6.217339] initialized device: /dev/synth, node (MAJOR 10, MINOR 25)
>> [    6.217792] speakup_ltlk: module is from the staging directory, the quality is unknown, you have been warned.
>> [    6.218396] synth probe
>> [    6.218398] Ports not available, trying to steal them
>> [    6.220396] LiteTalk: ttyS0, Driver Version 2.10
>> [    6.255596] LiteTalk: ROM version: <FF>2.42A
>>
>> 	After the above, the loop module loads, and the line in
>> /etc/modules is simply "speakup_ltlk", which appears to work just fine
>> when I bother to turn on the LiteTalk.  Since I don't appear to have any
>> problems booting up, I leave the thing switched off.  The synth is
>> connected to ttyS0.  ttyS1 is unused (no plug), ttyS2 is a US Robotics
>> PCI modem, and ttyS3 is on a Axxon searial/parallel PCIE card, as the
>> mobo came without a friggin printer port.  Both cards are reported to
>> work flawlessly with Linux.  Lemme know if you need the output from
>> something like lshw or something for this...
>>
>> 				Michael
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup at braille.uwo.ca
>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>>
>
> --
> Kirk Reiser				The Computer Braille Facility
> e-mail: kirk at braille.uwo.ca		University of Western Ontario
> phone: (519) 661-3061
> _______________________________________________
> Speakup mailing list
> Speakup at braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>

- -- 
Igor
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)

iQIVAwUBTJLnoae2pgKIdGq4AQp44w/5AQEWmL2yz7TlU1EfA98zGfoaOv7KTWEl
Jg2WjgYz2Rp9ppt6FG3meQI0ZeQNBka8etUROiW68VdbWPkh5hUVaks6YiH8UFYx
a/AYTHqMf2enb3htX8zw4ydQYqLnyPmSQJAdhJgA7J3NcGuPEQo06a0lXc5Ay6mx
CZIcwjLFQinuF5gIS4ka2fIk4xIqML79ws+tr2HAmUBL8hWJEqn/j9+R1PtViHfe
8bF1qyDH/AM0BGgwIyPxhpUwi6l3cEMUdR0Gs7wMv1Gq8mf+72ac4n9Rci52VsX5
iovcoWQ3QJUUpOSxJQacNpg/3Az+/HavpAAqLR9eO/s0odVT8zP19rpHNfEa0+Sx
ZNk0HRLpLjswRHZ6vTlxhPLhC+BBPC+WydJLwJ+ub8GK8/DiqDvtgS3h3QfbPxfR
txza7sxF3q5lBUNjGEobAKqNcnNQGnILJl92VFqBBdO98DbGk8k6hpo2LGHpJjdI
Z2AXWEYpaNWJhqLdMiN1PJRnES1WMHAZRBGKubo8HSkGPhv9I5yvSOjkqjXxnGVA
JmVB8N32t/2xqGgvwVl+gzyQc0MUfTU8ZrnDQyG18DYSNNXVqiyAOCVOUxmcTh61
kUMU59VBAIeXsX7/e0A0d3pWpsOAeJnUtYPao9hkYY3JEdFO3voukbdnJAgi8aKt
c4eVibnw6i4=
=r0v/
-----END PGP SIGNATURE-----

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.