From owner-freebsd-current Thu Jan 27 23:12:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from dinolt1.bing.org (adsl-63-199-30-243.dsl.snfc21.pacbell.net [63.199.30.243]) by hub.freebsd.org (Postfix) with ESMTP id 25A7815AD1 for ; Thu, 27 Jan 2000 23:12:43 -0800 (PST) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net (localhost [127.0.0.1]) by dinolt1.bing.org (8.9.3/8.9.3) with ESMTP id XAA00647; Thu, 27 Jan 2000 23:13:20 -0800 (PST) (envelope-from gdinolt@pacbell.net) Message-ID: <38914190.636BC099@pacbell.net> Date: Thu, 27 Jan 2000 23:13:20 -0800 From: "George W. Dinolt" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Cc: CGiordano@ids.net Subject: Re: newpcm (or newpnp?) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Giordano wrote: > Previous to newpnp, I forced the modem (sio2) to irq 15 and the soundcard to > irq 5 via pnp commands in my /boot/kernel.conf. I did this because I had > found by experimentation that this was the only combination of the supposedly > available PnP configurations which enabled both devices to work. I can report similar problems with my US Robotics internal 56K Fax/Modem and my SoundBlaster 16 isa card. On Freebsd 3.4 I "hard wire" the cards using kernel.conf file. On -Current I found that the only way I can get the cards to work is to configure my IWILL XA100P motherboard so that irq 3 and 5 are set up for "legacy" cards and are not automagically assigned. (I disable the 2nd serial port as well so that irq 3 is available.) When I do this reconfiguration of the motherboard, the modem and sound card work together with few problems. I can play sound and do a compilation without problems. I do have 192MB of memory add a 450Mhz processor so there is plenty of spare "horsepower" for essentially a "single user" system. I do occasionally get a flutter on startup and can reliably see a cutoff of sound at the end of reading a wave or midi file. But for most things it seems to work fine. The "say" program from the rsynth port provides a good demonstration of the "cutoff" phenomena. George Dinolt (gdinolt@pacbell.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message