public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arndt Schoenewald <abs-SA7OhAOe25xnNxvc45mVi0K323yFvGpRdefyYXQ/eNw@public.gmane.org>
To: Andreas Happe <andreashappe-hi6Y0CQ0nG0@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: HP Omnibook 6100
Date: Mon, 12 Aug 2002 16:02:48 +0200	[thread overview]
Message-ID: <20020812140247.GC1679@digda.intern.quelltext.com> (raw)
In-Reply-To: <slrnalap9u.4tf.andreashappe-r661u5w8kpLX9hvRLAZ2HmZy7eGcjJgl@public.gmane.org>

Hi Andreas!

On Sat, Aug 10, 2002 at 09:10:55PM +0200, Andreas Happe wrote:
> I cannot use ACPI on my Omnibook 6100 (i830m) with 2.4.17 or with
> 2.5.6+. Before 2.5.~16 (if this matters, i could rebuild my kernels to
> verbose this) the kernel booted with a "ACPI subsystem not initialized,
> disabling ACPI" - message, later kernels just go OOPS.

Sorry, but nobody on this list will care about problems you have with
2.4.17 or 2.5.16 kernels -- they are way to old.

Try 2.5.31, or 2.4.18 with a recent patch from http://sf.net/projects/acpi,
or wait a couple of days for the first "official" ACPI patch for 2.4.19
to appear. If those kernels don't work for you, post again to this list
and include your dmesg output along with a description of what goes wrong.

Good luck,
Arndt


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      parent reply	other threads:[~2002-08-12 14:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-10 19:10 HP Omnibook 6100 Andreas Happe
     [not found] ` <slrnalap9u.4tf.andreashappe-r661u5w8kpLX9hvRLAZ2HmZy7eGcjJgl@public.gmane.org>
2002-08-12 14:02   ` Arndt Schoenewald [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=20020812140247.GC1679@digda.intern.quelltext.com \
    --to=abs-sa7ohaoe25xnnxvc45mvi0k323yfvgprdefyyxq/enw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=andreashappe-hi6Y0CQ0nG0@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox