Bug 302365

Summary:	sys-power/cpufreqd-2.3.4-r2: false error message claiming no CONFIG_CPU_FREQ is available
Product:	Gentoo Linux	Reporter:	Martin Mokrejš <mmokrejs>
Component:	Current packages	Assignee:	Mobile Herd (OBSOLETE) <mobile+disabled>
Status:	RESOLVED TEST-REQUEST
Severity:	normal
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	config.gz

Description Martin Mokrejš 2010-01-26 20:37:47 UTC

Something got screwed on my system with recent updates. :( At the moment cpufreqd does not start, probably because of its dependency on lm_sensors. lm_sensors exit because i2c-proc cannot be loaded (probably because i2c_proc exists).

What I am reporting here is that the init.d script bundled with cpufreqd prints a false error message:
"cpufreqd requires the kernel to be configured with CONFIG_CPU_FREQ ...". I have /preoc/config.gz provided through my kernel. It looks the init.d script did not really bother to look into the file at all.

Comment 1 Martin Mokrejš 2010-01-26 20:38:21 UTC

Created attachment 217496 [details]
config.gz

Comment 2 Sheldon Hearn 2010-07-27 14:01:16 UTC

(In reply to comment #0)
> What I am reporting here is that the init.d script bundled with cpufreqd prints
> a false error message:
> "cpufreqd requires the kernel to be configured with CONFIG_CPU_FREQ ...". I
> have /preoc/config.gz provided through my kernel. It looks the init.d script
> did not really bother to look into the file at all.

Does your full error output look like this?

 * Caching service dependencies ...                                       [ ok ]
/lib64/rc/sh/runscript.sh: 252: [[: not found
/lib64/rc/sh/runscript.sh: 252: [[: not found
 * cpufreqd requires the kernel to be configured with CONFIG_CPU_FREQ
 * Make sure that the appropiate kernel drivers for your CPU are
 * built-in or loaded.
 * ERROR: cpufreqd failed to start

If so, you probably have /bin/sh linked to dash.  The init script for cpufreqd relies on /bin/sh being a symlink to bash, because it contains a bashism:

    if [[ ! -f ${CONFIGFILE} ]]; then
        ...
    fi

I've no idea why the script uses this syntax.  It's not required and works fine with single bracket conditionals.

Ciao,
Sheldon.

Comment 3 Pacho Ramos gentoo-dev

2012-10-28 12:20:25 UTC

please retry with 2.4.2-r1