Wifi And Suspend

[Mr. Sinister]

I have Opie 1.1.7 on OZ 3.5.2 on an SL-6000L.
When I suspend (or when it suspends on its own), the wifi connection becomes hosed.
I want to modify the script, or put an intermediate step in that calls "ifdown wlan0" in the suspend sequence. What script (or binary) does the suspend call?

[Chet]

I have Opie 1.1.7 on OZ 3.5.2 on an SL-6000L.
When I suspend (or when it suspends on its own), the wifi connection becomes hosed.
I want to modify the script, or put an intermediate step in that calls "ifdown wlan0" in the suspend sequence. What script (or binary) does the suspend call?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=76022\"][{POST_SNAPBACK}][/a][/div]

I have the same problem with OZ 3.5.3 (using OPIE) and a 6000L.  Despite being an experienced Linux user, I can't for the life of me find out why the wlan0 device won't "come back" after a suspend.  Your idea of manually shutting it off might be a suitable workaround.

I'm not familiar with hotplug (no USB devices on my usual Linux boxes), but everything _looks_ okay from what I can tell.  When I resume from any kind of suspend, I get the following whenever I run "ifup wlan0":

wlanctl-ng: No such device

Sure enough, both "ifconfig -a" and "iwconfig" show no wlan0 device.  But lsmod shows the p80211 and prism2_usb modules loaded.  And dmesg seems to indicate that prism2_usb is registered with usb.c.  So what's the deal?

[Chet]

Sure enough, both "ifconfig -a" and "iwconfig" show no wlan0 device.  But lsmod shows the p80211 and prism2_usb modules loaded.  And dmesg seems to indicate that prism2_usb is registered with usb.c.  So what's the deal?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=76108\"][{POST_SNAPBACK}][/a][/div]

To calrify, after a reboot and a successful "ifup wlan0", "dmesg" looks like this:

Code: [Select]

usb.c: registered new driver prism2_usb
hub.c: USB new device connect on bus1/2, assigned device number 2
ident: nic h/w: id=0x8026 1.0.0
ident: pri f/w: id=0x15 1.1.3
ident: sta f/w: id=0x1f 1.7.4
MFI:SUP:role=0x00:id=0x01:var=0x01:b/t=1/1
CFI:SUP:role=0x00:id=0x02:var=0x02:b/t=1/1
PRI:SUP:role=0x00:id=0x03:var=0x01:b/t=1/4
STA:SUP:role=0x00:id=0x04:var=0x01:b/t=1/12
PRI-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-CFI:ACT:role=0x01:id=0x02:var=0x02:b/t=1/1
STA-MFI:ACT:role=0x01:id=0x01:var=0x01:b/t=1/1
Prism2 card SN: \x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00
linkstatus=CONNECTED
prism2sta_ifstate: Cannot enter fwload state from enable state,you must disable first.
prism2mgmt_readpda: PDA may only be read in the fwload state.
prism2mgmt_ramdl_state: ramdl_state(): may only be called in the fwload state.
prism2mgmt_readpda: PDA may only be read in the fwload state.
linkstatus=DISCONNECTED (unhandled)
p80211knetdev_hard_start_xmit: Tx attempt prior to association, frame dropped.
linkstatus=CONNECTED
When it resumes from suspend, I can get the first line by modprobe-ing, but nothing else happens.

[Mr. Sinister]

Does anyone know what the suspend command calls?
I found a libsuspend.so that could be it, but I'm not sure.

[lardman]

'apm -s' I'd guess

Si

[Chet]

A couple of us on #openzaurus put together a quick-hack package to make the 6000L internal wireless survive a suspend.  Be aware that there seems to be something preventing the Power button from triggering "apm -s", so use the menu in Opie or the command line for now.

http://jacknife.org/zaurus/tosa-wireless-suspend_0.1_arm.ipk

This is for OZ 3.5.3, btw.