From: Kronos <kronos@kronoz.cjb.net>
To: linux-kernel@vger.kernel.org
Cc: perex@suse.cz
Subject: [2.6.0-test6] Troubles with ALSA via82xx
Date: Mon, 29 Sep 2003 19:04:37 +0200 [thread overview]
Message-ID: <20030929170437.GA805@dreamland.darkstar.lan> (raw)
Hi,
I have trouble with linux-2.6.0-test6 and via82xx. With default
parameters I'm unable to play sound. I've tracked down the problem to
this change:
- use dxs_support=3 (48k fixed) as default, since there are so many
problems with dxs_support=0.
Loading module I see this:
via82xx: Assuming DXS channels with 48k fixed sample rate.
Please try dxs_support=1 option and report if it works on your machine.
PCI: Setting latency timer of device 0000:00:11.5 to 64
and when I try to play anything the player locks and I see the
following messages:
ALSA sound/core/pcm_lib.c:2156: playback write error (DMA or IRQ trouble?)
ALSA sound/core/pcm_lib.c:2156: playback write error (DMA or IRQ trouble?)
ALSA sound/core/pcm_lib.c:2156: playback write error (DMA or IRQ trouble?)
dxs_support=1 doesn't help since I have a VT8233A. dxs_support=2 is ok.
Looking at the code I see that VT8233A (without dsx) and VT8233 (with
dsx) are selected using dxs_support parameter. Is this the only way to
do it? 2.6.0-t5 worked for me, not sure that this is a bug but at least
it's a regression.
This is my audio device:
00:11.5 Class 0401: 1106:3059 (rev 40)
Subsystem: 1695:3004
Flags: medium devsel, IRQ 5
I/O ports at e000 [size=256]
Capabilities: [c0] Power Management version 2
Luca
--
Reply-To: kronos@kronoz.cjb.net
Home: http://kronoz.cjb.net
Let me make your mind, leave yourself behind
Be not afraid
next reply other threads:[~2003-09-29 17:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-29 17:04 Kronos [this message]
2003-09-30 10:06 ` Takashi Iwai
2003-09-30 14:27 ` Kronos
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=20030929170437.GA805@dreamland.darkstar.lan \
--to=kronos@kronoz.cjb.net \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@suse.cz \
/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
all inboxes | Powered by JetHome®