Jeroen Ruigrok/Asmodai wrote:
> -On [19991201 20:01], Russell Cattelan ([EMAIL PROTECTED]) 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 <http://home.wxs.nl/~asmodai>
> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
