From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 9558] New: Frequency scaling not working after BIOS upgrade on Asus F3jc
Date: Thu, 13 Dec 2007 22:58:45 -0800 (PST) [thread overview]
Message-ID: <bug-9558-3570@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=9558
Summary: Frequency scaling not working after BIOS upgrade on Asus
F3jc
Product: Power Management
Version: 2.5
KernelVersion: 2.6.23.1-custom
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: cpufreq
AssignedTo: cpufreq@www.linux.org.uk
ReportedBy: scurippio@gmail.com
Most recent kernel where this bug did not occur: n/a
Distribution: Debian GNU/Linux
Hardware Environment: Asus F3jc
Software Environment: n/a
Problem Description: Frequency scaling is not working after bios version 206 on
my Asus f3jc laptop (and probably on many others Asus laptops)
Steps to reproduce:
BIOS images are located here -> ftp://dlsvr01.asus.com/pub/ASUS/nb/F3Jc/
(mostly down, at 5 o'clock is the right time to login :p)
/etc/init.d/powernowd: 156: cannot create
/sys/devices/system/cpu/cpu0//cpufreq/scaling_governor: Directory nonexistent
* CPU frequency scaling not supported
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-12-14 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 6:58 bugme-daemon [this message]
2007-12-14 7:00 ` [Bug 9558] Frequency scaling not working after BIOS upgrade on Asus F3jc bugme-daemon
2007-12-14 7:00 ` bugme-daemon
2007-12-14 7:01 ` bugme-daemon
2007-12-14 8:19 ` bugme-daemon
2007-12-14 8:22 ` bugme-daemon
2007-12-14 9:44 ` bugme-daemon
2007-12-14 22:49 ` [Bug 9558] AE_AML_PACKAGE_LIMIT, Evaluating _PSS - " bugme-daemon
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=bug-9558-3570@http.bugzilla.kernel.org/ \
--to=bugme-daemon@bugzilla.kernel.org \
--cc=cpufreq@www.linux.org.uk \
/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