You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 22, 2019. It is now read-only.
A quick google shows I'm not the only one who's temporarily bricked my system running nvidia-installer without the --bumblebee flag.
Since the GPU model is already checked via PCI ID, I suspect it should be fairly easily to check for mobile-version cards and provide a warning prompt.
I'd write it myself but I have little experience in this area.
The text was updated successfully, but these errors were encountered:
Thanks for your suggestion. I'll try to add this asap.
I'll leave this here just for future reference:
The quickest method to determine if your device uses an Optimus card is to search against the documented list on NVIDIA's website. Obtain the NVIDIA GPU identifier of your card with:
$ lspci | grep 3D
Compare the identifier (i.e. GeForce 7XXM, 8XXM, 9XXM) with the list, here: http://www.geforce.com/hardware/technology/optimus/supported-gpus
Also note the PCI identifier of the card, which is the 5-digit ID at the beginning of the previous command's output, XX:XX.X.
If you add a list of the pci id's of optimus supported gpu's, and add some code in the function that checks for device id, it should be fairly simple to automatically add the --bumblebee flag if pci id of optimus supported gpu is detected?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A quick google shows I'm not the only one who's temporarily bricked my system running nvidia-installer without the --bumblebee flag.
Since the GPU model is already checked via PCI ID, I suspect it should be fairly easily to check for mobile-version cards and provide a warning prompt.
I'd write it myself but I have little experience in this area.
The text was updated successfully, but these errors were encountered: