| View previous topic :: View next topic |
| Author |
Message |
Fulgurance
Veteran
Joined: 15 Feb 2017
Posts: 1199
|
 Posted: Sat Feb 24, 2018 7:23 am Post subject: Ethernet don't work |
 |
|
Hello, normally, i use only my wifi, because i never have success to make it work my ethernet device. Now, i've decided to to try to make it work.
But don't know totally what i must activate on my kernel. I have already tried many times without success.
Can you help me please ?
Config:
| Code: | fulgurance@msi-gs73vr-6rf ~ $ sudo lspci
Mot de passe :
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 07)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 530 (rev 06)
00:14.0 USB controller: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller (rev 31)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-H Thermal subsystem (rev 31)
00:16.0 Communication controller: Intel Corporation Sunrise Point-H CSME HECI #1 (rev 31)
00:17.0 SATA controller: Intel Corporation Sunrise Point-H SATA Controller [AHCI mode] (rev 31)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #1 (rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #5 (rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #9 (rev f1)
00:1d.5 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #14 (rev f1)
00:1d.6 PCI bridge: Intel Corporation Sunrise Point-H PCI Express Root Port #15 (rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-H LPC Controller (rev 31)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-H PMC (rev 31)
00:1f.3 Audio device: Intel Corporation Sunrise Point-H HD Audio (rev 31)
00:1f.4 SMBus: Intel Corporation Sunrise Point-H SMBus (rev 31)
01:00.0 VGA compatible controller: NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile 3GB] (rev a1)
3c:00.0 Non-Volatile memory controller: Toshiba America Info Systems NVMe Controller (rev 01)
3d:00.0 Ethernet controller: Qualcomm Atheros Killer E2400 Gigabit Ethernet Controller (rev 10)
3e:00.0 Network controller: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter (rev 32) |
|
|
| Back to top |
|
 |
