From owner-freebsd-current@FreeBSD.ORG Wed Dec 3 13:02:23 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2168016A4CE for ; Wed, 3 Dec 2003 13:02:23 -0800 (PST) Received: from morpheus.webteckies.org (node123e0.a2000.nl [24.132.35.224]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB3DE43FCB for ; Wed, 3 Dec 2003 13:02:21 -0800 (PST) (envelope-from freebsd-current@webteckies.org) Received: from sarevok.idg.nl (unknown [192.168.1.12]) by morpheus.webteckies.org (Postfix) with ESMTP id 50FF7107C6; Wed, 3 Dec 2003 21:58:58 +0100 (CET) From: Melvyn Sopacua Organization: WebTeckies.org To: Nate Lawson Date: Wed, 3 Dec 2003 22:02:16 +0100 User-Agent: KMail/1.5.93 References: <20031202143252.Y18107@root.org> <200312032131.15052.freebsd-current@webteckies.org> <20031203125614.U21122@root.org> In-Reply-To: <20031203125614.U21122@root.org> MIME-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="Boundary-02=_c9kz/JC0d//OiLu"; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200312032202.20527.freebsd-current@webteckies.org> cc: Francisco Solsona cc: current@freebsd.org Subject: Re: ACPI problem, my VAIO won't come back from suspension X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 21:02:23 -0000 --Boundary-02=_c9kz/JC0d//OiLu Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 no= t, > > > 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@sarevok ~ $ uname -v =46reeBSD 5.2-BETA #0: Wed Dec 3 20:13:44 CET 2003 =20 root@sarevok.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOACPI I noticed in my dmesg.boot: $ grep PNP /var/run/dmesg.boot unknown: can't assign resources (port) unknown: can't assign resources (irq) unknown: can't assign resources (port) unknown: 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 re= ad > > 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! =2D-=20 Melvyn =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D =46reeBSD sarevok.idg.nl 5.2-BETA FreeBSD 5.2-BETA #0: Wed Dec 3 20:13:44 = CET=20 2003 root@sarevok.webteckies.org:/usr/obj/usr/src/sys/SAREVOK_NOACPI =20 i386 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D --Boundary-02=_c9kz/JC0d//OiLu Content-Type: application/pgp-signature Content-Description: signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (FreeBSD) iD8DBQA/zk9cOv9JNmfFN5URAsMgAKC0ULPxfG2OsGaToTSSbaMmNQLubACfQ2I8 SQzWSP9rSUIFrBzluKhkIEQ= =fSrk -----END PGP SIGNATURE----- --Boundary-02=_c9kz/JC0d//OiLu--