[SOLVED] NetworkManager: Wi-Fi detected but no connection.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't get it. I choose DHCP. And then how do I use NetworkManager?
Try it and see. Takes less faith and energy that a complete reinstall. How did you get to "use" Network Manager this time? How about the last time? Same way! Try and see. Don't be afraid to experiment
Just don't get confused.
DHCP is configuration helper, it is not needed to make connections, but it allows to automate client configuration.
DHCPCD is the actual client which runs in client computer.
DHCPD is server which hands out network information which is then used by clients.
You can use DHCP with manual configuration, but it is not mandatory even with NM.
I suspect that @stf92 has configured DHCP in /etc/rc.d/rc.inet1.conf and has also enabled NetworkManager to start at boot.
This setup fails, as the dhcpcd daemon is started before NetworkManager. This creates a conflict as NetworkManager expects to start the dhcpd daemon.
The solution is to ensure that /etc/rc.d/rc.inet1.conf is empty of any network configuration, as here.
And why not download the 4.19 LTS, put it in /boot and say lilo to use that kernel? What is the necessity of compiling?
On Ubuntu you can not easily download a "4.19 LTS" from kernel.org and just install it. You would have to jump through many hoops to alter the source to comply with Canonical or download it from some repository as a package. As I stated above you can do essentially the same thing by downloading the kernel packages from Slackware Current AND you can also simply download whatever kernel you prefer from kernel.org and with zero hoops, build and install it.
Also as I stated, Current's kernel package is 5.10.27 and will work perfectly for 14.2, taking all of 10 minutes, tops.
The frimware package is in "/a" of that parent directory of the displayed "/k"
That will give you the updated iwlwifi firmware you need, likely even better that 4.19. As for dhcpcd you can run it from any terminal and see what it displays. You can then ping google.com, yahoo.com, your router, your ISP, whatever you like to see if it resolves. If it cannot be found, check "/etc/resolv.conf: with any text editor to see if a valid nameserver is named. If in doubt you can easily add "nameserver 1.1.1.1 which will solve and DNS issue. DHCPCD will likely remove your entry unless you lock it in but we can cross that bridge if and when you get to it. Hint: A simple text file called "resolv.tail" will do that. Ask if you're interested.
Another distinct possibility is simply upgrade to Current. It is called "Alpha" for now but I assure you it is as solid as most distro's Official Releases.
Enorbet, because of compiler & glibc changes , I thought it was best (perhaps paranoid?) practice to compile kernel natively instead of importing binaries compiled in a different slackware version? I am no expert (no coding background - just someone who got fed up with windows 15 years ago and haven't used it since), so I might be wrong. Also, I vaguely (perhaps inaccurately) recall a thread stating one needed to edit one line to get the latest kernels to compile under 14.2? I have have been with current for 5 years (gaming) so again, I never compiled 5.10.x or 5.11.x in 14.2 personally, and could be wrong about that too.
At the risk of being disrespectful I think before attempting a solution we should examine the symptoms. And so I'll quote myself:
Quote:
Originally Posted by stf92
Hi: I have just installed Slackware 14.2 and, during the installation chose NetworkManager (NM). At home I use a wi-fi modem to connect to the Internet. When running Xfce I find the NM icon with a red cross below and the message 'No network connection'. Well, then I click the icon and see my network has been detected. I select it and the system prompts me to enter a password. I begin to write the password but then and before I press the 'Connect' button a message appears saying
Code:
Disconnected.
The network connection has been disconnected.
This is very odd because the network was already disconnected. When finally I press the 'Connect' button what happens? Absolutely nothing. There is no notification saying what the result of the operation was. And the red cross is still there. I find this disconcerting. What can possibly be happening?
One other thing: in the same machine I have Ubuntu running. And it has absolutely no problem with the wi-fi.
How can the system tell me that the network has been disconnected when it has never been connected? Is this not very weird?
Enorbet, because of compiler & glibc changes , I thought it was best (perhaps paranoid?) practice to compile kernel natively instead of importing binaries compiled in a different slackware version? I am no expert (no coding background - just someone who got fed up with windows 15 years ago and haven't used it since), so I might be wrong. Also, I vaguely (perhaps inaccurately) recall a thread stating one needed to edit one line to get the latest kernels to compile under 14.2? I have have been with current for 5 years (gaming) so again, I never compiled 5.10.x or 5.11.x in 14.2 personally, and could be wrong about that too.
Hello biker_rat
I can assure you the kernel from Current will work as is from an "upgradepkg" install. I've done it and actually rebuilt install isos as far back as v13.37 with the Current kernel packages substituted in and they installed and ran fine. The only problems I encountered had nothing to do with the kernel in use but was what Firefox versions would install and work on systems prior to 14.2.
Also after installing as a package there is nothing stopping you from recompiling with your existing gcc though in my experience any serious gain is unlikely, unless you use the HUGE kernel. I don't like the added steps and complexity of an initrd since I don't need it as I don't do full disk encryption, so I use the HUGE kernel but either manually edit (in the past) or (presently) use "make localmodconfig" which essentially makes selections of optioons based on what is currently detected, instructed or for whatever reason is currently running. That makes an accurate, guaranteed to work, and rather small footprint bzImage/vmlinuz.
I have just installed 14.2-current (jul 2020). The kernel is 5.4.50. But with no better results. What is more, the wi-fi modem is not even detected. Under 14.2 a lot of networks were detected, including mine. In what follows I'll be using 14.2-current.
Quote:
Originally Posted by bassmadrigal
Let's gather some info:
Code:
grep '^[[:blank:]]*[^[:blank:]#]' /etc/rc.d/rc.inet1.conf
ls -l /etc/rc.d/rc.networkmanager
cat /etc/NetworkManager/conf.d/00-dhcp-client.conf
Code:
root@darkstar:~# grep '^[[:blank:]]*[^[:blank:]#]' /etc/rc.d/rc.inet1.conf
IPADDR[0]=""
NETMASK[0]=""
IPALIASES[0]=""
USE_DHCP[0]=""
DHCP_HOSTNAME[0]=""
IPADDR[1]=""
NETMASK[1]=""
IPALIASES[1]=""
USE_DHCP[1]=""
DHCP_HOSTNAME[1]=""
IPADDR[2]=""
NETMASK[2]=""
IPALIASES[2]=""
USE_DHCP[2]=""
DHCP_HOSTNAME[2]=""
IPADDR[3]=""
NETMASK[3]=""
IPALIASES[3]=""
USE_DHCP[3]=""
DHCP_HOSTNAME[3]=""
GATEWAY=""
DEBUG_ETH_UP="no"
root@darkstar:~#
root@darkstar:~# ls -l /etc/rc.d/rc.networkmanager
-rwxr-xr-x 1 root root 2674 May 29 2020 /etc/rc.d/rc.networkmanager*
root@darkstar:~# cat /etc/NetworkManager/conf.d/00-dhcp-client.conf
[main]
# Choose a DHCP client below. Upstream recommends internal, but results may vary.
# dhcpcd is the DHCP client usually used by Slackware:
dhcp=dhcpcd
# dhclient is the ISC reference DHCP client, part of the dhcp package:
#dhcp=dhclient
# This is a simple DHCP client that is built into NetworkManager:
#dhcp=internal
root@darkstar:~#
The last file was edited by me. I uncommented dhcpcd and commented out dhclient.
Good, the wlan0 device is unblocked and available, but is disconnected.
Have you configured the wireless connection? You can use 'nmtui' from the command line or, in a GUI, right click on the nm-applet icon and use Edit Connections.
PS - The only machine where I see a p2p-dev-wlan0 device is on a machine that is used to make a VPN connection. Are you also experimenting with a VPN connection?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
