Biostar 945GC-M7 TE - won't suspend ("oper not supported"), even though sysctl's say S1 S3 supported

[Rui Paulo]

Steve Franks wrote:
> On Thu, May 1, 2008 at 2:16 PM, Rui Paulo <rpaulo at freebsd.org> wrote:
>> Steve Franks wrote:
>>
>>> Ok, I admit, I had a ucom plugged in in the dmesg I sent, but I assure
>>> you, that isn't the issue.  I even just double-checked.
>>>
>>  I think your best bet is boot with ACPI debug turned on.
>>  Try adding:
>>  options ACPI_DEBUG
>>  to your kernel config file, and:
>>  debug.acpi.layer=ACPI_ALL_DRIVERS
>>  debug.acpi.level=ACPI_LV_ALL_EXCEPTIONS
>>
>>  If that doesn't show anything particularly interesting, try increasing the
>> debugging level.
>>  For more information, see the acpi(4) man page.
>>
>>  Good luck,
>>  --
>>  Rui Paulo
>>
> 
> Finally got around to rebuilding my kernel with options acpi debug.
> Not everyone recognizes blah.foo.bar=somestring as an input to sysctl,
> and the acpi manpage is less than explicit about it also, by the way,
> saying only "some of these things have equivalent sysctl's".
> 
> Not having much luck, other than a shiny new kernel, though:
> 
> Steve
> 
> [steve at dystant /usr/obj/usr/src/sys/DYSTANT]$ sudo sysctl
> debug.acpi.layer=ACPI_ALL_DRIVERS
> debug.acpi.layer: NONE -> ACPI_AC_ADAPTER ACPI_BATTERY ACPI_BUS
> ACPI_BUTTON ACPI_EC ACPI_FAN ACPI_POWERRES ACPI_PROCESSOR ACPI_THERMAL
> ACPI_TIMER ACPI_ALL_DRIVERS
> [steve at dystant /usr/obj/usr/src/sys/DYSTANT]$ sudo sysctl
> debug.acpi.level=ACPI_LV_ALL_EXCEPTIONS
> debug.acpi.level: NONE -> ACPI_LV_ERROR ACPI_LV_WARN ACPI_LV_INIT
> ACPI_LV_DEBUG_OBJECT ACPI_LV_INFO ACPI_LV_ALL_EXCEPTIONS
> [steve at dystant /usr/obj/usr/src/sys/DYSTANT]$ sudo sysctl hw.acpi.verbose=1
> hw.acpi.verbose: 0 -> 1
> [steve at dystant /usr/obj/usr/src/sys/DYSTANT]$ sudo acpiconf -s3
> acpiconf: request sleep type (3) failed: Operation not supported

:-(

Well, I'm really out of ideas...

Sorry,
-- 
Rui Paulo