archive mirror
 help / color / mirror / Atom feed
From: Claas Langbehn <>
To: Takashi Iwai <>
Subject: Re: Kernel 2.6.0-test1-ac3: alsa snd_via82xx
Date: Mon, 28 Jul 2003 12:19:00 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hello Takashi!

Takashi Iwai wrote:
> > I figured out some strange behaviour of the alsa drivers in kernel
> > 2.6.0-test1-ac3. 
> > When compiling everything into the kernel (=y), I was not able to get
> > sound out of my machine at all. But with CONFIG_SND_VIA82XX=m it worked.
> > Isn't that strange?
> what do you mean exactly "no sound"?  you can play the file but no
> sounds come out, or playback is not operational?

I mean, that it looked all good, the driver seemed to be operational,
but I did not get any Sound out of it. I stress, that this only happened
when everything was compiled into the kernel. Therefore, I did not use
a special modprobe.conf or such.

Now that it works, I can try again to compile everyting into the kernel
to do a second check. I will do later today and let you know the

> did you set any module options for ALSA in /etc/modprobe.conf?
at first none, and now this:

	# This file was automatically generated by alsa-base's debconf stuff
	alias char-major-116 snd
	alias char-major-14 soundcore

	options snd major=116 cards_limit=4 device_mode=0660 device_gid=29 device_uid=0

	alias sound-service-0-0 snd-mixer-oss
	alias sound-service-0-1 snd-seq-oss
	alias sound-service-0-3 snd-pcm-oss
	alias sound-service-0-8 snd-seq-oss
	alias sound-service-0-12 snd-pcm-oss

	alias snd-card-0 snd-via82xx

	alias snd-slot-0 snd-card-0
	alias sound-slot-0 snd-slot-0

Regards, claas

  reply	other threads:[~2003-07-28 10:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-27  9:17 Kernel 2.6.0-test1-ac3: alsa snd_via82xx Claas Langbehn
2003-07-27 10:18 ` Stephane Wirtel
2003-07-27 10:40   ` Rahul Karnik
2003-07-28  9:39 ` Takashi Iwai
2003-07-28 10:19   ` Claas Langbehn [this message]
2003-07-28 10:45     ` Takashi Iwai
2003-07-28 20:38       ` Claas Langbehn

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).