Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Jan 2001 11:57:12 -0800
From:      Greg Rumple <grumple@zaphon.llamas.net>
To:        The Hermit Hacker <scrappy@hub.org>
Cc:        Cameron Grant <gandalf@vilnya.demon.co.uk>, Michael Wells <michael@wells.org.uk>, freebsd-current@FreeBSD.ORG
Subject:   Re: Soundblaster 64 PCI
Message-ID:  <20010115115711.H69786@zaphon.llamas.net>
In-Reply-To: <Pine.BSF.4.31.0101141730110.599-100000@thelab.hub.org>; from scrappy@hub.org on Sun, Jan 14, 2001 at 05:30:19PM -0400
References:  <Pine.BSF.4.31.0101141727090.599-100000@thelab.hub.org> <Pine.BSF.4.31.0101141730110.599-100000@thelab.hub.org>

next in thread | previous in thread | raw e-mail | index | archive | help
This is the same problem I am having with a Soundblaster 16 PCI on
4.2-STABLE.  I found a work around for it.  It appears that there is
something that is being un-initialized by the FreeBSD es1371 driver that
other OS's do set.  I have built a linux boot floppy, boot it, modprobe
the linux es1371 driver, and than reboot into FreeBSD and the problem is
gone.  And until I power off the machine, the card works fine.

I have brought this up several times on the freebsd-multimedia list, but
have gone un-noticed each time.

Anyway, I have found a lame work around, until it is fixed properly.

Greg

* The Hermit Hacker (scrappy@hub.org) [010114 21:33]:
> 
> yup, just confirmed ... it does it with splay as well ...
> 
> 
> On Sun, 14 Jan 2001, The Hermit Hacker wrote:
> 
> > On Sun, 14 Jan 2001, Cameron Grant wrote:
> >
> > > > > If this is a known problem, I'll stop for now and watch out for fixes.
> > > > > If it's not the expected behaviour from the PCM driver though, can
> > > > > anyone advise?
> > > >
> > > > Okay, just checked and it appears tha htis is the same error that I'm
> > > > seeing on mine, as reported yesterday ... not sure if its known or not,
> > > > but its not "just you" ...
> > >
> > > are either of you using esound or xmms?  if so, i know the cause of this and
> > > it will be fixed shortly, once my primary development box recovers from
> > > killing its cpu.
> > >
> > > if not, i'll try to reproduce this.
> >
> > for me, I tried using splay ... but, not sure how old my compile was, so
> > am just installing a new copy and will report back ...
> >
> >
> >
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-current" in the body of the message
> >
> 
> Marc G. Fournier                   ICQ#7615664               IRC Nick: Scrappy
> Systems Administrator @ hub.org
> primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org
> 
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-current" in the body of the message

-- 
Greg Rumple
grumple@zaphon.llamas.net


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?20010115115711.H69786>