From owner-freebsd-current Thu Dec 2 9: 3:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from timbuk.cray.com (timbuk-fddi.cray.com [128.162.8.102]) by hub.freebsd.org (Postfix) with ESMTP id 336EC14E06; Thu, 2 Dec 1999 09:03:21 -0800 (PST) (envelope-from cattelan@thebarn.com) Received: from clink.americas.sgi.com (clink.cray.com [128.162.84.70]) by timbuk.cray.com (8.8.8/CRI-gate-news-1.3) with ESMTP id LAA04954; Thu, 2 Dec 1999 11:03:09 -0600 (CST) Received: from thebarn.com (localhost [127.0.0.1]) by clink.americas.sgi.com (980427.SGI.8.8.8/CRI-news-1.3) with ESMTP id LAA64959; Thu, 2 Dec 1999 11:03:07 -0600 (CST) Message-ID: <3846A64B.D75079EA@thebarn.com> Date: Thu, 02 Dec 1999 11:03:07 -0600 From: Russell Cattelan X-Mailer: Mozilla 4.7 [en] (X11; I; IRIX64 6.5-ALPHA-1275916020 IP27) X-Accept-Language: en MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai Cc: Dag-Erling Smorgrav , current@freebsd.org, cg@freebsd.org Subject: Re: Soundblaster 128 PCI References: <38455C25.D4E917A6@thebarn.com> <19991202080030.F12457@daemon.ninth-circle.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeroen Ruigrok/Asmodai wrote: > -On [19991201 20:01], Russell Cattelan (cattelan@thebarn.com) wrote: > >Dag-Erling Smorgrav wrote: > >> I have a Soundblaster 128 PCI (labeled "MODEL:CT4810") which I can't > >> get to work with newpcm. > > >What mother board are you using? > >There have been some reports of the new 1371's not working with > >non intel chip sets. Asus boards are know to be a problem. > >Apparently it is a timing bug in the sound card. > > The timing bug, is that a PCI bus clock/signal bug which the card has, or an > internal timing problem? I found this message in the als archives. http://hyppo.screwdriver.net/show.phtml?id=119845 Summary: I had quite a few conversations via email with David Sowa at Ensoniq, ran a boatload of tests, found that the card worked fine in a different system, swapped cards, and finally learned the answer. Turns out that there's a hardware bug in one batch of one vendor's codecs, which causes them to lock up if the PCI reset-line timing is just so. The ALI chipset in my ASUS motherboard tickled the bug, while the Intel chipset in my test system at work did not. I have been watching the list to see if anybody has found a solution to the problem. I've had at least 4 reports of the new PCI128 not working with an ASUS board. > > > -- > Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl > The BSD Programmer's Documentation Project > Network/Security Specialist BSD: Technical excellence at its best > Learn e-mail netiquette: http://www.lemis.com/email.html > We do not count a man's years, until he has nothing left to count... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message