I don't know if you can fix it for installation. But you can patch the
kernel code yourself and recompile your own kernel. It's not as
difficult as it sounds.
Actually, I don't know how to compile a kernel on slackware. It's easy
on debian. I wrote instructions for doing it for debian. See
http://www.iavit.org/~john/debian/
If you click on the "patch" link, you will get a file that contains a
patch for the single line in the speakup source that needs to be fixed
to make the litetalk and other hardware synths work. If you can
understand diff output, you could just go in and edit the code yourself.
All you really need to do is comment out one line. IIRC< it's line 46 in
serialio.c.
I can tell you exactly how to find the line you need to comment out. Go
into the directory where you downloaded the kernel code. Find the
spekaup directory, "Find . -type d -name speakup". Go into the speakup
directory and grep for "trying to steal". That will show you which file
you need to edit. I think it's called serialio.c. In that file just
below the comment that says "trying to steal" will be an exit command. I
think that's line 46. Comment out that line. Recompile your kernel, and
your litetalk will work.
On 12/07/2014 08:15 PM, Jude DaShiell wrote:
is anyone running a hardware speakup synthesizer on any of the modern
kernel releases? I'm thinking one possibility may be hardware kernels
have been disabled in these modern kernels as shipped from the developers.
I hope not, but if that is the case and distributors like Slackware do not
enable those hardware drivers that would explain why on the amd side 13.37
14.1 and slackware-current all fail to bring up the litetalk speakup
module in a way that gets my litetalk synthesizer speaking for an install.
It's possible this is not the case and if it's not the case, this system
is experiencing some kind of error that will show up on the screen when
one is plugged and a boot test is done with these failing slackware
distros. After I've logged in on slackware I've done echo "Hello, World!"
/dev/ttyS0 and hear the text spoken. However when I type modprobe
speakup_ltlk and hit enter, all the rest is silence. One way it might
work is if /dev/ttyS0 is first initialized as a serial port and then the
speakup parameters are passed in on the boot prompt. Why this should have
to be done now when it wasn't necessary in the past is a puzzle to me if
it does work.
jude <jdashiel@xxxxxxxxxxxxxx> Twitter: @jdashiel
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
