[Bug 13850] Need to 'rmmod airo', 'modprobe airo' after hibernation to get wireless to work (IBM T40)

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Tue Dec 6 07:43:21 UTC 2005

Please do not reply to this email.  You can add comments at
Ubuntu | linux

djwong+ubuntu at submarine.dyndns.org changed:

           What    |Removed                     |Added
                 CC|                            |djwong+ubuntu at submarine.dynd
                   |                            |ns.org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1

------- Additional Comments From djwong+ubuntu at submarine.dyndns.org  2005-12-06 07:43 UTC -------
I can confirm this bug on a fresh install of Breezy on a T40.  I've also figured
out what's going wrong here:

After the installer insmod's airo.ko, the system comes up with an Ethernet
device as eth1 and the raw 802.11 device as wifi0.  The installer sees the eth1
ethernet device and creates an iftab entry "eth1 mac XX:XX:XX:XX:XX:XX",
presumably so that the system will "remember" which MAC address mapped to which
interface at install time.

Unfortunately, this  entry is not sufficiently precise!  As far as ifrename is
concerned, eth1 and wifi0 have the same MAC address, and on my T40, ifrename
examines wifi0 first.  Thus, wifi0 (a raw 802.11 interface) is renamed to eth1
and the real ethernet interface gets pushed off to eth2.  Consequently, dhclient
is not attached to a real ethernet interface, which is why it appears that
wireless "doesn't work" upon first boot even though it does in the installer.

Quick solution: Change that iftab entry to read "eth1 arp 1 mac
XX:XX:XX:XX:XX:XX".  The "arp 1" forces ifrename to match to the Ethernet device
instead of the "Unspecified" (raw 802.11) device.

Ergo, this is not a bug with the kernel; it's a bug with whomever sets up iftab.

Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the kernel-bugs mailing list