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" ...
Geeking in technology since 1985, with IBM Development, focused upon Docker and Kubernetes on the IBM Z LinuxONE platform In the words of Dr Cathy Ryan, "If you don't write it down, it never happened". To paraphrase one of my clients, "Every day is a school day". I do, I learn, I share. The postings on this site are my own and don’t necessarily represent IBM’s positions, strategies or opinions. Remember, YMMV https://infosec.exchange/@davehay
Subscribe to:
Post Comments (Atom)
Reminder - installing podman and skopeo on Ubuntu 22.04
This follows on from: - Lest I forget - how to install pip on Ubuntu I had reason to install podman and skopeo on an Ubuntu box: - lsb_rel...
-
Why oh why do I forget this ? Running this command : - ldapsearch -h ad2012.uk.ibm.com -p 389 -D CN=bpmbind,CN=Users,DC=uk,DC=ibm,DC=com -w...
-
Error "ldap_sasl_interactive_bind_s: Unknown authentication method (-6)" on a LDAPSearch command ...Whilst building my mega Connections / Domino / Portal / Quickr / Sametime / WCM environment recently, I was using the LDAPSearch command tha...
-
Whilst building a new "vanilla" Kubernetes 1.25.4 cluster, I'd started the kubelet service via: - systemctl start kubelet.se...
1 comment:
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.
Post a Comment