public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Nick Gawronski" <nick@nickgawronski.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: now speakup won't speak on my fedora core 6 installation
Date: Thu, 5 Apr 2007 20:16:07 -0600	[thread overview]
Message-ID: <001a01c777f1$8c87c440$270110ac@CHIHUAHUAL1> (raw)
In-Reply-To: <20070402142140.GM26256@rednote.net>

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
> 



      reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Nick Gawronski
 ` Janina Sajka
   ` Nick Gawronski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='001a01c777f1$8c87c440$270110ac@CHIHUAHUAL1' \
    --to=nick@nickgawronski.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).