From: Brian W <icu4real@mchsi.com>
To: speakup@braille.uwo.ca
Subject: sound card and Gnome
Date: Sun, 2 May 2004 16:00:00 -0500 (CDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0405021534550.4500-100000@localhost.localdomain> (raw)
Hello,
I recently started with Linux - Fedora Core 1, and with help from Bill, I
am up and running with Speakup. After the installation, I ran sndconfig
and had sound working, but now it has stopped working.
In the interim I have installed Pine, updated to the latest version of
Brltty, and poked around in Gnome - this last with sighted help that is no
longer available. I also ran the yum update utility. I have not
configured Brltty yet.
I think the problem is with a change I made in Gnome, but am too new to
Linux to be sure of much of anything.)
We enabled the sound server in the
preferences. (I think that is what they called it at least.) I was trying
to find information on configuring gnopernicus, and in
frustration at finding only reference materials, but no step by step
information, I was just poking around to see what I could break or make
work by accident.
Well the only thing I have accomplished is to break the sound in the
console, where it used to work.
I have disabled the graphical boot to see if there are any errors, but
there are not. I intend to change the default boot so it does not boot up
into Gnome, but I do not know if that will help.
I use Speakup with a DEC Talk Express.
Any suggestions would be welcome.
(Well, most any suggestions...)
I should add that while I am new to Linux, I am not new to computers.
Unfortunately perhaps, the way I learn is by trial and error. once I break
it, I struggle until I fix it, and usually learn something in the process.
Brian
next reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Brian W [this message]
` Janina Sajka
` Brian W
` Kenny Hitt
` Brian W
` Stephen Clower
` Kenny Hitt
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=Pine.LNX.4.44.0405021534550.4500-100000@localhost.localdomain \
--to=icu4real@mchsi.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).