Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Nov 1999 06:49:35 +0000
From:      Timo Geusch <freebsd@timog.prestel.co.uk>
To:        current@freebsd.org
Subject:   Re: More newpcm breakage
Message-ID:  <19991130064935.A209@ginger.timog.prestel.co.uk>
In-Reply-To: <14403.10420.49833.29321F@rina.r.dl.itc.u-tokyo.ac.jp>; from tanimura@r.dl.itc.u-tokyo.ac.jp on Tue, Nov 30, 1999 at 10:30:28AM %2B0900
References:  <86zovx6tzn.fsf@niobe.ewox.org> <14403.10420.49833.29321F@rina.r.dl.itc.u-tokyo.ac.jp>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Nov 30, 1999 at 10:30:28AM +0900, tanimura@r.dl.itc.u-tokyo.ac.jp wrote:
> On 29 Nov 1999 19:19:24 +0100,
>   Dag-Erling Smorgrav <des@flood.ping.uio.no> said:
> 
> Dag-Erling> My SB32 PnP, which had so far worked nicely with newpcm except for the
> Dag-Erling> "fast forward" bug, stopped working after the newmidi import. This
> Dag-Erling> means that none of my sound cards (except for the GUS PnP, which I
> Dag-Erling> haven't tested) work any more, and I am seriously losing faith in the
> Dag-Erling> authors' ability to maintain a device driver.
> 
> Did you add sbc into your kernel configuration? Maybe I should add
> a warning in sb.c...

I don't if DES did, but I did. Turns out from his dmesg that he has a very
similar hardware config (which is why I don't include a copy of my dmesg)
and I am seeing *exactly* the same problems - suddenly my AWE32 is not
recognized any more.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991130064935.A209>