All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Sérgio Monteiro Basto" <sergiomb-5ng0By4jB+/QUPosyRRdSA@public.gmane.org>
To: acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: dsdt and more
Date: 27 Oct 2002 00:57:22 +0100	[thread overview]
Message-ID: <1035676644.1476.18.camel@darkstar.portugal> (raw)

[-- Attachment #1: Type: text/plain, Size: 1887 bytes --]

I will report all strange things acpi related in my Compaq pressario
706EA. 


./iasl -tc -i acpi_dsdt.dsl 
give me this strange error, the others error have fixes. 
acpi_dsdt.dsl   549:                     Zero 
Error    1037 -                 parse error ^ 


if I override bios with this dsdt fixed deleting or not deleting this
Zeros, my BAT is not recognized. 
without override I can read BATTERY information. 

"Table [SSDT] - 0 Objects with 0 Devices 0 Methods 0 Regions" 


" acpi_processor-0897 [21] acpi_processor_get_per: Unsupported address
space [127] (control_register) 
ACPI: Processor [CPU0] (supports C1 C2, 16 throttling states)" 

with this new verion this mesg disappears ;), know I don't have
/proc/processor. 

acpidmp > dmp.bin 
acpidmp DSDT > DSDT.bin 
acpidmp FACP > FACP.bin 
acpidmp FACS > FACS.bin 
acpidmp FADT > FADT.bin 
acpidmp RSDP > RSDP.bin 
acpidmp RSDT > RSDT.bin 
acpidmp SSDT > SSDT.bin 
cat /proc/acpi/fadt > fadt.bin 

from dmesg: 
ACPI: RSDP (v000 PTLTD                      ) @ 0x000f6dd0 
ACPI: RSDT (v001 PTLTD    RSDT   01540.00000) @ 0x0defb63b 
ACPI: FADT (v001 COMPAQ  EAGLES  01540.00000) @ 0x0defeeb6 
ACPI: SSDT (v001 PTLTD  POWERNOW 01540.00000) @ 0x0defef2a 
ACPI: DSDT (v001 COMAPQ   EAGLES 01540.00000) @ 0x00000000 
ACPI: Vendor "COMAPQ" System "  EAGLES" Revision 0x6040000 has a known
ACPI BIOS problem. 
ACPI: Reason: SCI issues (C2 disabled). This is a recoverable error 
ACPI: BIOS passes blacklist 


and finally 
Oct 21 03:42:57 darkstar kernel: [ACPI Debug] String: USB runtime event 
Oct 21 03:42:57 darkstar kernel: acpi_bus-0263 [15]
acpi_bus_get_device   : Error getting context for object [cde28ee8] 
Oct 21 03:42:57 darkstar kernel: hub.c: USB new device connect on
bus1/1, assigned device number 3 
Oct 21 03:42:57 darkstar kernel: usb.c: USB device 3 (vend/prod
0x5ab/0x200) is not claimed by any active driver. 


[-- Attachment #2: bins.tar.gz --]
[-- Type: application/x-gzip, Size: 6345 bytes --]

             reply	other threads:[~2002-10-26 23:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-26 23:57 Sérgio Monteiro Basto [this message]
     [not found] ` <1035676644.1476.18.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2002-10-27  0:41   ` dsdt and more Sérgio Monteiro Basto
  -- strict thread matches above, loose matches on Subject: below --
2002-10-28 18:04 Moore, Robert

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=1035676644.1476.18.camel@darkstar.portugal \
    --to=sergiomb-5ng0by4jb+/quposyrrdsa@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.