Re: Sound Woes
Dumb question probably, but did you include the csa(4) bridge driver? On Tue, Nov 28, 2000 at 03:30:09PM +1100, Anthony Williams wrote: > Howdy, > > Am having a little bit of trouble getting my soundcard to work under > 4.2-RELEASE...contents of /dev/sndstat is: > > FreeBSD Audio Driver (newpcm) Nov 28 2000 13:57:52 > Installed devices: > pcm0: at irq 10 (1p/1r channels duplex) > > when I try and play mp3s I get the following error: > > pcm0: play interrupt timeout, channel dead > > I checked the archives and for some people rebooting works but no go for > me...suggestions ?? > > TIA > Anthony > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Keith Jones E-Business Service Introduction, GBIT-E (Bristol) E: [EMAIL PROTECTED] T: [+44 117] 312-7602 I don't speak for Hewlett-Packard. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: emu10k1 (soundblaster live!) still crackling.
Since reinstalling my SBLive! Value card in my machine, I've encountered a similar problem, but _only_ with mono audio output, never with stereo. The card works fine under Win98 and (IIRC) worked reasonably well under Red Hat. Can anyone else confirm whether it's just mono that's messed up for them? (YMMV with other emu10k1 cards.) PR#: kern/23293 Ta, Keith On Mon, Nov 27, 2000 at 02:47:44PM -0500, David Lebel wrote: > Hello, > > I'm using 4.2-STABLE on a machine that has a SoundBlaster Live! > soundcard. Around the time 4.0 was released, I had bunch of problems > with the card giving bunch of static and crackling sound when sound > was being played. This was apparently fixed around the 4.1 release, > but since the latest MFC, I still notice occasional glitches in the > sound (mostly pops). > > Am I along having this problem? > > Ciao, > ...David > > -- > // david lebel <[EMAIL PROTECTED]> // nobiaze' Inc. > // http://www.lebel.org/ // http://www.nobiaze.com/ > // pgp: 3633 6999 D47E 73ED 099F // vox: (514) 943.3045 > 4341 08A4 8E48 EF56 61D1 // fax: (514) 938.8881 > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-stable" in the body of the message -- Keith Jones E-Business Service Introduction, GBIT-EMEA (Bristol) E: [EMAIL PROTECTED] T: [+44 117] 312-7602 I don't speak for Hewlett-Packard. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: 4.2-STABLE build fails
On Fri, Jan 05, 2001 at 03:04:55PM +0100, Janko van Roosmalen wrote: > > I've seen much of this discussed here but mine seems to break at this > > point: > > > > /usr/obj/usr/src/share/doc/usd/13.viref/troff.core > > > > ..and with this msg on the console... > > > > Jan 3 18:54:07 alouette /kernel: pid 54505 (troff), uid 0: exited on > > signal 11 (core dumped) > > Jan 3 18:54:07 alouette /kernel: pid 54523 (troff), uid 0: exited on > > signal 11 (core dumped) > > > > > > Even a fresh cvsup (after rm-ing all my srcs and usr/obj) does not help. > > Any pointer what this 13.viref thing is and how I can sort that out will > > be highly appreciated. > > The FreeBSD faq mentions that signal 11 points to hardware problems. Could people please STOP spreading this myth that all Signal 11's during 'make world' are a result of hardware problems. It is highly misleading. How would you feel if you acted on this advice and shelled out your hard-earned cash for new hardware only to find that it was a software problem after all? The chances are that if a signal occurs as the result of running a particular program (in this case 'troff'), it's likely to be the version of that program or a shared library on which it depends that is broken somehow on the user's machine, not the user's hardware. You could try manually recompiling and installing 'troff' et al. (located in the directory /usr/src/contrib/groff) then rerunning 'make world'. -- Keith Jones E-Business Service Introduction, GBIT-EMEA (Bristol) E: [EMAIL PROTECTED] T: [+44 117] 312-7602 I don't speak for Hewlett-Packard. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
