From: Whitley CTR Cecil H <WhitleyCH.ctr@cherrypoint.usmc.mil>
To: "'gentoo-accessibility@gentoo.org'"
<gentoo-accessibility@lists.gentoo.org>
Subject: [gentoo-accessibility] 2004.2 problem
Date: Thu, 2 Sep 2004 00:22:24 -0400 [thread overview]
Message-ID: <6D3A09C6CAB0D311BA5000902760D022040F2187@chpt0000se01.cherrypoint.usmc.mil> (raw)
[-- Attachment #1: Type: text/plain, Size: 2206 bytes --]
Hi,
I brought my external dectalk express home tonight to install 2004.2 on my
home system. I ran into a real problem, and I don't know what would be
really important in a bug report.
I have an Asus p4c800-e deluxe motherboard with p4 3.4 and an s-ata hd. I
also have an USB 2.0 external IDE drive bay with an ata-100 hd which shows
up as /dev/sda. All went well, booted with speech, mounted drives, etc.
Only problem, the onboard Intel CSA Gig-e network adapter wasn't fully
configured. When I ran net-setup the machine locked with no speech.
On-screen msg was
disabling interupt 17
n interrupt not disabled
Or something similar (working with a 13 year old).
I searched gentoo bugs for csa (no joy) and p4c800-e deluxe (joy, but only
for pnpbios).
It should be noted that I used the command line
smp speakup_synth=dectlk
So the smp enabled 2.6 kernel was loaded. Prior boot I had used
gentoo speakup_synth=dectlk
But the 2.4 kernel did not fully recognize/drive the onboard sound. Since I
was hoping to get software speech up and running the soundcard support is
critical. Also, the smp support for hyperthreading is a "nice to have". is
the driverr version listed is 5.x.x and the Asus site has an Intel 7.0.x
driver for linux for the CSA adapter. It also has an ALSA 0.9.6 soundmax
driver. The CSA driver is listed for RH 7.3, 8, 9 and SUSE 9.0, I assume
this is all 2.4.x kernels? I don't want to post a bug without fully vetting
the problem since I assume that since there is at least one posted/fixed bug
for the p4c800-e deluxe that someone else is using this board with no
problem now. The only question that is left is are they using the onboard
ethernet, and if so, is this a problem specific to having speakup or
optionally the serial port active? Guidance please? What can I do to
provide the most helpfull bug report with the most accurate problem
description I can come up with?
Thanks,
Cecil Whitley
P.s. Since I have the universal CD, should I try patching the
gentoo-dev-sources kernel with the driver from the Asus site? I presume
that I can get all of this built without networking, if my reading of the
install.txt is correct?
Now, what I have noticed
[-- Attachment #2: Type: text/html, Size: 3061 bytes --]
next reply other threads:[~2004-09-02 4:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 4:22 Whitley CTR Cecil H [this message]
2004-09-02 4:33 ` [gentoo-accessibility] 2004.2 problem Deedra Waters
-- strict thread matches above, loose matches on Subject: below --
2004-09-02 12:38 Whitley CTR Cecil H
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=6D3A09C6CAB0D311BA5000902760D022040F2187@chpt0000se01.cherrypoint.usmc.mil \
--to=whitleych.ctr@cherrypoint.usmc.mil \
--cc=gentoo-accessibility@lists.gentoo.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