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

Qubes OS 4.0rc1 on Macbook Pro 13" fails #3138

Closed
tsjavaloyes opened this Issue Oct 1, 2017 · 5 comments

Comments

Projects
None yet
3 participants
@tsjavaloyes

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

4.0rc1

Affected TemplateVMs (e.g., fedora-23, if applicable):

Not applicable


Steps to reproduce the behavior:

1.- Create USB installation using Rufus ('dd' option selected) on Windows 10 Pro without problems
2.- Put USB on MacBook Pro 13" (macbookpro9,2 version with 2.5GHz Core i5 processor compatible with doc (EPT and VT-d)
3.- Using an external USB SSD disk (I'm using a new Samsung T5 500GB) for destination
4.- Power on Macbook and press "option-key" and select USB "EFI boot"
5.- Boot ANACONDA and wait menu. Select "Test media and install Qubes R4.0-rc1" or "Install Qubes R4.0-rc1"

Expected behavior:

The installation should start...

Actual behavior:

The installation selection menu reappears

General notes:

I'm a Qubes newbie user.

Related issues:

@tsjavaloyes tsjavaloyes changed the title from Qubes OS 4.0tc1 on Macbook Pro 13" fails to Qubes OS 4.0rc1 on Macbook Pro 13" fails Oct 1, 2017

@marmarek

This comment has been minimized.

Show comment
Hide comment
@tsjavaloyes

This comment has been minimized.

Show comment
Hide comment
@tsjavaloyes

tsjavaloyes Oct 1, 2017

Added "/mapbs /noexitboot" at 'grub.cfg' as given in documentation and still does not start the installation and reappears the menu

Added "/mapbs /noexitboot" at 'grub.cfg' as given in documentation and still does not start the installation and reappears the menu

@marmarek

This comment has been minimized.

Show comment
Hide comment
@marmarek

marmarek Oct 1, 2017

Member

Do you have an option to boot in legacy mode?

Member

marmarek commented Oct 1, 2017

Do you have an option to boot in legacy mode?

@andrewdavidwong andrewdavidwong added this to the Release 4.0 milestone Oct 1, 2017

@tsjavaloyes

This comment has been minimized.

Show comment
Hide comment
@tsjavaloyes

tsjavaloyes Oct 3, 2017

Hi again...

After searching and reading documentation on the activation of legacy boot the command 'bless' do not work because there is a security system that prevents it (they call it 'System Integrity Protection'). I'm hoping that there is support for Apple's new APFS file system in 'rEFInd' (update already downloadable OS X 'High Sierra') to install it and test Qubes OS to start the installation in 'legacy mode'...

Hi again...

After searching and reading documentation on the activation of legacy boot the command 'bless' do not work because there is a security system that prevents it (they call it 'System Integrity Protection'). I'm hoping that there is support for Apple's new APFS file system in 'rEFInd' (update already downloadable OS X 'High Sierra') to install it and test Qubes OS to start the installation in 'legacy mode'...

@ghost

This comment has been minimized.

Show comment
Hide comment
@ghost

ghost Feb 13, 2018

Not sure if this will work in OS X High Sierra, but might be worth a shot.

How to turn off System Integrity Protection

  • Click the  menu.
  • Select Restart...
  • Hold down command-R to boot into the Recovery System.
  • Click the Utilities menu and select Terminal.
  • Type csrutil disable and press return.
  • Close the Terminal app.
  • Click the  menu and select Restart....

ghost commented Feb 13, 2018

Not sure if this will work in OS X High Sierra, but might be worth a shot.

How to turn off System Integrity Protection

  • Click the  menu.
  • Select Restart...
  • Hold down command-R to boot into the Recovery System.
  • Click the Utilities menu and select Terminal.
  • Type csrutil disable and press return.
  • Close the Terminal app.
  • Click the  menu and select Restart....
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment