Let's follow the GUI guide. Firstly, we have to gather all the necessary information:
We can get our IP by running ip a and looking for an entry that says link/ether. Below it, we should see one of the following: inet 192.168.0.10/24 or inet6 fe80::a00:27ff:fe76:1e71/64. Source.
Let's find out our getaway address and network interface name. Run ip route get ...
resolution on a system76 lemur6:
grab a copy of the latest r8168 driver (or download it via another computer and put it on USB storage)
Install that driver (will automatically regenerate initramfs kernel image with integrated driver)
dpkg -i r8168-dkms_8.047.02-...
I have searched many places and many resources for the required but not found firmware files iwlwifi-so-a0-hr-b0-XX.ucode where XX is any number from 39 to 63 inclusive. From your dmesg:
[ 12.810257] iwlwifi 0000:00:14.3: no suitable firmware found!
[ 12.810259] iwlwifi 0000:00:14.3: minimum version required: iwlwifi-so-a0-hr-b0-39
[ 12.810260] iwlwifi ...
After days of research on the web and trying different potential solutions, I have finally found the solution. It's plain and simple:
sudo apt install linux-oem-20.04d
As an issue in a github repository working on drivers indicates (https://github.com/lwfinger/rtw89/issues/75), the OEM variant of Ubuntu 20.04 does contain the drivers already. I tried it, ...
If the interface exists in /etc/network/interfaces NM won't manage it. So, just comment out the lines pertaining to enp3s0 if you want NM to manage the connection.
Next try: $ systemctl list-unit-files --state=disabled | grep NetworkManager to check if it's disabled. If it is, $ systemctl enable NetworkManager and systemctl NetworkManager start
I saw this and in my case switched nics which led to it being disabled. So, I had an existing static config but for the wrong interface. Once I got the interface name right in 01-network-manager-all.yaml I was all set.
I've had issues connecting to my Asus ROG g15 via Ethernet as well.
The Realtek driver in the kernel does not recognize this vendor ID.
This patch enables it but might take a while to be backported to other stable releases:
Here is what fixed the same problem for me (AndreaNoboli's answer sadly didn't help):
check /etc/NetworkManager/NetworkManager.conf and /etc/NetworkManager/conf.d/ to see if there's a managed=false entry which could be changed.
I got it from an only tangentially related issue elsewhere: https://access.redhat.com/discussions/6278791, but it worked perfectly ...
If you have connected both your desktop and laptop with an Ethernet cable and did not set up any specific IP addresses, both machines probably use randomly assigned "autoconfiguration" IP addresses, ie. addresses from the range 169.254.x.x. You need to check on both machines what addresses they have.
On Windows machine, type the following in the ...
I found a new solution for ubuntu 20.04 LTS on a mbp using a thunderbolt2 to ethernet connection, where the other answers
were not working very well.
I tried the commands:
modprobe -r <ethernet-driver>
modprobe -i <ethernet-driver>
in both the following systemd locations as listed in previous answers, but it still wasn't working.
Looks like the issue was the Netplan renderer of NetworkManager. After switching to networkd, I got the results I was looking for:
2: softether: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 40:6c:XX:XX:4a:93 brd ff:ff:ff:ff:ff:ff
Here's my new /etc/netplan/01-network-manager-all....