Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!agate!howland.reston.ans.net!news.sprintlink.net!hookup!relay.tor.hookup.net!nic.hookup.net!xenitec!vances From: vances@xenitec.on.ca (Vance Shipley) Subject: Re: SoundBlaster16 with FreeBSD-2.0-RELEASE Organization: XeniTec Consulting, Kitchener, Ontario, Canada Date: Sat, 21 Jan 1995 23:15:52 GMT Message-ID: <D2s3AI.AnA@xenitec.on.ca> Summary: /dev/dsp: Interrupted system call Keywords: SoundBlaster16 /dev/dsp FreeBSD References: <D2Kw4D.Et@xenitec.on.ca> Lines: 54 First the good news, thanks to some net.help I now have my Sound Blaster 16 recognized: snd2 at 0x220 irq 5 drq 1 on isa snd2: <SoundBlaster Pro 4.13> SoundBlaster 16: IRQ 5 DMA 5 OK snd6 at 0x220 drq 5 on isa snd6: <SoundBlaster 16 4.13> snd7 at 0x330 on isa snd7: <SoundBlaster MPU-401> snd1 at 0x388 on isa snd1: <Yamaha OPL-3 FM> The config I used was: ptions "EXCLUDE_GUS" options "EXCLUDE_PAS" options "EXCLUDE_GUS_IODETECT" options "EXCLUDE_GUSMAX" options "EXCLUDE_GUS16" options "EXCLUDE_MSS" options "EXCLUDE_PSS" options ALLOW_CONFLICT_IOADDR device snd2 at isa? port 0x220 irq 5 drq 1 vector sbintr device snd6 at isa? port 0x220 drq 5 device snd7 at isa? port 0x330 device snd1 at isa? port 0x388 The bad news is that I get an error when I try to access the device: $ dd if=/dev/dsp of=/tmp/dsp.out dd: /dev/dsp: Interrupted system call 0+0 records in 0+0 records out 0 bytes transferred in 4 secs (0 bytes/sec) I compile the debugging into sb16_dsp and get this output: sb16_dsp_open() dsp_set_bits(8) dsp_set_stereo(0) dsp_set_speed(8000) dsp_set_bits(8) dsp_set_bits(8) sb16_dsp_close() My machine is an older 386DX20 with 8MB DRAM. Is it just too old? ANY help would most appreciated. Thanks. -Vance -- Vance Shipley, vances@xenitec.on.ca