PDA

View Full Version : [Hybrid Graphics] How to turn off discrete gpu using acpi_call via graphic interface



marcoDallas
5th May 2013, 06:44 PM
Hi!
If you just want to have long battery life and slow temperature, you can use acpi_call: a linux kernel module that enables calls to ACPI. With acpi_call_GUI you can easily install and configure it via graphic interface, now with the support for systemd!

It is a java program that allows you to:

install the acpi_call kernel module (kernel would be recompiled automatically after each update);
Deactivate discrete GPU;
Automatically deactivate discrete GPU on every boot.


You can find it here: https://github.com/marcoDallas/acpi_call_GUI_systemd

How to install:
Type in a terminal:

sudo yum install git
sudo git clone https://github.com/marcoDallas/acpi_call_GUI_systemd.git
cd acpi_call_GUI_systemd
sudo chmod +x install.sh
sudo ./install.sh

How to use:
Type in a terminal:

sudo java -jar /usr/local/bin/acpi_call_GUI_systemd/acpi_call_GUI_systemd.jar

Here's a video tutorial that shows step-by-step how tu use this software (Commands are different because the video is made on ubuntu, but the usage of the program is the same):

Tutorial acpi_call_GUI (https://www.youtube.com/watch?v=h33bvoR14x8)

You can find the source code of the kernel module here: https://github.com/mkottman/acpi_call

Hope that it would be useful!
Bye!

DBelton
5th May 2013, 07:16 PM
Not too bad.

I notice you even take care of rebuilding the kernel module if it's a different kernel as well.

I don't have a machine currently where this could be used, but I did take a look through the code somewhat just to make sure you weren't posting anything that would obviously mess up someone's system.

I would still warn anyone wanting to use this to make sure of what you are installing before running it. It appeared to be safe from just a quick look, but no guarantees.

Edit:

BTW... Where is the code for the kernel module?

marcoDallas
5th May 2013, 07:44 PM
I notice you even take care of rebuilding the kernel module if it's a different kernel as well
Ehm.. (my english is not very good) did you mean if someone had already recompiled the kernel with its own modules?
Teorically my program will just add the acpi_call module without "touch" others..


I would still warn anyone wanting to use this to make sure of what you are installing before running it. It appeared to be safe from just a quick look, but no guarantees.

Edit:

BTW... Where is the code for the kernel module?

Well I had already wrote this in the readme of the program:
acpi_call module should be used with caution. I reccomend you to take a look to the readme of the acpi_call module: https://github.com/mkottman/acpi_call

And you can find the code of the kernel module here: https://github.com/mkottman/acpi_call
Michal Kottman owns the kernel module, I just made the graphic interface and the automatization scripts :)

DBelton
5th May 2013, 07:49 PM
Ok :) I just wanted it shown someplace here where you are pulling the kernel module from so people can look and make their own decision if they wish to run it or not. The source code is at the link above.

And, yes, I can tell that it doesn't affect any other modules that someone might have compiled in their kernel, unless they just happened to have one named acpi_call, which as far as I can see isn't an issue. :)

marcoDallas
5th May 2013, 07:57 PM
Ok I understand ;) I've added a link to the source code at the end of the first post :)
Thank you!