-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I believe I reported on this a while back when describing the kernel panics I got when trying to switch between bns, dtlk, and sftsyn. Unless something has changed since that report, (and I don't know if it has, since I haven't upgraded speakup since then yet), then you need to modprobe sftsyn by hand, at least that's something that I needed to do. Greg On Wed, May 17, 2006 at 04:23:46PM -0700, Steve Holmes wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: RIPEMD160 > > I think I'm on to something. I'm sorking this machine by remote ssh > session so can't be totally sure but What I see so far is the sftsyn > module is not being auto loaded when echoing "sftsyn" to > /proc/speakup/synth_name. That used to work. when I echoed "sftsyn" to > /proc..., the value did not stick; as soon as I modprobed > speakup_sftsyn, then the /proc variable got updated. Is this change by > design? do we have to explicitely modprobe speakup modules now or am I > missing something some place. I don't recall seeing keyhelp in there > either but that's for another discussion:). if it is by design, I'll > just add the modprobe line into my rc.speakup script and it'll be all > good. > - -- web site: http://www.romuald.net.eu.org gpg public key: http://www.romuald.net.eu.org/pubkey.asc skype: gregn1 (authorization required, add me to your contacts list first) - -- Free domains: http://www.eu.org/ or mail dns-manager at EU.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) iD8DBQFEa7SS7s9z/XlyUyARAjh5AKCnXFNuLhh2h4KtiqbQYaR7HBh2LACfWi0N 749xudhyZF3zh4j9vhvmNqA= =F0H9 -----END PGP SIGNATURE-----
