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

Cannot install Qubes #2838

Closed
alexschrod opened this Issue Jun 1, 2017 · 5 comments

Comments

Projects
None yet
5 participants
@alexschrod

alexschrod commented Jun 1, 2017

Qubes OS version (e.g., R3.2): R3.2


Expected behavior: I boot the installation medium and the installer starts

Actual behavior: I boot the installation medium, and get the following message: "Couldn't obtain the File System Protocol Interface." Then I am taken back to the boot menu, where any selection just prints the message again and returns to the boot menu.

General notes: The machine is an MSI GS63VR 7RF Stealth Pro, if that helps. Also, I believe the error comes from this place in the Xen code.

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Jun 1, 2017

Member

This may be a problem with UEFI implementation on this machine. Have you tried legacy mode?
Anyway, better place to ask such questions is qubes-users mailing list

Member

marmarek commented Jun 1, 2017

This may be a problem with UEFI implementation on this machine. Have you tried legacy mode?
Anyway, better place to ask such questions is qubes-users mailing list

@marmarek marmarek closed this Jun 1, 2017

@JanPappert

This comment has been minimized.

Show comment
Hide comment
@JanPappert

JanPappert Sep 24, 2017

Experiencing exactly the same issue with a MSI B250M Mortar and was wondering if the OP was able to resolve the issue.

Experiencing exactly the same issue with a MSI B250M Mortar and was wondering if the OP was able to resolve the issue.

@alexschrod

This comment has been minimized.

Show comment
Hide comment
@alexschrod

alexschrod Sep 24, 2017

Unfortunately, no. My computer was a work computer, and I did not have time to troubleshoot the issue, I just had to have a working OS. My company allowed me to use QubesOS, but would not allow me to spend time on it past installing it. So now I'm stuck with using Windows at work instead, as it "works" (for some limited definition of "works").

Unfortunately, no. My computer was a work computer, and I did not have time to troubleshoot the issue, I just had to have a working OS. My company allowed me to use QubesOS, but would not allow me to spend time on it past installing it. So now I'm stuck with using Windows at work instead, as it "works" (for some limited definition of "works").

@zylstra

This comment has been minimized.

Show comment
Hide comment
@zylstra

zylstra Dec 5, 2017

Just wanted to say that legacy mode is called CSM in some BIOSs.

zylstra commented Dec 5, 2017

Just wanted to say that legacy mode is called CSM in some BIOSs.

@lucaszanella

This comment has been minimized.

Show comment
Hide comment
@lucaszanella

lucaszanella Dec 9, 2017

This "CSM" tip helped me a lot, had no idea that my firmware actually supported it

(however, legacy boot will give me an empty screen when I try to install it)

lucaszanella commented Dec 9, 2017

This "CSM" tip helped me a lot, had no idea that my firmware actually supported it

(however, legacy boot will give me an empty screen when I try to install it)

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