This is what I get when I compiled the latest CVS of Speakup with Speakup and spkout both as modules. Oct 31 14:58:09 lnx3 kernel: Speakup: loading module "speakup_spkout" Oct 31 14:58:09 lnx3 kernel: spkout: device probe failed Oct 31 14:58:09 lnx3 insmod: /lib/modules/2.4.21/kernel/drivers/char/speakup/speakup_spkout.o: init_module: No such device Oct 31 14:58:09 lnx3 insmod: /lib/modules/2.4.21/kernel/drivers/char/speakup/speakup_spkout.o: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters. You may find more information in syslog or the output from dmesg Oct 31 14:58:09 lnx3 insmod: /lib/modules/2.4.21/kernel/drivers/char/speakup/speakup_spkout.o: insmod speakup_spkout failed Oct 31 14:58:09 lnx3 kernel: spkout: device probe failed I don't honestly know how any speakout user could possibly use the current CVS of Speakup as it is right now. I also get the device probe failures for both static and module use. Hope the log info helps. Perhaps CVS should be rolled back to before last Friday's work is that possible or reasonable? -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown
