public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Dawid <oliver-csNNzRR391izQB+pC5nmwQ@public.gmane.org>
To: "Starikovskiy,
	Alexey Y"
	<alexey.y.starikovskiy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Samsung P35
Date: Fri, 12 Nov 2004 16:29:50 +0100	[thread overview]
Message-ID: <4194D6EE.9020109@helios.de> (raw)
In-Reply-To: <6EDC9204B3704C4C8522539D5C1185E559CB72-g/v8ENnfjb4gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>

Hi,

Starikovskiy, Alexey Y wrote:

> nolapic means turning off use of Local APIC (Advanced Programmable
> Interrupt Controller), present in any Pentium processor. It has nothing
> to do with ACPI (stands for Advanced Configuration and Power Interface).

ok my fault I did not look close enough on that parameter stuff. But this
only answers the first of my questions. Any idea, why I get so much errors
on my fixed dsdt?

>> My problem:
>> Suspend does not work. Neither Fn + Sleep Key nor echo mem|disk >
>> /sys/.../state
>>
>> mem does something - display is switching to text mode but returns
>> immediately.
>>
>> As I read about problem with suspend-to-* on P30, I thought its a good
>> idea to edit the dsdt to correct a call for suspend.
>>
>> So in a second step I built my own kernel (kernel-source-2.6.8 from
>> debian distrib) with initrd patch to load my own dsdt. I dumped the
>> dsdt corrected all warnings an errors and cat it to the end of my initrd.
>>
>> Here is the result:
>> ---snip---
>> or: Method execution failed [\_SB_.PCI0.LPCB.PS2M._STA] (Node dff273e0),
>> AE_AML_REGION_LIMIT
>>    ACPI-0154: *** Error: Method execution failed
>> [\_SB_.PCI0.LPCB.PS2M._STA] (Node dff273e0), AE_AML_REGION_LIMIT
>>     ACPI-1133: *** Error: Method execution failed
>> [\_SB_.PCI0.IDEC.SECD.S_D0._STA] (Node dff27a40),
>>     ACPI-1133: *** Error: Method execution failed
>> [\_SB_.PCI0.LPCB.EC0_._Q69] (Node dff26c00), AE_AML_REGION_LIMIT
>> ---snip---
>>
>> the last few messages occur when I try to change display brightness.
>> The fan isn't working any more - this is maybe because the kernel isn't
>> able to access the corresponding acpi funcion any more.
>>
>> I wasn't able to get the beginning of the dmesg buffer because it was
>> alredy rolled out.
>>
>> Can anyone help me interpret this? What the hell went wron? The built
>> indsdt is damaged but it succeeds to handle a lot of acpi events. My own
>> one compiled without any warning or error seems to be badly damaged,
>> nearly each call fails on several errors.
>>
>> I now got a vanilla kernel 2.6.9 and start compiling but there went
>> something wrong with DRM so this is still in progress (btw. I could not
>> find any cramfs patch for 2.6.9 any more, is this path obsolete for 2.6
>> and even more, debian is using a bunch of patches, which of them are
>> really necessary, any idea?)
>>
>> Where do I need to start at?

Bye,
Oliver


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click

  parent reply	other threads:[~2004-11-12 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-12 11:23 Samsung P35 Starikovskiy, Alexey Y
     [not found] ` <6EDC9204B3704C4C8522539D5C1185E559CB72-g/v8ENnfjb4gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-11-12 15:29   ` Oliver Dawid [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-12 10:20 Oliver Dawid
     [not found] ` <41948E80.5030207-csNNzRR391izQB+pC5nmwQ@public.gmane.org>
2004-11-12 15:01   ` Pavel Machek
2004-11-12 17:44   ` Bruno Ducrot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4194D6EE.9020109@helios.de \
    --to=oliver-csnnzrr391izqb+pc5nmwq@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=alexey.y.starikovskiy-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox