Overclock does not work (E701)

[Axios]

I have tried the script on a clean Ubuntu 8.04.1 install on my EEEPC 701 (4g): everything works fine, EXCEPT that if I press "Fn + F6" I got the custom OSD saying that "The cpu is overclocked on 800 Mhz", BUT I cannot revert it to "normal" working even if I press the "Fn + F6" again....

I do not know if this is a bug about the OSD graphic/text or if it is really not working and the cpu remains overclocked all the time.

I have tried it many many times, every time it says the same thing... I have tried to reinstall and same happens... even after restarting several times the EEEPC...

[Carlos Jenkins Pérez (carlos.jenkins)]

Hi, thank you very much for the bug report.
The custom OSD that indicates "Your cpu is now overclocked to 900Mhz" appears when your computer is NOT overclocked and you're trying to enable it. If every time you press FN+F6 you got that message indicates your overclock never starts. In code you have this:
# OSD
/etc/acpi/eee-actions/eee-notify-overclock.py on
# Action
/etc/acpi/eee-actions/eee-overclock.sh on

The OSD comes first the action. The action "eee-overclock.sh on" it's not working in your installation I presume.
Could you please provide what type of installation did you choose with NiceeePC, Adam's custom Kernel or Generic Kernel modules?
The overclock should not be a problem with the Generic Kernel patched, but Adam's custom kernel work a little bit different.
I think I know what's the problem.
In eee-overclock.sh file you got:

#Check if the module exists
if [ -z "`ls /lib/modules/$(uname -r)/kernel/drivers/acpi | grep eee.ko`" ]; then
 echo "eee module not found."
 exit 1
fi

I think in Adam's Custom Kernel the module it's not located on the same place.
Please type in console to confirm:
sudo /etc/acpi/eee-actions/eee-overclock.sh on
Did you got "eee module not found."?
I'm leaving the bug to undecided until I know what Kernel did you choose.

Cheers.

[Carlos Jenkins Pérez (carlos.jenkins)]

Changing status.

[ermes (matteo-pirro)]

I known the solution! the problem is that the script /etc/acpi/eee-actions/eee-overclock.sh cannot load eee module! In fact if you try to run sudo modprobe eee you'll fail!

Looking for a solution I found RiceeeyTweak script in which module i2c_i801 is unblacklisted. In this way it's possible to load the module and the overclock is enabled. So you have just to comment line "i2c_i801" in /etc/modprobe.d/blacklist and reboot!

Sorry for my english!

[Carlos Jenkins Pérez (carlos.jenkins)]

Thank you very much ermes!
You're right. I could confirm this bug. This is already fixed in the new trunk version of the script.
Now we are one step forward to the 1.3 release.
Thanks again.

[Axios (no14ever)]

Hi,
I was away (vatacion) ;)

I confirm I use the custom kernel (Adam's?) that U can choose in your script and I confirm it gave me: "eee module not found.".

I see U have already found the solution or almost there, ready for 1.3 version of the script.

Just a small, not fully in-topic, question: will the newer versions of your script appliable to correct/add new features also for the people who already installed the very first version?

Many thanks in advance!

[Carlos Jenkins Pérez (carlos.jenkins)]

Question: will the newer versions of your script appliable to correct/add new features also for the people who already installed the very first version?

Heeee.... yes like always, you can run niceeepc in manual mode and apply specific patches. As NiceeePC is build thinking to be secure on multiple runnings it should be able to apply only the new changes. But, since now it's packed has a .deb package, I thing it's better if you remove the older version manually... I'll be thinking about it...

But the two mayor bugs was: unblacklist the i2c_i801 module, for that, run this command:

sudo sed -i '/blacklist i2c_i801/s/^/# NiceeePC :: Allow overclock on eeePC \n# /' /etc/modprobe.d/blacklist

And the seconds one type:

sudo gedit /etc/acpi/eee-actions/eee-overclock.sh

And comment lines 6 through 10 like this:

Original:

#Check if the module exists
if [ -z "`ls /lib/modules/$(uname -r)/kernel/drivers/acpi | grep eee.ko`" ]; then
 echo "eee module not found."
 exit 1
fi

Edited:

#Check if the module exists - Commented for Adam's kernel compatibility
#if [ -z "`ls /lib/modules/$(uname -r)/kernel/drivers/acpi | grep eee.ko`" ]; then
# echo "eee module not found."
# exit 1
#fi

That's because the module exists, but it's not located on the same place.
Apply this two patches and reboot. You must have now a full configured eeePC.

[ermes (matteo-pirro)]

I don't know if this is the right place to write, but I would propose a feature: the keys Fn+f5 switch VGA output, but in this way it's impossible to configure the monitor: it's impossible to set resolution or refresh frequency.
Googling i've found that the new architecture of xorg and the new auto-configuring procedures does not work perfectly.
for example I can obtain a resolution of only 800x600 in a monitor that could support 1600x1200, running the command xrandr --auto. (xrandr --prop does not list other option than 800x600)
I think fn+f5 invokes the same command... so is there a solution?? Is it possible to force a resolution? (the script could ask the resolution to use...). (it's the same for other parameters)

I propose this thing because i thing that this script is a very good job and remove all ubuntu's limit for the eeepc!

Good job!!

[Axios (no14ever)]

HI,
I confirm that with those fixes, now overclock works fine even with Adam's custom kernel! :)

Some more questions (feel free to move/delete these last lines if needed)

1) did U check these drivers: http://linuxwireless.org/en/users/Drivers/ath5k ??

2) please, if U can, make those efforts U were talking about to let every new script version be baackwards "compatible" with previous versions using manual update and, please, check interaction with already implemented fixes... because the first time I tried your script(with a bare new version of ubuntu) I noted anyway that your script seems very integrated and feels like it has a lot of "feedback" degree and can adapt itself and see wether some fies are already done or not... ;)

very good work!!!!!

[Carlos Jenkins Pérez (carlos.jenkins)]

@ ermes

Ermes, Launchpad has many tools for the developers. They exists "answers", where you can ask whatever you want. "Bugs" where we keep track of bugs, discuss them and correct them. But also exists a feature called "Blueprints", where you can put a feature request : https://blueprints.launchpad.net/niceeepc Feel free to register a blueprint if you like (with the same text if you want). I've been working on this, but is better if why discuss about it on the blueprint page.

@Axios

Is good to hear that everything is working now.

1) Yes, they're the future of the wireless drivers for the eeePC. I think they're not ready yet for the ASUS eeePC. Anyway, testing that on the eeePC is a hard work. In particular because I risk to lose my wifi connection. I can't do that right now because my eeePC is used constantly everyday, maybe on holidays.

2) I try to make good software, thanks ;) . Anyway, the mayor problem with 1.0 and 1.3 compatibility is that I changed the packaging system. Now it's a Debian package a not a tar ball. Debian package it's easier to install and update.
With the 1.3 release I'll be releasing instruction to update the systems, after 1.3, because of the Debian package, it should be seamless. Anyway, this is not the correct thread to discuss this. If you want to discuss this feature please fill a blueprint or a question.

Cheers.

[Carlos Jenkins Pérez (carlos.jenkins)]

Released version 1.3