You are not logged in.
Hi,
It's been some weeks since I posted a problem with my wired connection, the last time was the virtualbox module that was dropping the connection. But I do not have virtualbox anymore and I have a similar problem. I do not have ethernet connection.
From some digging I saw a new package with drivers for e1000e in https://aur.archlinux.org/packages/e1000e-dkms/ but I dont know if I can use them for my specific problem or may cause more harm than good.
Some similar posts I found in the forums refer to a power config related problem but I have all devices "on" (I check with cat /sys/bus/pci/devices/*/power/control), so, I have no idea what is happening or how to solve it.
Thanks in advance. Some extra info:
Complete dmseg: http://pastebin.com/1t2D3UUc
but the problem seems to be:
dmesg:
dmesg |grep e1000e
[ 6.964470] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.5-k
[ 6.964473] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 6.964662] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 7.382613] e1000e: probe of 0000:00:19.0 failed with error -2ip a:
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: wlp0s29u1u2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 54:b8:0a:46:2b:16 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.124/24 brd 192.168.1.255 scope global wlp0s29u1u2
valid_lft forever preferred_lft forever
inet6 fe80::56b8:aff:fe46:2b16/64 scope link
valid_lft forever preferred_lft foreverlspci -vvv:
...
00:19.0 Ethernet controller: Intel Corporation 82578DC Gigabit Network Connection (rev 06)
Subsystem: Acer Incorporated [ALI] Device 8000
Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin A routed to IRQ 20
Region 0: Memory at fbec0000 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at fbef8000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at d880 [size=32]
Capabilities: <access denied>
Kernel modules: e1000e
...lsmod | grep e1000e
lsmod | grep e1000e
e1000e 217088 0
ptp 20480 1 e1000emodinfo e1000e:
modinfo e1000e
filename: /lib/modules/4.2.5-1-ARCH/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko.gz
version: 3.2.5-k
license: GPL
description: Intel(R) PRO/1000 Network Driver
author: Intel Corporation, <linux.nics@intel.com>
srcversion: 79223D5E2B9C94070FE6B1C
alias: pci:v00008086d000015B8sv*sd*bc*sc*i*
alias: pci:v00008086d000015B7sv*sd*bc*sc*i*
alias: pci:v00008086d00001570sv*sd*bc*sc*i*
alias: pci:v00008086d0000156Fsv*sd*bc*sc*i*
alias: pci:v00008086d000015A3sv*sd*bc*sc*i*
alias: pci:v00008086d000015A2sv*sd*bc*sc*i*
alias: pci:v00008086d000015A1sv*sd*bc*sc*i*
alias: pci:v00008086d000015A0sv*sd*bc*sc*i*
alias: pci:v00008086d00001559sv*sd*bc*sc*i*
alias: pci:v00008086d0000155Asv*sd*bc*sc*i*
alias: pci:v00008086d0000153Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000153Asv*sd*bc*sc*i*
alias: pci:v00008086d00001503sv*sd*bc*sc*i*
alias: pci:v00008086d00001502sv*sd*bc*sc*i*
alias: pci:v00008086d000010F0sv*sd*bc*sc*i*
alias: pci:v00008086d000010EFsv*sd*bc*sc*i*
alias: pci:v00008086d000010EBsv*sd*bc*sc*i*
alias: pci:v00008086d000010EAsv*sd*bc*sc*i*
alias: pci:v00008086d00001525sv*sd*bc*sc*i*
alias: pci:v00008086d000010DFsv*sd*bc*sc*i*
alias: pci:v00008086d000010DEsv*sd*bc*sc*i*
alias: pci:v00008086d000010CEsv*sd*bc*sc*i*
alias: pci:v00008086d000010CDsv*sd*bc*sc*i*
alias: pci:v00008086d000010CCsv*sd*bc*sc*i*
alias: pci:v00008086d000010CBsv*sd*bc*sc*i*
alias: pci:v00008086d000010F5sv*sd*bc*sc*i*
alias: pci:v00008086d000010BFsv*sd*bc*sc*i*
alias: pci:v00008086d000010E5sv*sd*bc*sc*i*
alias: pci:v00008086d0000294Csv*sd*bc*sc*i*
alias: pci:v00008086d000010BDsv*sd*bc*sc*i*
alias: pci:v00008086d000010C3sv*sd*bc*sc*i*
alias: pci:v00008086d000010C2sv*sd*bc*sc*i*
alias: pci:v00008086d000010C0sv*sd*bc*sc*i*
alias: pci:v00008086d00001501sv*sd*bc*sc*i*
alias: pci:v00008086d00001049sv*sd*bc*sc*i*
alias: pci:v00008086d0000104Dsv*sd*bc*sc*i*
alias: pci:v00008086d0000104Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000104Asv*sd*bc*sc*i*
alias: pci:v00008086d000010C4sv*sd*bc*sc*i*
alias: pci:v00008086d000010C5sv*sd*bc*sc*i*
alias: pci:v00008086d0000104Csv*sd*bc*sc*i*
alias: pci:v00008086d000010BBsv*sd*bc*sc*i*
alias: pci:v00008086d00001098sv*sd*bc*sc*i*
alias: pci:v00008086d000010BAsv*sd*bc*sc*i*
alias: pci:v00008086d00001096sv*sd*bc*sc*i*
alias: pci:v00008086d0000150Csv*sd*bc*sc*i*
alias: pci:v00008086d000010F6sv*sd*bc*sc*i*
alias: pci:v00008086d000010D3sv*sd*bc*sc*i*
alias: pci:v00008086d0000109Asv*sd*bc*sc*i*
alias: pci:v00008086d0000108Csv*sd*bc*sc*i*
alias: pci:v00008086d0000108Bsv*sd*bc*sc*i*
alias: pci:v00008086d0000107Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000107Esv*sd*bc*sc*i*
alias: pci:v00008086d0000107Dsv*sd*bc*sc*i*
alias: pci:v00008086d000010B9sv*sd*bc*sc*i*
alias: pci:v00008086d000010D5sv*sd*bc*sc*i*
alias: pci:v00008086d000010DAsv*sd*bc*sc*i*
alias: pci:v00008086d000010D9sv*sd*bc*sc*i*
alias: pci:v00008086d00001060sv*sd*bc*sc*i*
alias: pci:v00008086d000010A5sv*sd*bc*sc*i*
alias: pci:v00008086d000010BCsv*sd*bc*sc*i*
alias: pci:v00008086d000010A4sv*sd*bc*sc*i*
alias: pci:v00008086d0000105Fsv*sd*bc*sc*i*
alias: pci:v00008086d0000105Esv*sd*bc*sc*i*
depends: ptp
intree: Y
vermagic: 4.2.5-1-ARCH SMP preempt mod_unload modversions
parm: debug:Debug level (0=none,...,16=all) (int)
parm: copybreak:Maximum size of packet that is copied to a new buffer on receive (uint)
parm: TxIntDelay:Transmit Interrupt Delay (array of int)
parm: TxAbsIntDelay:Transmit Absolute Interrupt Delay (array of int)
parm: RxIntDelay:Receive Interrupt Delay (array of int)
parm: RxAbsIntDelay:Receive Absolute Interrupt Delay (array of int)
parm: InterruptThrottleRate:Interrupt Throttling Rate (array of int)
parm: IntMode:Interrupt Mode (array of int)
parm: SmartPowerDownEnable:Enable PHY smart power down (array of int)
parm: KumeranLockLoss:Enable Kumeran lock loss workaround (array of int)
parm: WriteProtectNVM:Write-protect NVM [WARNING: disabling this can lead to corrupted NVM] (array of int)
parm: CrcStripping:Enable CRC Stripping, disable if your BMC needs the CRC (array of int)And journalctl -b: http://pastebin.com/VzX3jay5
"Not all those who wander are lost" J. R. R. Tolkien
Offline
Are you dual booting? If you are, the other o/s could be leaving the network chip in a strange state (perhaps WOL issue?).
Also are you running with the latest BIOS version for your motherboard?
What are the network port status lights doing while this is happening? Can you try booting without having the network cable attached and then connect it when the system is up?
Offline
Are you dual booting? If you are, the other o/s could be leaving the network chip in a strange state (perhaps WOL issue?).
Also are you running with the latest BIOS version for your motherboard?
What are the network port status lights doing while this is happening? Can you try booting without having the network cable attached and then connect it when the system is up?
No I am not dual booting, I have not the latest BIOS update but in the info for the bios update says nothing about network improvements.
Finally, I check the booting without the cable attached and didn't work. And I notice that the left light is green on even If the cable is not attach...i think is broken somehow and I will need to replace it.
Thanks for the answer.
"Not all those who wander are lost" J. R. R. Tolkien
Offline
And I notice that the left light is green on even If the cable is not attach...i think is broken somehow and I will need to replace it.
Yes that doesn't sound good - that kind of behaviour points to a hardware problem.
Offline
Larckov wrote:And I notice that the left light is green on even If the cable is not attach...i think is broken somehow and I will need to replace it.
Yes that doesn't sound good - that kind of behaviour points to a hardware problem.
Usually I never shutdown my PC, but this weekend I did, and what was my surprise when today the Ethernet connection is working fine. I have no idea why and how, but is working. Any idea why now is working?
Anyway, thank you very much for your time and the trouble.
"Not all those who wander are lost" J. R. R. Tolkien
Offline
Perhaps powering down has reset the hardware somehow?
I have not the latest BIOS update but in the info for the bios update says nothing about network improvements.
Documentation for bios updates doesn't always specifically mention everything that has been changed. You might still want to consider updating to the latest bios if you continue to have trouble.
Glad it is working in any case!
Regards Paul.
Offline