We believe that your issue has been closed by the upload of
Version 0.8.10 of grml-autoconfig from Michael Prokop <mika@grml.org>.
The explanation is attached below
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.7
Date: Fri, 15 Aug 2008 23:06:26 +0200
Source: grml-autoconfig
Binary: grml-autoconfig
Architecture: source all
Version: 0.8.10
Distribution: unstable
Urgency: low
Maintainer: Michael Prokop <mika@grml.org>
Changed-By: Michael Prokop <mika@grml.org>
Description:
grml-autoconfig - main bootup process of a grml system
Changes:
grml-autoconfig (0.8.10) unstable; urgency=low
.
* Update cpufrequency handling to reflect changes in current
kernel versions (like 2.6.26-grml). The cpufrequency modules
are available at $KERNEL/kernel/arch/x86/kernel/cpu/cpufreq
due to the x86/amd64 merge.
[Closes: issue505]
Files:
71b8b9086f8e66f26f109494af05cbd2 606 grml optional grml-autoconfig_0.8.10.dsc
6f9a6fa29f318a859e4956286fe4cfc2 54918 grml optional grml-autoconfig_0.8.10.tar.gz
c7d811d13466cad3e858c5299152de08 55330 grml optional grml-autoconfig_0.8.10_all.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIpfEg2N9T+zficugRAiCxAJ9gNghMs4gXWEVH00L/1Ynskj8M4QCfZqfD
EnXppXtYvfqZz2uGGPlLBM4=
=ZZsB
-----END PGP SIGNATURE-----
We have to check why current Debian/unstable and kernel 2.6.26 seem to need /
etc/init.d/loadcpufreq (from package cpufrequtils), maybe we have to activate
it per default in /etc/runlevel.conf from now on.