-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bumblebee Support #28
Comments
Hmm yeah, I haven't gotten bbswitch to work, not sure what we'd have to do to change that. Also I need to get up to date on the whole GPU switching thing, if I understand it correctly, getting vga-switcheroo to work would be the proper way forward (if that's even possible)? I'll definitely have a look into it. |
For anyone interested: I've been working on this. While it's not a drop-in replacement for bbswitch and not supported by bumblebee, you can manually switch the dGPU on before calling optirun and switch it off afterwards. |
Moved from https://github.com/qzed/linux-surfacegen5-acpi, as I want to keep these two modules separate for now and I think this should be handled here. |
Moving back to https://github.com/qzed/linux-surfacegen5-acpi as this module is now integrated there. The To get this to work with the bumblebee deamon, some additional configuration thereof is required via its |
This looks ACPI related. I'm running Ubuntu 18.10. After upgrading to 4.19 from Jake, I found out the 390 drivers are unsupported in 4.19 so I upgraded the nvidia driver to 410.
410 no longer uses prime-select and prefers bumblebee/optirun to enable the graphics card.
Looking at dmesg:
The device ID properly maps to the nvidia card but that _DSM call looks like ACPI related. Any ideas?
The text was updated successfully, but these errors were encountered: