Okay, under 3.2 I had this card and from my memory, I used wlanconfig (all worked well) and then lwconfig and typed in ath0, the channel, and my ssid. Now, that does not work, and when I typed "ath0" in the field, it just goes back to eth0. I eventually just clicked prism2 and put the info in there. It "went away" with no "connected!" pop up, but I do have a connection to the internet now. Oddly, no network statistics show up in torsmo, or with any app that shows traffic (says I don't have a connection). When I boot, my saved settings cause the system to hang with some errors. But I do have a connection.
myiwconfig looks like this #!/bin/bash /usr/local/bin/iwconfig.sh ath0 11 linksys 2>&1 >/dev/null
myprism2 looks like this #!/bin/bash /usr/local/bin/prism2.sh ath0 11 "" 2>&1 >/dev/null
my bootlocal looks like this with the /opt/myiwconfig.sh commented out because this is the only way I get a connection. If I comment out /opt/myprism2.sh, and leave /opt/myiwconfig.sh. I get no hanging, but no internet connection.
#!/bin/bash # put other system startup command here # /opt/myiwconfig.sh /opt/myprism2.sh /opt/sound.sh loadkeys us
Seriously, what the heck? The Linksys Atheros version 1.1 a/b/g card is supposed to work out of the box and not use prism2.
Quote
Oddly, no network statistics show up in torsmo
Not odd at all. Edit the lines below TEXT that count up/down eth0 to ath0.Thanks... you helped me iron some things out with DSL today that have been issues for quite some time. I even got rid of the prism2 issue (see this post) and got things working without the boot hang. Odd though that it did not connect when i first configured it even though mylwconfig in /opt looked okay. I just had to make the file execute, which I still think that when wlanconfig is activated, it should connect without doing this... as it used to under other DSL distros.
original here.