LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Home Forums Tutorials Articles Register
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 11-01-2019, 07:37 AM   #1
CyDFect
LQ Newbie
 
Registered: May 2019
Posts: 11

Rep: Reputation: Disabled
Stuck at "eth0: waiting for carrier" on boot on -current


Whenever I boot up my laptop, I get stuck at
Code:
eth0: waiting for carrier
, and when I'm able to login I have to run
Code:
wpa_supplicant -iwlan0 -B -c/etc/wpa_supplicant.conf
, then
Code:
dhcpcd
. I'm pretty sure this is because I never told /etc/rc.d/rc.inet1 that I want to use wlan0 instead of eth0, but I'm not certain. How would I get wpa_supplicant and dhcpcd to start on boot?

/etc/rc.d/rc.inet1.conf:
Code:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
IPALIASES[0]=""
USE_DHCP[0]="Terminated
 
Old 11-01-2019, 07:51 AM   #2
ehartman
Senior Member
 
Registered: Jul 2007
Location: Delft, The Netherlands
Distribution: Slackware
Posts: 1,674

Rep: Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888Reputation: 888
Quote:
Originally Posted by CyDFect View Post
/etc/rc.d/rc.inet1.conf:
Code:
# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
IPALIASES[0]=""
USE_DHCP[0]="Terminated
At least the last should be USE_DHCP[0]="" as you're not using eth0 at all.
Terminated means there is a terminator PLUG into the eth0 port, so that it will echo probes TO that port.
And then fill in the fields for wlan0 in that config. I do not have any, so cannot tell you how. Anyway, that is different on each system.
 
Old 11-01-2019, 10:51 PM   #3
slac
Member
 
Registered: May 2019
Posts: 265

Rep: Reputation: Disabled
Talking Here's the answer to your question

Hi. I'm going to help you (I hope)

In order to avoid getting stuck at boot time trying to connect through Ethernet do the following step(s):

Edit the file /etc/rc.d/rc.inet1.conf

> Just comment out the lines that were enabled to connect through Ethernet during your Slackware installation.

Just like this:

Code:
# Config information for eth0:
#IPADDR[0]=""
#NETMASK[0]=""
#IPALIASES[0]=""
#USE_DHCP[0]="yes"
#DHCP_HOSTNAME[0]=""

# Config information for eth1:
#IPADDR[1]=""
#NETMASK[1]=""
#IPALIASES[1]=""
#USE_DHCP[1]=""
#DHCP_HOSTNAME[1]=""

# Config information for eth2:
#IPADDR[2]=""
#NETMASK[2]=""
#IPALIASES[2]=""
#USE_DHCP[2]=""
#DHCP_HOSTNAME[2]=""

# Config information for eth3:
#IPADDR[3]=""
#NETMASK[3]=""
#IPALIASES[3]=""
#USE_DHCP[3]=""
#DHCP_HOSTNAME[3]=""

# Default gateway IP address:
#GATEWAY=""
Once those lines are commented you won't get stuck during boot time trying to connect to Ethernet.


NOW! In order to connect to a wireless network using wpa_supplicant during boot time you need to follow this/these step(s):

Edit the file /etc/rc.d/rc.inet1.conf and enable (remove the '#') these lines, OR you can write directly these lines by your own (just like I did):

Code:
IFNAME[4]="wlan0"
USE_DHCP[4]="yes"
WLAN_WPA[4]="wpa_supplicant"
WLAN_WPAWAIT[4]=5
Those lines are pretty explicit. Using wlan0 dev to connect to a wireless network using dhcp trough wpa_supplicant, if the connection is not successful just wait 5 seconds.

NOW! Let's configure which wpa_supplicant config file is going to be used to connect to the wireless network. Edit the file /etc/rc.d/rc.wireless:

Look up for these lines and edit according to your needs, ie:

Code:
WPACONF=${WLAN_WPACONF[$i]:-${WPACONF:="/etc/wpa_supplicant/wpa_supplicant-wlan0.conf"}}
WPAWAIT=${WLAN_WPAWAIT[$i]:-${WPAWAIT:="60"}}
The important line there is WPACONF, there's where you indicate which wpa_supplicant config file you're going to use to connect to the wireless network.

AND THAT'S IT! Let's resume:

Doing the above steps is the same as doing these commands manually:

# wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant/wpa_supplicant-wlan0.conf
# dhcpcd wlan0

... but now they're done automatically at boot time! Hope it works, if you are still in doubt you can ask again.

Last edited by slac; 11-01-2019 at 11:12 PM. Reason: some spell-checking
 
1 members found this post helpful.
Old 11-02-2019, 10:13 AM   #4
igadoter
Senior Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: many, primary Slackware
Posts: 2,717
Blog Entries: 1

Rep: Reputation: 625Reputation: 625Reputation: 625Reputation: 625Reputation: 625Reputation: 625
There is possible switch on your laptop ethernet/wifi. On my laptop this is being set in BIOS: enabling one network interface disables another. So you may have just hardware lock on on your network card: this is why kernel stops and waits. Also you may have a look for kernel boot parameters. There is possible workaround for such lock setting apriopriate boot parameter (there is above 200 of them).
 
  


Reply



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
eth0: waiting for carrier... vito_spatafore Slackware 16 07-28-2016 02:46 PM
Hard Drive Problems: timeout waiting for DMA; error waiting for DMA mintee Linux - Hardware 10 09-21-2007 05:06 AM
My browser, all day today: 'waiting for linuxquestions.org...' ..waiting.. waiting .. GrapefruiTgirl LQ Suggestions & Feedback 18 05-25-2007 05:35 AM
No Carrier Detected when Check Carrier = no jojotx0 Linux - Software 2 06-02-2006 10:52 AM
modem cant connect (log: Waiting for carrier) andavm Linux - Newbie 2 03-29-2004 10:06 PM

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

All times are GMT -5. The time now is 04:05 AM.

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