From owner-freebsd-questions Wed Sep 23 08:04:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10028 for freebsd-questions-outgoing; Wed, 23 Sep 1998 08:04:57 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from lucy.bedford.net (lucy.bedford.net [206.99.145.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09989 for ; Wed, 23 Sep 1998 08:04:50 -0700 (PDT) (envelope-from listread@lucy.bedford.net) Received: (from listread@localhost) by lucy.bedford.net (8.8.8/8.8.8) id KAA27243; Wed, 23 Sep 1998 10:49:50 -0400 (EDT) (envelope-from listread) Message-Id: <199809231449.KAA27243@lucy.bedford.net> Subject: Re: 2.2.7 and PCI In-Reply-To: from Evren Yurtesen at "Sep 21, 98 04:12:34 pm" To: yurtesen@turkey.ispro.net.tr (Evren Yurtesen) Date: Wed, 23 Sep 1998 10:49:50 -0400 (EDT) Cc: username@euronet.be, freebsd-questions@FreeBSD.ORG X-no-archive: yes Reply-to: djv@bedford.net From: "Woodchuck" X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Evren Yurtesen wrote: > when you are compiling kernel you should leave at least the first > isa ethernet card ed0 in your kernel...(or any?) > if you do not do that freebsd does not assign a driver for your card. > but after that if you do not want to see the error message > which says that the system could not find ed0 you may boot with > -cv parameter and then disable probing for ed0 device... > > well, if somebody knows why freebsd does not assign a driver to > pci ethernet devices if you do not specify any isa ethernet please > let me know, I wonder why it happens :) I am certainly running a machine with an fxp0 (Intel EE Pro/100B) ethernet "non-card" on the PCI bus (it's on the motherboard -- perhaps this makes an obscure difference??), with a kernel configuration that includes no ISA ethernet devices. All I have that seems related to ethernet is: device fxp0 and pseudo-device ether Perhaps Mr. Kuijpers removed this last line in his zeal? But the kernel with only the vx device but not ps-d ether will not link. Perhaps this need for ISA drivers is true only for certain PCI cards? (But how would the kernel link?) A kernel configured for vx but no other ethernet card will compile & link OK. (Since I have no 3C900 card, booting it does not detect the Intel device... this is different from Mr K's behavior -- detected by "no driver assigned"). Maybe Mr Kuijpers used the wrong device name for the driver? (I believe vx is the 3C900 driver, at least in 2.2.6R). At any rate, a kernel (2.2.6R) configured with fxp0+ether, but *no* ISA devices except sc0 (console) and nxp0 (coprocessor), boots correctly and runs for me. > On Mon, 21 Sep 1998, Theo Kuijpers wrote: > > > Hi there, > > > > I've got a strange problem : > > > > I just upgraded from 2.2.6 to 2.2.7 without any problems. When using the > > GENERIC kernel all my > > PCI devices (currently only a 3c900 card) are detected > > and assigned a driver. > > > > When I use a custom kernel (a propper one with the > > right devices etc.) it doesn't assign any driver > > to the PCI devices .. it detects the card as an PCI device (ethernet) but it > > reports [no driver assigned]. Maybe we need to see Mr K's config file? Dave -- Will hack for cabbages! Every day is Groundhog Day! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message