Hi all,
One of the EM nics we just got in comes up with
em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.19> port
0x9000-0x903f mem 0xe8700000-0xe871ffff,0xe86e0000-0xe86fffff irq 5 at
device 0.0 on pci1
em0: The EEPROM Checksum Is Not Valid
em0: Unable to initialize the hardware
device_probe_and_attach: em0 attach returned 5
when booting. Is this just a dud or just not recognized ?
none0@pci1:0:0: class=0x020000 card=0x11138086 chip=0x10768086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
class = network
subclass = ethernet
4.9-STABLE FreeBSD 4.9-STABLE #1: Thu Jan 8 14:19:25 EST 2004
--------------------------------------------------------------------
Mike Tancsa, tel +1 519 651 3400
Sentex Communications, mike@sentex.net
Providing Internet since 1994 www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike
Hi, At 18:25 26/2/04, Mike Tancsa wrote:>Hi all, > >One of the EM nics we just got in comes up with > >em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.19> port >0x9000-0x903f mem 0xe8700000-0xe871ffff,0xe86e0000-0xe86fffff irq 5 at >device 0.0 on pci1 >em0: The EEPROM Checksum Is Not Valid >em0: Unable to initialize the hardware >device_probe_and_attach: em0 attach returned 5 > >when booting. Is this just a dud or just not recognized ?FWIW I get something very similar under 5.2.1-RC2 on my shiny new ThinkPad T41, so it's likely just not recognised. -- Bob Bishop +44 (0)118 977 4017 rb@gid.co.uk fax +44 (0)118 989 4254
On Thu, 26 Feb 2004, Mike Tancsa wrote:> Hi all, > > One of the EM nics we just got in comes up with > > em0: <Intel(R) PRO/1000 Network Connection, Version - 1.7.19> port > 0x9000-0x903f mem 0xe8700000-0xe871ffff,0xe86e0000-0xe86fffff irq 5 at > device 0.0 on pci1 > em0: The EEPROM Checksum Is Not Valid > em0: Unable to initialize the hardware > device_probe_and_attach: em0 attach returned 5 > > when booting. Is this just a dud or just not recognized ?Last time I saw this, it was because there was a new rev of the silicon. If its an onboard, check for a new BIOS for your system.> > none0@pci1:0:0: class=0x020000 card=0x11138086 chip=0x10768086 rev=0x00 > hdr=0x00 > vendor = 'Intel Corporation' > class = network > subclass = ethernet > > 4.9-STABLE FreeBSD 4.9-STABLE #1: Thu Jan 8 14:19:25 EST 2004 > -------------------------------------------------------------------- > Mike Tancsa, tel +1 519 651 3400 > Sentex Communications, mike@sentex.net > Providing Internet since 1994 www.sentex.net > Cambridge, Ontario Canada www.sentex.net/mike > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >-- Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org
Hi again, At 19:57 26/2/04, Mike Tancsa wrote:>At 02:26 PM 26/02/2004, Bob Bishop wrote: >>Hi, >> >>At 18:25 26/2/04, Mike Tancsa wrote: >>> >>>em0: The EEPROM Checksum Is Not Valid [etc] >> >>FWIW I get something very similar under 5.2.1-RC2 on my shiny new >>ThinkPad T41, so it's likely just not recognised. > >Actually, I worked around the problem by swapping its location with an fxp >next to it. For some reason the em does not seem to like sharing its >interrupt with agp0 ? The fxp seems happy enough to do it however.On my T41, hw.pci.allow_unsupported_io_range="1" in /boot/loader.conf fixed it, so maybe the IRQ wasn't the problem. -- Bob Bishop +44 (0)118 977 4017 rb@gid.co.uk fax +44 (0)118 989 4254