From: Tino Keitel <tino.keitel@gmx.de>
To: Lee Revell <rlrevell@joe-job.com>, linux-kernel@vger.kernel.org
Subject: Re: No Coax digital out with SB Live! and 2.6.15
Date: Fri, 6 Jan 2006 10:49:38 +0100 [thread overview]
Message-ID: <20060106094938.GA8091@localhost.localdomain> (raw)
In-Reply-To: <20060106000921.GA4867@localhost.localdomain>
On Fri, Jan 06, 2006 at 01:09:21 +0100, Tino Keitel wrote:
[...]
> I booted with the 2.6.15 driver and got a silent digital out, like
> reported. The headphone which is plugged into the analog output gives
> sound.
>
> If I load the 1.0.10 driver, sound works in xmms. If I unload it and
> reload the original 2.6.15 driver, sound still works. If I reboot with
> the original 2.6.15 driver, the digital out is silent again, while the
> analog output works.
>
> However, if I now chose a specific output device in xmms, hw:0,2,
> instead of the default device, digital out gives sound. With the 1.0.10
> driver, this hw:0,2 device stays completely silent (digital and
> analog). With this version, the hw:0,0 device (which seems to be the
> default) gives analog and digital sound.
The solution looks more simple: just removing and reloading the
original snd-emu10k1 module reorders the devices so that the default
device gives sound on the digital output. The driver is blacklisted in
udev and loaded at boot time in /etc/modules, so the module-init-tools
initscript will load them. However, I have no idea why it behaves
different if loaded at boot time than when reloaded later.
Regards,
Tino
prev parent reply other threads:[~2006-01-06 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 18:08 No Coax digital out with SB Live! and 2.6.15 Tino Keitel
2006-01-04 7:26 ` Tino Keitel
2006-01-04 7:36 ` Tino Keitel
2006-01-05 22:01 ` Lee Revell
2006-01-06 0:09 ` Tino Keitel
2006-01-06 9:49 ` Tino Keitel [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=20060106094938.GA8091@localhost.localdomain \
--to=tino.keitel@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
/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