From owner-freebsd-questions Mon Jan 25 19:47:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA17741 for freebsd-questions-outgoing; Mon, 25 Jan 1999 19:47:07 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from peacock.tci.com (coral.tci.com [198.178.8.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA17735 for ; Mon, 25 Jan 1999 19:47:05 -0800 (PST) (envelope-from chris@tci.com) Received: from oreo.tci.com (co-chris-pc01.tci.com [172.18.27.65]) by peacock.tci.com (8.9.0/8.9.0) with ESMTP id UAA23647; Mon, 25 Jan 1999 20:47:03 -0700 (MST) Received: from tci.com (localhost [127.0.0.1]) by oreo.tci.com (8.9.1b+Sun/8.9.1) with ESMTP id UAA10620; Mon, 25 Jan 1999 20:46:50 -0700 (MST) Message-ID: <36AD3AA9.3D3A9CAC@tci.com> Date: Mon, 25 Jan 1999 20:46:49 -0700 From: Chris Tubutis Organization: Tele-Communications, Inc. X-Mailer: Mozilla 4.5 [en] (X11; U; SunOS 5.7 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: Ian Clendaniel CC: freebsd-questions@FreeBSD.ORG Subject: Re: modem and soundcard conflict?!? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ian Clendaniel wrote: > > I have a weird problem that seems to have cropped up. > > In my recent efforts to add a Zip 250 SCSI drive to my system I also > decided to add a Soundblaster AWE64...well I added the necessary support > and recompiled my kernel. Booted with no problem and everything was > recognized with no apparent errors. Sound works great and can now play > mp3's to my hearts content...BUT...with the soundcard in the machine I can > no longer get a connection to my ISP. > > The machine in question (2.2.6 Release)acts as a gateway for our LAN, > forwarding packets across the PPP connection. It has never had problems > getting a connection until now. If I pull the soundcard out the machine > will connect fine but if I try to replace it I can't get a connection. > Weird?!? I thought it was a coincidence at first but I tried it several > times with the same results (every time it'll connect the first attempt > with no soundcard). > > Anyone have a clue as to what's going on??...'cause I sure don't. > > Here's my sound entries from the kernel: > > controller snd0 > > device sb0 at isa? port 0x220 irq 5 drq 1 vector sbintr > device sbxvi0 at isa? drq 5 > device sbmidi0 at isa? port 0x330 > > And here's the line for com2: > > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr > > Just to be thorough here's the boot messages for both: > > Jan 24 01:25:24 kamikaze /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa > Jan 24 01:25:24 kamikaze /kernel: sio1: type 16550A > > Jan 24 01:25:25 kamikaze /kernel: sb0 at 0x220 irq 5 drq 1 on isa > Jan 24 01:25:25 kamikaze /kernel: sb0: > Jan 24 01:25:25 kamikaze /kernel: sbxvi0 at 0x0 drq 5 on isa > Jan 24 01:25:25 kamikaze /kernel: sbxvi0: > Jan 24 01:25:25 kamikaze /kernel: sbmidi0 at 0x330 on isa > Jan 24 01:25:25 kamikaze /kernel: > > Anybody have suggestions (besides leaving the soundcard out ;) )?? > > If you guys could copy me on any replies I'd appreciate it...I'm not > subscribed. I would suspect and IRQ and/or IO address conflict. I don't have an AWE64 so can't speak authoritatively on them, but I would go look at what resources each card claims as its own and see if maybe they're not both trying to use the same ones. ct To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message