From: "Jaap Struyk" <japie@deserver.nl>
To: alsa-devel@lists.sourceforge.net
Subject: Re: problems with via82xx alsa part
Date: Sun, 1 Oct 2006 16:58:22 +0000 (UTC) [thread overview]
Message-ID: <efos3e$g63$1@sea.gmane.org> (raw)
In-Reply-To: ef3pll$kng$1@sea.gmane.org
> ALSA lib pcm_direct.c:985:(snd_pcm_direct_initialize_slave) unable to install hw params
> ALSA lib pcm_dmix.c:876:(snd_pcm_dmix_open) unable to initialize slave
> aplay: main:550: audio open error: Ongepaste ioctl voor apparaat
>
> I'am using alsa-*-1.0.12 and kernel 2.6.18, I have two similar systems
I yust upgraded to alsa-1.0.13 (libs, tools, oss etc.) tryed another card
(ess1370) tryed another kernel but whatever I try still got the same
problems.
It's obvious it has something to do with that machine in particular but
what?
Is there someone who can tell me what I'am missing here here?
--
Greeting Japie
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-10-01 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 17:08 problems with via82xx alsa part Jaap Struyk
2006-10-01 16:58 ` Jaap Struyk [this message]
2006-10-04 17:50 ` Takashi Iwai
2006-10-06 8:02 ` Jaap Struyk
[not found] ` <1160121885.1790.2.camel@japie.deserver.nl>
2006-10-06 11:22 ` Takashi Iwai
[not found] ` <1160325289.2558.2.camel@japie.deserver.nl>
2006-10-09 18:59 ` Takashi Iwai
[not found] ` <1160499844.2449.5.camel@japie.deserver.nl>
2006-10-10 17:28 ` Takashi Iwai
2006-10-12 16:46 ` Jaap Struyk
2006-10-12 16:56 ` Takashi Iwai
2006-10-15 12:02 ` Jaap Struyk
2006-10-16 10:04 ` Takashi Iwai
2006-10-20 7:00 ` Jaap Struyk
2006-10-20 10:12 ` Takashi Iwai
2006-10-21 12:29 ` Jaap Struyk
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='efos3e$g63$1@sea.gmane.org' \
--to=japie@deserver.nl \
--cc=alsa-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.