From owner-freebsd-questions Thu Oct 22 08:53:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13492 for freebsd-questions-outgoing; Thu, 22 Oct 1998 08:53:04 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from stoner.nsg.bc.ca (stoner.vn.opentext.com [209.171.211.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13478 for ; Thu, 22 Oct 1998 08:53:00 -0700 (PDT) (envelope-from acton@stoner.vn.opentext.com) Received: from stoner.vn.opentext.com (localhost.vn.opentext.com [127.0.0.1]) by stoner.nsg.bc.ca (8.8.7/8.7.2) with ESMTP id IAA02647; Thu, 22 Oct 1998 08:51:05 -0700 (PDT) Message-Id: <199810221551.IAA02647@stoner.nsg.bc.ca> X-Mailer: exmh version 1.6.9 8/22/96 To: "Joe \"Marcus\" Clarke" cc: FreeBSD User Questions List Subject: Re: wdc1 not found: follow up In-reply-to: Your message of "Wed, 21 Oct 1998 22:27:22 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 08:51:05 -0700 From: Donald Acton Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I posted in a previous message of my own, I was experiencing similar problems with the default kernel shipped with 3.0 not being able to locate the secondary IDE controller (wdc1) even though the kernel messages appeared to indicate it was being looked for. Using the GENERIC kernel config file I constructed a new config file tailored to my machine and environment. I deleted most of the lines for devices I didn't have and I left the lines relating to the wdc1 controller and associated drives untouched. Of particular interest, I deleted all the Ethernet devices I didn't have installed and left the following line in the file device ed0 at isa? port 0x300 net irq 10 iomem 0xcc000 vector edintr Note that in the above configuration line I changed the port and iomem values. The kernel build went smoothly. Upon rebooting with this new kernel, wdc1 and the attached disk was found, but now the Ethernet controller wasn't found at location 0x300. After some mumbling under the breath I built a new kernel with the above ed0 line changed back to device ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 vector edintr (The above line was taken exactly from the GENERIC config file) This time when I rebooted I performed a manual configuration for ed0 and changed the port from 0x280 to 0x300 and changed iomem to 0xcc000. This time both ed0 and wdc1 were found. I had success! I have no idea why the second approach worked and the first didn't, as the first technique has worked fine in the past. Donald Acton acton@opentext.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message