From: "Rob Hudson" <captinlogic@gmail.com>
To: "Speakup List" <speakup@linux-speakup.org>
Subject: trying again, new talking arch and audio problems
Date: Wed, 14 Aug 2013 05:07:50 -0500 [thread overview]
Message-ID: <C36F83403C4A45A6ACA923FA9EE2B086@train> (raw)
Tried sending this to the list and got a message about it being too long, so here we are again. The exported errors are at a link which I will give below.
I put in the new TalkingArch cd. I heard yammering about choosing a sound card, listen
for the beep, blah blah, press any key, yack yack. All that went well, I heard a
beep and pressed enter twice. No espeak. I did
/bin/bash
speaker-test
heard the hiss, so alsa appeared to be working well. Fired up brltty
killall brltty
brltty -b al -d ttyS0
espeak "hello"
Saw a whole screen of errors, which I redirected to a text file.
pasted below. Not
knowing what was important and not, the whole thing is here.
Audio configuration is a sound blaster live card, and a disabled onboard audio sound
chip. It is this latter which I believe is causing the problem. Ok, scratch that, as of this new writing, even with the hcip re enabled, I still get the errors. Everything else seems to work except espeak.
What is happening here?
The link to the file with the errors is:
http://opopanax.net/speakup.txt
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Rob Hudson [this message]
` Kyle
` Rob Hudson
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=C36F83403C4A45A6ACA923FA9EE2B086@train \
--to=captinlogic@gmail.com \
--cc=speakup@linux-speakup.org \
/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).