speakup.synth= vs modprobe

speakup.synth= vs modprobe

[John G. Heim]

I installed the 2.6.26 kernel from debian lenny along with the speakup 
modules.  I modified my /boot/grub/menu.lst to use speakup.synth=ltlk as a 
boot parameter. But I don't get speech during boot. If I log in after it 
boots and type 'modprobe speakup_ltlk' then I get speech.

Any explanation for this? Below is the boot stanza from my menu.lst.

title  Debian GNU/Linux, kernel 2.6.26-1-486
root  (hd0,0)
kernel  /boot/vmlinuz-2.6.26-1-486 root=/dev/hda1 ro speakup.synth=ltlk
initrd  /boot/initrd.img-2.6.26-1-486

Re: speakup.synth= vs modprobe

[Gregory Nowak]

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

Yes, as far as I know, grub isn't the place to do what you're trying
to do. Samuel described the method for doing this in an earlier
message on this list:

http://speech.braille.uwo.ca/pipermail/speakup/2008-July/046850.html

Hth.

Greg


On Thu, Mar 26, 2009 at 08:09:12PM +0100, webczat@fws.pl.eu.org wrote:
> Hmm...
> Modules are separate from kernel, so kernel parameter speakup.synth can't work if kernel doesn't ewen know what is speakup.
> Add your proper speakup modules to some files to make the debian automatically load it.
> I don't remember where you can do this.
> Thanks.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


- -- 
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@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknLxnQACgkQ7s9z/XlyUyDEZQCZARB7upmweQmd9Buf7yLEb3mF
IQIAnRtjWG4lCwByKJuF9d79FKhinQM7
=BwSb
-----END PGP SIGNATURE-----

RE: speakup.synth= vs modprobe

[al Sten-Clanton]

"Hmm...
Modules are separate from kernel, so kernel parameter speakup.synth can't
work if kernel doesn't ewen know what is speakup.
Add your proper speakup modules to some files to make the debian
automatically load it.
I don't remember where you can do this.
Thanks."

Does this mean that, unlike with, say, Fedora 9 or the earlier versions of
GRML, you can't have speakup available early in the boot process?  I was
able to work around this for Fedora 10 using mkinitrd, but I couldn't find
that program when I tried this with the latest GRML.  I ask only in part out
of curiosity.  Thanks!

Al

Re: speakup.synth= vs modprobe

[webczat]

"John G. Heim" <jheim@math.wisc.edu> wrote:

> I installed the 2.6.26 kernel from debian lenny along with the speakup 
> modules.  I modified my /boot/grub/menu.lst to use speakup.synth=ltlk as a 
> boot parameter. But I don't get speech during boot. If I log in after it 
> boots and type 'modprobe speakup_ltlk' then I get speech.
>
> Any explanation for this? Below is the boot stanza from my menu.lst.
>
> title  Debian GNU/Linux, kernel 2.6.26-1-486
> root  (hd0,0)
> kernel  /boot/vmlinuz-2.6.26-1-486 root=/dev/hda1 ro speakup.synth=ltlk
> initrd  /boot/initrd.img-2.6.26-1-486
>
>
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
Hmm...
Modules are separate from kernel, so kernel parameter speakup.synth can't work if kernel doesn't ewen know what is speakup.
Add your proper speakup modules to some files to make the debian automatically load it.
I don't remember where you can do this.
Thanks.

RE: speakup.synth= vs modprobe

[al Sten-Clanton]

Thanks for this info.  I guess I should have seen what else I had for
messages before writing to that earlier one with my question.

Al
 

-----Original Message-----
From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
On Behalf Of Gregory Nowak
Sent: Thursday, March 26, 2009 2:16 PM
To: Speakup is a screen review system for Linux.
Subject: Re: speakup.synth= vs modprobe

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

Yes, as far as I know, grub isn't the place to do what you're trying to do.
Samuel described the method for doing this in an earlier message on this
list:

http://speech.braille.uwo.ca/pipermail/speakup/2008-July/046850.html

Hth.

Greg


On Thu, Mar 26, 2009 at 08:09:12PM +0100, webczat@fws.pl.eu.org wrote:
> Hmm...
> Modules are separate from kernel, so kernel parameter speakup.synth can't
work if kernel doesn't ewen know what is speakup.
> Add your proper speakup modules to some files to make the debian
automatically load it.
> I don't remember where you can do this.
> Thanks.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 


- --
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@EU.org -----BEGIN PGP
SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknLxnQACgkQ7s9z/XlyUyDEZQCZARB7upmweQmd9Buf7yLEb3mF
IQIAnRtjWG4lCwByKJuF9d79FKhinQM7
=BwSb
-----END PGP SIGNATURE-----
_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup

Re: speakup.synth= vs modprobe

[Gregory Nowak]

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

On Thu, Mar 26, 2009 at 03:06:54PM -0400, al Sten-Clanton wrote:
> Does this mean that, unlike with, say, Fedora 9 or the earlier versions of
> GRML, you can't have speakup available early in the boot process?

