Possible workaround for usb/apm problem

[bluey]

Suspend:
usb0: unregister usbnet usb-0000:00:05.2-1, Sharp Zaurus SL-5x00
Wake up:
usb 1-1: new full speed USB device using address 6
usb 1-1: device not accepting address 6, error -110
usb 1-1: new full speed USB device using address 7
usb 1-1: device not accepting address 7, error -110
usb 1-1: new full speed USB device using address 8
usb 1-1: device not accepting address 8, error -110

I was able to go around rebooting by reloading sa1100_bi:
# rmmod sa1100_bi
# modprobe sa1100_bi

Could this be a solution? Add this to wake up apm scripts? See what is the problem inside the module should be the best thing to do, no?




I added the following and works fine with me: (hide your kids, this is ugly! )

FILE: /etc/apm/suspend.d/S98sa1100_bi
#!/bin/sh
rmmod sa1100_bi

FILE: /etc/apm/resume.d/R01sa1100_bi
#!/bin/sh
modprobe sa1100_bi

RESULT:
usb 1-1: USB disconnect, address 19
usb0: unregister usbnet usb-0000:00:05.2-1, Sharp Zaurus SL-5x00
usb 1-1: new full speed USB device using address 20
usb0: register usbnet at usb-0000:00:05.2-1, Sharp Zaurus SL-5x00

Clean.

Does this help Mickey?
-------------8<-------------


root@openzaurus:~# cat /etc/apm/suspend.d/S99suspend
#!/bin/sh
# only use on 3600
. /etc/devdetect/identify.h3600
check_device
if [ \"$?\" != \"0\" ]; then
    exit;
fi
#
# This stuff was orignaly in /sbin/pm_helper before the switch to run-parts
#
if [ -w /proc/sys/pm/suspend ]; then
echo > /proc/sys/pm/suspend  <--- why isn\'t apm called with --suspend instead?
else
mesg \'Unable to find /proc/sys/pm/suspend\'
fi

[bluey]

To my understanding I did this the wrong way.

sa1100_bi script should be in scripts.d and should be linked from suspend.d and resume.d and it should take care of how it is called inside the script. That two individual files are not the way to do it!

It works like the scripts in init.d and the various rc<level>.d directories where they linked in.

[Mickeyl]

Interesting work. Please post this to openzaurus-devel@lists.sf.net because personally I\'m no longer interested in nursing the kernel 2.4 oddities and I\'m not sure if anyone else of the openzaurus team reads here.

[bluey]

Ok, I believe I\'m not yet subscribed to that list, is there a form on-line, or a subscribe body/subject is enough?