----- Original Message -----
Sent: Monday, May 17, 2004 11:44
PM
Subject: speakup on fedora?
hello
how do I get speak up speaking when fedora
boots?
it isn't speaking at all
and the directions don't work on setting that
up
Creating an INITRD
Follow these steps to create an initial ram
disk image for your installation. This is how we make Speakup speak while
your computer boots now that Speakup
is modular. Of course, if we were
smarter people, we would have modified the installation scripts to do this
for you automatically based on the Speakup
synthesizer keyword you
provided back when you first started the installation.. But, ... well let's
not go there!
List of 5 items
1. Switch to the second console by
holding down the Alt key and pressing theF2 key. When you release these
you'll find that you're at a # prompt.
2. Change to the directory
that contains your new installation by typing:
cd
/mnt/sysimage
3. Now, restrict your view to your installation by
typing the following command. Notice that your prompt changes when you do
this.
chroot .
4. Next, change directory one more time by
typing:
cd /lib/modules
5. Now, make a new initrd with Speakup by
issuing the following command. Where wis command has {TAB} you should press
the TAB key. Don't actually type {TAB}!
And, where we have
{synth.keyword}, replace this text with the correct sSpeakup word for your
speech synthesizer.
/sbin/mkinitrd -v -f /boot/initrd-{tab}
--with=speakup_{synth.keyword} {TAB}
list end
Here's an example of how this command looks for
the Accent SA speech synthesizer and the 2.4.22-2c.nptlspk2 Speakup Modified
Fedora Linux kernel:
List of 1 items
? /sbin/mkinitrd -v -f
/boot/initrd-2.4.22-2c.nptlspk2.img --with=speakup_acntsa
2.4.22-2c.nptlspk2
list end
Use your Speakup screen review commands to read
up the screen when this command completes. If you see references to your
speech synthesizer, you've correctly
completed this critical step in your
installation process.
Notice, also, how we used the TAB key to fill
out that long and complicated Linux kernel designation for us. Not only do
we save some typing by using TAB.
We also avoid critical errors. Remember
this trick. You can use it almost everywhere in Linux when issuing commands
and when specifying files. It's a very
handy feature that you'll never
outgrow.
Killing First Boot To Insure Speakup
Speaks
There is one more very critical step to perform
before you boot your installation. Be sure you are still in the restricted
view obtained by the first three
steps of the previous command when you
issue this last, very critical command:
List of 1
items
? /sbin/chkconfig --level 2345 firstboot off
list
end
If you fail to do this step you will find that
Speakup suddenly stops speaking just when it seems you've finished booting
your new installation of Linux.
That's because of the graphical (and
inaccessible) FirstBoot program Red Hat provides to help users define some
important configuration settings, such
as creating users and identifying
how this computer connects to the Internet. Unfortunately, FirstBoot
launches before any consoles launch, so there is
absolutely nothing you
can do as a blind user once FirstBoot is running either to work with
FirstBoot or to get out of it.
I couldn't even get that portion to
work
is there a easier way to fix this?
I all ready bootted the system
thanks
hank
Don't judge me because I'm blind. Judge me by
what's inside. if you judge me because I am blind, then it is you who is
blind.
"time is the fire in which we burn," Tollian Soran.
"grudges
aren't worth holding--One who holds them shows his
self-weakness."
Contact info:
hank@xxxxxxxxxxxxx
Email: Same as
MSN.
_______________________________________________
Blinux-list
mailing
list
Blinux-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/blinux-list