From: Tomas Pospisek's Mailing Lists <tpo2@sourcepole.ch>
To: alsa-devel@alsa-project.org
Subject: No state is present for card CMI8738
Date: Wed, 16 May 2007 00:28:02 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705160024160.13010@localhost> (raw)
Since alsa-user is rather ... errr ... silent, I dare to repost the same
question here.
I've seen that Alsa likes the Terratec cards, however since they're also
based on the CMI chipset, and at least /my/ onboard CMI chipset here sucks
badly I wonder what low cost card I can use?
I hope somebody can give me a clue,
*t
PS: Mic input is barely loud enough with my onboard sound. Mic boost has
no effect.
--
-----------------------------------------------------------
Tomas Pospisek
http://sourcepole.com - Linux & Open Source Solutions
-----------------------------------------------------------
---------- Forwarded message ----------
Date: Mon, 14 May 2007 14:39:36 +0200 (CEST)
From: Tomas Pospisek's Mailing Lists <tpo2@sourcepole.ch>
To: alsa-user@lists.sourceforge.net
Subject: [Alsa-user] No state is present for card CMI8738
The following is my problem:
$ alsactl -f .alsavoip restore
No state is present for card CMI8738
I see this "sometimes". Sometimes the above works and sometimes it returns
with that error message.
It needs to be noted that I am suspending to ram. Nevertheless, the
behaveour is not consistent in between "s2ram"s and I don't know whether
that has anything to do with it either.
It also needs to be noted that alsamixer *never* has any problems
accessing the card. But even after changing the card settings with
alsamixer, alsactl will keep on repeating that error message.
* $ lspci
00:0d.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10)
* alsa userspace is at 1.0.13
* kernel is Debian's 2.6.18-4-686
Further, minor problems:
* After waking up from suspend the card looses its microphone settings -
that is - "Mic Capture" is allway reset to zero.
* Further on the choice to hide the microphone setting "Mic Capture" in
alsamixer behind F5 irritates me a bit - there are *a lot* of very
obscure settings (such as "IEC958 5V" - huh?), that are displayed by
default.
What's up with that error above? What does it mean? Is there any
way I can fix or circumvent it? Anybody a hint?
*t
--
-----------------------------------------------------------
Tomas Pospisek
http://sourcepole.com - Linux & Open Source Solutions
-----------------------------------------------------------
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user
next reply other threads:[~2007-05-15 22:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-15 22:28 Tomas Pospisek's Mailing Lists [this message]
2007-05-18 14:42 ` No state is present for card CMI8738 Tomas Pospisek's Mailing Lists
2007-05-21 16:05 ` Takashi Iwai
2007-05-22 21:02 ` [patch] " Tomas Pospisek's Mailing Lists
2007-05-23 10:09 ` Takashi Iwai
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.64.0705160024160.13010@localhost \
--to=tpo2@sourcepole.ch \
--cc=alsa-devel@alsa-project.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 NNTP newsgroup(s).