From: Muskat Nuss <muskatnuss@gmx.at>
To: cpufreq@lists.linux.org.uk
Subject: Amd Turion TL-52 X2 on Amilo PA 1510> No way to change Frequency!
Date: Fri, 25 May 2007 22:22:23 +0200 [thread overview]
Message-ID: <1180124543.5822.4.camel@Tux-Devil> (raw)
So now i rebuild my kernel with cpufrequency dubugging module!
i added the cpufreq.debug=2 kernel command line parameter.
Rebooted my system .... but for now it wont boot anymore.
At booting screen my notebook got freezed @ 1 percent loading.
what now? or anything could my new kernel be wrong?
if so is there anyway to add the cmd line cpufreq.debug=2 without
rebuilding the kernel?
next reply other threads:[~2007-05-25 20:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 20:22 Muskat Nuss [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-05-29 22:48 Amd Turion TL-52 X2 on Amilo PA 1510> No way to change Frequency! Muskat Nuss
2007-05-28 19:12 Muskat Nuss
2007-05-29 17:51 ` Langsdorf, Mark
2007-05-29 19:15 ` Muskat Nuss
2007-05-29 19:42 ` Langsdorf, Mark
2007-05-30 7:15 ` Thomas Renninger
2007-05-30 16:42 ` Muskat Nuss
2007-05-30 17:05 ` Thomas Renninger
2007-05-25 20:41 Muskat Nuss
2007-05-25 5:09 Patrick Oberdorfer
2007-05-25 15:19 ` Langsdorf, Mark
2007-05-24 22:14 Muskat Nuss
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=1180124543.5822.4.camel@Tux-Devil \
--to=muskatnuss@gmx.at \
--cc=cpufreq@lists.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