Date: Tue, 30 Apr 2002 23:59:58 -0300 (ADT) From: "Marc G. Fournier" <scrappy@hub.org> To: John Utz <john@utzweb.net> Cc: freebsd-stable@FreeBSD.ORG, <freebsd-multimedia@FreeBSD.ORG> Subject: Re: ASUS A7M266-D: enabling 'on board sound' Message-ID: <20020430235723.X15173-100000@mail1.hub.org> In-Reply-To: <Pine.LNX.4.44.0204231734330.30017-100000@jupiter.linuxengine.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 23 Apr 2002, John Utz wrote: > 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: <CMedia CMI8738> 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. that is kinda what I'm figuring too ... > 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. Actually, I thought about this, and one problem with this theory ... right now, I have both serial ports and the parallel port disabled, which should free up 3/4 and 5 (or is it 7?) ... if I re-enable them, they come up fine with their respective IRQs ;( > 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..... Will try this one tomorrow at the office ... > > > > 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-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020430235723.X15173-100000>