How to add acpi_call to modules

[Durhammer]

Hi folks,

My old Samsung RF711 laptop has the Optimus hybrid graphics setup with a problematic Nvidia GE 540 that adds way more heat to the system when it's on than it's worth to have it around. On other distros I've downloaded and setup the acpi_call-dkms package, but no dkms stuff in Slackware, so downloaded the Slackware 15.0 acpi_call (.txz) module via slakfinder. It's been converted to .xzm and "activated" but I'm not sure where to go from here. Usually, once the module's built, I use "sudo modprobe acpi_call" and then run the commands needed to turn off the power to the Nvidia card. It doesn't look like that's what you do in Porteus, however.

Code: Select all

guest@porteus:~/Downloads$ sudo modprobe acpi_call
Password: 
modprobe: FATAL: Module acpi_call not found in directory /lib/modules/6.15.3-porteus

Ideas? Did I miss a step?

[beny]

https://slackware.nl/slakfinder/index.p ... e=#results
but you need also the kernel module,

[Durhammer]

https://slackware.nl/slakfinder/index.p ... e=#results
but you need also the kernel module,

Thanks, @beny. That IS the same modue I downloaded. Now what?

[beny]

hi, the kernel module is inside the acpi_call package but is for 5.15.193 kernel,you have to try to build for your kernel with the slackbuild and the kernel crippled source and devel package.

[Durhammer]

hi, the kernel module is inside the acpi_call package but is for 5.15.193 kernel,you have to try to build for your kernel with the slackbuild and the kernel crippled source and devel package.

AH! Thanks. I did that on Salix with some helpful guidance. Not sure how to go about doing it on Porteus. Need to learn but need teecher(s)!

[ncmprhnsbl]

Not sure how to go about doing it on Porteus.

steps:
1.get 05-devel.xzm from one of the mirrors eg. https://ftp.nluug.nl/os/Linux/distr/por ... -devel.xzm
2. at the same time, grab the crippled sources for the kernel: https://ftp.nluug.nl/os/Linux/distr/por ... -64bit.xzm
3. activate both of them
4.grab the SlackBuild and source from SBo :
slackbuild: https://slackbuilds.org/slackbuilds/15. ... all.tar.gz
source: https://github.com/mkottman/acpi_call/a ... 1.0.tar.gz
5. unpack the slackbuild archive to somewhere (right there in Downloads is fine)

Code: Select all

tar xvf acpi_call.tar.gz

6. move the source to that dir

Code: Select all

mv acpi_call-1.1.0.tar.gz acpi_call

7. cd to acpi_call

Code: Select all

cd acpi_call

8. switch to root (su)
9. run the SlackBuild:

Code: Select all

sh acpi_call.SlackBuild

10. if it works out, there'll be a package in /tmp
11. use txz2xzm to convert it to an xzm module and activate it.

[Durhammer]

THANK YOU, @ncmprhnsbl!!! I shall give it the ol' college try when I'm back in Porteus.

I apologize to all for having to have it spelled out for me, but such as it is!!!

[Ed_P]

I apologize to all for having to have it spelled out for me, but such as it is!!!

No need. It's how many of us learned, from the talented admins who like to help us.

[Durhammer]

I'M BAACK!!!

Thanks for the detailed set of instructions for building the acpi_call module, @ncmprhnsbl !! It worked perfectly!

However, now I'm lost as to how to use it. In other distros, where it's been downloaded and built, you have to do a "sudo modprobe acpi_call" command so that you then can run a command (as root) such as '/usr/bin/echo "\_SB.PCI0.PEG0.PEGP._OFF" > /proc/acpi/call' -- which actually does the job of turning OFF the GPU. I tried the commands, and they failed:

Code: Select all

guest@porteus:~$ su
Password: 
root@porteus:/home/guest# /usr/bin/echo "\_SB.PCI0.PEG0.PEGP._OFF"  > /proc/acpi/call
bash: /proc/acpi/call: No such file or directory
root@porteus:/home/guest# modprobe acpi_call
modprobe: FATAL: Module acpi_call not found in directory /lib/modules/6.15.3-porteus
root@porteus:/home/guest# ls /tmp/acpi*
/tmp/acpi_call-1.1.0_6.15.3_porteus-x86_64-1_SBo.tgz
/tmp/acpi_call-1.1.0_6.15.3_porteus-x86_64-1_SBo.xzm

So obviously there's more to it that I'm missing. FWIW, I DID remove the old acpi_call module from $MODDIR and copied the new one into it. BUT THEN AGAIN, I haven't rebooted with those changes. Gonna do that right now and report back.

[Durhammer]

AHA!!! That did it, at least as far as the above commands are now working without error messages. However, still not sure about the efficacy of the acpi_call function itself. While I do know that these user forums use scripting that chew up CPU, it's still disarming to see the system temps hovering around 75C temp (sheesh -- now 78C!). Still too warm for comfort. So far, the lowest I've seen is 47C. SIGH....

I'll give it some time after submitting this and getting the browser settled down....

EDIT:

OKAY!!!! I added the modprobe command and the acpi_call setting command, plus commands to remove the Nvidia bus(es) presence, and added a conf entry to blacklist the nouveau driver, and rebooted. Seems to be working much better now -- even with the forum's scripting ongoing, the system temp is pretty steady at 48C. Left the laptop idle to have a cuppa joe and came back with the temp monitor showing 39C! YAY!

THANKS AGAIN, @ncmprhnsbl and others!!! FABULOUS!!!

[Durhammer]

Well, sheesh -- it's still not enough for this old machine. I can't even run "sudo slapt-mod -m nsudoku" to install a sudoku game without getting to a thermal shutdown (twice now). Fails in the squashfs stuff. The first time, it caught me off guard. The second time, I watched my system temp monitor in horror when it got to 97C a couple of times before it finally shut down. SHEEEESH!