Closed FPSUsername closed 2 months ago
Sup @FPSUsername . How are things going?
Is this still reproducible in a more modern install with updated Linux kernel, acpi
dkms, nvidia
driver and using the optimus-manager-git
package?
Looking at the acpi_data.py
file, looks like the ACPI string your GPU expect ( "\\_SB.PCI0.PEG0.PEGP._OFF", "\\_SB.PCI0.PEG0.PEGP._ON"
) exists since this file was imported to optimus-manager
so it SHOULD work out of the box but for some reason it's not being correctly sent.
Out of curiosity. If you clear your acpi_call_strings.json
or move it, what is the JSON file that is generated? What tuple of strings is configured there or is it just empty?
Have a nice day.
If the issue is still there
Update your UEFI from an external Windows Live USB.
In the UEFI, check if any option influences this.
If that doesn't fix it, reopen.
Unfortunately I'm not using Linux on this laptop anymore. I believe at the time I already was using the latest UEFI provided by Dell (1.24). A lot of things could have changed in the past 3-4 years, so who knows if it's still an issue.
Whoops!
Describe the bug When I use acpi_call as a switching method, the laptop completely freezes after finding the correct call.
I rebooted in tty mode and saw that no "cache" file had been created under
/var/lib/optimus-manager/persistent/
1. I created my own file inacpi_call_strings.json
with the content:[["\\_SB.PCI0.PEG0.PEGP._OFF", "\\_SB.PCI0.PEG0.PEGP._ON"]]
When booting the system, I see that theAE_NOT_FOUND
messages aren't there anymore, yet the system still freezes.My workaround for now is to make use of the configuration files:
System info
1 The path and file name are mentioned incorrectly in the wiki if you compare it with the code