beginning to believe this may be the wrong module, until the correct MAC address for your device shows up in the "HWaddr", then the driver is not working. What did you mean earlier by "installing the other versions"?

also, may be time to verify via fccid: what is the fccid on the device?

anyway, going to dinner, be back later on...

If you look back at the thread I referenced, they say:

I searched the web for "mn-510" and only found failure stories. My first attempt failed, followed by a successful run:

1. Download linux-2.4.22 source and build it.
2. Download wlan-ng 0.2.1-pre11.
3. Configure with ALL OF THESE: pci, plx, pcmcia, and usb.
4. Follow the wlan direction

On step 3, that's what I'm refering to.

FCCID: HEDACCWN330168

edit: ok, (didn't see that last post) thanks for all the help so far!!

Well, wouldn't you know it, the database lookup for exhibits on the FCC site is broken so I can't get a look at a disassembled view of your device, all I managed to learn with that fccid is that it's an accton oem chipset.

Perhaps you should go back and configure with all those things, even though you don't have a pci or pcmcia adapter, perhaps there's some support code that your missing. When it says "Configure with ALL....", is it referring to configuring your kernel for compilation or the wlan-ng driver?

Now that I've actually downloaded the wlan-ng source and looked at the readme, I have to ask: did you do see this/do this?
------------------------------
FOR USB USERS:

A) Make sure your kernel usb support is running
B) Plug in the Prism2.x USB device
C) Run 'modprobe prism2_usb prism2_doreset=1' to load the driver into memory.
D) Run 'wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable' to initialize the
driver+MAC functions.
E) Run 'wlanctl-ng wlan0 lnxreq_autojoin ssid=<your ssid> authtype=opensystem'
to enable the MAC in Infrastructure Station mode.
F) Run 'ifconfig wlan0 <your IP address>'


item "D" would seem to be the one missed, as your MAC address is not listed, if you did all this and have been through the readme a dozen times let me know as I'll need to pour a *much* larger drink,

I didn't see that, I"ll try it now. I looked through the readme on the site, but never saw that peice of info.

Here are the results:
[root@localhost root]# wlanctl-ng wlan0 lnxreq_autojoin ssid=DATALINKS authype=opensystem
The required argument 'authtype' has no value.
message=lnxreq_autojoin
ssid='DATALINKS'
authtype=no_value
resultcode=no_value
[root@localhost root]# wlanctl-ng wlan0 lnxreq_ifstate ifstate=enable
message=lnxreq_ifstate
ifstate=enable
resultcode=success
[root@localhost root]# wlanctl-ng wlan0 lnxreq_autojoin ssid=DATALINKS authype=opensystem
The required argument 'authtype' has no value.
message=lnxreq_autojoin
ssid='DATALINKS'
authtype=no_value
resultcode=no_value
[root@localhost root]# ifconfig wlan0 192.168.2.76
[root@localhost root]#

The wireless light indicator was light and solid before I did this, now it blinks!! WHooo! But after I restarted the laptop, it returned to its blinkless state. Same error during bootup, too.

sounds like you got a bit furthur than "almost there" (heh) this time. Can you do the same thing and this time when you're done, post the output of ifconfg wlan0? I'd dearly love to see ifconifg displaying something besides 0's in the HWaddr field, it would be even better if it show bytes tx/rx'd too.

ps: this is linux, reboots are rarely required for configuration changes, what made you reboot?

[root@localhost root]# ifconfig wlan0
wlan0 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:192.168.2.76 Bcast:192.168.2.255 Mask:255.255.255.0
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Ok, so the addr field is still zeros, but the wireless guessed the subnet number and the base station number on its own, I didn't give it those. Glimmer of hope #2.

edit: reboot is from being used to eek, windows, and I wanted to see if the changes would stick.

Ok, this is looking better, at least you're not getting "no such device" errors. Time to go through that readme very carefully, it's the readme that comes with the source code, not the one on the website. I noticed a few potential "gotchas" in there but only you will know if they apply to your situation.

I'll go get the source code so I can get the readme there. And see what I can do next.

edit: stoopid question, I've installed the source code, where's the readme?

How long is the readme? Could you post it? I am having no luck finding it after I installed the source rpms.

it's a file named README in the top level directory named linux-wlan-ng-0.2.1-pre11

Hey, check this out!!

root@PillarofAutumn root]# /etc/init.d/wlan start [ OK ]
Starting WLAN Devices:message=dot11req_mibset
mibattribute=dot11WEPDefaultKeyID=1
resultcode=success
message=dot11req_mibset
mibattribute=dot11ExcludeUnencrypted=true
resultcode=success
message=dot11req_mibset
mibattribute=dot11PrivacyInvoked=true
resultcode=success
message=dot11req_mibset
mibattribute=dot11WEPDefaultKey0=xx:xx:xx:xx:xx
resultcode=success
message=dot11req_mibset
mibattribute=dot11WEPDefaultKey1=xx:xx:xx:xx:xx
resultcode=success
message=dot11req_mibset
mibattribute=dot11WEPDefaultKey2=xx:xx:xx:xx:xx
resultcode=success
message=dot11req_mibset
mibattribute=dot11WEPDefaultKey3=xx:xx:xx:xx:xx
resultcode=success
[root@PillarofAutumn root]# ifconfig wlan0 [ OK ]
wlan0 Link encap:Ethernet HWaddr 00:50:F2:77:1F:FA
inet addr:192.168.2.32 Bcast:192.168.2.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:258 (258.0 b)

You da man!! excellent work!