From owner-freebsd-questions Mon Aug 16 10:15:21 1999 Delivered-To: freebsd-questions@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 481D2154AF for ; Mon, 16 Aug 1999 10:15:15 -0700 (PDT) (envelope-from kee@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA27841; Mon, 16 Aug 1999 13:14:49 -0400 (EDT) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id NAA06703; Mon, 16 Aug 1999 13:14:47 -0400 (EDT) Received: from localhost (kee@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA06699; Mon, 16 Aug 1999 13:14:47 -0400 (EDT) X-Authentication-Warning: rac3.wam.umd.edu: kee owned process doing -bs Date: Mon, 16 Aug 1999 13:14:47 -0400 (EDT) From: Byoung-Kee Yi To: freebsd-questions@FreeBSD.org Cc: kee@wam.umd.edu Subject: Re: [Q] sb pro sound card problem in R3.2 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi - In regard to my previous question, I would like to add what I found afterwards. It seems that a kernel option "CONFIG_SBPRO" is needed. I added the following line in my kernel config file: options CONFIG_SBPRO "config" denied the option, but it worked - at least it fixed the starange "NOTE! blah blah..." message in `dmesg` and lacking mixer in `cat /dev/sndstat`. However, the "... IRQ/DRQ config error?" keeps coming out when I execute mpg123. I traced back the source location of the message, and it was "/sys/i386/isa/sound/dmabuf.c" as exerpted below. ....skip.... 501 /* XXX note -- nobody seems to set the mode to WK_TIMEOUT - lr */ 502 if ((in_sleep_flag[dev].mode & WK_TIMEOUT)) { 503 /* XXX hey, we are in splhigh here ? lr 970705 */ 504 printf("Sound: DMA (input) timed out - IRQ/DRQ config error? \n"); 505 err = EIO; ....skip.... According to the comments, something is going on here. By comparing the sources with those of R2.2.7, it seems that a significant overhaul was carried out and left some bugs. Cheers! -- Kee PS: again, please cc your reply to "kee@wam.umd.edu". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message