Why KDE doesn't init if dhcpcd is running?

Davigetto · 2007-10-02 22:23:42

Hello, I have had a problem that was the following:

1- I start KDE.
2- I connect to wireless using dhcpcd.
3- I logout and come in KDE again and KDE doesn't work.

The solution for this problem was adding "ifconfig lo up" to rc.local, but I can't understand why dhcpcd makes KDE stop working.

Can anyone explain me the reasons?

If you need more information, please tell it to me and I will post it.

Greetings.

Lone_Wolf · 2007-10-03 08:26:08

While i don't know why that happens, lo is normally brought up by rc.conf .
That you have to to bring lo up manually/rc.local, suggests your network setup is incorrect.

Please post the networking and daemons sections of /etc/rc.conf .

Davigetto · 2007-10-04 20:18:56

Network section:

lo="lo 127.0.0.1"
eth0="dhcp"
eth1="dhcp"
INTERFACES=(lo eth0 eth1)
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

Daemon Section:

DAEMONS=(syslog-ng !network hal hwd @alsa ipw3945d !dhcdbd !networkmanager !fam autowifi !autofs @laptop-mode kdm !gdm !entranced !netfs !crond)

Greetings

hacosta · 2007-10-05 01:03:45

the network daemon is the one in charge of bringing up the lo interface, if you don't want to wait for dhcp on the other interface you could do something like

INTERFACES=(lo !eth0 !eth1)

Arch Linux

#1 2007-10-02 22:23:42

Why KDE doesn't init if dhcpcd is running?

#2 2007-10-03 08:26:08

Re: Why KDE doesn't init if dhcpcd is running?

#3 2007-10-04 20:18:56

Re: Why KDE doesn't init if dhcpcd is running?

#4 2007-10-05 01:03:45

Re: Why KDE doesn't init if dhcpcd is running?

Board footer