From: David Relson <relson@osagesoftware.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] SOLVED [ was: codec read/write errors ]
Date: Mon, 30 Jun 2008 19:35:32 -0400 [thread overview]
Message-ID: <20080630193532.6cf6a11b@osage.osagesoftware.com> (raw)
In-Reply-To: <20080629221320.GA20099@princeton.edu>
On Sun, 29 Jun 2008 18:13:20 -0400
Willie Wong wrote:
> On Sun, Jun 29, 2008 at 01:02:39PM -0400, Penguin Lover David Relson
> squawked:
> > Jun 29 12:53:02 fpc Failure writing to cs5535 codec
> > Jun 29 12:53:02 fpc Failure reading codec reg 0x7a,Last
> > value=0x7a800000
> >
> > I've got no idea why this started nor what software is responsible
> > for generating these messages.
> >
> > Any thoughts?
> >
>
> cs5535 seems to refer to the alsa audio driver
> the only thing software-wise that I can find with acronym fpc is the
> free pascal compiler... which I admit doesn't make much sense: why
> would a compiler care about writing to an audio driver?
>
> HTH,
>
> W
Hi Willie,
The box with the problem is named "fpc" which is why that string is in
the logging record.
The box is a fit-pc -- a nifty little low power gentoo machine I got a
few months ago. The cs5535 problem went away after I upgraded its
kernel from 2.6.20 to 2.6.24. I still don't know the actual cause of
the problem and (since it's gone) have stopped worrying.
Thanks for taking the time to search & help.
Regards,
David
--
gentoo-user@lists.gentoo.org mailing list
prev parent reply other threads:[~2008-06-30 23:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 17:02 [gentoo-user] codec read/write errors David Relson
2008-06-29 22:13 ` Willie Wong
2008-06-30 23:35 ` David Relson [this message]
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=20080630193532.6cf6a11b@osage.osagesoftware.com \
--to=relson@osagesoftware.com \
--cc=gentoo-user@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