BTS

Issue610

Title speakup does not work with hardware synthesiser
Priority bug Status resolved
Superseder speakup kernel modules aren't loaded automatically
View: 620
Nosy List mika
Assigned To mika Topics release-stopper

Created on 2009-02-03.00:35:16 by mika, last changed 2009-05-20.21:22:01 by mika.

Messages
msg2242 (view) Author: mika Date: 2009-05-20.21:22:00
speakup.synth=apollo is supposed to work with grml 2009.05-rc1 which should hit 
the mirrors in those minutes... Setting status of this bugreport to resolved.
msg2165 (view) Author: mika Date: 2009-04-08.12:34:34
* Michael Whapples <bts@bts.grml.org> [20090408 14:28]:

> On my system it appears that the modprobe from the speakup.synth=synth_name is
> working except if this is meant to emulate the speakup kernel option (if speakup
> were built in the kernel) then synth_name differs from the module name slightly.
> I believe the difference is that the module name is the synth_name with speakup_
> prepended (eg. for the apollo synthesiser I give speakup.synth=apollo at the
> boot prompt but the module name is speakup_apollo, currently it seems like
> grml-autoconfig is using the synth_name as the module name, so in this case
> loading module apollo).

> So either this could be left as it currently is and users need to specify the
> full speakup module name (eg. speakup.synth=speakup_apollo) but I would
> recommend changing the option name to avoid confusion with the built in speakup
> standard (of course document this to make it clear) or add the speakup_ prefix
> to the synth_name given. I would prefer the latter as it then fits with the
> "usual". If doing the latter is there intention to support the other speakup
> kernel options? (eg. speakup.ser, speakup.quiet, etc)

Ah, thanks for the report! So speakup users are used to use
speakup.synth=apollo and not speakup.synth=speakup_apollo, right?
Then I'll just adjust grml-autoconfig to load speakup_$NAME instead.

regards,
-mika-
msg2164 (view) Author: mwhapples Date: 2009-04-08.12:28:50
On my system it appears that the modprobe from the speakup.synth=synth_name is
working except if this is meant to emulate the speakup kernel option (if speakup
were built in the kernel) then synth_name differs from the module name slightly.
I believe the difference is that the module name is the synth_name with speakup_
prepended (eg. for the apollo synthesiser I give speakup.synth=apollo at the
boot prompt but the module name is speakup_apollo, currently it seems like
grml-autoconfig is using the synth_name as the module name, so in this case
loading module apollo).

So either this could be left as it currently is and users need to specify the
full speakup module name (eg. speakup.synth=speakup_apollo) but I would
recommend changing the option name to avoid confusion with the built in speakup
standard (of course document this to make it clear) or add the speakup_ prefix
to the synth_name given. I would prefer the latter as it then fits with the
"usual". If doing the latter is there intention to support the other speakup
kernel options? (eg. speakup.ser, speakup.quiet, etc)
msg2139 (view) Author: mika Date: 2009-04-06.10:52:13
Michael Prokop <mika@grml.org> has uploaded a package that may fix your bug.
Please test the package and inform the maintainer whether
version 0.8.19 of grml-autoconfig works as intended or not.

Thank you

The changelog is attached below

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 06 Apr 2009 12:47:34 +0200
Source: grml-autoconfig
Binary: grml-autoconfig
Architecture: source all
Version: 0.8.19
Distribution: unstable
Urgency: low
Maintainer: Michael Prokop <mika@grml.org>
Changed-By: Michael Prokop <mika@grml.org>
Description: 
 grml-autoconfig - main bootup process of a grml system
Changes: 
 grml-autoconfig (0.8.19) unstable; urgency=low
 .
   * Add support for speakup.synth=... bootoption. [Testing: issue610]
     [Closes: issue620]
Checksums-Sha1: 
 2f22ff53fd80d145395797356a3df4d2332ac636 886 grml-autoconfig_0.8.19.dsc
 72e9384fbb1d950bd11cba8dac8abe2853c857d8 57735 grml-autoconfig_0.8.19.tar.gz
 0724671af454a96d419b0dac28e0b51159b23120 56756 grml-autoconfig_0.8.19_all.deb
Checksums-Sha256: 
 d6cc486795243c2d72148b51f8cda653bb8eb45b52cfa63a67a77b62995ae452 886 grml-autoconfig_0.8.19.dsc
 a3240a981f9c9ecffa889e47d8511e681955b1909498f14c9c50696a04b9ee99 57735 grml-autoconfig_0.8.19.tar.gz
 87d62d1747ba3f69eb6995181cb40abe34490c176f81f86a88a1738d249c6392 56756 grml-autoconfig_0.8.19_all.deb
Files: 
 aa2fa2562f7e44a8ee3143e16f799f62 886 grml optional grml-autoconfig_0.8.19.dsc
 e6477f7733ec7c562d9caaf8e94b0fe8 57735 grml optional grml-autoconfig_0.8.19.tar.gz
 c5f6ffa795b38d7f86a6728c2069c2ba 56756 grml optional grml-autoconfig_0.8.19_all.deb

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

iD8DBQFJ2d5x2N9T+zficugRArjKAJ9aoH+c0S3eKaJKPSOqNa5hycFHMgCeOUp4
rmMhj2XkFUPa3OEejzMqQ0k=
=zkJQ
-----END PGP SIGNATURE-----
msg1794 (view) Author: mika Date: 2009-02-03.00:35:14
Bugreport by Michael Whapples (thanks!):

I am unable to use speakup with a hardware apollo synthesiser. In
the file listing the cheat codes for GRML 2008.11 it says that the
option should be of the form speakup_synth=synthname, so I enter
the following command (it includes a brltty option for my Braille
display):

grml brltty=al speakup_synth=apollo
The Braille display works but no speech comes out.

I know that for speakup 3.0.x the options normally are of the form
speakup.synth=synthname (in the main the _ character is replaced
with the . character). So I tried booting with the following line:

grml brltty=al speakup.synth=apollo

Again Braille works but no speech. Once the system is booted if I do:
modprobe speakup_apollo
speakup will start.
History
Date User Action Args
2009-05-20 21:22:01mikasetstatus: testing -> resolved
messages: + msg2242
2009-04-08 12:50:06mikasetassignedto: mika
2009-04-08 12:34:35mikasetmessages: + msg2165
2009-04-08 12:28:51mwhapplessetmessages: + msg2164
2009-04-06 10:52:15mikasetstatus: unread -> testing
messages: + msg2139
2009-03-31 21:46:16mikasetsuperseder: + speakup kernel modules aren't loaded automatically
2009-03-31 21:46:03mikalinkissue620 superseder
2009-02-03 00:35:17mikacreate