From: Karol Kozimor <sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org>
To: rmuehlhoff <rmuehlhoff-52dn/g0OV9M@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
acpi-support-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
acpi4asus-user-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [Acpi4asus-user] ACPI with Kernel 2.6.0-test9 on Asus M2N
Date: Mon, 27 Oct 2003 18:03:59 +0100 [thread overview]
Message-ID: <20031027170359.GB11206@hell.org.pl> (raw)
In-Reply-To: <1067270730.4265.45.camel-RU1JJA7J9tM@public.gmane.org>
Thus wrote rmuehlhoff:
> I just updated from 2.4 to 2.6 kernel. I'm using the original sources wthout any patches.
> When compiling the kernel with ACPI support, it hangs on startup when initialising ACPI
> (hmm difficult to describe because I cant't give you a log for this happens so early, logging is not yt active).
>
> You know, when ACPI get initialised in the early startup phase, there are various moments where long lines of dots
> appear on the screen... In the third instance, the system hangs after a few dots.
A blind guess: try to reverse the patch [1] and recompile your kernel.
[1]
http://www.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/test/2.4.22/20031017152411-acpi_ec_gpe_query.patch
Best regards,
--
Karol 'sziwan' Kozimor
sziwan-DETuoxkZsSqrDJvtcaxF/A@public.gmane.org
-------------------------------------------------------
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community? Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
parent reply other threads:[~2003-10-27 17:03 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1067270730.4265.45.camel-RU1JJA7J9tM@public.gmane.org>]
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=20031027170359.GB11206@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=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.