Linux Lite Forums
Hardware - Support => Network => Topic started by: jerryc on November 11, 2019, 11:30:54 PM
-
Just did an LL install on a Win7 box and now we have no ethernet access. Fortunately, we have wifi working on it.
Here's what I got:
lspci | grep -i ethernet
00:19.0 Ethernet controller: Intel Corporation 82578DC Gigabit Network Connection (rev 06)
I tried googling it, but I couldn't find any simple instructions that work. Intel has a driver here:
https://downloadcenter.intel.com/download/15817/Intel-Network-Adapter-Driver-for-PCIe-Intel-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=55351 (https://downloadcenter.intel.com/download/15817/Intel-Network-Adapter-Driver-for-PCIe-Intel-Gigabit-Ethernet-Network-Connections-Under-Linux-?product=55351)
but, even with some nix experience, I couldn't follow the instructions. They talk about building an .rpm, but I've been a .deb guy for way too many years.
I tried the instructions here:
https://www.intel.com/content/www/us/en/support/articles/000005480/network-and-i-o/ethernet-products.html (https://www.intel.com/content/www/us/en/support/articles/000005480/network-and-i-o/ethernet-products.html)
Here's what I got:
root … > Downloads > e1000e-3.6.0 > src make install
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-66-generic'
Building modules, stage 2.
MODPOST 1 modules
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-66-generic'
Copying manpages...
Installing modules...
make[1]: Entering directory '/usr/src/linux-headers-4.15.0-66-generic'
INSTALL /home/diane/Downloads/e1000e-3.6.0/src/e1000e.ko
At main.c:160:
- SSL error:02001002:system library:fopen:No such file or directory: ../crypto/bio/bss_file.c:72
- SSL error:2006D080:BIO routines:BIO_new_file:no such file: ../crypto/bio/bss_file.c:79
sign-file: certs/signing_key.pem: No such file or directory
DEPMOD 4.15.0-66-generic
make[1]: Leaving directory '/usr/src/linux-headers-4.15.0-66-generic'
Running depmod...
Does anybody know a simple step by step guide to make this work on LL?
Thank you.
-
I've done some more digging. The driver needed is e1000e. It's supposed to be merged into the kernel already now.
I ran:lsmod | grep e1000
and got:
e1000e 249856 0
ptp 20480 1 e1000e
So, it appears as though I already have the proper driver. However, it's still not working.
Any ideas?
Thank you for your help on this.
-
More info. I ran:
lspci -nnk | grep 0200 -A3
and got:
00:19.0 Ethernet controller [0200]: Intel Corporation 82578DC Gigabit Network Connection [8086:10f0] (rev 06)
Subsystem: Acer Incorporated [ALI] 82578DC Gigabit Network Connection [1025:8000]
Kernel driver in use: e1000e
Kernel modules: e1000e
My guess it's probably a simple configuration issue.
Thank you again.
-
Here's more:
route -n
yields:
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 600 0 0 wlp2s0
192.168.1.0 0.0.0.0 255.255.255.0 U 600 0 0 wlp2s0
No IP address shows for the ethernet router.
-
Run and post result: nmcli connection show
TC
-
Per TC, I ran:
nmcli connection show
and got:
FiOS-QW2C2 43e439c1-0deb-4bef-bf29-865d0b1e435a wifi wlp2s0
Wired connection 1 281e9d38-5cd1-32b3-94eb-2a700fffc690 ethernet --
I also ran:
sudo ip addr show
and got:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
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: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether 60:eb:69:de:64:ec brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 1c:65:9d:ee:8a:0a brd ff:ff:ff:ff:ff:ff
inet 192.168.1.195/24 brd 192.168.1.255 scope global dynamic noprefixroute wlp2s0
valid_lft 78792sec preferred_lft 78792sec
inet6 fe80::1854:1802:d39f:9388/64 scope link noprefixroute
valid_lft forever preferred_lft forever
I sure hope some of this is helping. Thank you.
-
Well network manager is not picking up the interface system name. Looks like the kernel is updated for the card but not network manager. Try manually creating a new wired connection in network manager to enp0s25.
https://developer.gnome.org/NetworkManager/stable/nmcli.html (https://developer.gnome.org/NetworkManager/stable/nmcli.html)
I was intending to write on this subject myself, but I found this at tecmint.
https://www.tecmint.com/configure-network-connections-using-nmcli-tool-in-linux/
TC
-
Even more. The relevant output of:
inxi -Fxz:
is:
Network: Card-1: Intel 82578DC Gigabit Network Connection
driver: e1000e v: 3.6.0-NAPI port: e880 bus-ID: 00:19.0
IF: enp0s25 state: down mac: <filter>
Maybe "state: down" is something I can change, like maybe to "state:up."
Sign me up!
-
Try manually creating a new wired connection in network manager to enp0s25.
Tried it. It appears enp0s25 is already showing in the network manager for the wired connection as the same device:
enp0s25 (60:EB:69:DE:64:EC)
Now, I have two connections in network manager not working, wired connection 1 and ethernet collection 1.
Thanks for helping dig into this. I suspect it's something simple, just not easy to find, yet.
-
Neither of these worked, either:
sudo ip link set dev enp0s25 up
sudo /sbin/ifconfig enp0s25 up
-
Are you disconnected from WIFI while attempting to connect from wired? If not disconnect from WIFI and try, or try wired connecting to another computer to test the interface.
TC
-
Are you disconnected from WIFI while attempting to connect from wired? ... disconnect from WIFI and try
Didn't work.
or try wired connecting to another computer to test the interface.
Works fine on same computer with Win7 and has for years.
-
Neither of these worked, either:
sudo ip link set dev enp0s25 up
sudo /sbin/ifconfig enp0s25 up
Did you get any error message or any message at all after running either one of these commands? What did the message say?
-
Did you get any error message or any message at all after running either one of these commands? What did the message say?
Nope. Just new prompts.
Thanks for exploring this, moltke.
-
There are a number of suggestions online for this chipset. Let's work through them one at a time. Some report a fix by having the latest BIOS installed.
Sent from my Mobile phone using Tapatalk
-
Here's more:
sudo lshw -C network
gives, in relevant part:
*-network
description: Ethernet interface
product: 82578DC Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: enp0s25
version: 06
serial: 60:eb:69:de:64:ec
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.12-5 latency=0 link=no multicast=yes port=twisted pair
resources: irq:27 memory:fbec0000-fbedffff memory:fbef8000-fbef8fff ioport:e880(size=32)
I notice the driver version is old, but it's part of the kernel. Not sure if changing it would matter, because the computer is old, too, and changing kernel drivers is a little over my head. If that's what it'll take, that's what I'll do, but i expect there's a simpler solution.
Thanks for reviewing this and thinking about it.
-
I found this:
dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
Somebody said it worked for him. I don't understand it, if I should try it as is, or if some of those things are variables I need to replace, like the username.
I've read updating the driver in the kernel didn't work for several people.
-
Also, output please of:
sudo lshw -C net
and
dmesg | grep -e eth -e e1000
-
I found this:
dracut -f /boot/initramfs-$(uname -r).img $(uname -r)
Somebody said it worked for him. I don't understand it, if I should try it as is, or if some of those things are variables I need to replace, like the username.
I've read updating the driver in the kernel didn't work for several people.
I wouldn't do that at this stage.
-
Thank you for your input.
The computer with the recent LL install is at my gf's, and I'm away from it until next weekend. I'll jump back into this thread when I'm in front of it again.
However, I can make one side comment right now. I've been a xubuntu user for 15+ years, with two short deviations, one to mint, and one to mx linux. I left the both in short order because I found their forums almost useless. This forum, however, has been off the chart phenomenal.
I already loved the OS. Now, I really love it. I'll be converting my own box from xubuntu to LL soon.
Thank you all for the help.
-
You're very welcome.
Sent from my Mobile phone using Tapatalk
-
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.
-
Neither of these worked, either:
sudo ip link set dev enp0s25 up
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)
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)
sudo ifup ETH_Device
Then was it truly usable.
For your system...
sudo ifdown enp0s25 and sudo ifup enp0s25
Might be worth a try -- your not changing anything...
-
...
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.
-
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 ;)
-
Even easier, install the dkms deb package - https://github.com/koljah-de/e1000e-dkms-debian/releases
-
Even easier, install the dkms deb package - https://github.com/koljah-de/e1000e-dkms-debian/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.
-
@jerryc
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.
-
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.
-
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
-
Network Manager can be quirky with things that involve changing some drivers not in a repository kernel version.
I agree. That's why I'd prefer to just do something simple from the command line or edit a config file.
run the following: nmcli connection show
Here's what I got:
NAME UUID TYPE DEVICE
FiOS-QW2C2 43e439c1-0deb-4bef-bf29-865d0b1e435a wifi wlp2s0
Ethernet connection 1 9a0f134d-25df-449e-9b5d-91eb6a5d11d0 ethernet --
Wired connection 1 281e9d38-5cd1-32b3-94eb-2a700fffc690 ethernet --
And then run: nmcli connection up 'Wired connection 1' (or whichever you wish to activate)
I tried it and for Ethernet connection 1, and got:
Error: Connection activation failed: No suitable device found for this connection.
After that, I stopped.
Thank you for your help on this.
For the rest of you following this thread, it may be a while before I can try much else. I just got here, and I have a busy weekend planned, but I will get to all the posts. I really appreciate all the help.
-
Also, output please of:
sudo lshw -C net
In relevant part:
*-network
description: Ethernet interface
product: 82578DC Gigabit Network Connection
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: enp0s25
version: 06
serial: 60:eb:69:de:64:ec
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.12-5 latency=0 link=no multicast=yes port=twisted pair
resources: irq:26 memory:fbec0000-fbedffff memory:fbef8000-fbef8fff ioport:e880(size=32)
and
dmesg | grep -e eth -e e1000
[ 1.323272] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[ 1.323273] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[ 1.323509] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[ 1.510496] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 60:eb:69:de:64:ec
[ 1.510497] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[ 1.510533] e1000e 0000:00:19.0 eth0: MAC: 9, PHY: 9, PBA No: FFFFFF-0FF
[ 1.515662] e1000e 0000:00:19.0 enp0s25: renamed from eth0
[ 2.243320] Modules linked in: hid_generic usbhid hid i915(+) psmouse ahci i2c_algo_bit libahci drm_kms_helper syscopyarea e1000e sysfillrect sysimgblt fb_sys_fops ptp pps_core drm wmi video
Thank you for your help.
-
Some report a fix by having the latest BIOS installed.
I think I'll try that later if nothing else works. The chip works with the bios on win7.
Thank you.
-
run: nmcli dev status
This will show if the correct logical name 'enp0s25' of your device is listed as up.
Here's what I got:
DEVICE TYPE STATE CONNECTION
wlp2s0 wifi connected FiOS-QW2C2
enp0s25 ethernet unavailable --
lo loopback unmanaged --
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.
Checked it. Proper settings for home computer.
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.
Checked it. It's already configured to true.
Thank you. I feel confident we'll get it this weekend.
-
Here's what I got:
DEVICE TYPE STATE CONNECTION
wlp2s0 wifi connected FiOS-QW2C2
enp0s25 ethernet unavailable --
lo loopback unmanaged --
Thank you. I feel confident we'll get it this weekend.
HHMM Unavailable... maybe reseat the cable for kicks..
and still be curious if 'ifup' brings it up..
sudo ifdown enp0s25
then
sudo ifup enp0s25
Check a few commands - if state changes .... Hoping for UP LOL
-
No suitable device was found. The issue is with the driver not working/wrong/ or not installed correctly/ or with the device permissions i/e Network Manager permissions to the device. Network Manager seems to be working properly though.
You can check your /etc/network/interfaces file for eth configuration though I expect all is already there properly.
https://wiki.debian.org/NetworkConfiguration#Setting_up_an_Ethernet_Interface
Your probably going to be stuck re-configuring the driver.
TC
-
No suitable device was found. The issue is with the driver not working/wrong/ or not installed correctly/ or with the device permissions i/e Network Manager permissions to the device. Network Manager seems to be working properly though.
You can check your /etc/network/interfaces file for eth configuration though I expect all is already there properly.
https://wiki.debian.org/NetworkConfiguration#Setting_up_an_Ethernet_Interface
Nope, /etc/network/interfaces only had:
auto lo
iface lo inet loopback
So, I added:
# manual additions to get ethernet to work
auto enp0s25
allow-hotplug enp0s25
iface enp0s25 inet dhcp
Then ran:
sudo ifup enp0s25
And got:
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/enp0s25/60:eb:69:de:64:ec
Sending on LPF/enp0s25/60:eb:69:de:64:ec
Sending on Socket/fallback
DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 3 (xid=0x6ee01246)
DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 5 (xid=0x6ee01246)
...
[about a dozen more tries] ...
DHCPDISCOVER on enp0s25 to 255.255.255.255 port 67 interval 18 (xid=0x6ee01246)
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
Even though we're not there yet, I think this is progress.
Thank you for your help.
-
I take it, the dkms debian driver didn't work?
-
I take it, the dkms debian driver didn't work?
I still have wireless and can get by with that for a while, so I'm hoping for something like a simple config setting to fix it before I try changing a kernel driver, even with a deb package. Maybe I'm being overly cautious, but I'm also concerned, even with a new driver, there's still a config issue somewhere.
Did the readouts you asked for tell you anything?
Thank you for everything.
-
This is awfully dated but have you tried adding: pcie_aspm=off into the kernel parameters? See the old link below:
https://serverfault.com/questions/193114/linux-e1000e-intel-networking-driver-problems-galore-where-do-i-start
TC
-
I have the same problem .Some time it works some times not. lspci | grep -i ethernetI GET
Ethernet controller: Intel Corporation 82567LM-3 Gigabit Network Connection (rev 02)auto loiface lo inet loopback
what ever i place here is not working.
Some times working by remove the ethernet wire and place it back at list 3-5 times.
Then if i restart pc same thing. enp0s25 not working
Working 100% with windows 7 but not with LL or Ubuntu 18
So i stay with wireless stick working 100%