From owner-freebsd-questions Mon May 31 23: 0:40 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 78B4514F6D for ; Mon, 31 May 1999 23:00:38 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id XAA18551; Mon, 31 May 1999 23:00:35 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 31 May 1999 23:00:34 -0700 (PDT) From: Doug White To: Bruce Grisham Cc: questions@FreeBSD.ORG Subject: Re: make depend complains of missing files In-Reply-To: <3752C118.79697B93@accumatics.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 May 1999, Bruce Grisham wrote: > This same build has been successful on other machines, but make depend > complains: > > cc: ../../i386/scsi/93cx6.c: No such file or directory > cc: ../../i386/eisa/aic7770.c: No such file or directory > cc: ../../i386/eisa/aha1742.c: No such file or directory > cc: ../../i386/eisa/bt74x.c: No such file or directory > cc: ../../i386/isa/aha1542.c: No such file or directory > cc: ../../i386/isa/bt5xx-445.c: No such file or directory > cc: ../../i386/isa/kbdio.c: No such file or directory > cc: ../../i386/isa/syscons.c: No such file or directory > cc: ../../i386/scsi/aic7xxx.c: No such file or directory > cc: ../../i386/scsi/bt.c: No such file or directory > cc: ../../pci/wd82371.c: No such file or directory > ../../i386/isa/atapi.c:106: acd.h: No such file or directory > ../../i386/isa/atapi.c:108: wst.h: No such file or directory > mkdep: compile failed > *** Error code 1 > > And sure enough the files aren't in the kernel source tree. > > What surprises me here is that this build succeeded verbatim other > machines. > > ANY SUGGESTIONS? cp /sys/i486/conf/MYCONFIG ~/ rm -rf /usr/src/sys # then reinstall your kernel source. > On previous machines the generic kernel recognized the Fore cards > properly as network adapters, with the relevant boot message just > stating that there was no driver. After rebuilding the kernel, the boot > message indicated, as expected, that a driver was installed. Whee. > This time around, the cards don't even show up in the bus 0 scan > messages. Yes, we turned these messages off. They were confusing people. > > pciconf -l | grep none > > none0@pci0:7:2: class=0x0c0300 card=0x00000000 chip=0x71128086 > rev=0x01 hdr=0x00 > none1@pci0:9:0: class=0x020300 card=0x00000000 chip=0x03001127 > rev=0x00 hdr=0x00 > none2@pci0:11:0: class=0x020300 card=0x00000000 chip=0x03001127 > rev=0x00 hdr=0x00 > > shows the cards on IRQs 9 and 11. > > If I were having success building the kernel, then I would quickly know > whether it even matters that the bus scan doesn't show the cards in the > boot messages. > > DOES IT MEAN ANYTHING THAT THERE IS NO BOOT MESSAGE FOR THE CARDS? There is no driver to service these cards. Same as before, it isn't telling you explicitly that no driver was defined, that's all. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message