eth0: waiting for carrier...

vito_spatafore · 07-24-2016, 12:15 PM

few seconds, booting stalled at eth0 : waiting for carrier, then

timed out,

dhcpcd exited,

my system >>> slackware32,kernel huge,with Xfce and new KDE ...

thanks

slacker1337 · 07-24-2016, 12:17 PM

Are you attempting to connect via wireless or ethernet cable?

vito_spatafore · 07-24-2016, 12:27 PM

in fact WiFi (connectioneditor/networkmanager) is working flawless ...

but ...

I got that feel that I'm wasting seconds on that ...

drmozes · 07-24-2016, 12:27 PM

Quote:

Originally Posted by vito_spatafore

few seconds, booting stalled at eth0 : waiting for carrier, then

timed out,

dhcpcd exited,

my system >>> slackware32,kernel huge,with Xfce and new KDE ...

thanks

Try upgrading to the new network-scripts from -current, or just edit your /etc/rc.d/rc.inet1
All that change does is add "-L" to the dhcpcd operators, which you can do like this:

Code:

sed -i 's?/sbin/dhcpcd -t ?/sbin/dhcpcd -Lt ?g' /etc/rc.d/rc.inet1

You also might want to increase the timeout. If the machine is hard wired to a network port, try setting the timeout to "0". this is what I do for my ARM machines. If you do this stuff manually, on my machines dhcpcd will pick up an IP immediately if I run dhcpcd again. I have no idea what is wrong with this, so I settled for this work around.

kingbeowulf · 07-24-2016, 12:33 PM

On one of the laptops here, during boot, it tries to connect to eth0 (wired) then times out. After which networkmanger finally loads and connects via wifi (wlan0). I think this happens since the system network scripts in /etc/rc.d are run first THEN rc.networkmanager gets run toward the end of the boot process. During installation I had a wired connection for PXE boot and NFS installation and I told the installer to set up the network.

When you installed Slackware, did you tell setup you run the network configuration script (netconfig)?

slacker1337 · 07-24-2016, 12:48 PM

If you're using networkmanager to handle your wireless card, why not just turn off rc.inet1?

vito_spatafore · 07-24-2016, 12:58 PM

Quote:

Originally Posted by slacker1337

why not just turn off rc.inet1?

how pal , how ?

tia !

kingbeowulf · 07-24-2016, 01:01 PM

as root

chmod -x /etc/rc.d/rc.inet1

vito_spatafore · 07-24-2016, 01:03 PM

thx a lot folks ! we will see what happens or restart ...

STDOUBT · 07-24-2016, 01:09 PM

vito_spatafore,
The easy fix for this, and I believe, the proper fix is to change the settings for eth0 in /etc/rc.d/rc.inet1.conf as below

from:

Code:

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

to:

Code:

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

I believe this returns the conf file to it's state prior to running netconfig.

Alien Bob · 07-24-2016, 01:58 PM

Quote:

Originally Posted by kingbeowulf

as root

chmod -x /etc/rc.d/rc.inet1

BAD idea.
Tat script does more than you think, it also sets up your loopback. You disable its interface configuration by editing rc.inet1.conf and removing any interface parameters in it, or replace the whole .conf file with the original.

vito_spatafore · 07-24-2016, 05:12 PM

^
not at all !

Quote:

BAD idea

Momentarily turn off rc.inet1 did the trick !

************************************************

why do I have 3 rc.inet1 ?

thanks

Richard Cranium · 07-24-2016, 05:30 PM

Is that a trick question?

montagdude · 07-24-2016, 06:41 PM

If you don't have ethernet connected and you just want to decrease the timeout, you can change DHCP_TIMEOUT in /etc/rc.d/rc.inet1. The default is 10 seconds.

Alien Bob · 07-25-2016, 06:15 AM

Quote:

Originally Posted by Richard Cranium

Is that a trick question?

Not worth answering I guess... not a trick question but a total lack of understanding.