FS#7922 - iwlwifi driver for IPW4965 issue.

Attached to Project: Arch Linux
Opened by Zack (Sjoden) - Friday, 31 August 2007, 21:04 GMT
Last edited by Thomas Bächler (brain0) - Sunday, 02 September 2007, 09:22 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Thomas Bächler (brain0)
Architecture i686
Severity Medium
Priority Normal
Reported Version 2007.08 Don't Panic
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description: When I try to connect to an access point with 'dhcpcd wlan0', wlan0 times out. Iwconfig shows the essid but not the access point's MAC. I have reinstalled Arch, the drivers, and everything. I have to remove /var/run/dhcpcd-wlan0.pid and run 'iwlist wlan0 scan', then 'dhcpcd wlan0' again before it will work. I cannot run the scan unless I have already tried dhcpcd because it reports that the device doesn't support scanning and isn't active, and it fails everytime. I don't use rc.conf or /etc/wireless to set it up because I don't want it to connect to just any access point. I've requested help on IRC and was told to post a bug report. My system is up to date.


Additional info:
* package version(s)

[zack@rbox ~]$ pacman -Q iwlwifi
iwlwifi 1.0.0.1-1
[zack@rbox ~]$ pacman -Q iwlwifi-4965-ucode
iwlwifi-4965-ucode 4.44.17-1
[zack@rbox ~]$


* config and/or log files etc.
None...

Steps to reproduce:

Every time you try to run dhcp on the interface before running iwlist.

Temporary Solution:

[zack@rbox ~]$ cat npnwifi.sh
iwconfig wlan0 essid apnamehere;
iwconfig wlan0 key wepkeyhere;
rm /var/run/dhcpcd-wlan0.pid;
dhcpcd wlan0;
rm /var/run/dhcpcd-wlan0.pid;
iwlist wlan0 scan;
dhcpcd wlan0;
echo "finished...";
exit;
[zack@rbox ~]$
This task depends upon

Closed by  Thomas Bächler (brain0)
Sunday, 02 September 2007, 09:22 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Saturday, 01 September 2007, 10:19 GMT
It's not good to start dhcpcd multiple times on the same interface. Try this:

iwconfig wlan0 essid apname
iwconfig wlan0 key wepkey
ifconfig wlan0 up
iwlist wlan0 scan
dhcpcd wlan0

Probably you need to put the interface up before it will do anything. If you do the ifconfig wlan0 up before anything, I don't even think the scanning is required.
Comment by Thomas Bächler (brain0) - Sunday, 02 September 2007, 09:21 GMT
This is not a bug. The interface has to be up so that you can scan, therefore Jan's suggestion is the right way. You shouldn't use iwconfig/wep anyway, as it is unsecure, rather use wpa_supplicant to connect and use WPA or WPA2 mode (using wpa_supplicant will avoid problems like yours anyway, even in wep mode).

Loading...