Please not ask for commands, configuration, etc… im learning Linux… Simply i search… search… read…read and try, try, try… The next thing is the multimedia keyboards, the volume knob and the heardphones… ,mmm very busy … searching, reading…
one thing: the interface for me in ifconfig is wifi0 not wlan0… but all is ok.!!!
If this not working for you try with ndiswrapper… i be able to install windows xp driver in other Toshiba A135 with PCLinuxOS and with Linux Mint. If you need the Windows Xp driver i have it!.. Others have look with Windows 98 drivers of same AR5007eg…
So try… try… and try…
Im figthing!!! now installing Vmware in my Linux Mint box in my office … grrrr grrrrr… but i someday win this battle
>
> I will try your solution tonight as so far, anything I tried doesnt work
> with this stupid wireless.
> I will post results.
>
> Thank you for sharing this.
>
>
Have you tried using MadWifi from the madwifi.org repository?
Add it by adding the following url to your repo list:
Install / add the madwifi-kmp-default package, and the ‘madwifi’ package
from the madwifi repo.
in network devices -> network settings, delete ALL of your ar5007 devices
shown, they’ll indicate “not configured” or something like that.
Reboot your system. (important! this clears out ath5k from ram)
(yes guys, I know there’s a better way… but let’s keep this simple!)
In network devices -> network settings, configure your ar5007 device as
needed. (I recommend using traditional mode, I find network-manager
annoying and problematic)
You should be able to enjoy your wireless.
Often, after first setup, you’ll need to run ‘rcnetwork restart’ once (or
maybe twice) to get card / driver talking properly. Sounds odd, but it
works.
yes! i do exactly lornix write, and this work! Sorry i not remember the steps and not write anything… im very tired at 3:00 am . Thanks Lornix for your help!
>
> yes! i do exactly lornix write, and this work! Sorry i not remember the
> steps and not write anything… im very tired at 3:00 am . Thanks
> Lornix for your help!
>
>
well, didn’t work well for me.
however, after some botching and workarounds moving modules from wrong kernel to right one, I managed to get ath0 reckognized, set-up, but not operational.
