| View previous topic :: View next topic |
| Author |
Message |
BassDemon
Tux's lil' helper
Joined: 14 Jan 2004
Posts: 75
|
 Posted: Mon Feb 14, 2005 11:13 pm Post subject: linux-wlan-ng MA111 implementation_failure [solved] |
 |
|
hey all. i'm trying to get a netgear MA111 to work on a toshiba portege 3110ct. I've never really used linux-wlan-ng before but I think the configs are all ok. Kernel is 2.6.10-r6. Here's the error I get on /etc/init.d/wlan start:
| Code: |
Starting WLAN devices...
message=lnxreq_ifstate
ifstate=fwload
resultcode=success
Reading S-record file /etc/wlan//prism2_ru.hex...
NIC ID: 0x8026 v1.0.0
MFI ID: 0x1 v1 1->1
CFI ID: 0x2 v2 1->1
PRI ID: 0x3 v1 1->4
Version: ID 0x1f 1.8.3
Compat: Role 0 Id 0x4 v3 1->15
Compat: Role 0x1 Id 0x1 v1 1->1
Compat: Role 0x1 Id 0x2 v2 1->1
Compat: Role 0x1 Id 0x3 v1 4->4
Seq: 0
Platform: ID 0x800a 1.0.0
Platform: ID 0x800f 1.0.0
Platform: ID 0x8010 1.0.0
Platform: ID 0x8011 1.0.0
Platform: ID 0x801e 1.0.0
Platform: ID 0x801f 1.0.0
Platform: ID 0x8020 1.0.0
Platform: ID 0x8025 1.0.0
Platform: ID 0x8026 1.0.0
Platform: ID 0x8027 1.0.0
prism2dl: warning: Failed to find PDR for plugrec 0x0406.
prism2dl: warning: Failed to find PDR for plugrec 0x0302.
prism2dl: warning: Failed to find PDR for plugrec 0x0414.
prism2dl: finished.
Failed to enable the device, resultcode= implementation_failure .
wlanctl-ng: No such device
wlanctl-ng: No such device
error: Autojoin indicated failure! |
After searching online for wlan-ng and implementation_failure that basically seems to mean check your kernel logs. So here's the kernel logs:
| Code: | Feb 14 11:15:18 wiley_linux divert: allocating divert_blk for wlan0
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7e2ffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7e3ffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7e4ffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7e5ffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7e6ffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7e7ffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7e8ffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7e9ffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7eaffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7ebffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7ecffe
Feb 14 11:15:50 wiley_linux Writing 4096 bytes to ram @0x7edffe
Feb 14 11:15:50 wiley_linux Writing 3010 bytes to ram @0x7eeffe
Feb 14 11:15:50 wiley_linux Writing 416 bytes to ram @0x7efc20
Feb 14 11:15:50 wiley_linux Writing 16 bytes to ram @0x7efdd0
Feb 14 11:15:50 wiley_linux Writing 4044 bytes to ram @0x7f0800
Feb 14 11:15:50 wiley_linux Writing 3288 bytes to ram @0x7fe000
Feb 14 11:15:52 wiley_linux hfa384x_docmd: ctlx failure=REQ_FAILED
Feb 14 11:15:52 wiley_linux hfa384x_drvr_start: cmd_initialize() failed, result=-5
Feb 14 11:15:52 wiley_linux prism2sta_ifstate: hfa384x_drvr_start() failed,result=-5 |
Thanks.
bassdemon
Last edited by BassDemon on Tue Feb 15, 2005 10:00 pm; edited 1 time in total |
|
| Back to top |
|
 |
BassDemon
Tux's lil' helper
Joined: 14 Jan 2004
Posts: 75
|
| Posted: Tue Feb 15, 2005 10:00 pm Post subject: |
|
|
| Alright well it seems that it was an issue with that kernel version. 2.6.10-r7 seems to work alright and so does 2.6.9-r9. In case someone else has the same issues. |
|
| Back to top |
|
|
Sayonara
n00b
Joined: 12 Jul 2003
Posts: 18
Location: Germany, NRW
|
|
| Back to top |
|
|
BassDemon
Tux's lil' helper
Joined: 14 Jan 2004
Posts: 75
|
| Posted: Tue Feb 15, 2005 10:25 pm Post subject: |
|
|
| well that's the thing with mine...i don't really absolutely need the newest kernel possible. So i'm just going to use the crappy workaround of using an older kernel. no idea on a patch though. |
|
| Back to top |
|
|
CyD
Tux's lil' helper
Joined: 23 Jul 2004
Posts: 117
|
| Posted: Thu Feb 24, 2005 7:20 pm Post subject: |
|
|
Hey all,
I am having similar problems with the wlan-ng driver and 2.6.10 kernels, but only during boot. Wireless can be started after boot successfully with the following commands:
| Code: | wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
wlanctl-ng wlan0 lnxreq_autojoin ssid=<your ssid> authtype=opensystem
/etc/init.d/net.wlan0 start |
These commands can be found in /usr/share/doc/linux-wlan-ng*/README
This assumes that /etc/modules.autoload.d/kernel-2.6 has the line:
| Code: | | prism2_usb doreset=1 |
And /etc/modules.d/aliases:
| Code: | | alias prism2_usb wlan0 |
I will be studying the issue further, will post any results:) |
|
| Back to top |
|
|
|
Networking & Security
