You are not logged in.
Pages: 1
I've been trying out kdemod on a different computer using the iwl4965 intel wireless card. However, when I try to connect with knetworkmanager, it hangs on 28%, configuring device. Is there something set up wrong or is there a problem with the program. It is a password pretected network with a HEX key if it matters and I am choosing those options in the program.
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"
# 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.utf8"
HARDWARECLOCK="localtime"
TIMEZONE="Canada/Pacific"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
#
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# Scan hardware and load required modules at bootup
MOD_AUTOLOAD="yes"
# Module Blacklist - modules in this list will never be loaded by udev
MOD_BLACKLIST=()
#
# Modules to load at boot-up (in this order)
# - prefix a module with a ! to blacklist it
#
MODULES=(sky2 iwl4965 snd-mixer-oss snd-pcm-oss snd-hwdep snd-page-alloc snd-pcm snd-timer snd snd-hda-intel soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
#
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="reasons"
#
# 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
#
# Note: to use DHCP, set your interface to be "dhcp" (eth0="dhcp")
#
lo="lo 127.0.0.1"
eth0="dhcp"
wlan0="dhcp"
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
INTERFACES=(lo !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-profiles
#
#NET_PROFILES=(main)
#
# -----------------------------------------------------------------------
# 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 dbus !network dhcdbd networkmanager netfs @crond @alsa @acpid @cpufreq @hal @fam kdm)
# End of file
/etc/conf.d/wireless
#
# Settings for wireless cards
#
# For each wireless interface declared in INTERFACES (in rc.conf), declare
# a wlan_${IF} variable that contains the arguments to be passed to
# iwconfig(8). Then list the original interface name in the
# WLAN_INTERFACES array.
#
wlan_wlan0="wlan0"
WLAN_INTERFACES=(wlan0)
Offline
im not sure, but i think i had to put 0x in front of my wep key with knetwork manager, could be wrong
this is a signature
Offline
That doesn't look like it will work because it is a hex key and can only be so many characters long.
Offline
When you use knetwork manager, you don't need to use any of arch's wireless configuration files. I have all those commented out. Check the wiki article, there's instructions in there.
Offline
Wouldn't you still need the wireless one so it knows wlan0 is a wireless device?
Offline
clear away /etc/conf.d/wireless, your rc.conf is alright.
aside from that, which i'm pretty sure of, this is either a device driver issue or KNM's lack of ability to deal with some kinds of secure wireless.
Last edited by schivmeister (2008-01-11 15:58:02)
I need real, proper pen and paper for this.
Offline
It's knetworkmanger's fault. I'm at my college right now and was able to connect just fine. Is there a package you need for WEP keys in general?
Last edited by Reasons (2008-01-11 16:02:06)
Offline
Pages: 1