This worked like a charm. I had found something like this in another post (maybe yours) when I was using a broadcom wireless card and blindly copied the setting into a file named madwifi, as it was named in the post, and it also worked. I didn't know what the module name represented and I guess I just got lucky. When I switched to the linksys card it stopped working.
Anyway, thanks for the solution. Not sure how the file naming system works, but I added a file named /etc/pm/config.d/madwifi with the following line in it: SUSPEND_MODULES="rt61pci" and it worked just fine. - Mark On Mon, Mar 30, 2009 at 11:56 AM, Zak Kipling <zak.kipl...@cantab.net>wrote: > This still happens for me with the Jaunty beta (live CD; I haven't tried > the lbm modules yet). > > The workaround I described can be automated by adding a file containing > > SUSPEND_MODULES="rt2500pci" > > to /etc/pm/config.d/ > > > Substitute your particular module (eg rt61pci) as appropriate; on recent > versions of pm-utils (where > http://bugs.freedesktop.org/show_bug.cgi?id=19658 has been fixed) you > should be able to put "rt2x00lib" which will handle all cards in this > family. > > Unless the driver bug is easily fixed, could these modules be added to > the default unload-on-suspend list? > > -- > rt2500pci wireless interface not functional after suspend/resume > https://bugs.launchpad.net/bugs/293844 > You received this bug notification because you are a direct subscriber > of the bug. > > Status in “linux” source package in Ubuntu: New > Status in “linux-backports-modules-2.6.27” source package in Ubuntu: New > Status in “pm-utils” source package in Ubuntu: New > > Bug description: > Following an upgrade to Intrepid on a system where the rt2500pci wireless > was working in Hardy using linux-backports-modules, the wireless interface > still works on startup but becomes non-functional after a suspend/resume > cycle. The following error can be seen in syslog from NetworkManager: > > NetworkManager: <info> (wlan0): now managed > NetworkManager: <info> (wlan0): device state change: 1 -> 2 > NetworkManager: <info> (wlan0): bringing up device. > NetworkManager: <WARN> nm_device_hw_bring_up(): (wlan0): device not up > after timeout! > > and attempts to bring the interface up manually fail: > > $ sudo ifconfig wlan0 up > SIOCSIFFLAGS: No such device > > even though the interface does appear in the output of "iwconfig" and > "ifconfig -a" > > Reloading the module with: > > $ sudo rmmod rt2500pci && sudo modprobe rt2500pci > > seems to get the interface working again. > > > lspci -v output: > 01:03.0 Network controller: RaLink RT2500 802.11g Cardbus/mini-PCI (rev 01) > Subsystem: Micro-Star International Co., Ltd. Device 6833 > Flags: bus master, slow devsel, latency 64, IRQ 21 > Memory at ffcfc000 (32-bit, non-prefetchable) [size=8K] > Capabilities: [40] Power Management version 2 > Kernel driver in use: rt2500pci > Kernel modules: rt2500pci > > This occurs using both the default rt2x00 modules included with Intrepid, > and the ones in linux-backports-modules. > -- rt2500pci wireless interface not functional after suspend/resume https://bugs.launchpad.net/bugs/293844 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
