Ethernet Not Working, Intel e1000e 82578DC rev 06

[Valtam]

You're very welcome.

Sent from my Mobile phone using Tapatalk

[jerryc]

I wouldn't do that at this stage.

Good. It looked like swatting flies with a sledge hammer to me. We'll save it as a last resort and, hopefully, find a simpler solution instead.

[firenice03]

Neither of these worked, either:

Code:

sudo ip link set dev enp0s25 up

Code:

sudo /sbin/ifconfig enp0s25 up

I'm going to stick my head in for a sec... don't want to muddy the waters..


For kicks I was on my Ubuntu server...

I saw your code previously --- and thought I'd try..  (subbing my interface name - lol)

Code:

sudo ip link set dev enp0s25 up

Didn't do anything for me after I downed my interface.. (Pings wouldn't find a host after attempting to "up")

Only once I upped it via the code below did I pull an IPv4 addy (I think yours pulled IPv6)

Code:

sudo ifup ETH_Device

Then was it truly usable.


For your system...

Code:

sudo ifdown enp0s25 and sudo ifup enp0s25

Might be worth a try -- your not changing anything... 

[jerryc]

...
Might be worth a try -- your not changing anything...

For sure. Ever since I found out the kernel now already has the right driver built it, I've figured it would be something simple like this. If not this, I expect something similarly simple will do it.

Thanks for the input. I'll try it this weekend when I'm back at my sweetie's. Meanwhile, she'd doing fine on the wireless, and her computer is running much faster on LL than it did on Win7. She loves it.

[firenice03]

I've figured it would be something simple like this. If not this, I expect something similarly simple will do it.

More often than not... it usually something simple (atleast it seems to me)  ;D

Thanks for the input. I'll try it this weekend when I'm back at my sweetie's. Meanwhile, she'd doing fine on the wireless, and her computer is running much faster on LL than it did on Win7. She loves it.

LL is GREAT!! for me it has saved all kinds of hardware from scrap.. I run it on a lot 

[Valtam]

Even easier, install the dkms deb package - https://github.com/koljah-de/e1000e-dkms...n/releases

[jerryc]

Even easier, install the dkms deb package - https://github.com/koljah-de/e1000e-dkms...n/releases

Deb package? Now you're singing my song! Those, I know how to do.

And, it looks like there's a newer version than the one in my kernel. Looking forward to trying it this weekend.

Thank you.

[TheDead]

[member=10020]jerryc[/member]
And... maybe a simple thing to try, you know just in case it's not already done.
Try changing the wire itselft and/or the port in the switch/router it's connected too.
You'd be surprise how many times I solved a network issue checking the physical wire because the little plastic clip was broken and the wire was not fully clipping "in" the plug )

Just last week, I solved a VoIP issue for 20 people by changing the main ethernet cable. Connectors looked flaky and seemed to have "pulled" wires and was not "molded". Was also an old CAT5 so I put a CAT6 in its place.

[jerryc]

Try changing the wire itself and/or the port in the switch/router it's connected too.

Thanks, but it works fine with Win7 and has for years. It has to be a config issue of some kind. It's a desktop, not a laptop. Hasn't moved.

I've tried probing for the router's url, but nothing has shown up.

[trinidad]

Network Manager can be quirky with things that involve changing some drivers not in a repository kernel version. It can sometimes behave as if it was not installed as a GUI application prior to such a change.
To ease my mind concerning this run the following again: nmcli connection show

And then run: nmcli connection up 'Wired connection 1' (or whichever you wish to activate)

Then run: nmcli dev status
This will show if the correct logical name 'enp0s25' of your device is listed as up. If all this is correct and there is still no connection make sure your firewall is configured correctly. Perhaps you changed it at some point and forgot about it. If all is well there and you are still not connected you can try changing the ifupdown plugin configuration in your /etc/NetworkManager/NetworkManager.conf file from false to true. I'm not on LL right now so the file may have a different location.
TC