From owner-freebsd-questions Tue Nov 7 18:33:36 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id SAA13714 for questions-outgoing; Tue, 7 Nov 1995 18:33:36 -0800 Received: from virginia.edu (uvaarpa.Virginia.EDU [128.143.2.7]) by freefall.freebsd.org (8.6.12/8.6.6) with SMTP id SAA13708 for ; Tue, 7 Nov 1995 18:33:31 -0800 Received: from server.cs.virginia.edu by uvaarpa.virginia.edu id aa13129; 7 Nov 95 21:33 EST Received: from viper.cs.Virginia.EDU (viper-fo.cs.Virginia.EDU) by uvacs.cs.virginia.edu (4.1/5.1.UVA) id AA28793; Tue, 7 Nov 95 21:33:25 EST Posted-Date: Tue, 7 Nov 1995 21:33:24 -0500 (EST) Received: by viper.cs.Virginia.EDU (5.x/SMI-2.0) id AA23628; Tue, 7 Nov 1995 21:33:25 -0500 From: bah6f@server.cs.virginia.edu Message-Id: <9511080233.AA23628@viper.cs.Virginia.EDU> Subject: Re: Will sound drivers for SB16 be fixed in 2.1R? To: Colman Reilly Date: Tue, 7 Nov 1995 21:33:24 -0500 (EST) Cc: freebsd-questions@freebsd.org In-Reply-To: <199511071751.RAA00361@monoid.cs.tcd.ie> from "Colman Reilly" at Nov 7, 95 05:51:51 pm X-Mailer: ELM [version 2.4 PL24] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org Precedence: bulk Colman Reilly writes: -> -> Or are these still broken? I just built and ran a 2.1 kernel and they're -> still hanging after playing one sound. Sounds to me like you've got an IRQ conflict. This is what my sound drivers have always done whenever I've had an IRQ conflict. If you have a printer port and your SB uses IRQ 7, this is possible. If you have a network card using IRQ 10 and your SB uses that, this is possible. If you have anything (LPT2, bus mouse, network card, various other things) using IRQ 5, and your SB uses that IRQ, you might see this problem. Lastly, if you have the normal serial ports (COM1 and COM2) and your SB is set to IRQ 3 or 4, you could see this problem. Lastly, remember that the IRQ and I/O addresses that you specify in your kernel config file must match the configuration on your board and must match the entries in /sys/i386/isa/sound/sound_config.h It won't automatically update this file for you. You probably want to look at the board's jumpers, your kernel config file, /sys/i386/isa/sound/sound_config.h, and the output of the 'dmesg' command to get an idea what is going wrong. Hope that helps, Paco -- Brian "Paco" Hope Research Assistant, Technical Support Staff email: paco@virginia.edu Department of Computer Science WWW: http://www.cs.virginia.edu/~bah6f/ University of Virginia