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

Lenovo ThinkPad – installs, but does not boot #3461

Closed
DemiMarie opened this Issue Jan 14, 2018 · 1 comment

Comments

Projects
None yet
2 participants
@DemiMarie

DemiMarie commented Jan 14, 2018

Qubes OS version:

R4.0-rc3

Affected TemplateVMs:

N/A


Steps to reproduce the behavior:

Install on a very recent Lenovo ThinkPad

Expected behavior:

Qubes boots successfully

Actual behavior:

The firmware does not recognize Qubes and refuses to boot it

General notes:

I could not use R3.2 because it refused to start X, due to my NVidia graphics card.


Related issues:

@andrewdavidwong

This comment has been minimized.

Show comment
Hide comment
@andrewdavidwong

andrewdavidwong Jan 14, 2018

Member

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

Member

andrewdavidwong commented Jan 14, 2018

Based on our issue reporting guidelines, this appears to be too localized for qubes-issues, since it depends on a specific hardware configuration. We ask that you please send this to the qubes-users mailing list instead. qubes-users is intended for these sorts of issues and receives much more traffic, which means that your issue is more likely to receive a response there. If, after reading our issue reporting guidelines, you believe we are mistaken, please leave a comment briefly explaining why. We'll be happy to take another look, and, if appropriate, reopen this issue. Thank you for your understanding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment