Date: Sun, 13 Jun 2004 20:40:07 -0700 From: "Kevin Oberman" <oberman@es.net> To: "Dan Langille" <dan@langille.org> Cc: freebsd-mobile@freebsd.org Subject: Re: suspend/resume issues on ThinkPad T41 under 5.2.1-RELEASE Message-ID: <20040614034007.BA8045D09@ptavv.es.net> In-Reply-To: Your message of "Sun, 13 Jun 2004 21:42:24 EDT." <40CCCA40.13713.69080B47@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
> From: "Dan Langille" <dan@langille.org> > Date: Sun, 13 Jun 2004 21:42:24 -0400 > Sender: owner-freebsd-mobile@freebsd.org > > On 13 Jun 2004 at 21:35, Damian Gerow wrote: > > > Thus spake Dan Langille (dan@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. -- R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040614034007.BA8045D09>