From owner-freebsd-questions Wed Nov 13 23:44:53 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0938937B401 for ; Wed, 13 Nov 2002 23:44:51 -0800 (PST) Received: from snickers.hotpop.com (snickers.hotpop.com [204.57.55.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 415AB43E6E for ; Wed, 13 Nov 2002 23:44:50 -0800 (PST) (envelope-from bsdterm@HotPOP.com) Received: from hotpop.com (kubrick.hotpop.com [204.57.55.16]) by snickers.hotpop.com (Postfix) with SMTP id 3F4D076363 for ; Thu, 14 Nov 2002 07:44:43 +0000 (UTC) Received: from terminator.athome.net (as1b-82.chi.il.dial.anet.com [198.92.157.82]) by smtp-1.hotpop.com (Postfix) with ESMTP id 3BBCF2F811C; Thu, 14 Nov 2002 07:44:24 +0000 (UTC) Content-Type: text/plain; charset="iso-8859-1" From: "E.S." Reply-To: bsdterm@HotPOP.com To: Kent Stewart Subject: Re: make buildkernel says device atapicam is unknown!!?? Date: Thu, 14 Nov 2002 01:44:18 -0600 User-Agent: KMail/1.4.2 References: <200211132359.26336.bsdterm@HotPOP.com> <3DD34D9B.3010807@owt.com> In-Reply-To: <3DD34D9B.3010807@owt.com> Cc: freebsd-questions@FreeBSD.ORG MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200211140144.18808.bsdterm@HotPOP.com> X-HotPOP: ----------------------------------------------- Sent By HotPOP.com FREE Email Get your FREE POP email at www.HotPOP.com ----------------------------------------------- Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Well, 4.7-RELEASE was released before Nov. 1, 2002 (on Oct. 10). As I understand it, 4.7-RELEASE is can be obtained by cvsup'ing to RELENG_4_7 (and generally the only patches that are applied to -RELEASE are security patches)... whereas if I cvsup'd to RELENG_4, *then* I would be getting 4.7-STABLE. But because I'm cvsup'ing to RELENG_4_7, not RELENG_4, I'm getting 4.7-RELEASE, not -STABLE... right? I may be wrong there; feel free to correct me if I am... :) In any case, I tried building the kernel before applying those patches, and after applying them. The output I quoted earlier is the same either way... -ES On Thursday 14 November 2002 01:15 am, Kent Stewart wrote: > E.S. wrote: > > I figured out my make buildworld problem I mentioned earlier (I'd > > uncommented NO_OPENSSL=true in my make.conf - big mistake!), and now that > > world builds OK, I'm having kernel build problems. > > > > I'm building 4.7-RELEASE (cvsup'ing to RELENG_4_7), and here's all the > > output for "make buildkernel KERNCONF=KERNELCONF4": > > > > -------------------------------------------------------------- > > > >>>>Kernel build for KERNELCONF4 started on Wed Nov 13 23:45:17 CST 2002 > > > > -------------------------------------------------------------- > > ===> KERNELCONF4 > > mkdir -p /usr/obj/usr/src/sys > > cd /usr/src/sys/i386/conf; > > PATH=/usr/obj/usr/src/i386/usr/sbin:/usr/obj/usr/src/i386/usr/bin:/usr/ob > >j/usr/src/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin config -d > > /usr/obj/usr/src/sys/KERNELCONF4 KERNELCONF4 > > Don't forget to do a ``make depend'' > > Warning: device "atapicam" is unknown > > *** Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > > > > > I've applied the following of Thomas Cuivre's atapicam patches (from > > http://www.cuivre.fr.eu.org/~thomas/atapicam/): > > > > atapicam-20021031.diff > > atapicam-STABLE-config-20021031.diff > > > > ...to source I cvsup'd today (Nov. 13). But I've had this same make > > error for the last several days... > > > > I have all the necessary devices and options in my KERNELCONF4 file that > > Cuivre notes on his atapicam page that we need, but the above is still my > > output. > > > > I *can* comment out "device atapicam" in my config file -- and the kernel > > appears to build OK (I haven't tried building a full kernel without > > atapicam support, I've only tested to see if removing "device atapicam" > > from the config file makes a difference) if I do that, but I really don't > > want to lose ATAPI burning support using cdrecord, etc... > > > > Anybody know what's going on here? Suggestions? > > > > I would post my KERNELCONF4 file, but this list cuts off my messages when > > they're some 200KB+ in size (I know, for bandwidth and spam, etc.)... > > I don't understand why you are doing part of this. The web page says > the atapicam device has been in 4.7-stable source since 1-nov-2002. It > sounds like you have basically applied the patch twice. All I did was > add "device atapicam" after my atapicd like so > > device atapicd # ATAPI CDROM drives > device atapicam > device atapifd # ATAPI floppy drives > > and did a make buildkernel. The kernel built without any errors. > > Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message