suspend/resume issues on ThinkPad T41 under 5.2.1-RELEASE

[Dan Langille]

On 13 Jun 2004 at 20:40, Kevin Oberman wrote:

> > From: "Dan Langille" <dan at langille.org>
> > Date: Sun, 13 Jun 2004 21:42:24 -0400
> > Sender: owner-freebsd-mobile at freebsd.org
> > 
> > On 13 Jun 2004 at 21:35, Damian Gerow wrote:
> > 
> > > Thus spake Dan Langille (dan at langille.org) [13/06/04 21:32]:
> > > : The existing issues after a resume are:
> > > : 
> > > : - blinking cursor at top left (I'll try killing moused in 
> > > : /etc/suspend and starting it again in /etc/resume)
> > > : 
> > > : - em0 is dead upon resume (I'll try killing dhclient, and starting it 
> > > : again, as well as setting).  I keep getting 
> > > 
> > > Would this not be a good idea to do anyway?  As you're not guaranteed to
> > > resume on the same network you went to sleep on.  In fact, I'd wager a guess
> > > to say that the majority of resumes will occur on different networks,
> > > requiring a different DHCP lease.
> > 
> > Agreed.  FWIW, I'm just trying to figure out how to do this.
> 
> I have no clean solution. Tobias Roth is working on this and I think
> it's pretty close, but until he gets it ready for prime time, it's a
> manual operation. killall dhclient, route flush, ifconfig em0 down,
> ifconfig em0 up, dhclient em0. This assumes that the network you connect
> to has a DHCP server. Of course, this requires root permissions.

Manual is good enough for me.

FWIW, "route flush" takes a very long time to complete.  As in 
minutes.  dhclient em0 fails and reports several times in 
/var/log/messages that "send_packet: Network is down".

I think it's time for sleep.  ;)

Thanks for your help.
-- 
Dan Langille : http://www.langille.org/
BSDCan - http://www.bsdcan.org/