Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 148081 - Gnome Frequency Scaling Monitor: Setting governor for cpu1 fails
Summary: Gnome Frequency Scaling Monitor: Setting governor for cpu1 fails
Status: RESOLVED DUPLICATE of bug 168685
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] GNOME (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-18 09:21 UTC by Markus Herhoffer
Modified: 2007-03-04 23:16 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Herhoffer 2006-09-18 09:21:10 UTC
If Gnome Frequency Scaling Monitor 2.14.2 is used twice for CoreDuo systems, the second instance (configured for cpu1) doesn't work properly while the first instance for cpu0 works fine:
- setting the governor for cpu1 fails; no error message
- setting the frequency for cpu1 fails; no error message

Setting the frequency/governor with cpufreq-set or directly with echo "foobar" > /dev/sys/devices/system/cpu/cpux/...../governor works perfectly for both cores.
Comment 1 Rémi Cardona (RETIRED) gentoo-dev 2007-03-04 23:16:05 UTC
Check your sysfs, cpu1 should be a symlink to cpu0 as both cores always run at the same speed iirc.

Thanks

*** This bug has been marked as a duplicate of bug 168685 ***