quick fix for 2.6.34 problem with serial synths

quick fix for 2.6.34 problem with serial synths

[Kitty Litter]

In speakup/src/serialio.c comment out the return (NULL); line just below 
__release_region.
Looking at the kernel source in kernel/resource.c it seems that if 
__release_region fails you would get a kernel message. So speakup seems to 
think it fails but the kernel doesn't.
Someone with more smarts than me maybe can figure this all out.

Re: quick fix for 2.6.34 problem with serial synths

[William Hubbs]

On Sun, Jun 27, 2010 at 01:52:01PM -0400, Kitty Litter wrote:
> In speakup/src/serialio.c comment out the return (NULL); line just below 
> __release_region.
> Looking at the kernel source in kernel/resource.c it seems that if 
> __release_region fails you would get a kernel message. So speakup seems to 
> think it fails but the kernel doesn't.
> Someone with more smarts than me maybe can figure this all out.

Actually the failure was happening on the line below that in the call to
synth_request_region.

I don't have a fix for that yet, but now the code is set up to log the
error code and port number if that fails so hopefully we can see what is
going on.

Are you comfortable with pulling from git and testing with that code?
Any help would be appreciated.

Thanks,

William

Re: quick fix for 2.6.34 problem with serial synths

[Steve Holmes]

I also just tried to run my Speakout serial synth and got errors
similar to what others have been reporting.  I will paste in the most
relevant line from the system log.
Trying to free nonexistent resource
<00000000000003f8-00000000000003ff>
Before that, tynth probe was followed by being unable to get the port
and "trying to steal them."  I got the same results with talkwith and
manually trying to do echoing to speakup/synth.

In any case, the pride and joy of Speakup with serial synths doesn't
work for me either.  This happened with both the binary version on
ArchLinux and the git pull from just an hour ago (July 6th).

On Tue, Jun 29, 2010 at 10:58:06AM -0500, William Hubbs wrote:
> On Sun, Jun 27, 2010 at 01:52:01PM -0400, Kitty Litter wrote:
> > In speakup/src/serialio.c comment out the return (NULL); line just below 
> > __release_region.
> > Looking at the kernel source in kernel/resource.c it seems that if 
> > __release_region fails you would get a kernel message. So speakup seems to 
> > think it fails but the kernel doesn't.
> > Someone with more smarts than me maybe can figure this all out.
> 
> Actually the failure was happening on the line below that in the call to
> synth_request_region.
> 
> I don't have a fix for that yet, but now the code is set up to log the
> error code and port number if that fails so hopefully we can see what is
> going on.
> 
> Are you comfortable with pulling from git and testing with that code?
> Any help would be appreciated.
> 
> Thanks,
> 
> William
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: quick fix for 2.6.34 problem with serial synths

[Steve Holmes]

Are people still having trouble with serial synths with latest
Speakup? I haven't heard any further discussion on this since my last
post.

On Tue, Jul 06, 2010 at 01:14:55PM -0700, Steve Holmes wrote:
> I also just tried to run my Speakout serial synth and got errors
> similar to what others have been reporting.  I will paste in the most
> relevant line from the system log.
> Trying to free nonexistent resource
> <00000000000003f8-00000000000003ff>
> Before that, tynth probe was followed by being unable to get the port
> and "trying to steal them."  I got the same results with talkwith and
> manually trying to do echoing to speakup/synth.
> 
> In any case, the pride and joy of Speakup with serial synths doesn't
> work for me either.  This happened with both the binary version on
> ArchLinux and the git pull from just an hour ago (July 6th).
> 
> On Tue, Jun 29, 2010 at 10:58:06AM -0500, William Hubbs wrote:
> > On Sun, Jun 27, 2010 at 01:52:01PM -0400, Kitty Litter wrote:
> > > In speakup/src/serialio.c comment out the return (NULL); line just below 
> > > __release_region.
> > > Looking at the kernel source in kernel/resource.c it seems that if 
> > > __release_region fails you would get a kernel message. So speakup seems to 
> > > think it fails but the kernel doesn't.
> > > Someone with more smarts than me maybe can figure this all out.
> > 
> > Actually the failure was happening on the line below that in the call to
> > synth_request_region.
> > 
> > I don't have a fix for that yet, but now the code is set up to log the
> > error code and port number if that fails so hopefully we can see what is
> > going on.
> > 
> > Are you comfortable with pulling from git and testing with that code?
> > Any help would be appreciated.
> > 
> > Thanks,
> > 
> > William
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: quick fix for 2.6.34 problem with serial synths

[Joshua Lambert]

I am still having troubles of the kind already being reported.
On Fri, 9 
Jul 2010, Steve Holmes wrote:

> Date: Fri, 9 Jul 2010 18:55:07 -0700
> From: Steve Holmes <steve@holmesgrown.com>
> Reply-To: Speakup is a screen review system for Linux.
>     <speakup@braille.uwo.ca>
> To: speakup@braille.uwo.ca
> Subject: Re: quick fix for 2.6.34 problem with serial synths
> 
> Are people still having trouble with serial synths with latest
> Speakup? I haven't heard any further discussion on this since my last
> post.
>
> On Tue, Jul 06, 2010 at 01:14:55PM -0700, Steve Holmes wrote:
>> I also just tried to run my Speakout serial synth and got errors
>> similar to what others have been reporting.  I will paste in the most
>> relevant line from the system log.
>> Trying to free nonexistent resource
>> <00000000000003f8-00000000000003ff>
>> Before that, tynth probe was followed by being unable to get the port
>> and "trying to steal them."  I got the same results with talkwith and
>> manually trying to do echoing to speakup/synth.
>>
>> In any case, the pride and joy of Speakup with serial synths doesn't
>> work for me either.  This happened with both the binary version on
>> ArchLinux and the git pull from just an hour ago (July 6th).
>>
>> On Tue, Jun 29, 2010 at 10:58:06AM -0500, William Hubbs wrote:
>>> On Sun, Jun 27, 2010 at 01:52:01PM -0400, Kitty Litter wrote:
>>>> In speakup/src/serialio.c comment out the return (NULL); line just below
>>>> __release_region.
>>>> Looking at the kernel source in kernel/resource.c it seems that if
>>>> __release_region fails you would get a kernel message. So speakup seems to
>>>> think it fails but the kernel doesn't.
>>>> Someone with more smarts than me maybe can figure this all out.
>>>
>>> Actually the failure was happening on the line below that in the call to
>>> synth_request_region.
>>>
>>> I don't have a fix for that yet, but now the code is set up to log the
>>> error code and port number if that fails so hopefully we can see what is
>>> going on.
>>>
>>> Are you comfortable with pulling from git and testing with that code?
>>> Any help would be appreciated.
>>>
>>> Thanks,
>>>
>>> William
>>>
>>> _______________________________________________
>>> Speakup mailing list
>>> Speakup@braille.uwo.ca
>>> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>