ACPI problem, my VAIO won't come back from suspension

[Melvyn Sopacua]

On Wednesday 03 December 2003 21:57, Nate Lawson wrote:
> On Wed, 3 Dec 2003, Melvyn Sopacua wrote:
> > On Tuesday 02 December 2003 23:34, Nate Lawson wrote:
> > > Try other states (acpiconf -s 1, 2, 4).  If one works, use it.  If not,
> > > try disabling acpi and using apm(4) to suspend and resume.
> >
> > Normally that would be grand, but now that I've not compiled acpi into
> > the kernel, I have no /dev/apm anymore as well.
>
> If you don't have acpi(4), then you need to add "device apm" to your
> kernel to enable apm(4) support.

$ grep apm /sys/i386/conf/SAREVOK_NOACPI
device          apm
mdev at sarevok    ~
$ uname -v
FreeBSD 5.2-BETA #0: Wed Dec  3 20:13:44 CET 2003     
root at sarevok.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOACPI

I noticed in my dmesg.boot:
$ grep PNP /var/run/dmesg.boot
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0f13> can't assign resources (irq)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0401> can't assign resources (port)

I hope that's not what I think it is :)

> > Even with acpi, I never got a /dev/apmctl so apmd never worked. I've read
> > through devfs(5)/(8), but as far as I understand, it is the driver's
> > responsibility to create the device and even if you could do it in
> > userland, than it will just be a non-configured device.
>
> You can't use apmd with acpi(4).  It has /dev/acpictl.

Thanx!
-- 
Melvyn

=======================================================
FreeBSD sarevok.idg.nl 5.2-BETA FreeBSD 5.2-BETA #0: Wed Dec  3 20:13:44 CET 
2003     root at sarevok.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOACPI  
i386
=======================================================
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: signature
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20031203/f5ec20c2/attachment.bin