now speakup won't speak on my fedora core 6 installation

now speakup won't speak on my fedora core 6 installation

[Nick Gawronski]

Hi, I have added the following lines to /boot/grub/menu.lst

title           fedora core 6
root            (hd0,2)
kernel /boot/vmlinuz-2.6.20-1.2933.fc6spk
initrd  /boot/initrd-2.6.20-1.2933.fc6spk.img
savedefault
When I upgraded the kernel from downloading the rpms from
speakupmodified.org using ftp in binary mode and installing the kernel,
kernel-doc and the kernel-headers after removing the old kernel.  I then
rebuilt the initrd image as explained in the how to.  I am able to login
as root to my fedora core 6 system and even if I do modprobe
speakup_dectlk I get no speech and hear no beep when pressing back space
as I hear before issuing the modprobe command.  So far to work on my
fedora core 6 system I have just been mounting it in /mnt on my debian
etch system and then using chroot to set the root directory to the mounted
directory.  What can I do to tell the scripts that build the initrd when a
new kernel is installed to build speakup with the dectalk express module
so I won't need to rebuild it each time I install a new kernel?  Sorry for
all of these issues but I just don't know where else to look as this is
the largest source of speakup users so I am not trying to bother anyone
here with my questions, just need a little help starting out with fedora
core 6.

Re: now speakup won't speak on my fedora core 6 installation

[Janina Sajka]

Nick Gawronski writes:
> Hi, I have added the following lines to /boot/grub/menu.lst
> 
> title           fedora core 6
f you want grub to beep, stick a ctrl-g in there, perhaps before the 'F'
in Fedora.

> When I upgraded the kernel
Suggest you do install for kernels and not upgrade. That way you will
still have the older, presumably working kernel until you establish the
new one is OK. You can always 'rpm -e' the old kernel once you know the
new one is good.


> I am able to login
> as root to my fedora core 6 system and even if I do modprobe
> speakup_dectlk I get no speech and hear no beep when pressing back space

With Speakup built into the initrd you should have had speech through
the entire boot process, but I have seen this sometimes not working over
the past half year or so.
It has sometimes been bad enough for me that I've had to reseat my RS232
connector and power cycle both computer and external synth. Go
figure.

I presume you're issuing the modprobe natively on the console? And not
over ssh?

PS: I'm currently on the same kernel as you, but with a Doubletalk.

Janina

Re: now speakup won't speak on my fedora core 6 installation

[Nick Gawronski]

Hi, I uninstalled the kernel and did an install when installing the kernel. 
Is there any point in downloading the source rpm for the kernel and 
recompiling it?  I installed the rpm like it says on the speakupmodified.org 
site to keep my fedora kernels with speakup up to date.  After installing 
this rpm should I remove the exclude lines from /etc/yum.conf or leave them 
in?
----- Original Message ----- 
From: "Janina Sajka" <janina@rednote.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Monday, April 02, 2007 8:21 AM
Subject: Re: now speakup won't speak on my fedora core 6 installation


> Nick Gawronski writes:
>> Hi, I have added the following lines to /boot/grub/menu.lst
>>
>> title           fedora core 6
> f you want grub to beep, stick a ctrl-g in there, perhaps before the 'F'
> in Fedora.
>
>> When I upgraded the kernel
> Suggest you do install for kernels and not upgrade. That way you will
> still have the older, presumably working kernel until you establish the
> new one is OK. You can always 'rpm -e' the old kernel once you know the
> new one is good.
>
>
>> I am able to login
>> as root to my fedora core 6 system and even if I do modprobe
>> speakup_dectlk I get no speech and hear no beep when pressing back space
>
> With Speakup built into the initrd you should have had speech through
> the entire boot process, but I have seen this sometimes not working over
> the past half year or so.
> It has sometimes been bad enough for me that I've had to reseat my RS232
> connector and power cycle both computer and external synth. Go
> figure.
>
> I presume you're issuing the modprobe natively on the console? And not
> over ssh?
>
> PS: I'm currently on the same kernel as you, but with a Doubletalk.
>
> Janina
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>