laptop standby

[Aroon Pahwa]

On Mon, 11 Oct 2004 13:37:36 +1000, Daniel McLean
<daniel.mclean at optusnet.com.au> wrote:
> lsmod is the commmand that will LiSt the MODules you have running...
> 
> run lsmod and see which one usbcore is using. The command below will do
> the job:
> 
> lsmod | grep 'usb'
> 
> Running this will give u something like this:
> 
> usbcore               115684  3 ohci_hcd
> 
> and the name on the far right is the driver/module u need to remove..
> 
> modprobe -r ohci_hcd
> 
> will remove the OHCI USB module...
> 
> So yeah if you apply that to your system it should do the trick..
> 
> Oh and in answer to your question I am not sure if it is possible to map
> the device number directly to a module name.. But doing above will work.
> 
> 
> 
> 
> On Sun, 2004-10-10 at 02:35 -0400, Aroon Pahwa wrote:
> > On Sun, 10 Oct 2004 11:38:13 +1000, Daniel McLean
> > <daniel.mclean at optusnet.com.au> wrote:
> > > On Sat, 2004-10-09 at 20:24 +0100, Jan Kokoska wrote:
> > >
> > > > Make a script for sleep event, unload all problematic modules prior to
> > > > "echo mem > /sys/power/state" and reload the back afterwards in the same
> > > > script. This can be used in your acpid configuration and with proper
> > > > laptop-specific driver support bound to your special function buttons.
> > >
> > > Using this script:
> > >
> > > modprobe -r ohci_hcd
> > > echo standby > /sys/power/state
> > > modprobe ohci_hcd
> > >
> > > It seems to suspend (suspend LED on my laptop comes on) but my LCD stays
> > > on (ie. I can still see a console type view)??
> > >
> > > Below is the corresponding dmesg output:
> > >
> > > ohci_hcd 0000:00:14.0: remove, state 1
> > > usb usb1: USB disconnect, address 1
> > > ohci_hcd 0000:00:14.0: USB bus 1 deregistered
> > > PM: Preparing system for suspend
> > > Stopping tasks: ==================================================================================================|
> > > orinoco_lock() called with hw_unavailable (dev=d0b26800)
> > > ali_stimer_read: stimer is not ready.
> > > ali_stimer_read: stimer is not ready.
> > > ali_stimer_read: stimer is not ready.
> > > ali_stimer_read: stimer is not ready.PM: Entering state.
> > > Back to C!
> > > PM: Finishing up.
> > > ACPI: PCI interrupt 0000:00:10.0[A]: no GSI - using IRQ 15
> > > ACPI: PCI interrupt 0000:00:14.0[A] -> GSI 10 (level, low) -> IRQ 10
> > > eth0: New link status: Connected (0001)
> > > Restarting tasks... done
> > >
> >
> > when you do modprobe -r [something], how do you find out what
> > [something] is for each device?  what is that called?  so for
> > instance, would [something] for the following be ICH4?
> >
> > $lspci
> > 0000:00:1d.7 USB Controller: Intel Corp. 82801DB (ICH4) USB2 EHCI
> > Controller (rev 01)
> >
> > thats the device im currently having trouble with when tring to go into standby.
> >
> > aroon pahwa
> > viperstyx at gmail.com
> 
> 


thanks for the help Daniel.  I created a bash script as follows:

modprobe -r uhci_hcd
modprobe -r ehci_hcd
modprobe -r ath_pci #wlan

echo standby > /sys/power/state

modprobe ehci_hcd
modprobe uhci_hcd
modprobe ath_pci

i first tried echo mem > /sys/power/state, however i couldnt figure
out how to get my machine to come back to life!  now trying standby,
the machine goes into standby but returns emmediatly.  any ideas with
whats wrong?  im not getting any errors in /var/log/syslog like xyz
refuses to suspend like many of us experienced with usb.  does it look
like script problem or may be something with my machine?  i've got an
IBM X40.

thanks!

aroon pahwa
viperstyx at gmail.com