Find the answer to your Linux question:
Results 1 to 2 of 2
I have my server routing my internet for me. I was tired of the routers, the performance just wasn't there. My setup is as follows: ETH1 is "Ethernet controller: D-Link ...
  1. #1
    Just Joined! wmatthews702's Avatar
    Join Date
    Mar 2009
    Location
    Las Vegas, Nevada
    Posts
    11

    Angry Network card dies on heavy load

    I have my server routing my internet for me. I was tired of the routers, the performance just wasn't there.

    My setup is as follows:
    ETH1 is "Ethernet controller: D-Link System Inc DL2000-based Gigabit Ethernet (rev 0c)" is connected to the DSL, I had it connect to my lan but I figured it might work on the DSL.

    ATH0 "Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)" is connected for the wireless clients.

    ETH0 is "Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)" is connected to the internal network.

    The problem is that anytime there is a load on ETH1 it will just stop. I will have to restart the computer to get it to work again. I don't know what module is being used for the card. It would be helpful to find if anyone can help with that also.

    I also seen a driver for it called the "dl2k" that I can't get to compile. There is also nothing at all in dmesg nor /var/log/messages when it does go down.

    Any help that anyone can contribute will be greatly appreciated.

    Thanks in advance.

    lspci output:
    Code:
    00:00.0 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
    00:00.1 RAM memory: nVidia Corporation C51 Memory Controller 0 (rev a2)
    00:00.2 RAM memory: nVidia Corporation C51 Memory Controller 1 (rev a2)
    00:00.3 RAM memory: nVidia Corporation C51 Memory Controller 5 (rev a2)
    00:00.4 RAM memory: nVidia Corporation C51 Memory Controller 4 (rev a2)
    00:00.5 RAM memory: nVidia Corporation C51 Host Bridge (rev a2)
    00:00.6 RAM memory: nVidia Corporation C51 Memory Controller 3 (rev a2)
    00:00.7 RAM memory: nVidia Corporation C51 Memory Controller 2 (rev a2)
    00:02.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
    00:04.0 PCI bridge: nVidia Corporation C51 PCI Express Bridge (rev a1)
    00:09.0 RAM memory: nVidia Corporation MCP51 Host Bridge (rev a2)
    00:0a.0 ISA bridge: nVidia Corporation MCP51 LPC Bridge (rev a3)
    00:0a.1 SMBus: nVidia Corporation MCP51 SMBus (rev a3)
    00:0a.2 RAM memory: nVidia Corporation MCP51 Memory Controller 0 (rev a3)
    00:0b.0 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
    00:0b.1 USB Controller: nVidia Corporation MCP51 USB Controller (rev a3)
    00:0d.0 IDE interface: nVidia Corporation MCP51 IDE (rev a1)
    00:0e.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
    00:0f.0 IDE interface: nVidia Corporation MCP51 Serial ATA Controller (rev a1)
    00:10.0 PCI bridge: nVidia Corporation MCP51 PCI Bridge (rev a2)
    00:10.1 Audio device: nVidia Corporation MCP51 High Definition Audio (rev a2)
    00:14.0 Bridge: nVidia Corporation MCP51 Ethernet Controller (rev a3)
    00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration
    00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map
    00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller
    00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Miscellaneous Control
    02:00.0 VGA compatible controller: nVidia Corporation GeForce 8400 GS (rev a1)
    03:09.0 Ethernet controller: Atheros Communications Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)
    03:0a.0 Ethernet controller: D-Link System Inc DL2000-based Gigabit Ethernet (rev 0c)
    Last edited by wmatthews702; 03-21-2009 at 05:00 AM. Reason: forgot to add some details.

  2. #2
    Just Joined! wmatthews702's Avatar
    Join Date
    Mar 2009
    Location
    Las Vegas, Nevada
    Posts
    11

    Solved

    For a second I thought that upgrading the kernel didn't work. I had to learn how to make the kernel use the module that I needed for the card.

    After 2 1/2 long days it is finally working.

    There is a module called dl2k that is included in kernels that need to be enabled. You can also download the module from Sourceforge. I didn't have any luck compiling it so I suggest just learning how to compile a kernel. It isn't hard at all.

    I haven't figured out how to blacklist the ipp module that was being used but that can wait until tomorrow.
    Last edited by wmatthews702; 03-21-2009 at 12:34 PM. Reason: Update on it working.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
...