Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-accessibility
Lists: gentoo-accessibility: < Prev By Thread Next > < Prev By Date Next >
To: "'gentoo-accessibility@g.o'" <gentoo-accessibility@g.o>
From: Whitley CTR Cecil H <WhitleyCH.ctr@...>
Subject: p4c800-e problems
Date: Fri, 3 Sep 2004 13:51:35 -0400
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2653.12">
<TITLE>p4c800-e problems</TITLE>

<P><FONT SIZE=2 FACE="Arial">Hi,</FONT>
<BR><FONT SIZE=2 FACE="Arial">BTW I worked around the issues so far by booting with the 2.4.x kernel (gentoo speakup_synth=dectlk).&nbsp; I don't have soundcard support, but i'll be building a 2.6 kernel (gentoo-dev-sources) and hopefully will be able to work around the network issues, or I may need to go to a vanilla-2.6 kernel and go with latest sources from; p4c800-e issues are know to the kernel development community and patches were submitted but not in 2.6.8rc2.&nbsp; Deedra, i've passed this along to John Davis, thanks for forwarding my original email to the list to him.&nbsp; This appears to be a reoccurance of bug id 42345, but the jury is still out on that.&nbsp; </FONT></P>

<P><FONT SIZE=2 FACE="Arial">If it ends up that I need to go with a vanilla kernel, I am sure that I will be writing this list for any assistance that can be offered.&nbsp; </FONT></P>

<P><FONT SIZE=2 FACE="Arial">Regards,</FONT>
<BR><FONT SIZE=2 FACE="Arial">Cecil</FONT>

Lists: gentoo-accessibility: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
RE: 2004.2 problem
Next by thread:
Software speech
Previous by date:
RE: 2004.2 problem
Next by date:
Software speech

Updated Jun 17, 2009

Summary: Archive of the gentoo-accessibility mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.