You are not logged in.

#1 2010-01-23 21:08:22

xelados
Member
Registered: 2007-06-02
Posts: 314
Website

netcfg doesn't automatically connect, required to manually load ath5k

Hello. I have an issue with my installation of Arch on my Samsung NC10. I installed netcfg and added profiles to /etc/network.d/ as I'm supposed to. On boot, however, it won't connect to an access point. In fact, it doesn't connect at all unless I manually load the ath5k module as root (when it's already in /etc/rc.conf). After that point, I have to run `netcfg <profile>` twice to get it to work.

The boot error says it can't access private ioctl or something similar.

The first attempt to run netcfg as root after loading ath5k is "Wireless association failed". The second attempt works.

This is rather fishy... is there anything I can do to get this working smoothly?

rc.conf:

#
# /etc/rc.conf - Main Configuration for Arch Linux
#

# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
#   in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="en_US.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="America/Menominee"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"

# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(acpi-cpufreq cpufreq_ondemand !btusb ath5k !sky2 snd_hda_intel snd_pcm_oss)

# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"

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

# 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="dhcp"
eth0="dhcp"
INTERFACES=(!eth0)

# 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.1.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=(dragonair dannywifi)

# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
#   - prefix a daemon with a ! to disable it
#   - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng netfs crond cpufreq hal alsa)

/etc/network.d/dragonair:

CONNECTION="wireless"
DESCRIPTION="Home network, Mike's router"
INTERFACE="wlan0"
SECURITY="wep"
ESSID="dragonair"
KEY="FDDA70BDD37C98A4C5BB64EC77"
DHCP_TIMEOUT="15"
IP="dhcp"
IWCONFIG="essid dragonair"

I'd like to add that I couldn't connect to the access point at all until I added the IWCONFIG line to the profile... This used to work flawlessly but now gives me a lot of issues.

Offline

Board footer

Powered by FluxBB