Results 1 to 6 of 6

Thread: SIOCSIFFLAGS: Unknown error 132

Hybrid View

  1. #1
    Join Date
    Nov 2009
    Beans
    8

    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/ubuntu-bugs@lists.ubuntu.com/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.
    Last edited by nicklausmichael; November 4th, 2009 at 03:40 AM. Reason: SOLUTION FAIL

  2. #2
    Join Date
    Nov 2009
    Beans
    1

    Re: SIOCSIFFLAGS: Unknown error 132

    Something from my experience:

    23:39:25 <mr00wka@r2d2>[~] rfkill list
    0: tpacpi_bluetooth_sw: Bluetooth
    Soft blocked: yes
    Hard blocked: yes
    <b>1: phy0: Wireless LAN
    Soft blocked: yes
    Hard blocked: no
    </b>


    Now if I knew WHAT software is blocking this device I could probably disable it permanently. It might be the same in your case.... Anyhow, after running rfkill unblock all my wireless is working perfectly
    Last edited by Krogulec; November 5th, 2009 at 12:23 AM.

  3. #3
    Join Date
    May 2008
    Beans
    10

    Re: SIOCSIFFLAGS: Unknown error 132

    Thanks very much!!!

    After two days messing about, "rfkill unblock all" worked for me (you need to do it after every start up).

    Now both:-
    Ralink rt2501usb
    Netgear rtl8187

    have both started working on 9.10 (they both work out-of-the-box on 9.04)

  4. #4
    Join Date
    Nov 2009
    Beans
    0

    Re: SIOCSIFFLAGS: Unknown error 132

    This didn't work for me. Still showing as disabled.

    Using Broadcom4318. I think this might be the Satan of wireless cards after trying for the past day to figure this out.

    EDIT:
    It's showing up under *-network:1 as opposed to wlan0...could this be an issue? Also the driver is listed as b43-pci-bridge but it's not a PCI card...
    Last edited by kinley3; November 24th, 2009 at 06:00 PM.

  5. #5
    Join Date
    Aug 2008
    Beans
    3

    Re: SIOCSIFFLAGS: Unknown error 132

    Any news on how to find a solutions to this problem?

  6. #6
    Join Date
    Apr 2010
    Beans
    1

    Re: SIOCSIFFLAGS: Unknown error 132

    Demn... So many stupid replies to all the related bug-reports and everybody saying it's not my falt/It's not my problem/It's BIOS problem/It's wicd problem/It's NetworkManager problem/It's b43-fwcutter/Blah Blah Blah

    The only real solution is on Russian Site, of course, where else...
    Решение проблем с WiFi в Ubuntu 9.10 (SIOCSIFFLAGS: Unknown error 132)
    (Troubleshooting WiFi in Ubuntu 9.10)
    If steps are not obvious then translate.google.com

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •