Thursday, 8 January 2009

More wireless wierdness post suspend/resume

Following my initial "discovery" that I needed to add a configuration file in order to allow my wireless network adapter ( Atheros Communications Inc. AR5212 802.11abg ) to "wake" up and work after I resumed my Thinkpad.

Well, it gets more wierd - since the most recent set of "hacks" that I had to put in place to get Ubuntu to successfully resume ( I'm using Intrepid Ibex on a 2007-AE7 Thinkpad T60p ), I found that, whilst the wireless adapter would appear to wake up, it still struggled to reconnect to my wireless network.

Thanks to a friend @ work, I've found that there are now TWO "hacks" required: -

a) Add the configuration file /etc/pm/config.d/madwifi containing the single line:

SUSPEND_MODULES=ath_pci

b) Add the line: -

MODULES="ath_pci" to /etc/default/acpi-support

Following a reboot, I now find that the wireless adapter will (a) wake up and (b) reconnect when I resume Ubuntu.

Will dig further to see whether this is a new bug, or a "feature" ...

1 comment:

Unknown said...

I believe the behaviour you are seeing is anticipated... I experienced it as well on Ubuntu 8.10 on a T61.

I'd recommend reviewing www.thinkwiki.org.

Note to self - use kubectl to query images in a pod or deployment

In both cases, we use JSON ... For a deployment, we can do this: - kubectl get deployment foobar --namespace snafu --output jsonpath="{...