Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!news-xfer.netaxs.com!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!news-peer.sprintlink.net!news-peer.sprintlink.net!news.sprintlink.net!sprint!cs.utexas.edu!news.tamu.edu!news.utdallas.edu!nrchh45.rich.nt.com!bcarh189.bnr.ca!bmerhc5e.bnr.ca!news From: Andrew Atrens <atrens@nortel.ca> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Problem with Creative Technology Sound Card - Help! Date: Thu, 10 Apr 1997 10:24:20 -0400 Organization: Nortel Technology (formerly Bell Northern Research) Lines: 40 Message-ID: <334CF813.B3@nortel.ca> References: <5ieane$8i0$1@spaceghost.cat.pdx.edu> <5ig8j1$l93$2@sol.ctr.columbia.edu> NNTP-Posting-Host: bmerh278.bnr.ca Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.0b2 (X11; I; HP-UX A.09.05 9000/712) X-Priority: 3 (Normal) Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38860 Bill Paul wrote: Daring to challenge the will of the almighty Leviam00se, Dave Roethig (daver@sirius.cs.pdx.edu) had the courage to say: : The problem: : The sound is horrible!! : It will not play anything for more than 1 second and then : it stops playing and then kernel errors appear: : Apr 8 13:34:39 rebec /kernel: Sound: DMA timed out - IRQ/DRQ config error? : Apr 8 13:34:44 rebec last message repeated 2 times Don't use IRQ 7! That's the printer port! I don't care if you took out the 'lpt' lines in your kernel config file: unless you actually turned off the printer port in your BIOS config (or set the appropriate jumpers), the hardware is still there. Change the card to use a different IRQ. Mine is set up this way ( irq 7 ), and it works just fine. That said, I spent a couple of weeks pulling hair with the same symptoms that Dave describes. This while running a Fall '96 snapshot of 2.2. All these problems vanished when I upgraded to the official 2.2 release. If you are running a 2.2 snapshot Dave, I'll bet my lunch money that upgrading to 2.2.1 will fix this problem. Cheers, Andrew. ( opinions are mine, not Nortel's. )