From: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>
To: "Rasmus Bøg Hansen" <moffe@amagerkollegiet.dk>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>,
Daniel Nofftz <nofftz@castor.uni-trier.de>,
Andrew Grover <andrew.grover@intel.com>
Subject: Re: ACPI trouble (Was: Re: [patch] amd athlon cooling on kt266/266a chipset)
Date: Thu, 24 Jan 2002 22:15:32 +0100 [thread overview]
Message-ID: <20020124212507Z290307-13996+11382@vger.kernel.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0201241803540.1345-100000@grignard.amagerkollegiet.dk>
In-Reply-To: <Pine.LNX.4.44.0201241803540.1345-100000@grignard.amagerkollegiet.dk>
On Thursday, 24. January 2002 18:22, Rasmus Bøg Hansen wrote:
> Hello Dieter
>
> > Hello Rasmus,
> >
> > I hope that I've extracted your name right?
>
> Yup, just a danish letter in my middle-name :-)
You see, my KDE-2.2.2 (iso-8859-15, Europe) kann handle it easily...;-)
> > > However, after disabling APM and enabling ACPI, my system won't power
> > > off anymore :-(
> >
> > This should be easily solved.
> >
> > I point on your distro's startup scripts. They only look if apm is
> > enabled but _NOT ACPI...
>
> Well, RedHat 7.2 does not look if apm or acpi is configured, it just
> uses -p unless the command run was 'halt' or 'reboot'.
OK.
> When running '/sbin/poweroff' from single-user, 'halt -i -d p' is the
> last command run by the halt script. The I get the message 'Power down.'
> from the kernel and my system just hangs here.
What if you do it by hand?
> When running /sbin/poweroff from runlevel 3 or 5, 'halt -i -d -p' is
> again the last command run, follwing this from the kernel:
>
> Power down.
> hwsleep-0178 [02] Acpi_enable_sleep_state: Entering S5
Maybe this is an indication of broken BIOS.
You should grep for the ACPI diagnosis tools and send your results to the
acpi-devel list.
> And again my system hangs. Pressing the power button for 4 seconds turns
> off the computer (the BIOS is set to 'immediate power off').
What? This is contradictorily.
> In runlevel 3, the following modules are loaded (some are patched in
> from the iptables package. They should not cause this, as I can
> reproduce this without iptables configured/patched at all):
Should all be unrelated.
>
> From my 'make menuconfig:
>
> [*] Power Management support
> [*] ACPI support
> [*] ACPI Debug Statements
> <*> ACPI Bus Manager
> <*> System
> <*> Processor
> < > Button
> < > AC Adapter
> < > Embedded Controller
> < > Advanced Power Management BIOS support
I have Button enabled, too. Please try.
My .config file looks like this:
CONFIG_ACPI=y
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUSMGR=y
CONFIG_ACPI_SYS=y
CONFIG_ACPI_CPU=y
CONFIG_ACPI_BUTTON=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_EC is not set
# CONFIG_APM is not set
> At bootup I get the following regarding ACPI:
Can you send the fist lines from your boot log?
Maybe you should CC to acpi-devel.
>
> tbxface-0099 [01] Acpi_load_tables : ACPI Tables successfully
> loaded
> Parsing
> Methods:...................................................................
>................................................ 115 Control Methods found
> and parsed (364 nodes total)
> ACPI Namespace successfully loaded at root c0286ee0
> ACPI: Core Subsystem version [20011018]
> evxfevnt-0081 [02] Acpi_enable : Transition to ACPI mode
> successful
> Executing device _INI methods:.......................................
> 39 Devices found: 39 _STA, 0 _INI
> Completing Region and Field initialization:...................
> 17/24 Regions, 2/2 Fields initialized (364 nodes total)
> ACPI: Subsystem enabled
> ACPI: System firmware supports S0 S1 S4 S5
> Processor[0]: C0 C1 C2, 8 throttling states
Here is something missing. Ah, the power button thing.
>
> My motherboard is an Asus A7V133-C. Output from lspci -v:
> 00:04.4 Bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev
> 40) Subsystem: Asustek Computer, Inc.: Unknown device 8042
> Flags: medium devsel, IRQ 9
> Capabilities: <available only to root>
Unknown device 8042
Maybe here is something missing, too.
The ACPI people should lighten this. --- Andrew?
> I have very little knowledge of ACPI,
I am, too...;-)
But hey, we have OSS and Andrew and his team. They did very good work!
> ut I'll be happy to help
Every "new" ACPI chip need support.
> (if this is not my fault of course - then I will apologize for taking your
> time
Never mind.
Regards,
Dieter
next prev parent reply other threads:[~2002-01-24 21:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 15:58 [patch] amd athlon cooling on kt266/266a chipset Dieter Nützel
2002-01-24 17:22 ` ACPI trouble (Was: Re: [patch] amd athlon cooling on kt266/266a chipset) Rasmus Bøg Hansen
2002-01-24 21:15 ` Dieter Nützel [this message]
2002-01-24 23:28 ` Rasmus Bøg Hansen
2002-01-24 17:49 ` Wayne Whitney
2002-01-24 18:40 ` Petr Vandrovec
2002-01-25 0:47 ` Wayne Whitney
2002-01-25 9:48 ` Rasmus Bøg Hansen
2002-01-25 18:47 ` Pavel Machek
2002-01-24 18:48 ` pogosyan
2002-01-24 19:49 ` Kevin P. Fleming
2002-01-24 21:39 ` Daniel Nofftz
2002-01-24 19:27 ` Rasmus Bøg Hansen
2002-01-24 21:29 ` Daniel Nofftz
2002-01-24 22:24 ` Craig Knox
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=20020124212507Z290307-13996+11382@vger.kernel.org \
--to=dieter.nuetzel@hamburg.de \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=moffe@amagerkollegiet.dk \
--cc=nofftz@castor.uni-trier.de \
/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
all inboxes | Powered by JetHome®