Announcement

Collapse
No announcement yet.

Installed new GbitLAN Card (Intel 82574L) - no network connection

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Installed new GbitLAN Card (Intel 82574L) - no network connection

    Hi there,

    I added a PCI Express LAN interface card to my machine, and am having trouble getting it to work with Jaunty (AM64).

    The card is recognised as "eth2". When I plug in the LAN cable, nothing happens, and Network Manager reports that eth2 is unavailable.

    LSPCI reports the card as the following:
    02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

    I assume that the related driver for this card is Intel e1000e.

    To check if the driver is available I did

    modprobe -l |grep e1000e

    and got

    kernel/drivers/net/e1000e/e1000e.ko

    in which case I assume that the driver is loaded.

    I then started digging in Syslog. At the end of this post, I added what happened after plugging in the LAN cable at this card.

    To me, it looks like the driver is working somehow (Message 2009-05-01 07:00:35 Link is up)
    Then "dhclient" tries to start the DHCP procedure.

    Somewhere, I saw the following message:

    2009-05-01 07:00:37 jaunty kernel [ 1403.805801] 0000:02:00.0: eth2: Detected Tx Unit Hang:


    This leads me to assume that there is something wrong. When I do the same with the on board LAN interface, this is where it starts to get different. The on board LAN controller finally ends up providing a LAN connection.

    eth2 however ends up in a kind of loop until I unplug the network cable.

    I booted Win XP on the same machine (Media Centre Edition SP3) and there, I don't have any issues. This tells me it's not a defective piece of hardware.

    Here I get stuck, I have no idea how to further investigate. Has anybody got an idea what to try next?

    Regards,

    Jens


    Syslog extract:

    2009-05-01 07:00:35 JLPC3 NetworkManager <info> (eth2): device state change: 2 -> 3
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) starting connection 'Auto eth2'
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> (eth2): device state change: 3 -> 4
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled...
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started...
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled...
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete.
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting...
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> (eth2): device state change: 4 -> 5
    2009-05-01 07:00:35 JLPC3 kernel [ 1402.021912] 0000:02:00.0: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 2 of 5 (Device Configure) successful.
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) scheduled.
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete.
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) started...
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> (eth2): device state change: 5 -> 7
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Beginning DHCP transaction.
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> dhclient started with pid 4669
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) complete.
    2009-05-01 07:00:35 JLPC3 dhclient Internet Systems Consortium DHCP Client V3.1.1
    2009-05-01 07:00:35 JLPC3 dhclient Copyright 2004-2008 Internet Systems Consortium.
    2009-05-01 07:00:35 JLPC3 dhclient All rights reserved.
    2009-05-01 07:00:35 JLPC3 dhclient For info, please visit http://www.isc.org/sw/dhcp/
    2009-05-01 07:00:35 JLPC3 dhclient
    2009-05-01 07:00:35 JLPC3 NetworkManager <info> DHCP: device eth2 state changed normal exit -> preinit
    2009-05-01 07:00:35 JLPC3 dhclient Listening on LPF/eth2/00:1b:21:2f:f6:2c
    2009-05-01 07:00:35 JLPC3 dhclient Sending on LPF/eth2/00:1b:21:2f:f6:2c
    2009-05-01 07:00:35 JLPC3 dhclient Sending on Socket/fallback
    2009-05-01 07:00:36 JLPC3 dhclient DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 5
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805801] 0000:02:00.0: eth2: Detected Tx Unit Hang:
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805804] TDH <0>
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805806] TDT <2>
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805808] next_to_use <2>
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805809] next_to_clean <0>
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805810] buffer_info[next_to_clean]:
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805812] time_stamp <1000434df>
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805813] next_to_watch <0>
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805815] jiffies <1000435ef>
    2009-05-01 07:00:37 JLPC3 kernel [ 1403.805816] next_to_watch.status <0>
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805215] 0000:02:00.0: eth2: Detected Tx Unit Hang:
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805219] TDH <0>
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805221] TDT <2>
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805222] next_to_use <2>
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805224] next_to_clean <0>
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805225] buffer_info[next_to_clean]:
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805227] time_stamp <1000434df>
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805228] next_to_watch <0>
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805230] jiffies <1000437e3>
    2009-05-01 07:00:39 JLPC3 kernel [ 1405.805231] next_to_watch.status <0>
    2009-05-01 07:00:41 JLPC3 dhclient DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 11
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806156] 0000:02:00.0: eth2: Detected Tx Unit Hang:
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806159] TDH <0>
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806161] TDT <2>
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806163] next_to_use <2>
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806164] next_to_clean <0>
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806166] buffer_info[next_to_clean]:
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806167] time_stamp <1000434df>
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806169] next_to_watch <0>
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806170] jiffies <1000439d7>
    2009-05-01 07:00:41 JLPC3 kernel [ 1407.806171] next_to_watch.status <0>
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805159] 0000:02:00.0: eth2: Detected Tx Unit Hang:
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805163] TDH <0>
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805165] TDT <2>
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805166] next_to_use <2>
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805168] next_to_clean <0>
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805169] buffer_info[next_to_clean]:
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805170] time_stamp <1000434df>
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805172] next_to_watch <0>
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805173] jiffies <100043bcb>
    2009-05-01 07:00:43 JLPC3 kernel [ 1409.805175] next_to_watch.status <0>
    2009-05-01 07:00:45 JLPC3 NetworkManager <info> (eth2): carrier now OFF (device state 7)
    2009-05-01 07:00:45 JLPC3 NetworkManager <info> (eth2): device state change: 7 -> 2
    2009-05-01 07:00:45 JLPC3 NetworkManager <info> (eth2): deactivating device (reason: 40).
    2009-05-01 07:00:45 JLPC3 NetworkManager <info> eth2: canceled DHCP transaction, dhcp client pid 4669
    2009-05-01 07:00:45 JLPC3 NetworkManager <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> (eth2): carrier now ON (device state 2)
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> (eth2): device state change: 2 -> 3
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) starting connection 'Auto eth2'
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> (eth2): device state change: 3 -> 4
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 1 of 5 (Device Prepare) scheduled...
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 1 of 5 (Device Prepare) started...
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 2 of 5 (Device Configure) scheduled...
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 1 of 5 (Device Prepare) complete.
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 2 of 5 (Device Configure) starting...
    2009-05-01 07:00:48 JLPC3 kernel [ 1415.061926] 0000:02:00.0: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> (eth2): device state change: 4 -> 5
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 2 of 5 (Device Configure) successful.
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) scheduled.
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 2 of 5 (Device Configure) complete.
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) started...
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> (eth2): device state change: 5 -> 7
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Beginning DHCP transaction.
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> dhclient started with pid 4727
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> Activation (eth2) Stage 3 of 5 (IP Configure Start) complete.
    2009-05-01 07:00:48 JLPC3 dhclient Internet Systems Consortium DHCP Client V3.1.1
    2009-05-01 07:00:48 JLPC3 dhclient Copyright 2004-2008 Internet Systems Consortium.
    2009-05-01 07:00:48 JLPC3 dhclient All rights reserved.
    2009-05-01 07:00:48 JLPC3 dhclient For info, please visit http://www.isc.org/sw/dhcp/
    2009-05-01 07:00:48 JLPC3 dhclient
    2009-05-01 07:00:48 JLPC3 NetworkManager <info> DHCP: device eth2 state changed normal exit -> preinit
    2009-05-01 07:00:48 JLPC3 dhclient Listening on LPF/eth2/00:1b:21:2f:f6:2c
    2009-05-01 07:00:48 JLPC3 dhclient Sending on LPF/eth2/00:1b:21:2f:f6:2c
    2009-05-01 07:00:48 JLPC3 dhclient Sending on Socket/fallback
    2009-05-01 07:00:50 JLPC3 kernel [ 1416.732165] 0000:02:00.0: eth2: Link is Down
    2009-05-01 07:00:50 JLPC3 NetworkManager <info> (eth2): carrier now OFF (device state 7)
    2009-05-01 07:00:50 JLPC3 NetworkManager <info> (eth2): device state change: 7 -> 2
    2009-05-01 07:00:50 JLPC3 NetworkManager <info> (eth2): deactivating device (reason: 40).
    2009-05-01 07:00:50 JLPC3 NetworkManager <info> eth2: canceled DHCP transaction, dhcp client pid 4727
    2009-05-01 07:00:50 JLPC3 NetworkManager <info> Policy set 'Auto eth0' (eth0) as default for routing and DNS.

    Tags: None
    • Top
    • Bottom
    #2
    Re: Installed new GbitLAN Card (Intel 82574L) - no network connection

    Do you still have your old network cards in the system? If not edit /etc/udev/rules.d/70-persistent-net.rules and change the MAC address of eth0 to the mac address of your new card. It will then probably work, although you Might need a reboot to get the stupid network-manager to do something. If you have removed network-manager or are fortunate enough that network-manager is behaving as designed and not managing interfaces in /etc/network/interfaces, and if youhave defined eth0 there, which I think you have from the logs, you could run
    sudo invoke-rc.d network stop
    sudo invoke-rc.d network start

    If that seems like a lot of ifs then welcome to the club. The networking situation is absurd.
    • Top
    • Bottom

    Comment

      #3
      Re: Installed new GbitLAN Card (Intel 82574L) - no network connection

      I had the old network adapter still in the system. (It's onboard). I tried your hint, disabled it in the bios and put the new cards MAC address in place. However, after a reboot there was now eth0 showing the same behaviour.

      When I restored the old 70-persistent-net.rules file, re-enabled the On-board LAN and booted Jaunty again,the network manager behaviour changed a bit: When I now plug in a LAN cableat the new card's port, the status of this interfacepermanentlychanges between "eth2:setting network address" and "eth2 not plugged in".
      In the syslog, the same messages appear as I have described in my first posting, so there nothing changes.

      Thus,I assume I am not dealing with a networkmanager problem but rather something "under the hood", such as the e1000e driver

      Regards,

      Jens
      • Top
      • Bottom

      Comment

        #4
        Re: Installed new GbitLAN Card (Intel 82574L) - no network connection

        Which release of Kubuntu are you running and which kernel?
        • Top
        • Bottom

        Comment

          #5
          Re: Installed new GbitLAN Card (Intel 82574L) - no network connection

          I am running Jaunty (9.04)

          uname -a gives me

          Kernel 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 01:58:03 UTC 2009 x86_64 GNU/Linux
          • Top
          • Bottom

          Comment

            #6
            Re: Installed new GbitLAN Card (Intel 82574L) - no network connection

            I Googled e1000e DHCP and found many discussions of this problem. Some of them mentioned patched but I didn't see any that looked particularly promising or applicable to Kubuntu. It does seem that static IP configuration is likely to work.
            • Top
            • Bottom

            Comment

              #7
              Re: Installed new GbitLAN Card (Intel 82574L) - no network connection

              Ok, I tried it with a static IP address. (In the meantime, I have replaced the network manager in KDE by wicd, since network manager would not let me enter a static IP address......)

              I got stuck in the next level then. WICD reports that I am connected to the network. However, there's no traffic at all, neither HTTP to the internet nor NFS to a NAS in the network.

              In the syslog, I found the same TX unit hang issue again. So this problem apparently does not only show up with DHCP, but looks rather like a driver problem, DHCP problems being the first symptom since this is usually the first thing an interface does when it's up.

              In IRC I got the hint to try a newer kernel version. I installed mainline kernel 2.6.29 and 2.6.30 according to https://wiki.ubuntu.com/KernelMainlineBuilds
              The kernel installation procedure worked well and easy. However, even with the latest 2.6.30 the problem was not fixed, so no hope that the problem will fix itself by waiting for Ubuntu 9.10 or so.......








              Extract from Syslog

              2009-05-02 07:56:56 JLPC3 kernel [ 104.168028] ADDRCONF(NETDEV_UP): eth2: link is not ready
              2009-05-02 07:56:56 JLPC3 avahi-daemon[3110] Joining mDNS multicast group on interface eth2.IPv4 with address 192.168.2.220.
              2009-05-02 07:56:56 JLPC3 avahi-daemon[3110] New relevant interface eth2.IPv4 for mDNS.
              2009-05-02 07:56:56 JLPC3 avahi-daemon[3110] Registering new address record for 192.168.2.220 on eth2.IPv4.
              2009-05-02 07:56:59 JLPC3 kernel [ 107.201905] 0000:02:00.0: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
              2009-05-02 07:56:59 JLPC3 kernel [ 107.203740] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready
              2009-05-02 07:57:01 JLPC3 avahi-daemon[3110] Registering new address record for fe80::21b:21ff:fe2f:f62c on eth2.*.
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805164] 0000:02:00.0: eth2: Detected Tx Unit Hang:
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805168] TDH <11>
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805169] TDT <14>
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805171] next_to_use <14>
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805172] next_to_clean <11>
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805174] buffer_info[next_to_clean]:
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805175] time_stamp <ffff4676>
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805176] next_to_watch <11>
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805178] jiffies <ffff4837>
              2009-05-02 07:57:04 JLPC3 kernel [ 111.805179] next_to_watch.status <0>
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805160] 0000:02:00.0: eth2: Detected Tx Unit Hang:
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805163] TDH <11>
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805165] TDT <14>
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805167] next_to_use <14>
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805169] next_to_clean <11>
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805170] buffer_info[next_to_clean]:
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805171] time_stamp <ffff4676>
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805173] next_to_watch <11>
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805174] jiffies <ffff4a2b>
              2009-05-02 07:57:06 JLPC3 kernel [ 113.805176] next_to_watch.status <0>
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805163] 0000:02:00.0: eth2: Detected Tx Unit Hang:
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805166] TDH <11>
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805168] TDT <14>
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805170] next_to_use <14>
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805171] next_to_clean <11>
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805172] buffer_info[next_to_clean]:
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805174] time_stamp <ffff4676>
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805175] next_to_watch <11>
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805177] jiffies <ffff4c1f>
              2009-05-02 07:57:08 JLPC3 kernel [ 115.805178] next_to_watch.status <0>
              2009-05-02 07:57:10 JLPC3 kernel [ 117.729022] eth2: no IPv6 routers present
              2009-05-02 07:57:13 JLPC3 kernel [ 121.169925] 0000:02:00.0: eth2: Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX
              • Top
              • Bottom

              Comment

                #8
                Re: Installed new GbitLAN Card (Intel 82574L) - no network connection

                The only thing I would disagree with is the part about no hope of a fix. The linux kernel itself is continually under development and Intel writes their drivers and submits the to the kernel. It is not unusual for there to be a brief period after Intel makes a change in the hardware in which the drivers have not yet caught up. Keep googling and you will see the solutions evolve.
                • Top
                • Bottom

                Comment

                Previous template Next
                Working...
                X