From: Effortless Union with the Divine <omeron@earthlink.net>
To: speakup@braille.uwo.ca
Subject: Hello.
Date: Mon, 29 Mar 2004 13:40:53 -0500 [thread overview]
Message-ID: <20040329184053.GF440@goodvibes> (raw)
Hi, hopefully this works, still getting the kinks worked out of this
Debian system. Speakup has presented a whole new world of opportunity to
the blind, and it feels excited to become involved with it. A few things
imediately noticed: Debian installation media needs updating. The reiser
disk doesn't work, and for the part where the installer needs to copy
the installation media, you need to use the regular root disk as opposed
to the speakup-enabled one. After getting the system installed OK, an
annoying bios problem tripped us up for a while, totally unrelated to
speakup of course, but just for note if anyone haas two drives, and lilo
just won't even load (use the serial option to hear it), a bug in the
bios may reverse the drive letters. For a stop-gap solution you can use
the swap and drive directives (read up on them) in the lilo.conf. Lilo
will complain bitterly, so you will have to get a sighted friend go into
the bios and disable the second hard drive. Also, maybe disabling the
hardware jumper on the second drive.
Back to the intallation, which went OK after that. Now some speakup
problems:
using an Artic Transport.
The rate, vol, and pitch parameters don't seem to take imediate effect.
Putting them in the append line of lilo.conf with the speakup_ser and
speakup_synth parameters wich do work, doesn't. Putting them in
~/.bash_profile doesn't work when logging in, though it does copy the
correct values to the /proc/speakup files, it only takes effect when
rerunning the .bash_profile. Strangeness. Anyone have any ideas?
Oh yes and that brings up the next question. This system ahas the
awesomely enabling speakup-2.4.24 kernel image, from the Debian testing
branch. Some posts refer to a new version of speakup, 2.0, available
through cvs. Would anyone have any recommendations as to staying with
the current setup, or getting cvs working, getting the new source, and
making a custom kernel, which this would require, true?
Thanks for any help anyone can give. Speakup rocks. One post said 2.0
allows easier reassigning of keys. Speaking of, where does debian keep
that? Oh also, sometimes when reading the screen, it won't print a new
line of text. Oh and it read the string
-rwx--x--x as a single - "dash".
and some cursor tracking would come in handy, say in lynx for arrowing
to a link on which to hit d.
Seeya.
--
Currently playing: Koxbox
Good Vibes Radio: http://clearwhitelight.org/goodvibes
Omeron - Effortless Union with the Divine
next reply other threads:[~ UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
Effortless Union with the Divine [this message]
-- strict thread matches above, loose matches on Subject: below --
Hello KatolaZ
` Hello Parham Doustdar
` Hello KatolaZ
` Hello Jude DaShiell
` Hello KatolaZ
` Hello Jude DaShiell
` Hello KatolaZ
` Hello John G Heim
` Hello Gregory Nowak
` Hello John G Heim
` Hello KatolaZ
` Hello Gregory Nowak
` Hello Zachary Kline
` Hello Gregory Nowak
` Hello John G Heim
` Hello covici
` Hello Gregory Nowak
` Hello John G Heim
` Hello KatolaZ
` Hello John G Heim
` Hello Rob
` Hello KatolaZ
` Hello covici
` Hello John G Heim
` Hello KatolaZ
Hello William Rivera
` Hello Albert E. Sten-Clanton
` Hello Gaijin
` Hello William Rivera
` Hello VaShaun Jones
` Hello Frank Carmickle
` Hello Gaijin
` Hello VaShaun Jones
` Hello Mike Reiser
` Hello VaShaun Jones
` Hello John Heim
` Hello VaShaun Jones
` Hello VaShaun Jones
` Hello Mike Reiser
` Hello VaShaun Jones
` Hello Alex Snow
` Hello VaShaun Jones
Hello Parham
hello Jude DaShiell
hello tony seth
hello Jude DaShiell
` hello Doug Sutherland
` hello Alex Snow
hello Jude DaShiell
` hello Jim Grimsby Jr.
` hello Glenn Ervin
` hello Sina Bahram
` hello Gaijin
hello Jude DaShiell
Hello Gaijin
` Hello Cody Hurst
` Hello Gaijin
` Hello Littlefield, Tyler
` Hello ace
` Hello Gaijin
` Hello Gregory Nowak
` Hello Gaijin
` Hello Hermann
` Hello Littlefield, Tyler
` Hello Glenn Ervin
` Hello Doug Sutherland
` Hello Gaijin
` Hello Doug Sutherland
` Hello Gaijin
` Hello Doug Sutherland
` Hello Gaijin
` Hello Gregory Nowak
` Hello Doug Sutherland
` Hello Gaijin
` Hello Doug Sutherland
` Hello Alex Snow
` Hello Gregory Nowak
` Hello Jim Grimsby Jr.
` Hello Steve Holmes
` Hello Albert E. Sten-Clanton
` Hello ace
` Hello Littlefield, Tyler
` Hello Gaijin
` Hello Cody Hurst
hello Juan Hernandez
[not found] <PMEKJADADDDBJODCLJIHAEDOCLAA.erick@ekosten.dynip.com>
` hello Janina Sajka
Hello Ryan Mcmanomy
` Hello Erik Heil
` Hello Edward L. Barnes
` Hello Gregory Nowak
hello Pete
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=20040329184053.GF440@goodvibes \
--to=omeron@earthlink.net \
--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).