Arch Linux

Atreides

Member

Registered: 2009-11-24

Posts: 60

[solved]Arch gets hung up on "Network" at start up

Arch starts up very fast on my machine, only it takes forever to complete the network step each time. It says [busy] for quite a while, followed then by [failed] with "dhcp: timed out". It takes at least as long as the whole rest of the start up to go through this process each time. I don't really understand why it takes so long, only to fail, as my wifi works perfectly find once I'm actually within Arch.

Here is the networking section of my rc.conf

# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="arch"

# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
#   - prefix an entry in INTERFACES with a ! to disable it
#   - no hyphens in your interface names - Bash doesn't like it
#
# DHCP:     Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#

#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid home" # Unencrypted
INTERFACES=(eth0 wlan0)

 Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
#   - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)

# Enable these network profiles at boot-up.  These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
#   - set to 'menu' to present a menu during boot-up (dialog package required)
#   - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)

Last edited by Atreides (2009-12-23 02:30:54)

anonymous_user

Member

Registered: 2009-08-28

Posts: 3,059

Re: [solved]Arch gets hung up on "Network" at start up

1. Try changing the timeout limit:

http://bbs.archlinux.org/viewtopic.php? … 55#p667755

2. Or try using Wicd:

http://wiki.archlinux.org/index.php/Wicd

3. Or forget about DHCP and setup a static IP

graysky

Wiki Maintainer

From: :wq

Registered: 2008-12-01

Posts: 10,597

Website

Re: [solved]Arch gets hung up on "Network" at start up

+1 for au's third suggestion

---

CPU-optimized Linux-ck packages @ Repo-ck  • AUR packages • Zsh and other configs

cerbie

Member

Registered: 2008-03-16

Posts: 124

Re: [solved]Arch gets hung up on "Network" at start up

I went with #2, and it's all been peachy.

---

"If the data structure can't be explained on a beer coaster, it's too complex." - Felix von Leitner

myxolam

Member

Registered: 2009-09-21

Posts: 12

Re: [solved]Arch gets hung up on "Network" at start up

I have the exact same problem.
Only I am on a desktop  , not wifi.

I will try try setting a shorter timeout as suggested above.
What I would like to know is why does this occur. The network works fine once i am logged in.
How is the network once logged in different from what happens when dhcpd is running at startup?

thanks

Atreides

Member

Registered: 2009-11-24

Posts: 60

Re: [solved]Arch gets hung up on "Network" at start up

Thanks for the help, I ended up installing custom firmware (DD-WRT) on my router (WRT54G) to give myself the ability to assign a static ip to my laptops mac address. In the process of configuring rc.conf right now.

3])

Member

From: Netherlands

Registered: 2009-10-12

Posts: 215

Re: [solved]Arch gets hung up on "Network" at start up

Add a @ to run it as a background daemon in /etc/rc.conf

DAEMONS=(hal syslog-ng [b] @network[/b] @netfs etc...)

That will speed things up as the whole DHCP failure business would be run in the background.

---

“There are two ways of constructing a software design. One way is to make it so simple that there are obviously no deficiencies. And the other way is to make it so complicated that there are no obvious deficiencies.”-- C.A.R. Hoare

jacko

Member

Registered: 2007-11-23

Posts: 840

Re: [solved]Arch gets hung up on "Network" at start up

Backgrounding network can have consequences. Like causing netfs to fail even if network 'did' succeeded. Openntp is another... The list goes on.

I don't really think anything in DAEMONS=() that is a dep of another daemon should be backgrounded at all.

Static IP and the connection is almost instant without backgrounding.

Last edited by jacko (2009-12-24 12:57:07)