In addition to the software switch via rfkill, there's a hardware switch
to turn wireless off. It's tiny, and its position at the right-side
front can sometimes lead to inadvertently switching it. On my
T410(currently broken, but that's another story), 100% of "error 132"
are caused by activating the switch when jamming it into my laptop backpack.
-- Philipp
Dr. Ed Morbius wrote:
> Two issues with a Thinkpad 410s running testing/unstable.
>
> Custom-compiled 2.6.34 kernel (to fix issues with Thinkpad
> volume/brightness controls):
>
> Linux altaira 2.6.34-custom-1- #1 SMP Thu Oct 21 18:30:43 PDT 2010 x86_64 GNU/Linux
>
>
> 1: Wifi's stopped working. Yes, it did initially.
>
> Sometime early in November. Simply haven't had the time to look into
> it.
>
> I did try installing rfkill to reset the wireless card, but no dice
>
> https://bugzilla.redhat.com/show_bug.cgi?id=502329
>
>
> I use a script to load modules and attempt WiFi configuration. If
> there's anything obviously wrong:
>
> ------------------------------------------------------------------------
> #!/bin/bash
>
> rmmod iwlagn iwlcore mac80211 cfg80211; sleep 4
> modprobe iwlagn; sleep 4
> rfkill block wifi; sleep 2
> rfkill unblock wifi; sleep 2
> iwconfig wlan0; sleep 2
> iwconfig wlan0 essid 'SSID-name' key '********'
> iwconfig wlan0; sleep 2
> dhclient -v wlan0
> ------------------------------------------------------------------------
>
> Invoking that:
> ------------------------------------------------------------------------
> # bash -x ./setup-wifi
> + rmmod iwlagn iwlcore mac80211 cfg80211
> ERROR: Module iwlagn does not exist in /proc/modules
> ERROR: Module iwlcore does not exist in /proc/modules
> ERROR: Module mac80211 does not exist in /proc/modules
> ERROR: Module cfg80211 does not exist in /proc/modules
> + sleep 4
> + modprobe iwlagn
> WARNING: All config files need .conf: /etc/modprobe.d/libpisock9, it will be ignored in a future release.
> + sleep 4
> + rfkill block wifi
> + sleep 2
> + rfkill unblock wifi
> + sleep 2
> + iwconfig wlan0
> wlan0 IEEE 802.11abgn ESSID

ff/any
> Mode:Managed Access Point: Not-Associated Tx-Power=off
> Retry long limit:7 RTS thr

ff Fragment thr

ff
> Encryption key

ff
> Power Management

ff
>
> + sleep 2
> + iwconfig wlan0 essid SSID-name key ********
> + iwconfig wlan0
> wlan0 IEEE 802.11abgn ESSID:"SSID-name"
> Mode:Managed Access Point: Not-Associated Tx-Power=off
> Retry long limit:7 RTS thr

ff Fragment thr

ff
> Encryption key:3E4B-C128-D116-5630-C414-4072-BB
> Power Management

ff
>
> + sleep 2
> + dhclient -v wlan0
> Internet Systems Consortium DHCP Client 4.1.1-P1
> Copyright 2004-2010 Internet Systems Consortium.
> All rights reserved.
> For info, please visit https://www.isc.org/software/dhcp/
>
> Corrupt lease file - possible data loss!
> Corrupt lease file - possible data loss!
> SIOCSIFFLAGS: Unknown error 132
> SIOCSIFFLAGS: Unknown error 132
> Listening on LPF/wlan0/00:27:10:9a:3b:00
> Sending on LPF/wlan0/00:27:10:9a:3b:00
> Sending on Socket/fallback
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 7
> send_packet: Network is down
> receive_packet failed on wlan0: Network is down
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
> send_packet: Network is down
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 17
> send_packet: Network is down
> DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 20
> send_packet: Network is down
> No DHCPOFFERS received.
> No working leases in persistent database - sleeping.
> ------------------------------------------------------------------------
>
>
>
> 2: When closing the laptop lid, apparently my display sleeps and won't
> wake up.
>
> I also can't view console after starting X.
>
> Graphics are Intel:
> PCI:*(0:0:2:0) 8086:0046:17aa:2159 Intel Corporation Core Processor Integrated Graphics Controller rev 2, Mem @ 0xf2000000/4194304, 0xd0000000/268435456, I/O @ 0x00001800/8
>
> I believe this is the relevent portion of Xorg0.log, can post full
> contents is preferable:
>
> ------------------------------------------------------------------------
> (II) LoadModule: "intel"
> (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
> (II) Module intel: vendor="X.Org Foundation"
> compiled for 1.7.7, module version = 2.13.0
> Module class: X.Org Video Driver
> ABI class: X.Org Video Driver, version 6.0
> (II) LoadModule: "vesa"
> (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
> (II) Module vesa: vendor="X.Org Foundation"
> compiled for 1.7.7, module version = 2.3.0
> Module class: X.Org Video Driver
> ABI class: X.Org Video Driver, version 6.0
> (II) LoadModule: "fbdev"
> (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so
> (II) Module fbdev: vendor="X.Org Foundation"
> compiled for 1.7.6.901, module version = 0.4.2
> ABI class: X.Org Video Driver, version 6.0
> (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
> i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
> E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
> 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
> 4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
> Sandybridge, Sandybridge, Sandybridge, Sandybridge, Sandybridge,
> Sandybridge, Sandybridge
> (II) VESA: driver for VESA chipsets: vesa
> (II) FBDEV: driver for framebuffer: fbdev
> (II) Primary Device is: PCI 00@00:02:0
> (WW) Falling back to old probe method for vesa
> (WW) Falling back to old probe method for fbdev
> (II) Loading sub module "fbdevhw"
> ------------------------------------------------------------------------
>
>