We believe that your issue has been closed by the upload of
Version 0.7.5 of grml-autoconfig from Michael Prokop <mika@grml.org>.
The explanation is attached below

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Wed, 04 Jul 2007 12:02:49 +0200
Source: grml-autoconfig
Binary: grml-autoconfig
Architecture: source all
Version: 0.7.5
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.7.5) unstable; urgency=low
 .
   * Integrate /etc/init.d/loadcpufreq in config_cpu() [Closes: issue238]
Files: 
 e937d10b4e00a95d2d04af110b93c13c 511 grml optional grml-autoconfig_0.7.5.dsc
 647b68a84bea8e044f6f908b84da3a21 51213 grml optional grml-autoconfig_0.7.5.tar.gz
 443d6f2b858198df16ec2c0ebcb04436 51754 grml optional grml-autoconfig_0.7.5_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFGi3QG2N9T+zficugRAg9kAJ4hpwycZjzzFUKvCseN+j7KwlkP6wCfRz05
/MD2ZIL73W7arKnjhPrJ6xM=
=Nqpp
-----END PGP SIGNATURE-----

Since cpufrequtils version 002-2.1 the file /etc/init.d/loadcpufreq is 
available which does most parts we used to do in cpufreq-detect.sh from within 
grml-scripts. Especially since the speedstep->acpi-cpufreq change for >=2.6.20 
is part of it we should adjust our script.