Date: Mon, 20 Jan 2003 19:54:57 +0100 From: Joan Picanyol i Puig <lists-freebsd-questions@biaix.org> To: freebsd-questions@freebsd.org Subject: weirdness in NIC probing Message-ID: <20030120185457.GA3148@grummit.biaix.org>
next in thread | raw e-mail | index | archive | help
(please honour Mail-Followup-To, I'm not subscribed) Hi, I upgraded a box from 4.5 to 4.7, and to my surprise, it didn't recognize the NIC at bootup anymore (having miibus and wb in the kernel). However, it does recognize it if I plug another NIC in. This is what I get when it recognizes it: wb0: <Winbond W89C840F 10/1 00BaseTX> port 0xd800-0xd87f mem 0xdb000000-0xdb00007f irq 5 at devic e 10.0 on pci0 wb0: Ethernet address: 00:0 2:03:06:00:e5 miibus0: <MII bus> on wb0 lxtphy0: <LXT970 10/100 med ia interface> on miibus0 lxtphy0: 100baseFX, 100bas eFX-FDX, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto The relevant entries from pciconf are: wb0@pci0:10:0: class=0x020000 card=0x08401050 chip=0x08401050 rev=0x00 hdr=0x00 vendor = 'Winbond Electronics Corp.' device = 'W89C840F 100/10Mbps Ethernet Controller' class = network subclass = ethernet none1@pci0:13:0: class=0x020000 card=0x00118086 chip=0x12298086 rev=0x09 hdr=0x00 vendor = 'Intel Corporation' device = '82557/8/9 EtherExpress PRO/100(B) Ethernet Adapter' class = network subclass = ethernet Note that the second NIC does not have a driver compiled for it in the kernel. Now, does anyone know what is causing this? Why does FreeBSD need the other NIC plugged in? It's probably some option in the kern config I don't know about (unfortunately, I don't keep the old config) tks -- pica To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030120185457.GA3148>