Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#9331 - Wpa_supplicant, ndiswrapper and kernel 2.6.23 won't associate on bootup.

Attached to Project: Arch Linux
Opened by dillweed (dillweed) - Friday, 25 January 2008, 02:06 GMT
Last edited by Tobias Powalowski (tpowa) - Saturday, 09 February 2008, 11:00 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture All
Severity Medium
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After updating to kernel 2.6.23, my network card won't associate with my AP when booting. However, I am able to manually associate the card. Commands like /etc/rc.d/network restart don't work.

I'm using a Dlink DWL-520+ pci card and use ndiswrapper with the latest Windows drivers for this card. I have not changed anything on my AP.

lspci -v:

00:08.0 Network controller: Texas Instruments ACX 100 22Mbps Wireless Interface
Subsystem: D-Link System Inc DWL-520+ 22Mbps PCI Wireless Adapter
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at c000 [size=32]
Memory at ef111000 (32-bit, non-prefetchable) [size=4K]
Memory at ef100000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [40] Power Management version 2

ndiswrapper -v:
utils version: '1.9', utils version needed by module: '1.9'
module details:
filename: /lib/modules/2.6.23-ARCH/kernel/drivers/net/wireless/ndiswrapper/ndiswrapper.ko
version: 1.51
vermagic: 2.6.23-ARCH SMP preempt mod_unload 686

wpa_supplicant -v:
wpa_supplicant v0.5.9
Copyright (c) 2003-2007, Jouni Malinen <j@w1.fi> and contributors

=====================================================================================
rc.conf:
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
HOSTNAME="mythtv"
#
# 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)
#
# 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=(wlan0)

=====================================================================================
/etc/network_profiles/wlan0

#
# Network Profile
#

DESCRIPTION="Wireless Profile"

# Network Settings
INTERFACE=wlan0
HOSTNAME=mythtv

# Interface Settings (use IFOPTS="dhcp" for DHCP)
#IFOPTS="192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
#GATEWAY=192.168.0.1

IFOPTS="dhcp"

# DNS Settings (optional)
DOMAIN=tweet.net

# Wireless Settings (optional)
ESSID=getafreevirushere
#KEY=
WOPTS="mode managed essid $ESSID"

WIFI_INTERFACE=wlan0 # use this if you have a special wireless interface
# that is linked to the real $INTERFACE

WIFI_WAIT=30 # seconds to wait for the wireless card to
# associate before bringing the interface up
USEWPA="yes" # start wpa_supplicant with the profile
WPAOPTS="-D wext" # use "" for normal operation or specify additional
# options (eg, "-D ipw")
# see /etc/wpa_supplicant.conf for configuration
AUTOWPA="yes" # automatically configure WPA
PASSKEY="my password" # wpa passkey/phrase. for use with AUTOWPA
Additional info:

====================================================================================
/etc/wpa_supplicant.conf

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1

ap_scan=2

fast_reauth=1

network={
ssid="getafreevirushere"
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk=mypassword here
}

=============================================================================================
some dmesg information after I type wpa_supplicant -D wext -i wlan0 -c /etc/wpa_supplicant.conf -dd

ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_UP): wlan0: link is not ready
ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

This task depends upon

Closed by  Tobias Powalowski (tpowa)
Saturday, 09 February 2008, 11:00 GMT
Reason for closing:  Fixed
Comment by Tobias Powalowski (tpowa) - Saturday, 26 January 2008, 16:27 GMT
status on .24 kernel from testing?
Comment by dillweed (dillweed) - Monday, 28 January 2008, 04:26 GMT
Ok tested with .24 kernel and had the same result with the same log messages as before.
Comment by Börje Holmberg (linfan) - Wednesday, 06 February 2008, 18:37 GMT
I have a d-link 524 atheros chip and also use the new driver for xp32. I can only run wireless, if i choose Security: none in the router config in the browser.

The wpa_supplicant.conf is a total mess, completely impossible to understand, so I just have these lines in rc.conf:

# Don't use this for wireless interfaces, see network profiles below
#
#lo="lo 127.0.0.1"
#eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid xxxxxxxx"
WLAN_INTERFACES=(wlan0)
INTERFACES=(lo wlan0)
#INTERFACES=(lo)

#
# 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=(wlan0)
____________________

regards,

linfan
Comment by Börje Holmberg (linfan) - Friday, 08 February 2008, 07:35 GMT
hehe, whether i did right or not - got it to work. I did read the man on the net and changed in /etc/network-profiles/wlan0 and /etc/wpa_supplicant.conf not as in the wiki!

/etc/network-proviles/wlan0:

# Network Settings

DESCRIPTION="Wireless Profile"

INTERFACE=wlan0
HOSTNAME=XXXXXXXX

IFOPTS="dhcp"

# Wireless Settings (optional)
ESSID=XXXXXXXX
IWOPTS="essid $ESSID"

USEWPA="yes"
WPAOPTS="-D wext"

The XXXXXXXXX I set myself.
_________________________

etc/wpa_supplicant.conf:

ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=0
eapol_version=1
ap_scan=1
fast_reauth=1
# Only WPA-PSK is used. Any valid cipher combination is accepted.
network={
ssid="XXXXXXXXX"
scan_ssid=1
key_mgmt=WPA-PSK
psk=XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
}
______________________________

The XXXXXXXXXXXX are personal.

In router I chose WPA-PSK

__________________

iwconfig gives:

wlan0 IEEE 802.11g ESSID:"XXXXXXXXX"
Mode:Managed Frequency:2.437 GHz Access Point: XXXXXXXXXXXXXX
Bit Rate=54 Mb/s
Encryption key:7B0D-2A91-CF6F-6E52-13D2-22AD-BD1C-8768-77B3-16E5-CD12-8E98-5490-CBF9-2359-87DB Security mode:restricted
Power Management:off
Link Quality:98/100 Signal level:-33 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Comment by Roman Kyrylych (Romashka) - Friday, 08 February 2008, 08:31 GMT
> hehe, whether i did right or not - got it to work. I did read the man on the net and changed in /etc/network-profiles/wlan0 and /etc/wpa_supplicant.conf not as in the wiki!

Then I suggest you to note the differences in the wiki ;-)
Comment by Tobias Powalowski (tpowa) - Friday, 08 February 2008, 20:03 GMT
can i close this then?
Comment by Börje Holmberg (linfan) - Friday, 08 February 2008, 20:28 GMT
I think you should ask dillweed who opened this bug.
Comment by dillweed (dillweed) - Saturday, 09 February 2008, 00:38 GMT
Actually I bought a new network card for this machine and it works for me. As far as linfan's card goes I don't think you can compare the two situations, because it is a totally different driver that he is using. I still feel that this has something to do with ndiswrapper, wpa_supplicant and the newer kernels not working well together. Something in the kernel changed from the .22 series to the current ones. It was enough of a change that wpa_supplicant takes about 1-2 minutes to associatei with my router. Because of this the boot scripts would timeout and then go on booting the rest of the machine. Manual association worked fine, but I didn't like having to run to the other room after rebooting the machine, type the crap in and then go back to my workstation to ssh the machine to work on it.

I guess in the end this bug still isn't fixed, but I'm tired of trying to get ndiswrapper (windows driver) working on bootup. Anyways, I don't think this bug is fixed, but I'm not affected by it anymore, because I changed my hardware.

So, if you want to close that's fine with me. :)

Loading...