public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Andreas Leppert <wudmx-S0/GAf8tV78@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	"Moore,
	Robert" <robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: ACPI_OS_NAME: no battery or no ac_adapter
Date: Tue, 21 Sep 2004 14:13:19 +0200	[thread overview]
Message-ID: <20040921121319.GA2383@elf.ucw.cz> (raw)
In-Reply-To: <1570067295-S0/GAf8tV78@public.gmane.org>

Hi!

> 
> ok, ac_adapter events are possible, but why on hell is now /proc/acpi/battery/BAT0/state -> present rate always unknown (so acpi -V doesnt give me any battery information!) if i change the ACPI_OS_NAME to "Linux", acpi -V gives me information about the battery... but there aren't any ac_adapter events!
> 
> where's the problem with this? it has to do something with the
> ACPI_OS_NAME ... 

Fix DSDT... See archives for tutorials.
								Pavel


-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 24. Go here: http://sf.net/ppc_contest.php

  parent reply	other threads:[~2004-09-21 12:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-17 17:23 ACPI_OS_NAME: no battery or no ac_adapter Andreas Leppert
     [not found] ` <1570067295-S0/GAf8tV78@public.gmane.org>
2004-09-21 12:13   ` Pavel Machek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-09-17 20:48 Moore, Robert
2004-09-17 17:10 Moore, Robert
2004-09-17 13:04 Andreas Leppert

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=20040921121319.GA2383@elf.ucw.cz \
    --to=pavel-+zi9xunit7i@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=robert.moore-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=wudmx-S0/GAf8tV78@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