Upgrade to Unstable: Problems with USB Wifi Adapter
I've just upgraded to sid on my powerpc, but my D-Link DWL-122 USB wifi
adapter has stopped working as it was under sarge.
When I plug the device in, /var/log/messages shows it's loading the
prism2_usb module. I still have alias wlan0 prism2_usb in my modules,
but it's no longer associating with the network automatically.
When I plug the device in, /var/log/messages has:
Mar 9 17:56:58 localhost kernel: ohci_hcd 0001:10:1b.0: wakeup
Mar 9 17:56:58 localhost kernel: usb 2-1: new full speed USB device
using address 2
Mar 9 17:56:59 localhost kernel: prism2_usb: no version for
"p80211netdev_rx" found: kernel tainted.
Mar 9 17:56:59 localhost kernel: prism2usb_init: prism2_usb.o:
0.2.1-pre25 Loaded
Mar 9 17:56:59 localhost kernel: prism2usb_init: dev_info is:
prism2_usb
Mar 9 17:56:59 localhost kernel: usbcore: registered new driver
prism2_usb
Mar 9 17:56:59 localhost usb.agent[4737]: prism2_usb: loaded
successfully
Beforehand, the rest of the interface association would happen. However,
now if I try ifup wlan0, I get:
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; Operation not supported.
Internet Software Consortium DHCP Client 2.0pl5
Copyright 1995, 1996, 1997, 1998, 1999 The Internet Software Consortium.
All rights reserved.
Please contribute if you find this software useful.
For info, please visit http://www.isc.org/dhcp-contrib.html
<snip>
Listening on LPF/wlan0/00:11:95:88:17:8f
Sending on LPF/wlan0/00:11:95:88:17:8f
Sending on Socket/fallback/fallback-net
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 8
DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 12
...and in /var/log/messages there is:
Mar 9 17:58:17 localhost kernel: ident: nic h/w: id=0x8026 1.0.0
Mar 9 17:58:17 localhost kernel: ident: pri f/w: id=0x15 1.1.3
Mar 9 17:58:17 localhost kernel: ident: sta f/w: id=0x1f 1.7.1
Mar 9 17:58:17 localhost kernel:
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
Mar 9 17:58:17 localhost kernel:
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
Mar 9 17:58:17 localhost kernel:
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
Mar 9 17:58:17 localhost kernel:
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/12
Mar 9 17:58:17 localhost kernel:
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Mar 9 17:58:17 localhost kernel:
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
Mar 9 17:58:17 localhost kernel:
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Mar 9 17:58:17 localhost kernel: Prism2 card SN: 000000000000
Mar 9 17:58:18 localhost kernel: linkstatus=CONNECTED
The adapter shows a solid link LED, which occasionaly switches off and
back on again.
If I then try iwconfig, I get:
wlan0 IEEE 802.11-DS ESSID:"{MYID}" Nickname:"{MYID}"
Mode:Ad-Hoc Frequency:2.412 GHz Cell: 02:11:F9:56:17:8F
Bit Rate:2 Mb/s Tx-Power:2346 dBm
Retry min limit:8 RTS thr:off Fragment thr:off
Encryption key:off
Link Quality=14/92 Signal level=9/154 Noise level=0/154
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
...which looks like it's in ad-hoc mode, and not associated with the AP.
So, it's twofold; firstly the device isn't being set up on hotplug, and
even if I do it manually, it doesn't associate with the AP.
Any ideas would be great!
Cheers,
Ben
--
ben@serosoft.com - www.seigan.org
PGP Key fingerprint = 4309 1C58 5143 AFAC F69E 11CD 76FD 56D4 1223 E387
Reply to: