[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <s5hbq29et0k.wl%tiwai@suse.de>
Date: Tue, 10 Jun 2008 07:52:27 +0200
From: Takashi Iwai <tiwai@...e.de>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: 2.6.26-rc5-git2: snd-emu10k1 does not work
At Mon, 9 Jun 2008 22:45:01 +0200,
Rafael J. Wysocki wrote:
>
> On Monday, 9 of June 2008, Rafael J. Wysocki wrote:
> > On Monday, 9 of June 2008, Takashi Iwai wrote:
> > > At Sun, 8 Jun 2008 23:03:58 +0200,
> > > Rafael J. Wysocki wrote:
> > > >
> > > > Hi,
> > > >
> > > > snd-emu10k1 doesn't work on one of my test boxes. The driver apparently loads,
> > > > but the card is not visible, for example, to any mixer apps (including the ALSA
> > > > mixer). However, YaST correctly detects and reports the card (the system is
> > > > openSUSE 10.3, x86-64). The openSUSE-made kernel (2.6.22-something) does
> > > > correctly work on the same hardware.
> > > >
> > > > Is there anything I should pay attention to, like any options related to /proc
> > > > or sysfs that could have an effect on the audio adapter?
> > >
> > > First off, check /proc/asound/cards whether snd-emu10k1 driver is
> > > really loaded on the first slot. I guess something else occupies the
> > > position.
> >
> > This is quite possible, as there is an on-board audio in this box too and I'm
> > not sure if the setup switch really turns it off.
> >
> > > If yes, a simple solution is to add the following option for snd module:
> > >
> > > options snd slots=snd-emu10k1
> > >
> > > then the first slot is reserved for emu10k1. Note that this option is
> > > available for 2.6.25 or later kernel.
> >
> > I'll try later today and let you know.
>
> No, it didn't work.
>
> Here's what I got from /proc/asound/cards:
>
> 0 [Audigy ]: Audigy - Audigy 1 [SB0090]
> Audigy 1 [SB0090] (rev.3, serial:0x531102) at 0xa000, irq 17
> 1 [UART ]: MPU-401 UART - MPU-401 UART
> MPU-401 UART at 0x330, irq 10
>
> so I think this is correct, and the "options snd slots=snd-emu10k1" thing had
> no visible effect.
Then this must be OK. Then the remaining possible problems are:
- Device files and permissions.
Check whether /dev/snd/* files exist and have proper permissions and
ACL (see "getfacl /dev/snd/*")
- The default ALSA configuration is hijacked, e.g. via pulse plugin.
Try to remove /etc/asound-pulse.conf if present.
Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists