LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 04-05-2021, 02:44 PM   #31
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~arch
Posts: 7,039

Rep: Reputation: Disabled

DHCP is a network management protocol, DHCPCD is the actual client tool, and DHCPD is server daemon.
 
Old 04-05-2021, 08:55 PM   #32
Gordie
Member
 
Registered: Aug 2007
Location: Nolalu, Ontario, Canada
Distribution: Slackware64
Posts: 759

Rep: Reputation: 291Reputation: 291Reputation: 291
Quote:
Originally Posted by stf92 View Post
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
 
Old 04-05-2021, 09:03 PM   #33
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~arch
Posts: 7,039

Rep: Reputation: Disabled
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.
 
Old 04-05-2021, 09:08 PM   #34
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,582

Rep: Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158
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.
 
Old 04-06-2021, 06:42 AM   #35
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,501

Rep: Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392
Quote:
Originally Posted by stf92 View Post
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.

This is but one example of where you can get the main kernel packages - http://slackware.cs.utah.edu/pub/sla...slackware64/k/

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.

Here is one good location https://slackware.nl/slackware/slackware64-current-iso/

Last edited by enorbet; 04-06-2021 at 06:55 AM.
 
Old 04-06-2021, 08:03 AM   #36
biker_rat
Member
 
Registered: Feb 2010
Posts: 152

Rep: Reputation: 76
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.
 
Old 04-06-2021, 08:40 AM   #37
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,438

Original Poster
Rep: Reputation: 76
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 View Post
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?
 
Old 04-06-2021, 08:56 AM   #38
Emerson
LQ Sage
 
Registered: Nov 2004
Location: Saint Amant, Acadiana
Distribution: Gentoo ~arch
Posts: 7,039

Rep: Reputation: Disabled
How do you know it never connected? It may have made brief connection at startup.

Anyhow, to start from beginning, is your wireless interface even functional? Does it show up in 'ifconfig -a' or 'ip a' or 'iw list'?
 
Old 04-06-2021, 09:46 AM   #39
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,438

Original Poster
Rep: Reputation: 76
Quote:
Originally Posted by Emerson View Post
How do you know it never connected? It may have made brief connection at startup.

Anyhow, to start from beginning, is your wireless interface even functional? Does it show up in 'ifconfig -a' or 'ip a' or 'iw list'?
"How do you know it never connected?": because the NM icon shows a red cross.
Code:
root@darkstar:~# ifconfig -a
eth0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether c8:d3:ff:f6:d7:c7  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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  (Local Loopback)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 94:e9:79:d7:51:37  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@darkstar:~#
It seems like it IS functional (wlan0).
 
Old 04-06-2021, 09:47 AM   #40
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,008

Rep: Reputation: 5557Reputation: 5557Reputation: 5557Reputation: 5557Reputation: 5557Reputation: 5557Reputation: 5557Reputation: 5557Reputation: 5557Reputation: 5557Reputation: 5557
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
 
Old 04-07-2021, 02:25 PM   #41
enorbet
Senior Member
 
Registered: Jun 2003
Location: Virginia
Distribution: Slackware = Main OpSys
Posts: 3,501

Rep: Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392Reputation: 3392
Quote:
Originally Posted by biker_rat View Post
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.
 
Old 04-07-2021, 04:38 PM   #42
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,438

Original Poster
Rep: Reputation: 76
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 View Post
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.
 
Old 04-07-2021, 09:03 PM   #43
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,582

Rep: Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158
That configuration looks good.

Please show the output of
Code:
rfkill
nmcli device status

Last edited by allend; 04-07-2021 at 09:08 PM. Reason: Missed the switch to -current
 
Old 04-08-2021, 07:11 AM   #44
stf92
Senior Member
 
Registered: Apr 2007
Location: Buenos Aires.
Distribution: Slackware
Posts: 4,438

Original Poster
Rep: Reputation: 76
Code:
root@darkstar:~# rfkill
ID TYPE      DEVICE      SOFT      HARD
 0 wlan      phy0   unblocked unblocked
 1 bluetooth hci0   unblocked unblocked
root@darkstar:~# nmcli device status
DEVICE         TYPE      STATE         CONNECTION
wlan0          wifi      disconnected  --
p2p-dev-wlan0  wifi-p2p  disconnected  --
eth0           ethernet  unavailable   --
lo             loopback  unmanaged     --
root@darkstar:~#
 
Old 04-08-2021, 09:18 AM   #45
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,582

Rep: Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158Reputation: 2158
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?
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
NetworkManager wired connection will not autoconnect. connection.autoconnect is set to yes lq_usr_5million Linux - Networking 2 07-25-2020 06:05 PM
[SOLVED] I can't manage NetworkManager via /etc/rc.d/rc.networkmanager script igadoter Slackware 20 03-22-2018 03:17 PM
[SOLVED] NetworkManager enabled but no internet connection at startup philippe972 Slackware 4 07-17-2016 08:45 AM
usb mouse NOT detected, but usb keyboard IS detected mr.anderson Slackware 16 04-26-2006 09:09 PM
CD-Rs not detected, but DVD-Rs detected O(V)eGA_l2el) Fedora 2 04-24-2006 01:18 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 02:17 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration