linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Brown, Len" <len.brown@intel.com>
To: "Tomasz Torcz" <zdzichu@irc.pl>,
	"LKML" <linux-kernel@vger.redhat.com>,
	<acpi-devel@lists.sourceforge.net>
Subject: RE: 2.6.0-test4 - lost ACPI
Date: Sat, 23 Aug 2003 12:47:04 -0400	[thread overview]
Message-ID: <BF1FE1855350A0479097B3A0D2A80EE009FCC7@hdsmsx402.hd.intel.com> (raw)

If you're using run-time ACPI features, you'll probably want to
make sure that your MB BIOS is the latest available.

I didn't see which VIA 693 MB you've got, but it could be that a
BIOS upgrade would move it from 09/13/00 to something past 1/1/2001 --
the (yes, arbitrary) cutoff for enabling ACPI by default.

Or you could add "acpi=force" to your command line, as suggested in the
dmesg output.

Or you could change the source to alter or disable #define
ACPI_BLACKLIST_CUTOFF_YEAR 2001

If your system misbehaves when ACPI is enabled by one of these methods,
please let me know.

Thanks,
-Len


> -----Original Message-----
> From: Tomasz Torcz [mailto:zdzichu@irc.pl] 
> Sent: Saturday, August 23, 2003 6:53 AM
> To: LKML
> Subject: 2.6.0-test4 - lost ACPI
> 
> 
> 
> Hi,
> 
> I am using ACPI for few years now. As far as I can see, on my
> machine it is only usfeul for binding events to Power button (like
> running fbdump) and for powering off. I'm also experimenting
> with swsusp, which I run by /proc/acpi/sleep.
> 
> 2.6.0-test4 has a surprise for me:
> 
> Linux version 2.6.0-test4 (zdzichu@mother) (gcc version 
> 3.3.1) #15 Sat Aug 23 12:03:
> 02 CEST 2003
> Video mode to be used for restore is ffff
> BIOS-provided physical RAM map:
>  BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
>  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
>  BIOS-e820: 0000000000100000 - 0000000013ff0000 (usable)
>  BIOS-e820: 0000000013ff0000 - 0000000013ff3000 (ACPI NVS)
>  BIOS-e820: 0000000013ff3000 - 0000000014000000 (ACPI data)
>  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
> 319MB LOWMEM available.
> On node 0 totalpages: 81904
>   DMA zone: 4096 pages, LIFO batch:1
>   Normal zone: 77808 pages, LIFO batch:16
>   HighMem zone: 0 pages, LIFO batch:1
> DMI 2.1 present.
> ACPI disabled because your bios is from 00 and too old
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> You can enable it with acpi=force
> ACPI: RSDP (v000 VIA693                                    ) 
> @ 0x000f70c0
> ACPI: RSDT (v001 AWARD  AWRDACPI 0x42302e31 AWRD 0x00000000) 
> @ 0x13ff3000
> ACPI: FADT (v001 AWARD  AWRDACPI 0x42302e31 AWRD 0x00000000) 
> @ 0x13ff3040
> ACPI: DSDT (v001 VIA693 AWRDACPI 0x00001000 MSFT 0x0100000a) 
> @ 0x00000000
> 
> WTF? My BIOS was perfectly good all those years! And no, there is
> no upgrade for my motherboard available. Using acpi=force is ugly
> and un-understandable.
> 
> There are also some strange directories in /proc :
> dr-xr-xr-x    2 root     root            0 Aug 23 12:50 
> /proc/ac_adapter/
> dr-xr-xr-x    2 root     root            0 Aug 23 12:50 /proc/fan
> 
> they are empty, but they should be in /proc/acpi/
> 
> Attached files:
> Output from dmidecode, lspci -v, my dmesg and /proc/cpuinfo
> 
> [Please CC me on replies. Thank you].
> 
> -- 
> Tomasz Torcz                 "God, root, what's the difference?" 
> zdzichu@irc.-nie.spam-.pl         "God is more forgiving."   
> 

             reply	other threads:[~2003-08-23 16:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 16:47 Brown, Len [this message]
2003-08-23 16:59 ` Tomasz Torcz
  -- strict thread matches above, loose matches on Subject: below --
2003-08-24  2:07 Felipe Alfaro Solana
2003-08-23 22:31 Brown, Len
2003-08-23 20:58 Brown, Len
2003-08-23 10:52 Tomasz Torcz
2003-08-23 21:55 ` Andrew Morton
2003-08-23 22:04   ` Tomasz Torcz
2003-08-23 22:24     ` Andrew Morton
2003-08-24 21:27     ` Wes Janzen

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=BF1FE1855350A0479097B3A0D2A80EE009FCC7@hdsmsx402.hd.intel.com \
    --to=len.brown@intel.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.redhat.com \
    --cc=zdzichu@irc.pl \
    --subject='RE: 2.6.0-test4 - lost ACPI' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).