Date: Wed, 30 Nov 2005 06:49:36 +0100 From: Joerg Pernfuss <elessar@bsdforen.de> To: freebsd-stable@freebsd.org Subject: Re: device em0 not showing up at boot Message-ID: <20051130064936.7f320d09@loki> In-Reply-To: <2a41acea0511292052g55ec0e91t75675000437b472e@mail.gmail.com> References: <438B9E14.7040007@forrie.com> <44acfnjzmu.fsf@be-well.ilk.org> <6.2.3.4.0.20051129103951.08abb790@64.7.153.2> <2a41acea0511291726h2a90eb91l64700ec16ecba1f5@mail.gmail.com> <438D15ED.60204@forrie.com> <2a41acea0511292052g55ec0e91t75675000437b472e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 29 Nov 2005 20:52:23 -0800 Jack Vogel <jfvogel@gmail.com> wrote: > em0@pci0:13:0: class=0x020000 card=0x11768086 chip=0x10768086 > rev=0x00 > > hdr=0x00 > > vendor = 'Intel Corporation' > > device = '82547EI Gigabit Ethernet Controller' > > class = network > > subclass = ethernet > > > > So, the kernel does see the device Forrest. If you are not seeing any > sort of > message on boot then it is probably because you dont have the driver > configured into your kernel maybe?? > > Jack Shouldn't it be `none@pci0:13:0' if he hadn't configured the driver? Looks quite attached to the device to me. I am not sure if pciconf kldloads if_em.ko, but I doubt it. `kldstat -v' might give clues. `if_em_load="YES"' in /boot/loader.conf might help in case he does not have em in his kernel, but somehow loaded it before making the above output. Joerg -- | /"\ ASCII ribbon | GnuPG Key ID | c7e4 d91d 64e2 6321 9988 | | \ / campaign against | 0xb248b614 | f27a 4e5b 06ce b248 b614 | | X HTML in email | .the next sentence is a lie. | | / \ and news | .the previous sentence was true. |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051130064936.7f320d09>