lkml.org 
[lkml]   [2011]   [May]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: 2.6.39: kernel igb and e1000e-1.3.17 driver broken?

    On Wed, 25 May 2011, Justin Piszcz wrote:

    > Hello,
    >
    > I recently bought a 4-port Intel NIC (82580)
    >
    > 03:00.0 Ethernet controller: Intel Corporation 82580 Gigabit Network
    > Connection (rev 01)
    > 03:00.1 Ethernet controller: Intel Corporation 82580 Gigabit Network
    > Connection (rev 01)
    > 03:00.2 Ethernet controller: Intel Corporation 82580 Gigabit Network
    > Connection (rev 01)
    > 03:00.3 Ethernet controller: Intel Corporation 82580 Gigabit Network
    > Connection (rev 01)
    >
    > Model name: Intel I340 Server Adapter
    >
    > Which uses this driver:
    > | | <M> Intel(R) 82575/82576 PCI-Express Gigabit Ethernet support | |
    > | | [ ] Direct Cache Access (DCA) Support | |
    >
    > I have tried with and without the DCA support.
    >
    > Out of the four ports in the back, only two work, why is this?
    >
    > [ CARD ]
    > 1 2 3 4
    > X X
    >
    > Where X = working.
    >
    > I've tried the built-in kernel driver from 2.6.39 as well as the latest
    > e1000e driver from sf.net (1.3.17), any thoughts?
    >
    > eth0: negotiated 1000baseT-FD flow-control, link ok <- onboard
    > eth1: negotiated 100baseTx-FD, link ok <- middle port 1
    > eth2: negotiated 1000baseT-FD flow-control, link ok <- middle port 2
    > eth3: no link <- left most port
    > (plugged in)
    > eth4: no link <- right most port
    > (plugged in)
    >
    > The last two parts of each mac addr:
    >
    > eth1 Link encap:Ethernet HWaddr XX:XX:XX:XX:3b:f9 WORKING
    > eth2 Link encap:Ethernet HWaddr XX:XX:XX:XX:3b:fa WORKING
    > eth3 Link encap:Ethernet HWaddr XX:XX:XX:XX:3b:f8 no link
    > eth4 Link encap:Ethernet HWaddr XX:XX:XX:XX:3b:fb no link
    >
    > Thoughts?
    >
    > Justin.
    >

    Whoa,

    Sent this out too early =)
    My mistake, configuration error on user end :)
    Problem was interfaces were not initialized properly (not UP).
    Please disregard, sorry for the noise!

    eth1: negotiated 100baseTx-FD, link ok
    eth2: negotiated 1000baseT-FD flow-control, link ok
    eth3: negotiated 1000baseT-FD flow-control, link ok
    eth4: negotiated 1000baseT-FD flow-control, link ok

    Justin.



    \
     
     \ /
      Last update: 2011-05-26 01:45    [W:0.023 / U:0.028 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site