Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Wed, Mar 09, 2011 at 11:11:11PM -0500, David Kramer wrote: > On 03/09/2011 12:13 PM, Nuno Sucena Almeida wrote: > > On Sunday, March 06, 2011 11:42:58 PM David Kramer wrote: > >> What else can I try? > > > > As a temporary measure you can try to disable power saving from the computer > > BIOS ? > > I did a quick search and found the following bug > > <https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/637845> > > > > and from comment #12 onwards: > > > > <https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/637845/comments/12> > > " > > To see if you have the same problem, do a: > > $ cat /sys/devices/system/cpu/cpu0/cpufreq/bios_limit > > In my case, anything less than 2400000 means the workaround is necessary. > > Hmm. I don't even have that file. Sounds like you haven't loaded the appropriate module to control your CPU's power saving feature. What CPU? From /proc/cpuinfo, please? -dsr- -- http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference. You can't defend freedom by getting rid of it.
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |