public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
* slackware can't install
@  cody
   ` Gregory Nowak
                   ` (2 more replies)
  0 siblings, 3 replies; 35+ messages in thread
From: cody @  UTC (permalink / raw)
  To: speakup

Hi all.

  I'm not having too much luck with this braillenote or this double talk. I read the speakup installation guide and did exactly to the word what it said. so I stuck the slackware cd inand booted and when it stopped I typed

speakup.i speakup_synth=ltlk

and pressed enter and got no speech. I downloaded and burned the slackware 10.0 d1 iso image and burned it, is it that 10.0 doesn't have speakup included or does that have the 2.6.22 kernel which is broeken with speakup? People give me a clue here google has beenn nothing but a pain for research and can't find any answers. What I need is a list of distros that have brltty and speakup support and a list of boot commands. It's driving me absolutely crazy not being able to get anythigng to work and everyone else is working fine.

Cody

^ permalink raw reply	[flat|nested] 35+ messages in thread
* re: slackware can't install
@  Jude DaShiell
   ` Adam Myrow
   ` cody
  0 siblings, 2 replies; 35+ messages in thread
From: Jude DaShiell @  UTC (permalink / raw)
  To: speakup

Because the speakup.i kernel was removed.  It used to be there at one 
time.  I think a determination was made that the speakup.s kernel would 
work for ide disks too and that freed up some space on the CD for other 
software. One note that should maybe be added to the speakup documentation 
for slackware is about swap partitions needing to be twice the ram size 
that's on a computer.  With slackware, it's possible to create a swap 
partition first then create the remaining partitions after that.  A note 
about shadowconfig on might help some, and a note about slapt-get could go 
a little way towards helping new users keep up with new updates.  None of 
this stuff is mentioned by Patrick in the welcome message.  The hosts.deny 
and hosts.allow files would be another good topic to cover even if all 
that's done is to suggest new installers read their man pages.



^ permalink raw reply	[flat|nested] 35+ messages in thread
* Slackware can't install
@  Gaijin
   ` Gregory Nowak
  0 siblings, 1 reply; 35+ messages in thread
From: Gaijin @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

[-- Attachment #1: Slackware can't install.eml.txt --]
[-- Type: text/plain, Size: 2011 bytes --]

> I stand to be corrected, not having used slackware in a while, but I
> think you'll find that the cd/dvd-rom drive is still detected under
> slackware as /dev/hdx, so the ide-scsi emulation isn't why speakup is
> in the speakup.s, rather than speakup.i kernel, 

    Hmmm.  I don't remember where, but I heard they were using SCSI 
emulation for DVD-RW drives because some other program wanted some 
hard drive attention at the same time, and messed up the DVD.  The IDE 
module is still being used, but it's being filtered through the SCSI 
module, or something.  I didn't fully gather how things were being 
handled; just that they're now using SCSI for CD/DVD writing.  Maybe on 
the Slackware bug mailing list, because I do very little web surfing.  
I don't remember.  I knew they'd compiled everything into a single 
kernal for speakup, though.  Cory will have no problem with IDE 
modules, anyway, and I hope I spelt their name right.

> Well, since we're ranting, can you please either turn on line wrap in
> your mail client, or remember to hit the enter key once in a while? 

    Sorry about that.  Can't see it. <laughs>  As it is, I'm using NVDA 
with Thunderbird, and they don't work well together.  I have to save 
the email to a text file, quote everything manually, editting it with 
notepad, and send the text file as an attachment.  I can't even 
do an actual reply, as I can't read the stewpid HTML pass-through 
buffer to see what I've written, deleted, etc., so have to post 
everything as new messages.  Word wrap *is* on in notepad, anyway.  
I'll try ending every line with a carriage return though.  Thanks for 
the heads-up on it.  
    Best thing about ranting is someone else always points out what 
you're doing wrong, too.  At least 99% of the time, anyway. <laughs>  
Yanno if this doesn't work, I'm gonna have to edit things from Linux, 
right? <grins>  Lemme know how this one looks, because it's hard to 
tell how many characters notepad is using per line.

        Michael

^ permalink raw reply	[flat|nested] 35+ messages in thread
* Slackware can't install
@  Gaijin
   ` Gregory Nowak
  0 siblings, 1 reply; 35+ messages in thread
From: Gaijin @  UTC (permalink / raw)
  To: Speakup is a screen review system for Linux.

[-- Attachment #1: Type: text/plain, Size: 1 bytes --]



[-- Attachment #2: slackware can't install.eml.txt --]
[-- Type: text/plain, Size: 2004 bytes --]

On 
Sat, 25 Aug 2007, cody wrote:

> > what I don't get is why I have to type .s rather than .i, because my drives
> > are ide, not scsi as mentioned in the instructions, and am not even sure why
> > that has anything to do with the price of meat to begin with..

    Speakup was compiled into the SCSI kernal for two reasons.  1) It saves space on the installation CD-ROMs, and 2) Today's CD/DVD-RW drives are being run under SCSI emulation to prevent crashing and/or disk-write errors when the system is overly busy, which is a common occurance on IDE setups.  This is because, unlike IDE, SCSI can actually do more than one disk-write at the same time.  They're even trying this method in Mickey...er. Microsoft Windows so DVDs can get properly written once in a while.

    Anyway, they haven't updated the speakup installation instructions yet to reflect the new practice.  The speakup.i kernal won't be found on the install CD.  I've looked, since it's a common practice to put installation instructions on the install CD, in just about every distro out there, and the speakup readme file was written for Slackware v8 or something.  Once you have the sucker installed, edit your /etc/lilo.conf file, looking for a line saying:

append=

...and edit it to say:

append="speakup_synth=dtlk"

...and run lilo to reflect the change.  That way you won't have to type the thing in every time you boot the computer.

PS: I wish some of you guys would edit your replies and remove .the 50-odd messages. posted in their entirety,  following the two cents that you've added.  It's very frustrating having to listen to it all over again for no reason, especially threads like this one, which have four or more long replies being reposted over and over again.  Sorry for the rant.

PPS: Has anyone heard of plans to make quoted text in emails be spoken in alternate voices?  It sure would be nice to have quoted text sound different than the reply text.  Maybe a python script in JAWS?  TIA,

        Michael


^ permalink raw reply	[flat|nested] 35+ messages in thread
end of thread, other threads:[~ UTC | newest]

Thread overview: 35+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
 slackware can't install cody
 ` Gregory Nowak
   ` cody
 ` Chris Norman
   ` cody
 ` dan Murphy
   ` Steve Holmes
     ` cody
       ` Gregory Nowak
         ` Katie Durden
           ` cody
             ` Katie Durden
               ` cody
                 ` Katie Durden
         ` cody
           ` Gregory Nowak
   ` cody
     ` dan Murphy
  -- strict thread matches above, loose matches on Subject: below --
 Jude DaShiell
 ` Adam Myrow
   ` Katie Durden
 ` cody
   ` Katie Durden
     ` cody
       ` Katie Durden
 Slackware " Gaijin
 ` Gregory Nowak
   ` Gaijin
     ` Doug Sutherland
       ` Gaijin
         ` Igor Gueths
   ` Katie Durden
     ` Gaijin
 Gaijin
 ` Gregory Nowak

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).