[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#258091: marked as done (no cpufreq avaible)



Your message dated Wed, 25 Aug 2004 19:41:24 +0200
with message-id <20040825174124.GA14002@lst.de>
and subject line Bug#258091: #258091 no cpufreq avaible
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 7 Jul 2004 15:50:31 +0000
>From m.rieche@o2online.de Wed Jul 07 08:50:31 2004
Return-path: <m.rieche@o2online.de>
Received: from (mail.o2.co.uk) [193.113.160.39] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1BiEgp-0007X3-00; Wed, 07 Jul 2004 08:50:31 -0700
Received: from host-176.gdv.uni-hannover.de (130.75.26.176) by mail.o2.co.uk (7.0.028) (authenticated as 01794766499@o2online.de)
        id 40EC1AAA0000013E for submit@bugs.debian.org; Wed, 7 Jul 2004 16:48:27 +0100
Subject: no cpufreq avaible
From: Marcus Rieche <m.rieche@o2online.de>
To: submit@bugs.debian.org
Content-Type: text/plain
Message-Id: <1089215294.13775.4.camel@localhost>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Wed, 07 Jul 2004 17:48:15 +0200
Content-Transfer-Encoding: 7bit
Delivered-To: submit@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-7.0 required=4.0 tests=BAYES_01,HAS_PACKAGE 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: kernel-image
Version: 2.6.5k7,2.6.6k7,2.6.7k7

I am using an Acer Aspire 1300DXV Laptop with an AMD Mobile Duron
1,2GHz. The subdirectory cpufreq in /sys/devices/system/cpu/cpu0 is
missing, so i can't change cpu governor or watch the frequency.
I tried to recompile a kernel, but there was the same result.


---------------------------------------
Received: (at 258091-done) by bugs.debian.org; 25 Aug 2004 17:41:27 +0000
>From hch@lst.de Wed Aug 25 10:41:26 2004
Return-path: <hch@lst.de>
Received: from verein.lst.de (mail.lst.de) [213.95.11.210] 
	by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
	id 1C01m2-000217-00; Wed, 25 Aug 2004 10:41:26 -0700
Received: from verein.lst.de (localhost [127.0.0.1])
	by mail.lst.de (8.12.3/8.12.3/Debian-6.6) with ESMTP id i7PHfO95014022
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Wed, 25 Aug 2004 19:41:25 +0200
Received: (from hch@localhost)
	by verein.lst.de (8.12.3/8.12.3/Debian-6.6) id i7PHfONQ014020;
	Wed, 25 Aug 2004 19:41:24 +0200
Date: Wed, 25 Aug 2004 19:41:24 +0200
From: Christoph Hellwig <hch@lst.de>
To: Marcus Rieche <m.rieche@o2online.de>
Cc: 258091-done@bugs.debian.org
Subject: Re: Bug#258091: #258091 no cpufreq avaible
Message-ID: <20040825174124.GA14002@lst.de>
References: <[🔎] 20040825170158.GA13053@lst.de> <200408251938.38352.m.rieche@o2online.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200408251938.38352.m.rieche@o2online.de>
User-Agent: Mutt/1.3.28i
X-Spam-Score: -4.901 () BAYES_00
X-Scanned-By: MIMEDefang 2.39
Delivered-To: 258091-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER 
	autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

On Wed, Aug 25, 2004 at 07:38:37PM +0200, Marcus Rieche wrote:
> Hi!
> I am sorry, but I forgot to close this thread. The kernel modules were 
> missing. I added the powernow-k7 module to /etc/modules. Now it works...
> 
> Thank you for your answer.

Thanks, I'm closing the bug now. (and yes, there should be a way to
autodetect these modules..)



Reply to: