From owner-freebsd-questions Sat Mar 25 6:12:53 2000 Delivered-To: freebsd-questions@freebsd.org Received: from kestrel.prod.itd.earthlink.net (kestrel.prod.itd.earthlink.net [207.217.121.155]) by hub.freebsd.org (Postfix) with ESMTP id 47F0737B65C for ; Sat, 25 Mar 2000 06:12:51 -0800 (PST) (envelope-from bduk@arthlink.net) Received: from arthlink.net (sdn-ar-004orportP320.dialsprint.net [63.178.68.226]) by kestrel.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id GAA16483; Sat, 25 Mar 2000 06:11:41 -0800 (PST) Received: (from bduk@localhost) by arthlink.net (8.9.3/8.9.3) id GAA02898; Sat, 25 Mar 2000 06:09:17 -0800 (PST) (envelope-from bduk) Date: Sat, 25 Mar 2000 06:09:17 -0800 (PST) Message-Id: <200003251409.GAA02898@arthlink.net> From: Derrick Baumer To: sdt@gmx.net Cc: questions@FreeBSD.ORG In-reply-to: (message from Stefanus Du Toit on Sat, 25 Mar 2000 19:15:25 +0800 (BNT)) Subject: Re: 2nd IDE controller Reply-To: bduk@earthlink.net Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: Stefanus Du Toit > > Hi, > > I've been running FreeBSD for half a week now - it's great - but > unfortunately have so far been unable to get it to recognise my second IDE > controller. I checked in Linux + Windows 98, it's definitely at 0x170, but > whenever I boot up FreeBSD it tells me "wdc1 not found at > 0x170". Interesting is also the fact that my BIOS lists a few devices > (PCI, I think) at startup, including the _first_ IDE controller (at 0x1f0, > irq 14), but _not_ the second one (and yet the second controller works > without problems on the other OSes on here). I had an identical problem, did the same checking, and somewhere along the way it started working right, but I'm not sure precisely what I did. Here are the things I tried: 1. Recompiled the kernel, putting the appropriate flags on the disk controller lines as outlined in LINT - these told the system to look for DMA, block transfers, 32bit access, etc... I don't think this is what fixed it. 2. In my BIOS, I had the two IDE drives that were on the controller that was not being found set up for DMA access even though they were not DMA drives. Somehow they worked fine like that under Windows? Made sure all BIOS settings reflected actual hardware. 3. Rearranged the drives so they were on different controllers - just swapped them. Now everything works. ? -- Derrick Baumer bduk@earthlink.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message