From owner-freebsd-stable Tue Apr 23 15:41:15 2002 Delivered-To: freebsd-stable@freebsd.org Received: from jupiter.linuxengine.net (jupiter.linuxengine.net [209.61.188.254]) by hub.freebsd.org (Postfix) with ESMTP id 3015C37B41A; Tue, 23 Apr 2002 15:41:03 -0700 (PDT) Received: from jupiterweb.commercevault.com (jupiterweb.commercevault.com [209.61.179.16] (may be forged)) by jupiter.linuxengine.net (8.11.6/8.11.0) with ESMTP id g3NMewb13613; Tue, 23 Apr 2002 17:40:58 -0500 Date: Tue, 23 Apr 2002 17:40:58 -0500 (CDT) From: John Utz X-X-Sender: john@jupiter.linuxengine.net To: "Marc G. Fournier" Cc: freebsd-stable@FreeBSD.ORG, Subject: Re: ASUS A7M266-D: enabling 'on board sound' In-Reply-To: <20020423150218.O1721-100000@mail1.hub.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG huh, bet this might be an smp problem.... works like a champ on my ASUS board. On Tue, 23 Apr 2002, Marc G. Fournier wrote: > > Morning all ... > > Just recently picked up an ASUS A7M266-D Motherboard with Dual: > "(AMD Athlon(TM) MP Processor (1200.05-MHz 686-class CPU)" ... the system > purrs like the proverbial kitten ... but the one thing that is eluding me > so far is getting the onboard sound to work ... > > I think I've gone through just about everything ... I enabled > PNPBIOS in my kernel, made sure the sound device was enabled in the BIOS > ... nadda ... > > The error I'm seeing in dmesg is: > > pcm0: at device 4.0 on pci2 > pcm0: cmi_attach: Cannot allocate bus resource > device_probe_and_attach: pcm0 attach returned 6 this could be one of two things: 1. your version of the CMI8738 might have a new pnp number, but i sorta doubt it because then you wouldnt get the 'CMedia CMI8738' string. 2. All Your Interrupts Are Belong To Somebody Else! the extra bits of tomfoolery involved in getting a second cpu to live in an architecture than never imagined more than one (daisy chained 8259a's, still?) may have consumed the available interrupts. 3. Other, more reasonable, but more subtle problems that i cant imagine :-) I'd suggest the ol' boot -v and see what you get for a dmesg..... > I've tried manually setting in the kernel: > > > strings /kernel | grep pcm0 > pcm0_resources > ___device pcm0 at isa? irq 5 drq 1 flags 0x0 > > but that hasn't made any difference ... > > Anyone have any experience with this board, or this chipset, that > might be able to suggest a course of action here? > > thanks ... > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-multimedia" in the body of the message > -- John L. Utz III john@utzweb.net Idiocy is the Impulse Function in the Convolution of Life To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message