public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
To: Markus Gaugusch <markus-z+rTbpWsRgbk7+2FdBfRIA@public.gmane.org>
Cc: ACPI-Devel
	<Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: 2002-10-22 processor&thermal module broken?
Date: Thu, 24 Oct 2002 21:51:54 +0200	[thread overview]
Message-ID: <20021024195154.GC8003@poup.poupinou.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0210242106010.16976-100000-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>

On Thu, Oct 24, 2002 at 09:06:45PM +0200, Markus Gaugusch wrote:
> On Oct 24, Sebastian Zimmermann <wegwerf-juni02-XrphxVexwn4ANkabGmIAxw@public.gmane.org> wrote:
> > > Hi,
> > > I just tried 2.4.20-pre11 with latest acpi patch (+ swsusp) and there is
> > > no processor/thermal entry in my /proc anymore. Any hints?
> > Here they are also missing. 2.4.20-pre11-acpi20021022
> > Thermal zone is enabled in config file.
> Are you per chance using gcc 3.2, like me?
> May this be the problem??
> 

I just give it a try.  Do not have anymore processor too (grumble, grumble :)


ducrot@novae:~$ ls -1 /proc/acpi/
ac_adapter
alarm
battery
button
debug_layer
debug_level
dsdt
embedded_controller
event
fadt
info
sleep
thermal_zone
ducrot@novae:~$ gcc -v
Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
gcc version 2.95.4  (Debian prerelease)

-- 
Ducrot Bruno
http://www.poupinou.org        Page profaissionelle
http://toto.tu-me-saoules.com  Haume page


-------------------------------------------------------
This sf.net email is sponsored by: Influence the future 
of Java(TM) technology. Join the Java Community 
Process(SM) (JCP(SM)) program now. 
http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0003en

  parent reply	other threads:[~2002-10-24 19:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-23  9:10 2002-10-22 processor&thermal module broken? Markus Gaugusch
     [not found] ` <Pine.LNX.4.44.0210231109110.24534-100000-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2002-10-24 19:06   ` Sebastian Zimmermann
     [not found]     ` <1035486370.2453.9.camel-M6ZexevewGRpO1kdggaS62d32FDJZ+6+@public.gmane.org>
2002-10-24 19:06       ` Markus Gaugusch
     [not found]         ` <Pine.LNX.4.44.0210242106010.16976-100000-sxQ525G0OhRQK2oVCIMtW7NldLUNz+W/@public.gmane.org>
2002-10-24 19:44           ` Sebastian Zimmermann
2002-10-24 19:51           ` Ducrot Bruno [this message]
2002-10-26 23:47   ` Sérgio Monteiro Basto
     [not found]     ` <1035676074.1478.7.camel-4/PLUo9XfK/yXfm4dIG/yWZHpeb/A1Y/@public.gmane.org>
2002-10-31 15:02       ` Don Langworthy
     [not found]         ` <000001c280ee$9c442a80$02ffff0a-pDtHNsj1o9eEb1ujJ5R0Fw@public.gmane.org>
2002-11-01 23:23           ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2002-10-24 20:03 Grover, Andrew
     [not found] ` <EDC461A30AC4D511ADE10002A5072CAD0236DF7B-OU+JdkIUtvd9zuciVAfUoVDQ4js95KgL@public.gmane.org>
2002-10-25  6:31   ` Markus Gaugusch

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=20021024195154.GC8003@poup.poupinou.org \
    --to=ducrot-kk6yzipjem5g9huczpvpmw@public.gmane.org \
    --cc=Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=markus-z+rTbpWsRgbk7+2FdBfRIA@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