06-10-2020, 01:07 PM
Just trying out Linux-Lite on a desktop 4G RAM, Intel dual-core processor. WIFI did not work out of the box even on the live CD (actually memory stick) - everything else seemed fine but no WIFI - rather I should say that the WIFI actually worked but there was no DNS. So, I could ping 8.8.8.8 for eg but not www.google.com Went ahead and installed to desktop hard drive (500G Seagate) but no change. Install seemed to proceed normally and completed normally but still no DNS. I am not able to test with a cable ethernet link so the WIFI operation is critical. After some googling I found a number of helpful suggestions, none of which worked.
/etc/resolv.conf as installed contained (apart from the warning not to edit it) just 1 line nameserver 127.0.0.53 - this I understand is correct but for some reason, does not work. In the end I edited /etx/resolv.conf and added nameserver 8.8.8.8 and nameserver 8.8.4.4 , saved the file after which DNS came alive and the internet was accessible. However, this did not survive a reboot and the file returned to default even when flagged read-only. Finally I switched on the "Immutable" attribute which stopped the update and I was able to reboot and DNS stayed active.
Hopefully, someone might explain why this problem exists and offer a more correct way of correcting it.
Note: this problem only happens on this machine with Linux-lite - Linux-Mint, MX, Ubuntu and Debian all installed and worked without any problem with DNS.
/etc/resolv.conf as installed contained (apart from the warning not to edit it) just 1 line nameserver 127.0.0.53 - this I understand is correct but for some reason, does not work. In the end I edited /etx/resolv.conf and added nameserver 8.8.8.8 and nameserver 8.8.4.4 , saved the file after which DNS came alive and the internet was accessible. However, this did not survive a reboot and the file returned to default even when flagged read-only. Finally I switched on the "Immutable" attribute which stopped the update and I was able to reboot and DNS stayed active.
Hopefully, someone might explain why this problem exists and offer a more correct way of correcting it.
Note: this problem only happens on this machine with Linux-lite - Linux-Mint, MX, Ubuntu and Debian all installed and worked without any problem with DNS.