Skip to content
This repository has been archived by the owner on Oct 27, 2019. It is now read-only.

Handle prime-select unknown #22

Open
Era-Dorta opened this issue Nov 27, 2016 · 4 comments
Open

Handle prime-select unknown #22

Era-Dorta opened this issue Nov 27, 2016 · 4 comments
Assignees
Milestone

Comments

@Era-Dorta
Copy link

Under certain error conditions prime-select query might return unknown rather than nvidia or intel. It'd be nice to have that case included, with a custom icon so that the user knows that something is wrong.

@andrebrait
Copy link
Owner

It was in the plans. I ended up forgetting to add this option (it would be a '?' icon or something like that). I'll mark this as a request for improvement :)

@andrebrait andrebrait added this to the 1.5 milestone Nov 27, 2016
@andrebrait andrebrait self-assigned this Nov 27, 2016
@Era-Dorta
Copy link
Author

Era-Dorta commented Dec 10, 2016

Thanks, a reproducible way to get the unknown status is to active secure boot.
Which by the way makes the readme a bit misleading, the nvidia drivers do work with secure boot, but only after the modules have been signed

@andrebrait
Copy link
Owner

@Garoe I'll add an icon for Unknown then. Will do as soon as I can. This December is being an unusually busy month for me.

Also, thanks for the information. I knew why the NVIDIA drivers wouldn't work but I had no idea one could sign them!

@mmhobi7
Copy link

mmhobi7 commented Feb 14, 2018

#28

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants