Re: [TCLUG:10481] Sound Blaster 64 trouble.

[Justin Coyne <jcoyne@breakout.micro.umn.edu>]

I'm sorry, I am getting general system messages, just nothing out of the
ordinary or arround the time the system crashes.

Justin Coyne <jcoyne@software.umn.edu>

On Mon, 29 Nov 1999, Jon Schewe wrote:

> Are you getting anything at all on the screen?  You should see general
> messages from anything else that's running, or at least the boot messages.
> Just want to make sure that the stuff in /etc/syslogd.conf is taking effect.
> 
> ----- Original Message -----
> From: Justin Coyne <jcoyne@breakout.micro.umn.edu>
> To: <tclug-list@mn-linux.org>
> Sent: Monday, November 29, 1999 1:21 PM
> Subject: Re: [TCLUG:10481] Sound Blaster 64 trouble.
> 
> 
> > Nothing at all is showing up before it crashes.
> >
> >
> > Justin Coyne <jcoyne@software.umn.edu>
> >
> > On Mon, 29 Nov 1999, Jon Schewe wrote:
> >
> > > Are you getting anything on there?  Or is it just that nothing useful
> shows
> > > up?
> > >
> > > ----- Original Message -----
> > > From: Justin Coyne <jcoyne@breakout.micro.umn.edu>
> > > To: <tclug-list@mn-linux.org>
> > > Sent: Wednesday, November 24, 1999 3:35 PM
> > > Subject: Re: [TCLUG:10481] Sound Blaster 64 trouble.
> > >
> > >
> > > > I added *.* /dev/tty10 to syslogd.conf but still nothing showing up
> giving
> > > > me any clue about how to procede.
> > > >
> > > >
> > > > On Wed, 24 Nov 1999, Jon Schewe wrote:
> > > >
> > > > >
> > > > >
> > > > > > On Wed, 24 Nov 1999, Justin Coyne wrote:
> > > > > >
> > > > > > > I finally got my SB 64 to start functioning under linux. I'm now
> > > able to
> > > > > > > play sounds, but only for a short while. About 2 minutes after I
> > > start
> > > > > > > playing an mp3 the whole system locks. I can't type anything,
> switch
> > > to
> > > > > > > another term, telnet in, or ctrl-alt-del. It is completely
> locked. I
> > > > > even
> > > > > > > allocated the appropriate IRQ's and DMA's to the ISA Legacy bus
> in
> > > the
> > > > > > > BIOS but that seemed to have no effect at all. I have no idea
> where
> > > to
> > > > > > > begin troubleshooting this problem.
> > > > > > >
> > > > > > >
> > > > > > > Justin Coyne <jcoyne@software.umn.edu>
> > > > > > >
> > > > > >
> > > > > > Check out /var/log/messages after you coldboot and see if there
> are
> > > any
> > > > > > error messages that the sound driver put out before the system
> locked.
> > > > > >
> > > > > If it's locking before that information gets written to disk you'll
> miss
> > > it
> > > > > though.  Something I do when debugging is to setup syslog to spew
> all
> > > > > messages to a tty and then switch to that to see them.  So add *.*
> > > > > /dev/tty10 to /etc/syslog.conf and restart syslogd, kill -HUP will
> work
> > > too.
> > > > > Then start playing you're mp3, then switch to VC 10 with
> ctrl-alt-f10
> > > and
> > > > > watch the messages and see what appears.
> > > > >
> > > > >
> > > >
> > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> > > > > For additional commands, e-mail: tclug-list-help@mn-linux.org
> > > > >
> > > > >
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> > > > For additional commands, e-mail: tclug-list-help@mn-linux.org
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> > > For additional commands, e-mail: tclug-list-help@mn-linux.org
> > >
> > >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> > For additional commands, e-mail: tclug-list-help@mn-linux.org
> >
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tclug-list-unsubscribe@mn-linux.org
> For additional commands, e-mail: tclug-list-help@mn-linux.org
> 
>