LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Intel Pro/1000 can not go online problem (https://www.linuxquestions.org/questions/linux-networking-3/intel-pro-1000-can-not-go-online-problem-790335/)

shogun1234 02-20-2010 02:13 AM

Intel Pro/1000 can not go online problem
 
env: debian kernel 2.6.31/ gcc 4.x/ hp6910p

I encounter a problem whilst trying to connect online using Intel PRO/1000 nic, but fail. It seems the problem of nic (Intel PRO/1000 'e1000e').

dmesg | grep e10001 shows
Code:

Intel(R) PRO/1000 Network Driver - 1.0.2-k2
PCI INT A -> GSI 22 (level, low) -> IRQ 22
pci_enable_pcie_error_reporting failed 0xfffffffb
irq 29 for MSI/MSI-X

dmesg | grep eth0 shows
Code:

(PCI Express:2.5GB/s:Width x1)
Intel PRO/1000 Network Connection
Mac: 6, PHY: 6, PBA No: 1032ff-0ff
ADDRCONF(NETDEV_UP):eth0: link is not ready

eth0 is configured using dhcp and wilress card (iwl4965), which works correctly, is disabled.

What should I do so that I am able to solve this issue or does any resource/ doc tell how to configure e1000e to enable Intel PRO/1000 nic?

Please let me know if additional information are required.

Thanks for help.

estabroo 02-20-2010 08:03 AM

I occasionally have a problem with my intel pro/1000 nic at boot and to get it working again I just unload the e1000e module then reload it and it works perfect. I think it's actually my switch that is the problem, like it has a hard time negotiating speed or doesn't respond quick enough.

rmmod e1000e
modprobe e1000e

shogun1234 02-26-2010 08:54 AM

Quote:

Originally Posted by estabroo (Post 3870442)
I occasionally have a problem with my intel pro/1000 nic at boot and to get it working again I just unload the e1000e module then reload it and it works perfect. I think it's actually my switch that is the problem, like it has a hard time negotiating speed or doesn't respond quick enough.

rmmod e1000e
modprobe e1000e

After examining the media one by one, eventually I found the root cause. It is the cable problem that causes the packet was blocked, not issue about the dirver.

Thanks again for your help.


All times are GMT -5. The time now is 06:50 PM.