Date: Tue, 31 Jan 2006 20:34:30 +0100 From: Manfred Lotz <manfred.lotz@arcor.de> To: "Kevin Oberman" <oberman@es.net> Cc: freebsd-acpi@freebsd.org Subject: Re: suspend/resume event Message-ID: <20060131203430.6c9ebe0c.manfred.lotz@arcor.de> In-Reply-To: <20060126161526.EDF304503E@ptavv.es.net> References: <20060126143040.a6b1f796.manfred.lotz@arcor.de> <20060126161526.EDF304503E@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Jan 2006 08:15:26 -0800
"Kevin Oberman" <oberman@es.net> wrote:
> > Date: Thu, 26 Jan 2006 14:30:40 +0100
> > From: Manfred Lotz <manfred.lotz@arcor.de>
> > Sender: owner-freebsd-acpi@freebsd.org
> >=20
> > On Sat, 21 Jan 2006 20:50:23 -0800
> > Nate Lawson <nate@root.org> wrote:
> >=20
> > > Manfred Lotz wrote:
> > > > Hi there,
> > > > With my Samsung X20 1730 suspend /resume works fine when doing
> > > > acpiconf -s 3. I added /etc/rc.d/moused restart
> > > > in /etc/rc.resume and the touchpad mouse gets awake after
> > > > resuming. That's great.
> > > >=20
> > > > However when closing the lid (I set
> > > > hw.acpi.lid_switch_state=3DS3) and then pressing the power button
> > > > although suspend/resume works fine the mouse won't get
> > > > restarted. This means /etc/rc.resume and
> > > > presumably /etc/rc.suspend won't get called in this case.
> > > >=20
> > > > Same happen when pressing Fn-ESC the key for suspend.
> > > >=20
> > > > How can I make sure /etc/rc.suspend as well as /etc/rc.resuem
> > > > gets called in the "non-acpiconf" cases?
> > >=20
> > > Ok, I committed code to -current to provide a resume event and
> > > will mfc in a week or two. You can catch it in devd.conf with:
> > >=20
> > > notify 10 {
> > > match "system" "kern";
> > > match "subsystem" "power";
> > > match "type" "resume";
> > > action "SOME SCRIPT";
> > > };
> > >=20
> >=20
> > Well, I had problems testing it. I actually have a 6.0 STABLE on my
> > Samsung and installed a small 7.0 current system. However, it didn
> > =B4't even boot with ACPI. It stumbles over acd0 where it is simply
> > hanging with timeout stuff or so.
> >=20
> > Could I possible copy some src files to my 6.0 system and rebuild a
> > kernel in order to test it?
>=20
> This is a known problem with current. The work-around is to disable
> DMA for the cd. Add hw.ata.ata_dma=3D0 to /boot/loader.conf.
>=20
Thanks for the hint. Actually it was hw.ata.atapi_dma=3D0 which made it.
--=20
Manfred
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060131203430.6c9ebe0c.manfred.lotz>