Date: Mon, 2 Apr 2007 07:54:34 +0000 (UTC) From: Andrew <aremo@ngi.it> To: freebsd-acpi@freebsd.org Subject: Re: No resume on Acer Aspire 5101AWLMi (6.2-RELEASE) Message-ID: <euqcrq$i0u$1@sea.gmane.org> References: <eu9jp9$aa8$1@sea.gmane.org> <eulrj7$s24$1@sea.gmane.org> <461013F0.2090503@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 01 Apr 2007 13:20:00 -0700, Nate Lawson <nate@root.org> wrote: > If you don't get a beep at all, something is hanging before FreeBSD even > gets control. Try removing extra hardware, compiling out various device > drivers, etc. > > STR is very hard to get right given the wide number of BIOS-specific > bugs that we can't even see from the OS. Add to that the immature state > of many X/display drivers in supporting resume and you can understand > why even Linux, which has 10x the developers and assistance from Intel > employees still has a lot of the same problems. Hi, thanks for your replies. There is an update: I have found that if I issue "acpiconf -s 3" from the KDE Konsole (rather than the VGA console), the laptop goes to sleep correctly AND it even wakes up. Unfortunately, when it wakes up, all window decorations and fonts are corrupt (desktop background and icons are OK). Killing kdm-bin and X and then restarting them does not fix the problem. What I find strange, is that KDE seems to make part of the resume process work, while the computer hangs if the suspend/resume is handled only from the VGA console. I can testify that this laptop used to suspend/resume flawlessly under Kubuntu. That and the lack of errors when compiling acpidump's output lead me to think that the problem might not lie in Acer's ACPI bytecode. I'll post my experiments and findings, but at the kernel level I think there's not much I can strip away because it's already very bare-bones now. Bye, Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?euqcrq$i0u$1>