Date: Mon, 24 Mar 2008 15:03:30 -0700 From: John Pettitt <jpp@cloudview.com> To: Gavin Atkinson <gavin.atkinson@ury.york.ac.uk> Cc: freebsd-stable@freebsd.org Subject: Re: 7-STABLE not seeing second em interface on supermicro mb Message-ID: <47E82532.4030105@cloudview.com> In-Reply-To: <20080324110329.S16125@ury.york.ac.uk> References: <47E4B1BC.6020005@cloudview.com> <20080324110329.S16125@ury.york.ac.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Gavin Atkinson wrote: > On Sat, 22 Mar 2008, John Pettitt wrote: > >> I just installed 7-STABLE on a new dual/quad machine based on a >> supermicro motherboard - it works fine except that it's not seeing >> the second network interface (em driver) - is there a magic >> incantation to make this work? >> >> FreeBSD echelon.localnet 7.0-STABLE FreeBSD 7.0-STABLE #0: Fri Mar 21 >> 23:27:31 PDT 2008 >> root@echelon.localnet:/usr/src/sys/amd64/compile/ECHELON amd64 >> >> The only word from the em driver is this >> >> em0: <Intel(R) PRO/1000 Network Connection Version - 6.7.3> port >> 0x3000-0x301f mem 0xde200000-0xde21ffff irq 17 at device 0.0 on pci5 >> em0: Using MSI interrupt >> em0: Ethernet address: 00:30:48:64:d9:45 >> em0: [FILTER] >> >> ifconfig doesn't show anything other than em0 and lo0 > > Can you give us the output from "dmesg" after a verbose boot, and also > the output of "pciconf -l"? Are the network interfaces on board, or > on a separate card? > > Gavin > Doh! Turns out to be a hardware problem - when checking the jumpers I discovered a transistor on the MB next to the failed nic that is too hot to touch - new MB is on the way from Silicon Mechanics (who by the way are great to deal with) With hardware today I see so few dead components that I stopped checking the obvious first. John
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47E82532.4030105>