Yes, you can have speakup loaded even before the root file system
comes up, if you're using an initrd which contains speakup built as
modules. Basically, the behavior would be as if speakup was built into
the kernel, except that speakup is built as modules in this case, and
the kernel doesn't need to be rebuilt to include speakup.

Greg


- -- 
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@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAknL0+4ACgkQ7s9z/XlyUyBpUgCgvYUiY/fYdSEAJHp5hvw0hhDY
r+sAoNuJxWOd/dDmzk7LGkZiM6iIBfW3
=IzMs
-----END PGP SIGNATURE-----

Re: speakup.synth= vs modprobe

[Alex Snow]

You probably have to put the modules into your initrd...I'm not 
familiar with this as I use slackware which doesn't use 
initrds...though looking at mkinitrd I think it is should help. THen 
you have to find a way for the startup script to detect the 
speakup.synth param and load the correct module.
On 
Thu, Mar 26, 2009 at 01:02:16PM -0500, John G. Heim wrote:
> I installed the 2.6.26 kernel from debian lenny along with the speakup 
> modules.  I modified my /boot/grub/menu.lst to use speakup.synth=ltlk as a 
> boot parameter. But I don't get speech during boot. If I log in after it 
> boots and type 'modprobe speakup_ltlk' then I get speech.
> 
> Any explanation for this? Below is the boot stanza from my menu.lst.
> 
> title  Debian GNU/Linux, kernel 2.6.26-1-486
> root  (hd0,0)
> kernel  /boot/vmlinuz-2.6.26-1-486 root=/dev/hda1 ro speakup.synth=ltlk
> initrd  /boot/initrd.img-2.6.26-1-486
> 
> 
> 
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

-- 
If you want to travel around the world and be invited to speak at a lot
of different places, just write a Unix operating system.
	-- Linus Torvalds

RE: speakup.synth= vs modprobe

[Erik Heil]

Hi their.
In Debian, their is something called modconf, and also their is Module
Assistant. I have not personally tried these tools, but wouldn't they be
helpful  in this situation? Just my two sense.
--Erik

On Thu, 26 Mar 2009, al Sten-Clanton wrote:

> Date: Thu, 26 Mar 2009 15:06:54 -0400
> From: al Sten-Clanton <Albert.E.Sten_Clanton@verizon.net>
> Reply-To: Speakup is a screen review system for Linux.
>     <speakup@braille.uwo.ca>
> To: 'Speakup is a screen review system for Linux.' <speakup@braille.uwo.ca>
> Subject: RE: speakup.synth= vs modprobe
>
> "Hmm...
> Modules are separate from kernel, so kernel parameter speakup.synth can't
> work if kernel doesn't ewen know what is speakup.
> Add your proper speakup modules to some files to make the debian
> automatically load it.
> I don't remember where you can do this.
> Thanks."
>
> Does this mean that, unlike with, say, Fedora 9 or the earlier versions of
> GRML, you can't have speakup available early in the boot process?  I was
> able to work around this for Fedora 10 using mkinitrd, but I couldn't find
> that program when I tried this with the latest GRML.  I ask only in part out
> of curiosity.  Thanks!
>
> Al
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>

eheil@sdf.lonestar.org
SDF Public Access UNIX System - http://sdf.lonestar.org

Re: speakup.synth= vs modprobe

[John G. Heim]

----- Original Message ----- 
From: "Gregory Nowak" <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Thursday, March 26, 2009 2:13 PM
Subject: Re: speakup.synth= vs modprobe


> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Thu, Mar 26, 2009 at 03:06:54PM -0400, al Sten-Clanton wrote:
>> Does this mean that, unlike with, say, Fedora 9 or the earlier versions 
>> of
>> GRML, you can't have speakup available early in the boot process?
>
> Yes, you can have speakup loaded even before the root file system
> comes up, if you're using an initrd which contains speakup built as
> modules. Basically, the behavior would be as if speakup was built into
> the kernel, except that speakup is built as modules in this case, and
> the kernel doesn't need to be rebuilt to include speakup.

Oh yeah, I never made that connection before. I always compiled speakup 
drivers as modules and then loaded them with the speakup.synth kernel parm. 
I never put any thought into whether I should put an m or a y in that box 
for compiling the drivers.  It seemed to work just as well either way. But 
it didn't really. I was missing some boot messages.

So that's why they went to initrd. I asked about that on a general linux 
list a few years ago and didn't understand the answers i got. I suppose 
there's lots of stuff that can go in there but for one thing, it allows the 
kernel to have access to would normally be in /lib/modules at a point before 
it can read the disk.

Ah, now I get it.

I really tricked myself though. I put a stock debian kernel on my PC at home 
and it came up talking. So I figured the speakup.synth parameter was still 
working. As it turns out, I had the module in /etc/modules too. So that's 
why it was loading it.