LinuxQuestions.org
Latest LQ Deal: Latest LQ Deals
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 05-06-2020, 05:22 PM   #76
burning
Member
 
Registered: Jan 2020
Location: Canada
Distribution: Slackware
Posts: 172

Original Poster
Rep: Reputation: Disabled

I made sure network manager and wicd are not set to be executable. Running the first command you listed told me that dhcpcd was already running.

Quote:
Polling for DHCP server on interface wlan0:
dhcpcd already running on PID 988 (run/dhcpcd/dhcpcd-wlan0.pid)
But upon restarting it successfully connected! Thank you so much for your patience and help throughout this thread! I really do feel bad about it having had to take this long.

So I take it the problem was just that I had network manager and wicd running everytime?

And one follow up question though, just to check, does PID stand for Process ID? Or is it something else?
 
Old 05-06-2020, 05:55 PM   #77
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Yes, something was causing dhcpcd to run. If it continues to happen after a reboot, we'd need to figure out what's going on, but if it just happened this one time, it's likely related to networkmanager or wicd.

And yes, PID does stand for Process ID.
 
1 members found this post helpful.
Old 05-06-2020, 07:12 PM   #78
chris.willing
Member
 
Registered: Jun 2014
Location: Brisbane, Australia
Distribution: Slackware,LFS
Posts: 635

Rep: Reputation: 399Reputation: 399Reputation: 399Reputation: 399
Been occasionally watching from the sideline - great effort @bassmadrigal
 
1 members found this post helpful.
Old 05-06-2020, 07:22 PM   #79
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,599

Rep: Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887
Quote:
Originally Posted by chris.willing View Post
Been occasionally watching from the sideline - great effort @bassmadrigal
Indeed! And yet again, one more example for me about why I should continue to disconsider those GUI connection helpers and stick with the "standard", simple and transparent Slackware/Linux network configuration.
 
1 members found this post helpful.
Old 05-06-2020, 11:00 PM   #80
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Quote:
Originally Posted by abga View Post
Indeed! And yet again, one more example for me about why I should continue to disconsider those GUI connection helpers and stick with the "standard", simple and transparent Slackware/Linux network configuration.
It really works great on computers that stay with the same wireless network, but if you need to frequently add new networks (if you take your laptop to new locations), NM or wicd certainly makes it easier to add networks to it.
 
1 members found this post helpful.
Old 05-06-2020, 11:16 PM   #81
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,599

Rep: Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887
Quote:
Originally Posted by bassmadrigal View Post
It really works great on computers that stay with the same wireless network, but if you need to frequently add new networks (if you take your laptop to new locations), NM or wicd certainly makes it easier to add networks to it.
I agree with you on the convenience, although I can handle the few WiFi networks I'm connecting to from command line. And, wpa_supplicant also has cli interface I frankly never used, still on my to-do list for learning/using.
It looks like these GUI helpers are not really helping after all, but produce more fallout and cost a lot of support efforts. I had my own experience with wicd and its dumb interface(ncurses), where pressing Enter by mistake messed up my whole networking and had to manually restart the system. And this incomplete "work of art" called NetworkManager should handle exceptions a little bit better, even if its developers are maybe Agile brainwashed and not prioritizing quality, they should at least do some checks and inform the user (it would be nice to handle the problems - remove pid files (leftovers) from the system utilities they make use of).
 
1 members found this post helpful.
Old 05-07-2020, 03:10 PM   #82
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 7,240

Rep: Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932Reputation: 4932
Quote:
Originally Posted by abga View Post
I agree with you on the convenience, although I can handle the few WiFi networks I'm connecting to from command line. And, wpa_supplicant also has cli interface I frankly never used, still on my to-do list for learning/using.
It looks like these GUI helpers are not really helping after all, but produce more fallout and cost a lot of support efforts. I had my own experience with wicd and its dumb interface(ncurses), where pressing Enter by mistake messed up my whole networking and had to manually restart the system. And this incomplete "work of art" called NetworkManager should handle exceptions a little bit better, even if its developers are maybe Agile brainwashed and not prioritizing quality, they should at least do some checks and inform the user (it would be nice to handle the problems - remove pid files (leftovers) from the system utilities they make use of).
Honestly, reasons like these and others on the forum have given me no desire to try and use these programs. I had a bash script I developed years ago (back when it was mostly WEP networks) when I was using a laptop at several friends' houses. I don't think wicd or network manager existed. Eventually, when wpa became more common, I actually wasn't using a laptop and was mostly wired for my ethernet. Once I did have wireless again, using the rc.inet1.conf file just seemed so much easier and would connect automatically on boot, even if I was just runlevel 3.
 
1 members found this post helpful.
Old 06-21-2020, 06:08 AM   #83
burning
Member
 
Registered: Jan 2020
Location: Canada
Distribution: Slackware
Posts: 172

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by bassmadrigal View Post
Yes, something was causing dhcpcd to run. If it continues to happen after a reboot, we'd need to figure out what's going on, but if it just happened this one time, it's likely related to networkmanager or wicd.

And yes, PID does stand for Process ID.
So, since I recently updated from 14.2 to Current, I haven't been able to connect with my wireless automatically at startup. I re-edited my rc.d/rc.inet1.conf and wpa_supplicant.conf files and wpa_supplicant seems to work just fine, the problem seems to arise with dhcpcd wlan0.

On startup, I'm unable to establish successful connections to any websites. Running dhcpcd wlan0 gives the usual "dhcpcd is already running on pid...etc" message. But everything starts to work perfectly fine as soon as I killall dhcpcd and run dhcpcd wlan0 again.

Any idea what's causing this?
 
Old 06-21-2020, 04:41 PM   #84
abga
Senior Member
 
Registered: Jul 2017
Location: EU
Distribution: Slackware
Posts: 1,599

Rep: Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887Reputation: 887
Maybe the new (updated) WiFi driver from the -current kernel.
Try increasing the time dhcpcd waits for obtaining the ip config in rc.inet1.conf
DHCP_TIMEOUT[4]=30
 
2 members found this post helpful.
Old 06-24-2020, 08:48 AM   #85
burning
Member
 
Registered: Jan 2020
Location: Canada
Distribution: Slackware
Posts: 172

Original Poster
Rep: Reputation: Disabled
Actually, For some reason it works fine now? I didn't even need to change the DHCP_TIMEOUT value. It just works again. nvm lol
 
  


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
Fedora 17 being run by a xps m1530 & wireless connectivity is not working pixelhack Linux - Wireless Networking 2 08-27-2012 08:17 PM
Slackware 13 (64 bit) Wireless with WPA2-PSK and WPA Cipher set to AES KrazyKanuk Slackware 3 01-26-2010 05:52 AM
Centos 5.1 bootup stops at Setting up Logical Volume Management - repeatedly tiber Red Hat 6 02-11-2008 12:37 PM
Trouble setting up WPA-PSK in Ubuntu crash75uk Linux - Wireless Networking 1 04-04-2005 03:34 PM
connectivity or not connectivity munkie_poo Linux - Newbie 0 05-07-2004 06:47 AM

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

All times are GMT -5. The time now is 08:16 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