NIC's after Upgrade from 1.2.2 to 1.2.3 RC2 inoperational

[urba]

Hi at all they use a AAEON FWS-7300 network appliance or similar!

Ok - this unit is a little bit brand new and use a intel pentium M-CPU equipped with intel 910GMLE / 82801FBM Chipset, CF-Card, IDE, SATA and 6 times intel-NIC's with gig-ports.
and at least LCD built in find on: http://www.aaeon.com/PD_Products_Detail_E062ABE0294D40E1B2_DA4C0AB8C74D41D0BD_292C23A7DBF34A63B4_TW_UTF-8.html

The prob is, after install with pfSense 1.2.2 (disabled ACPI in bios) and installed on disk, every thing works fine unless 2 x intel gig NIC's 82574 aren't supportet because driver for
freebsd 7.0 aren't included. Four NIC's (82541) are available.

After an upgrade to 1.2.3 RC2 the device boot normaly and display on console the familiar "Welcome to pfSense 1.2.3-RC2!"
LAN -> em0
WAN -> em1
and so one …

If I try to assign an other interface all six times valid interfaces will displayed with mac and (up) state

** but it's never possible to link up one of the assigned interfaces, although the LED is lit when the cable is in! What damned happen?**

check to ping interface from an other pc - never to reach!
check to ping local host - ok works
check to ping defined IP - ok works
check release - this mean 7.2-Release-p3
check em0 - all seems to be all right but status: no carrier but cable is in and LED lit

Have any one the same strange thing?
I've done this upgrade by an other older hw equipped with intel Pro NIC 10/100 and RTL and this thing works fine all the time!!

!!Hope some one have any idea!! ???

[Dean]

I had the same issue and discovered that disabling RX Checksum on the NICs enabled them to work again.

My devices are fxp0, fxp1 and fxp2.  To disable RX Checksum, I dropped to shell (8), then entered:

ifconfig fxp0 -rxcsum
ifconfig fxp1 -rxcsum
ifconfig fxp2 -rxcsum