Compaq Presario V3000

[Nate Lawson]

Three things to try:

1. Disable burst mode by setting debug.acpi.ec.burst="0" in loader.conf.
 If that doesn't help, try adding debug.acpi.ec.timeout="1000" to
loader.conf

2. If that doesn't help, enable the code in the #if 0 segment.  (Just
delete the #if 0 and #endif lines and recompile).

3. 1 & 2 together.

-Nate

David Schulz wrote:
> I downloaded and applied this patch without any errors. when booting up
> i manually loaded the new acpi.ko, but once finished booting i still get
> the exact same messages.
> 
> On Mar 19, 2007, at 2:22 AM, Nate Lawson wrote:
> 
>>> On Mar 18, 2007, at 6:59 PM, Abdullah Ibn Hamad Al-Marri wrote:
>>>
>>>> On 3/18/07, David Schulz <mailinglists at tca-cable-connector.com> wrote:
>>>>> Hello all,
>>>>>
>>>>> i have a Compaq Presario V3000. After installing FreeBSD i am getting
>>>>> these type of Messages to my Log.
>>>>>
>>>>>      ACPI-0501: *** Error: Handler for [EmbeddedControl] returned
>>>>> AE_NO_HARDWARE_RESPONSE
>>>>>      ACPI-1304: *** Error: Method execution failed [\
>>>>> \_SB_.PCI0.LPCB.EC0_.GBST] (Node 0xc32a1ca0), AE_NO_HARDWARE_RESPONSE
>>>>>      ACPI-1304: *** Error: Method execution failed [\
>>>>> \_SB_.PCI0.LPCB.EC0_.BAT0._BST] (Node 0xc32a1b60),
>>>>> AE_NO_HARDWARE_RESPONSE
>>>>>
>>>>> I have attached my full dmesg output in dmesg.txt.
>>>>>
>>>>> Is there any way of resolving this? Basically, these Messages
>>>>> continue to appear at maybe 30 second interval.
>>>>>
>>>>> Thanks a lot,
>>>>> David
>>>>
>>>> Hello,
>>>>
>>>> You may need to check [HEADSUP] ACPI-CA 20070126 import  thread.
>>>
>>> So this means there is a patch out somewhere that could fix this? could
>>> i apply that patch to 6.2 ?
>>>
>>> Thanks,
>>> David
>>>
>>
>> I recently committed a major reworking of the embedded controller
>> driver in -current.  See this message:
>>
>> http://lists.freebsd.org/pipermail/freebsd-current/2007-February/069525.html
>>
>>
>> It includes a patch to try for 6.x.  You may need to tweak the various
>> parameters, again, see the message.
>>