-
Two ideas:
1. Run ifconfig up at the end of your script/command list. My card often won't associate (it's also an atheros) until I deactivate/activate the interface. Maybe that is what the gnome tool is doing for you.
2. If you are going to be using it in the same place, try setting the channel as well as the other parameters. Sometimes that gets cards to associate much easier for me.
-
I used to use the kde applet for setting mine, but also had poor luck through reboots. What I had posted previously is exactly what works now, either through rc.local. or manually. One other question, are you running dhcpcd eth1 after the ifconfig settings?
-
I see you're online, are you wireless with slack???
-
well, hal crapped out and crashed my laptop.
The good news is i figured out the wireless thing
real simple
rc.wireless.conf was the first net device. so i put my settings for key, etc in rc.wireless.conf then added "/etc/rc.d/rc.wireless eth1" to rc.local that sets my network settings to eth1.
thanks for the help. now i gotta figure out why hal no worky
soule
-
Have you run swaret current? I'm curious because that's exactly how I did it but my last swaret upgrade broke it, which is why I do the rc.local thing now.
-
im using slapt-get right now(havent update new install yet) to see if it fixes my hal problem. if it breaks wireless ill let ya know.
soule
-
Keep an eye out! What it did was throw an error about not being able to call rc.wireless directly, but doing wireless settings through rc.inet1. I was unable to get that working, thus the ugly rc.local hack.