Problem with NetLink BCM5787 Gigabit Ethernet PCI Express

My NetLink BCM5787 Gigabit Ethernet PCI Express card does not work although everything looks pretty well:

From lshw I get:

           *-network
                description: Ethernet interface
                product: NetLink BCM5787 Gigabit Ethernet PCI Express
                vendor: Broadcom Corporation
                physical id: 0
                bus info: pci@0000:03:00.0
                logical name: eth1
                version: 02
                serial: 00:19:99:3c:60:cb
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical
                configuration: broadcast=yes driver=tg3 driverversion=3.94 firmware=5787-v3.26 latency=0 module=tg3 multicast=yes

lsmod:

tg3 142596 0
libphy 31104 1 tg3

lspci:

03:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5787 Gigabit Ethernet PCI Express (rev 02)

ifconfig:

eth0 Link encap:Ethernet HWaddr 00:19:99:58:14:04
          inet addr:192.168.1.42 Bcast:192.168.1.255 Mask:255.255.255.0
          inet6 addr: fe80::219:99ff:fe58:1404/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:3991 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4070 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:3400846 (3.4 MB) TX bytes:666377 (666.3 KB)
          Memory:fc300000-fc320000

eth1 Link encap:Ethernet HWaddr 00:19:99:3c:60:cb
          UP BROADCAST MULTICAST MTU:1500 Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
          Interrupt:16

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:100 (100.0 B) TX bytes:100 (100.0 B)

dmesg:

[ 6.078230] tg3.c:v3.94 (August 14, 2008)
[ 6.078242] tg3 0000:03:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 6.078250] tg3 0000:03:00.0: setting latency timer to 64
[ 6.100093] eth1: Tigon3 [partno(BCM95787) rev b002 PHY(5787)] (PCI Express) 10/100/1000Base-T Ethernet 00:19:99:3c:60:cb
[ 6.100095] eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1]
[ 6.100096] eth1: dma_rwctrl[76180000] dma_mask[64-bit]
....
[ 29.005325] ADDRCONF(NETDEV_UP): eth1: link is not ready

Hm, I can add a static IP. That works, I can see it then wit ipconfig! But RX/TX packets always
is 0. It looks for me as a IRQ problem but from /proc/interrupt I get:

           CPU0 CPU1 CPU2 CPU3
  0: 48293 46517 47988 46983 IO-APIC-edge timer
  1: 709 772 667 721 IO-APIC-edge i8042
  4: 1 0 1 0 IO-APIC-edge
  7: 348 348 350 351 IO-APIC-edge parport0
  8: 1 0 0 0 IO-APIC-edge rtc0
  9: 0 0 0 0 IO-APIC-fasteoi acpi
 16: 1243 1278 1227 1254 IO-APIC-fasteoi nvidia
 18: 8 6 5 4 IO-APIC-fasteoi uhci_hcd:usb2, ehci_hcd:usb4
 19: 0 0 0 0 IO-APIC-fasteoi uhci_hcd:usb3
 20: 24020 25690 24288 25019 IO-APIC-fasteoi uhci_hcd:usb1, uhci_hcd:usb5, ehci_hcd:usb8, HDA Intel
 21: 0 0 0 0 IO-APIC-fasteoi uhci_hcd:usb7
 22: 8 9 8 9 IO-APIC-fasteoi uhci_hcd:usb6
2298: 2170 2113 2218 2272 PCI-MSI-edge eth0
2299: 1 0 1 1 PCI-MSI-edge eth1
2300: 10772 10752 10748 10883 PCI-MSI-edge ahci
NMI: 0 0 0 0 Non-maskable interrupts
LOC: 55812 52234 30900 52372 Local timer interrupts
RES: 45306 43011 24883 26523 Rescheduling interrupts
CAL: 10614 16240 18445 10975 function call interrupts
TLB: 135 122 98 216 TLB shootdowns
TRM: 0 0 0 0 Thermal event interrupts
THR: 0 0 0 0 Threshold APIC interrupts
SPU: 0 0 0 0 Spurious interrupts
ERR: 0

There is a mismatch: In /proc/interrupt the interrupt is redirected to 2299. But ifconfig tells me
that the Interrupt is 16. Could that be the problem? And: How can I solve it.

Any idea?

Regards tunix