From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: "Yu, Luming" <luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: rmuehlhoff <rmuehlhoff-52dn/g0OV9M@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
acpi-support-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: [Acpi4asus-user] ACPI with Kernel 2.6.0-test9 on Asus M2N
Date: Mon, 3 Nov 2003 02:21:49 +0100 [thread overview]
Message-ID: <20031103012149.GA19629@hell.org.pl> (raw)
In-Reply-To: <3ACA40606221794F80A5670F0AF15F8401720B72-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
Thus wrote Yu, Luming:
> Did you have APIC enabled ? If so, please try patch at http://bugme.osdl.org/show_bug.cgi?id=1269
A sidenote: this patch allows to boot an ASUS L3800C with both APIC and
ACPI enabled. LAPIC is disabled by BIOS by default and since some early
2.4.23-pre (when the patch to explicitely reenable such an APIC went in),
this particular laptop locked dead while executing _STA and _INI -- the
reason why it eventually got blacklisted.
In summery: booting with this patch, ACPI and LAPIC (adding lapic to the
commandline to force-enable it) works fine. Once the patch is merged, the
laptop may be removed from the blacklist.
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
prev parent reply other threads:[~2003-11-03 1:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 3:49 [ACPI-sppt] RE: [ACPI] Re: [Acpi4asus-user] ACPI with Kernel 2.6.0-test9 on Asus M2N Yu, Luming
[not found] ` <3ACA40606221794F80A5670F0AF15F8401720B72-4yWAQGcml64gGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2003-11-03 1:21 ` Karol Kozimor [this message]
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=20031103012149.GA19629@hell.org.pl \
--to=sziwan-detuoxkzssqrdjvtcaxf/a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=acpi-support-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=luming.yu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=rmuehlhoff-52dn/g0OV9M@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.