Bug#372730: Provide hints if APM/ACPI/cpufreq cannot be found
Package: cpufreqd Version: 2.0.0-1 On installation, cpufreqd probes to see whether power management (APM, ACPI or PMU) and CPUFreq are available. If they are not, it aborts configuration with an explanatory message. These messages should provide some pointers to the user as to what do to. At the moment, they just say please enable ACPI, APM or PMU in your kernel or please enable a CpuFreq driver in your kernel without any hint as to what to do. For people without in-depth knowledge about power management on Linux (like me :-) ) it is not at all obvious how to get cpufreqd to work. Proposed fix: Make the texts a bit more verbose. Append some lines to the power management warning dialog, like: To enable ACPI or APM, you may need to configure your kernel appropriately (not normally necessary for stock Debian kernels) and load appropriate modules. It is recommended to install the package acpid or apmd respectively, which will automatically load the required modules. ACPI is more powerful than APM, so you should generally try it first. Append some lines to the cpufreq management warning dialog, like: To enable the CpuFreq interface, you may need to configure your kernel appropriately (not normally necessary for stock Debian kernels) and load appropriate modules. Try loading the modules under /lib/modules/kernel-version/kernel/arch/architecture/kernel/cpu/cpufreq/ and /lib/modules/kernel-version/kernel/drivers/cpufreq (replace kernel-version and architecture with the values of your system). The texts are, of course, only proposals, which may not even be correct :-). If the texts grow longer, it might be better to put them into a file under /usr/share/doc/cpufreqd and refer to that in the dialog texts. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372730: Provide hints if APM/ACPI/cpufreq cannot be found
Hello, thanks for your suggestions. On Sun, Jun 11, 2006 at 12:16:49PM +0200, Sebastian Leske wrote: Package: cpufreqd Version: 2.0.0-1 [...] The texts are, of course, only proposals, which may not even be correct :-). If the texts grow longer, it might be better to put them into a file under /usr/share/doc/cpufreqd and refer to that in the dialog texts. Yes, I'd rather put them there, in README.Debian. bye -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372730: Provide hints if APM/ACPI/cpufreq cannot be found
On Sun, Jun 11, 2006 at 02:06:01PM +0200, Mattia Dongili wrote: Hello, thanks for your suggestions. On Sun, Jun 11, 2006 at 12:16:49PM +0200, Sebastian Leske wrote: Package: cpufreqd Version: 2.0.0-1 [...] The texts are, of course, only proposals, which may not even be correct :-). If the texts grow longer, it might be better to put them into a file under /usr/share/doc/cpufreqd and refer to that in the dialog texts. Yes, I'd rather put them there, in README.Debian. That may actually be a better place for them. But in that case please add a short note to the debconf failure messages, so people will know to look into README.Debian, something like Additional configuration may be needed to activate this feature. See /usr/share/doc/cpufreqd/README.Debian for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#372730: Provide hints if APM/ACPI/cpufreq cannot be found
On Sun, Jun 11, 2006 at 08:02:50PM +0200, Sebastian Leske wrote: On Sun, Jun 11, 2006 at 02:06:01PM +0200, Mattia Dongili wrote: Hello, thanks for your suggestions. On Sun, Jun 11, 2006 at 12:16:49PM +0200, Sebastian Leske wrote: Package: cpufreqd Version: 2.0.0-1 [...] The texts are, of course, only proposals, which may not even be correct :-). If the texts grow longer, it might be better to put them into a file under /usr/share/doc/cpufreqd and refer to that in the dialog texts. Yes, I'd rather put them there, in README.Debian. That may actually be a better place for them. But in that case please add a short note to the debconf failure messages, so people will know to look into README.Debian, something like Additional configuration may be needed to activate this feature. See /usr/share/doc/cpufreqd/README.Debian for more information. yes, I thought about that just a little after sending my previous mail :) -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
