Re: Suspend Mode SuSE 9.2 and Autostart for SuSE

[Jeremey Wise <Jeremey Wise Agilysys com>]

Thx for the reply

On Mon, 2005-03-07 at 11:40 -0500, Jason 'vanRijn' Kasper wrote:
> On Monday 07 March 2005 10:14, Jeremey Wise wrote:
> > Cleaning up some of the last bits o' irritating things I have to do to
> > get Linux as my work OS perfect.
> >
> > Profile:
> > IBM Thinkpad T41 running fully patched version of SuSE 9.2. Evolution
> > 2.x. Pilot device is a SPi500 Samsung phone
> >
> 
> Cool.  =:)  I have an IBM A31 laptop, so we've similar systems.
> 
> > Issues:
> > 1) I use suspend a lot as it easy to just suspend the laptop and go
> > home.... vs shutting it down every day. I have found that gpilotd does
> > NOT EVER work after waking up from a suspended state. I alway end up
> > killing the process and respawning it. Is their a way to have this
> > respawn upon restart or to work better with suspend?
> >
> 
> I believe the culprit here is the USB subsystem on our laptops.  I have to do 
> the same thing.  I have 2 files sitting in /etc/sysconfig/apm-scripts on my 
> Fedora Core 3 system that do this for me.  The apmcontinue-pre script is run 
> at suspend and the apmcontinue script is run at resume.  
> 
> #/etc/sysconfig/apm-scripts/apmcontinue-pre
> killall gpilotd
> rmmod -f -v visor
> rmmod -f -v uhci-hcd
> 
> #/etc/sysconfig/apm-scripts/apmcontinue
> modprobe uhci-hcd
> modprobe visor
> 
I tried adding these scripts but (correct me if I am wrong) this is
called via APM and if I am using ACPI then this may explain why this has
no effect on the current issue. Question still stands as to how to get
SUSE to parse said requested stops and starts.

> I've other stuff in there too, but that's what's relevant to your question.  
> I've switched from gpilot to kpilot a couple of months ago, so I can't tell 
> you if it's gotten any better since.  And, if you run the gnome-pilot applet, 
> when your system resumes, the applet should take care of restarting gpilotd 
> properly, iirc.
> 
I have to use gpilotd as it is the only pilot sync supported with
Evolution (which I have to have to work with my corp exchange
environment).
> 
> 
> > 2) When I boot the laptop fresh (ie not sleep) gpilotd never starts
> > automatically. I have not found a way to get it to start the
> > gpilod-control process in the background automatically... .this kind of
> > dove-tails in to question one because the likely (at least short term
> > fix) is to figure out how to tell suspend script to unload gpilotd and
> > the reload after suspend). Is their a way to call it to automatically
> > spawn? (I realize that this could / more likely is a SuSE question but I
> > have yet to find a good user group for these kinds of questions).
> >
> 
> I believe if you add gnome-pilot-applet to your session and tell the session 
> to start it and restart it if need be, this should work.
If you mean 'session' as in leave the control applet open and let it
hang around ... it works to have it restart but I prefer to just have it
work in the background (ie not an open session on my desktop) but I can
find no automated way to do this.

> 
> > 3) I have found that my PALM / Phone does not work well with transfer of
> > large files. gpilotd just times out and on occasion will hang hard
> > (reboot laptop or go into some kind of state where I can not 'kill -9'
> > the process. This is  very rare and I believe the issue will be resolved
> > in with the new pilot-link version. Any comments on this?
> 
> Ouch.  By transfer, you mean installation?  Did you try pilot-xfer -i from a 
> command line (after killing off gpilotd) to see if you can see what's 
> failing?
I get no errors I can post the logs from /var/log/messages but their is
nothing but timeouts from phone trying to establish sync and nobody
responding (that is until I reboot which I HATE to do). Is their a way
to debut when a thread is hung/ non-responsive. I will be glad to do
this if it will help.

-- 
Thanks,

Jeremey Wise
jeremey wise agilysys com

All opinions or information expressed here are personal in nature and do
not reflect the official position of Agilysys Inc.