From: "Ihar 'Philips' Filipau" <filia@softhome.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: USB Audio, Alsa & HK SoundSticks
Date: Tue, 02 Dec 2003 18:33:42 +0100 [thread overview]
Message-ID: <3FCCCCF6.4030302@softhome.net> (raw)
In-Reply-To: <s5had6be25h.wl@alsa2.suse.de>
Hi!
Takashi Iwai wrote:
>
> try ALSA 1.0.0rc1.
> if the usb driver is NOT usb-uhci, try async_unlink=1 option for
> snd-usb-audio. because usb-uhci has a bug in the async unlinking, the
> async-unlink mode is disabled as default for 2.4 kernels.
>
Half of an hour - works without problems.
Thanks.
[ I am using exactly usb-uhci. "Works For Me" (tm) without any
parameters. ]
[ I have spend more time to f*ck up RHL9 to load automatically alsa.
And bit more time to figure-out that RHL start-up scripts do screw
things up completely. gamix, alsamixer do work, but xmms fails to open
alsa's dsp. "rmmod snd*; modprobe sound-slot-0" in late start-up helped.
Need to upgrade my RHL9 to Debian...
Too old for this /desktop/ non-sense.
But still I am (as a device driver developer) trying to understand
how it is possible to screw something in module loading process so mixer
is here but dsp is not, while they are represented by the very same
module. ]
--
Ihar 'Philips' Filipau / with best regards from Saarbruecken.
-- _ _ _
Because the kernel depends on it existing. "init" |_|*|_|
literally _is_ special from a kernel standpoint, |_|_|*|
because its' the "reaper of zombies" (and, may I add, |*|*|*|
that would be a great name for a rock band).
-- Linus Torvalds
prev parent reply other threads:[~2003-12-02 17:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 10:27 USB Audio, Alsa & HK SoundSticks Ihar 'Philips' Filipau
2003-12-02 14:15 ` Takashi Iwai
2003-12-02 17:33 ` Ihar 'Philips' Filipau [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=3FCCCCF6.4030302@softhome.net \
--to=filia@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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