From owner-freebsd-current Sun Jan 3 05:42:56 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA26846 for freebsd-current-outgoing; Sun, 3 Jan 1999 05:42:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wraith.uswest.net (adsla195.dnvr.uswest.net [209.180.248.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA26840 for ; Sun, 3 Jan 1999 05:42:55 -0800 (PST) (envelope-from tod.morrison@usa.net) Received: from usa.net (localhost.dnvr.uswest.net [127.0.0.1]) by wraith.uswest.net (8.9.1/8.9.1) with ESMTP id GAA08279 for ; Sun, 3 Jan 1999 06:43:19 -0700 (MST) (envelope-from tod.morrison@usa.net) Message-ID: <368F73F7.B2972F6D@usa.net> Date: Sun, 03 Jan 1999 06:43:19 -0700 From: Tod Morrison X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 CC: freebsd-current@FreeBSD.ORG Subject: Re: SoundBlaster 128 References: <199901030644.HAA26076@labinfo.iet.unipi.it> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The pcm driver works nicely, except for that the module doesn't register if there are not any isa devices (? - I don't really understand the problem, I just found a patch in the mailing list archives to fix it ). Actually, I wound up applying the changes by hand since the driver has evolved since the original posting of the patch. Tring to get my PCI128 to work nearly drove me insane till I found that post. "es1" and "pcm1" were showing up at boot, but /dev/sndstat etc... kept returning "device not configured". Tod Morrison Luigi Rizzo wrote: > > > I'm trying to get my soundblaster 128 working with 3.0-current, would > > anyone tell me if they have got it working? > > there "pcm" driver now in current should support it. > > luigi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message