Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I built a new computer and want to install Linux on it. I loaded a couple different flavors and they detect there is a NIC but it won't connect to the network. It looks like it tries and tries but never connects. Network is using DHCP so not getting an address shouldn't be the issue. I figured the drivers might be an issue but the NIC on the mobo didn't have linux drivers so I bought a PCI NIC that people seemed to not have issues with, by searching the internet. I bought a D-Link DGE-530T. I put it in and it's acting the same way. I install windows and the intgrated NIC works fine so it can't be the hardware itself. Anyone use this D-Link card before or anyone have any advice on what to try? Went to the D-Link site to get the latest drivers too.

Also, looking at the README in the drivers folder, it references files that aren't even included so I don't get what that's about.

share|improve this question
Almost all network cards (PCI and internal) should work with a modern Linux kernel. What is your kernel version (found by typing uname -r in a terminal)? – drs Apr 24 '13 at 15:54
Also, make sure your router isn't applying a MAC address filtering that's preventing new wired connections. – drs Apr 24 '13 at 16:12
Last used Ubuntu 12.10 so it would be v3.5. Shouldn't be using MAC filtering as I've never turned it on. My router also only has filtering for wireless connections. – Jarvis Frost Apr 24 '13 at 17:49
@drs, if there were a network issue OP would be having problems on Windows as well. – Bratchley Apr 24 '13 at 18:12
If you see a line with "eth0" in /proc/net/dev then it's not the driver, it's something else. – Keith Apr 24 '13 at 21:44

I'm seeing Linux drivers on the official D-Link Website and it's going back to 2008. If it's a consumer grade NIC that's been out for five years or more, Linux is going to support it out of the box. Something else must be going on.

First things first, It would see if the NIC shows up on lspci, and if it does see if the associated module is loaded ("lspci -v" gives you the first and the module name and "lsmod | grep " tells you if its loaded). If it's recognized and the module for it is loaded, then I would check link status with ethtool and if that shows a link detected and a speed negotiated, try to run "dhclient" on the interface from the command line and try to see if it tells you anything informative at that point.

That's the most advice I can give without knowing what the above results are.

share|improve this answer
Yes the NIC shows up with the lspci command but not when I use lsmod. How can I load it? – Jarvis Frost Apr 25 '13 at 2:19
I take that back. I was looking for something like "dlink" in the lsmod output. In "lspci" the module for both the NICs I have is "r8169". The "lsmod" output for "r8169" is "size: 61650 used by: 0" – Jarvis Frost Apr 25 '13 at 3:04
I do not have ethtools installed but using "cat /sys/class/net/eth0/operstate" it claims the NIC is "up". Running "dhclient" alone does not do anything. Is there any switches or anything I should use? Thank you. – Jarvis Frost Apr 25 '13 at 4:37
To send dhcp requests over a particular interface use something like dhclient eth0 What distro is this BTW? – Bratchley Apr 25 '13 at 11:48
BTW a better sysfs attribute to check is "speed" if it's detected a link and negotiated a speed it should be a non-zero value. – Bratchley Apr 25 '13 at 11:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.