From owner-freebsd-questions Tue Sep 10 15:02:44 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA17946 for questions-outgoing; Tue, 10 Sep 1996 15:02:44 -0700 (PDT) Received: from atlantis.nconnect.net (root@atlantis.nconnect.net [206.54.227.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA17941 for ; Tue, 10 Sep 1996 15:02:38 -0700 (PDT) Received: from arabian.sylvester (cd-rom.execpc.com [169.207.8.135]) by atlantis.nconnect.net (8.7.3/8.7.3) with SMTP id QAA16072; Tue, 10 Sep 1996 16:57:24 -0500 (CDT) Message-ID: X-Mailer: XFMail 0.4 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <3236495C.29C8@teton.com> Date: Tue, 10 Sep 1996 17:00:34 -0500 (CDT) Organization: Computer Specialists From: Randy To: "David A. Stover" Subject: RE: Kernel Compilation Problems Cc: questions@FreeBSD.org Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On 11-Sep-96 "David A. Stover" wrote: >>While attempting to recompile my kernel, my Adaptec AHC2842 fails to be >recognized. > >If I boot GENERIC with "-c", the ahc0 line doesn't even show, but the >system probes and finds my 2842 correctly (listing it out as an >AHC28xx), and then boots fine. > >I also tried to leave the aha0 line active and comment out the ahc0 line >-- no luck there. Controller was not detected. > >I also tried to append some of the arguments from the aha0 line to the >ahc0 line; e.g. port bio irq drq and vector (all with the correct >parameters where required), changing the ahaintr to ahcintr. On this >instance, the kernel would not even compile, failing on the ahcintr. > >A friend of mine who knows BSD much better than I do has no ideas on >correcting the problem, either. > ---------------------------------------- Greetings, Without your kernel config file it's hard to tell. Just a guess... The 2842 is a VLB device but is probed as an EISA device ( I got bit by this one myself ) so you must have.... controller eisa0 in your config. If it's there... send your config file. It's much easier to diagnose that way. :) Randy