cant compile drivers for atheros ar8151

[chili555]

What we have here is a textbook perfect, oh so sweet example of a successful DHCP transaction for your wireless. It tells us nothing about the ethernet.

Please turn off the wireless with the airplane mode switch. Hook up a known working ethernet cable to the computer and the router. Next, run:

sudo service network-manager stop
sudo dhclient enp4s0
cat /var/log/syslog | grep dhclient | tail -n10

Let's see what the ethernet isn't doing as expected.

[the-technomancer]

thanks for the help so far

georgevaio@Georgevaio:~$ cat /var/log/syslog | grep dhclient | tail -n10
Feb 23 22:14:44 Georgevaio dhclient[6367]: bound to 192.168.0.24 -- renewal in 1766 seconds.
Feb 23 22:16:01 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 3 (xid=0x97791352)
Feb 23 22:16:04 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 6 (xid=0x97791352)
Feb 23 22:16:10 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 6 (xid=0x97791352)
Feb 23 22:16:16 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 9 (xid=0x97791352)
Feb 23 22:16:25 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 8 (xid=0x97791352)
Feb 23 22:16:33 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 8 (xid=0x97791352)
Feb 23 22:16:41 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 11 (xid=0x97791352)
Feb 23 22:16:52 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 17 (xid=0x97791352)
Feb 23 22:17:09 Georgevaio dhclient[6726]: DHCPDISCOVER on enp4s0 to 255.255.255.255 port 67 interval 10 (xid=0x97791352)
georgevaio@Georgevaio:~$

[the-technomancer]

what can i do now?

[chili555]

I'm sorry, but we see nothing wrong and therefore fixable. I can offer no explanation as to why the ethernet won't work perfectly.

If your wireless is working well, I'd just use it and compromise. Otherwise, I'd look into any number of alternative devices such as USB ethernet adapters.

I am confident that if Jeremy or the other networking gurus on this forum had any other suggestions, they would have pointed out anything I had overlooked. They are very good about that!