From owner-freebsd-questions Sun May 4 23:59:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA08124 for questions-outgoing; Sun, 4 May 1997 23:59:21 -0700 (PDT) Received: from gatekeeper.barcode.co.il (gatekeeper.barcode.co.il [192.116.93.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA08118 for ; Sun, 4 May 1997 23:59:13 -0700 (PDT) Received: (from smap@localhost) by gatekeeper.barcode.co.il (8.8.5/8.6.12) id JAA28434; Mon, 5 May 1997 09:57:20 +0300 (IDT) X-Authentication-Warning: gatekeeper.barcode.co.il: smap set sender to using -f Received: from localhost.barcode.co.il(127.0.0.1) by gatekeeper.barcode.co.il via smap (V1.3) id sma028430; Mon May 5 09:56:51 1997 Message-ID: <336D84F7.2268@barcode.co.il> Date: Mon, 05 May 1997 09:57:59 +0300 From: Nadav Eiron X-Mailer: Mozilla 3.0 (X11; I; SunOS 5.5 sun4m) MIME-Version: 1.0 To: Spock CC: questions@FreeBSD.ORG Subject: Re: Probing Hardware References: <199705041919.OAA00182@aheffner.netnet.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Spock wrote: > > I would like to install my cd-rom drive and my sound card, > but i don't know the irq, drq, i/o addresses of them. I > have win95 running on my first drive, but i went to the > device manager in win95 and wrote down the irq,drq, i/o > addresses that it said the hardware was at, but when > i boot with "-c" and go into visual, and use those > numbers, freebsd still can't find the devices. I've > tried using all possible different combinations, but > it still won't find the hardware. Is there any way > to easily find out the addresses of the hardware, or > have it probe all addresses or something, until it finds > the devices? > > Thanx, > > Michael Heffner > aheffner@lakefield.net If your CDROM has an IDE interface, don't connect it to the SoundBlaster but rather to one of the main EIDE controllers, either as the slave on the primary controller, or as the master on the secondary controller. If that is the case, also make sure you have the lines option ATAPI device wcd0 in your kernel config file, and that the device wcd0c exists in /dev. Nadav