wlan0 unknown error 132 [SOLVED]

SIOCSIFFLAGS: Unknown error 132

---

Im having issues with getting my wifi card in my laptop to work.. it was working last night but when I woke up this morning and powered up my laptop and tryed to use it I kept getting this error...
Code:
c0ld@c0ld-laptop:~$ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Unknown error 132
Code:
c0ld@c0ld-laptop:~$ sudo iwconfig
lo        no wireless extensions.


eth0      no wireless extensions.


wmaster0  no wireless extensions.


wlan0     IEEE 802.11bg  ESSID:""  
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=off   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0
Chipset Information
Code:
wlan0        Atheros     ath5k - [phy0]
Code:
c0ld@c0ld-laptop:~$ sudo dhclient
[sudo] password for c0ld: 
Internet Systems Consortium DHCP Client V3.1.2
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/


SIOCSIFFLAGS: Unknown error 132
SIOCSIFFLAGS: Unknown error 132
Listening on LPF/wlan0/00:23:4d:0f:c4:57
Sending on   LPF/wlan0/00:23:4d:0f:c4:57
Listening on LPF/eth0/00:1d:72:72:c1:07
Sending on   LPF/eth0/00:1d:72:72:c1:07
Sending on   Socket/fallback
receive_packet failed on wlan0: Network is down
DHCPREQUEST of 192.168.0.187 on wlan0 to 255.255.255.255 port 67
send_packet: Network is down
DHCPREQUEST of 192.168.1.100 on eth0 to 255.255.255.255 port 67
DHCPACK of 192.168.1.100 from 192.168.1.1
bound to 192.168.1.100 -- renewal in 32900 seconds.
c0ld@c0ld-laptop:~$
Any advice or suggestions on how to eliminate this issue is most appreciated..Ive researched all day and have yet to find a solution..Thank You!




SOLUTION:Using these commands fixed the issue...Just make sure you specify the drivers of your interface..
Code:
rmmod ath5k
rfkill block all
rfkill unblock all
modprobe ath5k
rfkill unblock all
ifconfig wlan0 up
Sources:
HTML Code:
http://www.mail-archive.com/[email protected]/msg1813445.html
Hope this helps any others out there with same issue!


LIKE TO STATE THIS SOLUTION ONLY WORKED 1 DAY FOR ME!! LOL SO IM STILL OPEN TO SUGGESTIONS ON WHAT TO DO.