Is this a new bug, a known bug, or did I just do it wrong? I compiled CVS Speakup as modules (all of it). After 2.6.18 successfully booted, I followed the instructions in section seven of the spkguide.txt file. In so doing, I ran: modprobe speakup_dectlk At which point modprobe hangs indefinitely. When I tried it in /etc/modules (speakup_dectlk), which I stupidly did first, I was forced to boot this Ubuntu system with the talking Debian Installation CD, in order to fix /etc/modules. When I tried "modprobe speakup_dectlk" from a command line on a console, and it obviously hung, I was able to log into a second console, and do a "killall modprobe", to get it to stop. I reconfigured the *exact* same kernel, compiling speakup main directly in, and leaving the synth as a module. When I next booted, I was able to run "echo dectlk > /proc/speakup/synth_name", and have the system talking just fine! (Well, except for the zero followed by alpha problem, which I explained in another message) So: what is the problem with having speakup_main as a module, if in fact that is the problem? AMD K7 system; kernel 2.6.18; GCC 4.0.3. Thanks Luke
