From owner-freebsd-hackers Fri Mar 10 11:52:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by hub.freebsd.org (Postfix) with ESMTP id B5B0E37B78F for ; Fri, 10 Mar 2000 11:52:53 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id LAA09228; Fri, 10 Mar 2000 11:36:00 -0800 (PST) Date: Fri, 10 Mar 2000 11:36:00 -0800 (PST) From: Jim Shankland Message-Id: <200003101936.LAA09228@biggusdiskus.flyingfox.com> To: dg@root.com Subject: Re: Onboard Intel fxp network chip, unknown PHY 17 type 2 Cc: hackers@freebsd.org In-Reply-To: <200003101922.LAA25494@implode.root.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: >Hmm. That reminds me: I've also got a box with an onboard >8255X that isn't recognized. The relevant parts of "boot -v" >output are: > >found-> vendor=0x8086, dev=0x1209, revid=0x09 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[10]: type 1, range 32, base ffaff000, size 12 > map[14]: type 1, range 32, base 0000ef00, size 6 > map[18]: type 1, range 32, base ffac0000, size 17 > >[...] > >pci0: unknown card (vendor=0x8086, dev=0x1209) at 14.0 irq 11 ^^^^^ And David Greenman responds: > Don't know what that is, but's not a part that is supported by > the fxp driver. It would help if you could find out the part > number (8255X isn't sufficient since it isn't really just one > series - some of the parts are similar, and others are > completely different). Yes, sorry, "8255X" was a little vague, wasn't it? It appears to be an 82559ER -- see also http://developer.intel.com/design/network/82559er.htm Jim Shankland NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message