From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932252AbVLVLfx (ORCPT ); Thu, 22 Dec 2005 06:35:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932257AbVLVLfx (ORCPT ); Thu, 22 Dec 2005 06:35:53 -0500 Received: from mx2.suse.de ([195.135.220.15]:36510 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S932252AbVLVLfw (ORCPT ); Thu, 22 Dec 2005 06:35:52 -0500 Date: Thu, 22 Dec 2005 12:39:07 +0100 Message-ID: From: Takashi Iwai To: Adrian Bunk Cc: Linus Torvalds , Sergey Vlasov , Ricardo Cerqueira , mchehab@brturbo.com.br, Linux Kernel Mailing List , video4linux-list@redhat.com, perex@suse.cz, alsa-devel@alsa-project.org Subject: Re: [Alsa-devel] 2.6.15-rc6: boot failure in saa7134-alsa.c In-Reply-To: <20051221224025.GC3917@stusta.de> References: <20051220131810.GB6789@stusta.de> <20051220155216.GA19797@master.mivlgu.local> <20051220191412.GA4578@stusta.de> <20051220202325.GA3850@stusta.de> <20051221182214.GB3888@stusta.de> <20051221224025.GC3917@stusta.de> User-Agent: Wanderlust/2.12.0 (Your Wildest Dreams) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (=?ISO-8859-4?Q?Sanj=F2?=) APEL/10.6 MULE XEmacs/21.5 (beta21) (corn) (+CVS-20050720) (i386-suse-linux) MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org At Wed, 21 Dec 2005 23:40:25 +0100, Adrian Bunk wrote: > > On Wed, Dec 21, 2005 at 07:38:39PM +0100, Takashi Iwai wrote: > > At Wed, 21 Dec 2005 19:22:14 +0100, > > Adrian Bunk wrote: > > > > > > On Wed, Dec 21, 2005 at 03:23:09PM +0100, Takashi Iwai wrote: > > > > At Tue, 20 Dec 2005 21:23:25 +0100, > > > > Adrian Bunk wrote: > > > > > > > > > > On Tue, Dec 20, 2005 at 11:59:20AM -0800, Linus Torvalds wrote: > > > > > > > > > > > > > > > > > > On Tue, 20 Dec 2005, Adrian Bunk wrote: > > > > > > > > > > > > > > > Adrian, does it work if you change the "module_init()" in > > > > > > > > sound/sound_core.c into a "fs_initcall()"? > > > > > > > > > > > > > > No, this didn't work. > > > > > > > > > > > > > > What did work was to leave sound/sound_core.c alone > > > > > > > > > > > > Can you do try the other way again, with sound/core/sound.c fixed too? > > > > > >... > > > > > > > > > > This works in the sense that the kernel boots and my saa7134 TV card is > > > > > giving both audio and video output. > > > > > > > > > > But the non-saa7134 access to my soundcard (e.g. rexima or xmms) is no > > > > > longer working. > > > > > > > > What is missing there? No sound card entry in /proc/asound/cards? > > > >... > > > > > > <-- snip --> > > > > > > 0 [SAA7134 ]: SAA7134 - SAA7134 > > > saa7134[0] at 0xed800000 irq 18 > > > 1 [V8237 ]: VIA8237 - VIA 8237 > > > VIA 8237 with AD1888 at 0xe000, irq 21 > > > > > > <-- snip --> > > > > > > What changed compared to the working setup (if the bug is really here) > > > is the order of the two. > > > > Well, that's not anyway guaranteed unless you pass the proper index > > options. > > I'm not sure whether this is really related to my problem: > > No matter how they are ordered, shouldn't my soundcard still be > accessible from xmms or rexima? Yes, it is. You could have accessed to the secondary card from audio apps. In the case of ALSA, it's accessed via "default:1". For OSS, via /dev/dsp1. > > In the case above, snd_via82xx.index=0 saa7134.index=1 should work. > > This results in my soundcard being no longer available: > > <-- snip --> > > ... > Unknown boot option `saa7134.index=1': ignoring Sorry, it should be "saa7134_alsa.index=1", of course. > ... > cannot find the slot for index 0 (range 0-0) > VIA 82xx Audio: probe of 0000:00:11.5 failed with error -12 > ALSA device list: > #0: saa7134[0] at 0xed800000 irq 18 > NET: Registered protocol family 2 > ... > > <-- snip --> > > But as said above, I don't suspect the order of the devices being the > problem. I'm sure it is. The above shows simply confliction of indices. > > Or you may tune with udev, too. > > -ENOUDEV Still you can remap the device files manually as you like :) Takashi