The appliance is in a 1U form-factor with just a single riser-based slot
(PCIe 2.0).
Thanks for your help with this,
Charles
On 11/15/10 6:14 PM, Jack Vogel wrote:
The way you talked about this at first made me think this was
something new, but its actually
fairly old, its just a quad port 82571, id is 0x10A5, support has been
in the drivers for ages :)
The issue is the hardware not the OS or driver, even if the
motherboard is PCIE 2.0, does it
not have slots that are 1 ?
For server adapters you might consider going 82576 or 82580.
Jack
On Mon, Nov 15, 2010 at 2:38 PM, Charles Owens
<cow...@greatbaysoftware.com <mailto:cow...@greatbaysoftware.com>> wrote:
Well, I believe we have an answer:
http://www.intel.com/support/network/adapter/pro100/sb/CS-030873.htm
The motherboard definitely is PCIe 2.0 . The page suggests these
cards for use with a PCIe2.0 system:
# Intel® PRO/1000 PT Quad Port LP Server Adapter (P/N EXPI9404PTL)
# Intel® Gigabit ET Quad Port Server Adapter (P/N E1G44ET)
# Intel® Gigabit ET2 Quad Port Server Adapter (P/N E1G44ET2)
Notably there's not a PF option shown, so we're going to have to
think about that. But in any case, do you think these models
will function with 8.0? 8.0 plus a patch? .... or is 8.1 the
only option?
Thanks,
Charles
On 11/15/10 4:58 PM, Jack Vogel wrote:
Well, if the system doesnt show the hardware in a PCI scan there
isn't much my driver can do :)
The last line in your log says 'eth0', what's that about?
You could try booting 8.1 64 bit, you can also send me all the
details about the board, just to
make sure I can get the exact one and then I'll try it here. This
is quad port fiber, right? I was
thinking this was PCI ID 0x1527, 82580 adapter. The support is
in HEAD now.
Regards,
Jack
On Mon, Nov 15, 2010 at 1:45 PM, Charles Owens
<cow...@greatbaysoftware.com
<mailto:cow...@greatbaysoftware.com>> wrote:
Jack, I'm afraid that with the card _not_ installed we get
identical pciconf output. We're running 32 bit simply
because that's where we got rolling with our product, and
have not yet made the call to invest in the effort required
to make the jump to 64. Do you think that our being at 32
bit could be a factor here?
So far the same card model has been tested on several of
these server appliances, so I doubt it's a bad-slot situation.
In case it's helpful, I've attached a boot log. Anything
else that I can provide that might help?
Thank you,
Charles
On 11/15/10 3:23 PM, Jack Vogel wrote:
UH, did you do that with the adapter in the system?? I do
not see the ID I
expected
to see. Some reason you're running 32 bit??
Can you run the pciconf with the adapter in and out,
compare and tell me
what its
ID is? All the unidentified devices I see are in the
0x3XXX range and those
are not
network devices.
Maybe its a bad slot?
Jack
On Mon, Nov 15, 2010 at 11:59 AM, Charles
Owens<cow...@greatbaysoftware.com
<mailto:cow...@greatbaysoftware.com>
wrote:
Great... thanks! Please see attached. BTW, the
system is running
8.0-RELEASE-p2 i386 (PAE).
Charles
On 11/13/10 2:24 AM, Jack Vogel wrote:
pciconf -l please, I'll betcha these are the new quad
ports that are in my
next igb driver
update, it would have gone in already but I've been
fighting a bug in the
header split
code.
Show me what the output looks like, and I'll get ya
fixed up, dont worry :)
Jack
On Fri, Nov 12, 2010 at 2:08 PM, Charles Owens<
cow...@greatbaysoftware.com
<mailto:cow...@greatbaysoftware.com>> wrote:
Hello,
We're trying to work with newly purcharsed Intel
EXPi9404PF NICs ("Intel
PRO/1000 PF Quad Port Server Adapter") but they
do not seem to be detected
(no ports showing with 'ifconfig -l'). We're
having no problems with the
2-port version of the same card -- is there a
known issue with the 4-port
version?
We've tried three different cards of this model,
all with same result.
Thanks in advance for any help.
Charles
--
Charles Owens
Great Bay Software, Inc.
_______________________________________________
freebsd-net@freebsd.org
<mailto:freebsd-net@freebsd.org> mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
<mailto:freebsd-net-unsubscr...@freebsd.org>"
_______________________________________________
freebsd-net@freebsd.org <mailto:freebsd-net@freebsd.org>
mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to
"freebsd-net-unsubscr...@freebsd.org
<mailto:freebsd-net-unsubscr...@freebsd.org>"
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