mike155
Advocate
Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany
|
| Posted: Sat Feb 24, 2018 9:41 am Post subject: |
|
|
Does this post (especially the echo statement) solve your problem?
Last edited by mike155 on Sat Feb 24, 2018 9:50 am; edited 1 time in total |
|
| Back to top |
|
|
Marcih
Apprentice
Joined: 19 Feb 2018
Posts: 213
|
| Posted: Sat Feb 24, 2018 9:49 am Post subject: Re: Ethernet don't work |
|
|
Hi Fulgurance,
I assume the lspci output you posted is from your actual machine, and not the MinimalCD. It looks like you already have the driver either compiled in or loaded as a module. Could you elaborate on what exactly it is that's not working, what you've tried so far and also post the output of ifconfig -a to see whether the interface is being recognized and find /sys | grep devices.*3d:00.0 to see what the name of the driver is (to check if there have been any issues bringing up the interface in dmesg).
EDIT:
Nevermind, see post above and try that first (I guess going through the steps would've arrived at the same point eventually but eh).  |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54220
Location: 56N 3W
|
| Posted: Sat Feb 24, 2018 12:44 pm Post subject: |
|
|
Fulgurance,
You need the alx driver. It was added to the kernel around 4.4 or so.
| Code: | │ Symbol: ALX [=n] │
│ Type : tristate │
│ Prompt: Qualcomm Atheros AR816x/AR817x support │
│ Location: │
│ -> Device Drivers │
│ -> Network device support (NETDEVICES [=y]) │
│ -> Ethernet driver support (ETHERNET [=y]) │
│ (1) -> Atheros devices (NET_VENDOR_ATHEROS [=y]) │
│ Defined at drivers/net/ethernet/atheros/Kconfig:64 │
│ Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_ATHEROS [=y] && PCI [=y] |
The prompt will be hidden until the Depends on: is true.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
|
| Back to top |
|
|
Fulgurance
Veteran
Joined: 15 Feb 2017
Posts: 1199
|
| Posted: Mon Feb 26, 2018 4:49 pm Post subject: |
|
|
Now, i have enabled Qualcomm Atheros AR816x/AR817x support and have doing sudo modprobe alx.
I have configuring my /etc/conf.d/net file for use ethernet, make symbolic link with sudo ln -sf /etc/init.d/net.lo /etc/init.d/net.enp61s0 and reboot.
But when i start ping test:
I think my ethernet connection don't use dhcpcd... no idea? |
|
| Back to top |
|
|
ct85711
Veteran
Joined: 27 Sep 2005
Posts: 1791
|
| Posted: Mon Feb 26, 2018 5:08 pm Post subject: |
|
|
Ok, you have the interface, but does it have an IP address? (An 169.254.*.* address is an APIPA trash address, so wouldn't be useful.)
You can easily check with ifconfig or ip add, both will tell you what your interface ip address is (if it has one). An alternative, is ping an actual ip address like 8.8.8.8 (google's public dns server). If that works, you just need to setup your /etc/resolv.conf to list a nameserver to use.
The resolv.conf, tells your system who to use to convert the www.google.fr to an ip address. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54220
Location: 56N 3W
|
| Posted: Mon Feb 26, 2018 5:13 pm Post subject: |
|
|
Fulgurance,
One step at a time. Putting it all together, then testing 'end to end ' is not helpful.
We can't tell which bit is broken.
First, Are there any errors on the command line or at the end of dmesg.
If so, stop there and quote them here. Nothing else will work until the errors are resolved.
If step 1 works, step 2 is to look at Can you see your wired interface?
If not, step 1 was either incorrect, or required but not sufficient.
Provided the interface appears in step 2, make a note of its name and feed it to dhcpcd
| Code: | | dhcpcd <interface_name> |
This should get you an ip address.
look in As long as the IP adddress does not start 169, you are good.
At this point, if you have an two IP addresses in the same subnet, one wired and one wireless, your connectivity is likely to be horribly broken.
That's a feature. It can be fixed.
Until you can complete the above steps, in order, successfully, nothing else matters.
Build on what you know works.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Fulgurance
Veteran
Joined: 15 Feb 2017
Posts: 1199
|
| Posted: Mon Feb 26, 2018 6:41 pm Post subject: |
|
|
| Code: | fulgurance@msi-gs73vr-6rf ~ $ sudo dhcpcd enp61s0
sending commands to master dhcpcd process
fulgurance@msi-gs73vr-6rf ~ $ ifconfig
enp61s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.55 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::9429:69de:608e:e92 prefixlen 64 scopeid 0x20<link>
ether 4c:cc:6a:80:14:e2 txqueuelen 1000 (Ethernet)
RX packets 30 bytes 2866 (2.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 935 bytes 82059 (80.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Boucle locale)
RX packets 1104 bytes 88336 (86.2 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1104 bytes 88336 (86.2 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp62s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.30 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::7b25:a1dc:72d5:4508 prefixlen 64 scopeid 0x20<link>
ether 9c:b6:d0:0e:57:d1 txqueuelen 1000 (Ethernet)
RX packets 415972 bytes 291357417 (277.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 440255 bytes 61029577 (58.2 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
fulgurance@msi-gs73vr-6rf ~ $ ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
link/sit 0.0.0.0 brd 0.0.0.0
3: enp61s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 4c:cc:6a:80:14:e2 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.55/24 brd 192.168.1.255 scope global enp61s0
valid_lft forever preferred_lft forever
inet6 fe80::9429:69de:608e:e92/64 scope link
valid_lft forever preferred_lft forever
4: wlp62s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 9c:b6:d0:0e:57:d1 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.30/24 brd 192.168.1.255 scope global wlp62s0
valid_lft forever preferred_lft forever
inet6 fe80::7b25:a1dc:72d5:4508/64 scope link
valid_lft forever preferred_lft forever |
But when i disable wpa connection:
| Code: | fulgurance@msi-gs73vr-6rf ~ $ sudo dhcpcd enp61s0
sending commands to master dhcpcd process
fulgurance@msi-gs73vr-6rf ~ $ ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
link/sit 0.0.0.0 brd 0.0.0.0
3: enp61s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 4c:cc:6a:80:14:e2 brd ff:ff:ff:ff:ff:ff
4: wlp62s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 9c:b6:d0:0e:57:d1 brd ff:ff:ff:ff:ff:ff
fulgurance@msi-gs73vr-6rf ~ $ ifconfig
enp61s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 4c:cc:6a:80:14:e2 txqueuelen 1000 (Ethernet)
RX packets 34 bytes 3112 (3.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1512 bytes 134125 (130.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 17
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1 (Boucle locale)
RX packets 1184 bytes 94240 (92.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 1184 bytes 94240 (92.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlp62s0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 9c:b6:d0:0e:57:d1 txqueuelen 1000 (Ethernet)
RX packets 440132 bytes 311443733 (297.0 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 454623 bytes 62683416 (59.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
fulgurance@msi-gs73vr-6rf ~ $ ip add
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: sit0@NONE: <NOARP> mtu 1480 qdisc noop state DOWN group default qlen 1
link/sit 0.0.0.0 brd 0.0.0.0
3: enp61s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 4c:cc:6a:80:14:e2 brd ff:ff:ff:ff:ff:ff
4: wlp62s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
link/ether 9c:b6:d0:0e:57:d1 brd ff:ff:ff:ff:ff:ff |
Is it good ? But just help me for resolv.conf file, i haven't any knowledges about internet configuration. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54220
Location: 56N 3W
|
| Posted: Mon Feb 26, 2018 7:25 pm Post subject: |
|
|
Fulgurance,
That's good. Everything I asked you to test worked.
Go into /etc/rc.conf and read the comment above | Code: | | #rc_depend_strict="YES" |
The default setting is to require that all your network interfaces are working before the network service is considered to be working.
With a laptop, you may use any one interface.
You probably want | Code: | | rc_depend_strict="NO" |
here.
Now things that need the network will work when either interface works.
Both are not required.
When both interfaces are in use, routing may get confused if their addresses are in the same subnets.
Look in
You will have a set of routes via each interface.
The kernel routing works by matching routing rules from the bottom of the table.
The first match is used to route the packet.
default matches all packets, so how does having two default routes work?
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
Fulgurance
Veteran
Joined: 15 Feb 2017
Posts: 1199
|
| Posted: Mon Feb 26, 2018 7:55 pm Post subject: |
|
|
I have set:
| Code: | | rc_depend_strict="NO" |
But:
| Quote: | fulgurance@msi-gs73vr-6rf ~ $ sudo wpa_cli
Mot de passe :
wpa_cli v2.6
Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Selected interface 'wlp62s0'
Interactive mode
> list_network
network id / ssid / bssid / flags
0 Redmi any [DISABLED]
1 Fulgurance-5GHz any [DISABLED]
> q
fulgurance@msi-gs73vr-6rf ~ $ ping www.google.fr
ping: www.google.fr: Temporary failure in name resolution
fulgurance@msi-gs73vr-6rf ~ $ ping www.google.fr
ping: www.google.fr: Temporary failure in name resolution
fulgurance@msi-gs73vr-6rf ~ $ sudo dhcpcd enp61s0
sending commands to master dhcpcd process
fulgurance@msi-gs73vr-6rf ~ $ ping www.google.fr
ping: www.google.fr: Temporary failure in name resolution
fulgurance@msi-gs73vr-6rf ~ $ sudo ping www.google.fr
ping: www.google.fr: Temporary failure in name resolution
fulgurance@msi-gs73vr-6rf ~ $ ping www.google.fr
ping: www.google.fr: Temporary failure in name resolution
fulgurance@msi-gs73vr-6rf ~ $ ping www.google.fr
ping: www.google.fr: Temporary failure in name resolution
fulgurance@msi-gs73vr-6rf ~ $ ip route show
fulgurance@msi-gs73vr-6rf ~ $ sudo ip route show
fulgurance@msi-gs73vr-6rf ~ $ sudo wpa_cli
wpa_cli v2.6
Copyright (c) 2004-2016, Jouni Malinen <j@w1.fi> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Selected interface 'wlp62s0'
Interactive mode
> enable_network 1
OK
<3>CTRL-EVENT-SCAN-STARTED
<3>CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
<3>CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
<3>CTRL-EVENT-REGDOM-CHANGE init=BEACON_HINT type=UNKNOWN
<3>CTRL-EVENT-SCAN-RESULTS
<3>SME: Trying to authenticate with ac:84:c9:5f:a3:d4 (SSID='Fulgurance-5GHz' freq=5200 MHz)
<3>Trying to associate with ac:84:c9:5f:a3:d4 (SSID='Fulgurance-5GHz' freq=5200 MHz)
<3>Associated with ac:84:c9:5f:a3:d4
<3>CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
<3>CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=FR
<3>WPA: Key negotiation completed with ac:84:c9:5f:a3:d4 [PTK=CCMP GTK=CCMP]
<3>CTRL-EVENT-CONNECTED - Connection to ac:84:c9:5f:a3:d4 completed [id=1 id_str=]
> q
fulgurance@msi-gs73vr-6rf ~ $ sudo ip route show
default via 192.168.1.254 dev wlp62s0 src 192.168.1.30 metric 304 mtu 1500
192.168.1.0/24 dev wlp62s0 proto kernel scope link src 192.168.1.30 metric 304 mtu 1500 |
|
|
| Back to top |
|
|
ct85711
Veteran
Joined: 27 Sep 2005
Posts: 1791
|
| Posted: Mon Feb 26, 2018 8:07 pm Post subject: |
|
|
As I said earlier, the easy way to test if it is a name resolution (dns) issue or routing, is try pinging an ip address (not a name like www.google.com). A easy ip address to test would be 8.8.8.8 or 8.8.4.4. If you can ping either of them, but not say www.google.com; it means the system doesn't know how to translate www.google.com to an ip address (that the internet uses).
To define a dns (name resolution server), you can put in your /etc/resolv.conf
| Code: | nameserver 8.8.8.8
nameserver 8.8.4.4 |
Note: If you don't have an ip address, then doing this wouldn't work to begin with, as the computer isn't connected to the network. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
