Results 1 to 6 of 6
Enjoy an ad free experience by logging in. Not a member yet? Register.
NIC detected but wont connect to network
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.
- Join Date
- Jul 2008
Start with providing needed info from
Don't be worried about the wireless title. Landline will show up in readouts also.I refuse to let fear and fear of others rule my life. It puts my humanity at risk.
Accepting Death is the only way to stay alive.
Sorry I don't have the exact output from the script in the thread you provided but I did type it out and put the output you should be looking for...
lspci > Ethernet controller : D-Link System Inc DGE-530T Gigabit Ethernet Adapter (rev.C1) [Realtek RTL8169] [1186:4302] (rev 10) Kernel driver in use: r8169 Kernel modules: r8169, skge
Ethernet Controller : Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 06) Kernel driver in use: r8169 Kernel modules: r8169
lsmod > Module: r8160 Size: 61650 Used By: 0
dmesg > blank when grep-ing for "firmware"
uname -r > 3.5.0-17-generic
ifconfig > 3 interfaces - 1 loopback (lo), 2 ethernet (eth0, eth1) (looks right)
no wireless interfaces (dont have any)
Using "cat /sys/class/net/eth0/operstate" it claims the NIC is "up".
I did try ubuntu 13.04 and it's still doing the same thing. I thought since it seemed like a DHCP issue, I could just statically assign an address. I did and for all intents and purposes, ubuntu detected it as connected to the network (tray icon shows connected and the message bubble/blip pops up saying "connected"), but it isn't. I can't get to internet and can't ping anything even on my network. I've checked the router setting and there just isn't any reason for this not to work. As I said, I have 2 NICs in the computer now and they both do the exact same thing.
Well I found the answer to my issue and figured I should share. The issue is 32 bit and 64 bit. The networking works fine for 32 bit but not 64. To get it to work for 64 bit you need to enable "IOMMU". You turn this on in the BIOS. I have a Gigabyte board and was able to enable it and fix the issue.